infoPLC Net ErrorCodes 2015-02-05 PDF

infoPLC.
net Error
Error Code Type Error Message Cause Remedy
Fail to run DETECT The AccuCal2 Motn failed to run. The Clear all the errors before
ACAL-000 WARN Motn AccuCal2 motion cannot be started. executing AccuCal2.
The robot is not ready. The system Clear all faults, then retry
ACAL-001 WARN Robot is not ready. cannot issue motion because it is in an the operation.
Perform the following: *
Increase the number of
AccuCal2 cannot converge within the iterations allowed. *
ACAL-002 WARN Fail to fit circle. set threshold. Increase the convergence
The robot is in contact with the part Reteach the starting
ACAL-003 WARN Contact before search. before starting a search motion. position.
No contact was made during the Make sure the sensor and
ACAL-004 WARN No contact detected. AccuCal2 motion. software are installed
Undefined program The AccuCal2 program name was not Select an AccuCal2 teach
ACAL-005 WARN name. defined. pendant program before
Abort the program and
run again. If this doesn't
resolve the problem, cycle
This is an internal teach pendant editor power and try again. If
ACAL-006 WARN TPE operation error. program error. this doesn't resolve the
Turn off the controller,
and turn it on again to
Calibration internal recover. If the problem
ACAL-007 WARN error. This is an AccuCal2 internal error. persistes, reinstall the
Check the path, and file
ACAL-008 WARN File open error. The output file cannot be opened. name to be sure they are
You are trying to execute a CALIB END Add a CALIB START
ACAL-009 WARN No matching Start inst. instruction without a matching CALIB instruction before the
Invalid schedule The schedule number in CALIB, UTOOL, Provide a correct schedule
ACAL-010 WARN number. or UFRAME START is invalid. number in CALIB (or
Cannot access The current $MNUFRAMENUM[] is Go to the USER FRAME
ACAL-011 WARN $MNUFRAME. incorrect and cannot be accessed. menu to select a valid
Cannot access Cannot access $MNUTOOL. The current Display the FRAME menu
ACAL-012 WARN $MNUTOOL. $MNUTOOLNUM[] is incorrect. to select a valid tool
Backward execution were ignored. The The backward execution
Backward execution AccuCal2 instructions can not be of the AccuCal2
ACAL-013 WARN ignored. executed backward. instructions is ignored.
System loading error. The AccuCal2 is Reload the controller.
ACAL-014 WARN System loading error. Not
loaded incorrectly.
enough data exists to compute the Refermore
Add to the FANUC
Detect
ACAL-015 WARN Not enough data. frame offset.
No Preplan motion for The Detect instruction does not allow instructions in the
ACAL-016 STOP Detect pre-plan motion. None.
Re-teach the AccuCal2
program with an
Wrong number of An incorrect number of searches was appropriate number of
ACAL-017 WARN searches. performed. searches. Refer to the
Nonorthogonal search The 3 planes method requires three Re-teach the cell finder
ACAL-018 WARN vector search directions be normal to each program with three
Positions are too close. The taught Re-teach the cell finder
ACAL-019 WARN Positions are too close. positions areframe
The current too close to each
number other.
setting is program so that the
Use the SETUP/FRAME
ACAL-020 WARN Invalid Frame number. invalid. menu to set up the
Run the calibration
program again to make
The computed frame offset exceeds the sure the robot makes solid
ACAL-021 WARN Large Frame deviation. pre-set value. contacts with the part.
Detect without An AccuCal2 teach pendant program is Display the AccuCal2
ACAL-022 WARN mastering running without performing mastering menu, and master the
No EXEC at Single Step The robot cannot execute an AccuCal2 Turn off Single Step
ACAL-023 WARN Mode. program in Single Step Mode. before executing the cell
A failure occurred while trying to Re-master the frame
ACAL-024 WARN Master Update failed. update the master data in a FIND search teach pendant
Check the UTOOL and the
ACAL-025 WARN Large frame shift. A very large frame shift has occurred. fixture to make sure that
No CALIB END No CALIB END instruction. AccuCal2 Add CALIB END instruction
ACAL-026 WARN instruction. program does not have a FIND END at the end of the frame
The number of master data and Run the finder program
ACAL-027 WARN Counts do not match. number of run time data does not again.
No logged frame data exists and the
ACAL-028 WARN No logged frame data. frame cannot
No change be restored.
occurred in the offset Select a logged
Run Cell Finder frame.
again to
ACAL-029 WARN Zero offset, No Update. frame. compute a new offset.
ACAL-030 WARN Frame Log is disabled. The Frame data log is disabled. Enable the frame log first.
Cold start to set $USEUFRAME is set to FALSE. AccuCal2 TUrn off the controller,
ACAL-031 WARN $USEUFRAME reset it to TRUE. the turn it on again to
Use only one group in the
ACAL-032 WARN Invalid motion group. The motion group number is invalid. program
Abort theand make
other sure
running
ACAL-033 WARN Other group is running. The other program has motion control. program.
Use only one group in the
ACAL-034 WARN Group mismatched. The motion group number is not right. program, and make sure
ACAL-035 WARN Press Shift Key. The SHIFT key was not pressed. Press the SHIFT key.
Check the following: *
Failed to create TPE The teach pendant program could not Make sure enough
ACAL-036 WARN program be created. memory is available. *
TPE Position is not The teach pendant position has not Unprotect the write
ACAL-037 WARN recorded been recorded. Make sure the program protected program.
TPE Program does not The selected teach pendant program Select an existing teach
ACAL-038 WARN exist. was not found and does not exist. pendant program.
Move to recorded posn The robot could not move to the Make sure the position is
ACAL-039 WARN failed
Invalid Detection TP recorded position.
The detection teach pendant program reachable and detection
Load a proper that
ACAL-040 WARN program is not usable. program.
Override should be Before running the
ACAL-041 WARN 100%. The speed override is not 100%. program, increase the
Large orientation The found orientation is larger than the Adjust the object so that
ACAL-042 WARN change. tolerance allows. orientation is smaller.
Points & solution The number of search points does not Select a different solution
ACAL-043 WARN mismatch. match
An the selected
unsupported solution
solution type.
type error type, or aadjust
Choose number of
different
ACAL-044 WARN Solution type error. was selected. solution
Make type.
sure the specified
ACAL-045 WARN Failed to set register. The specified register was not set. register exists.
Failed to convert The position failed to convert. The Make sure the points are
ACAL-046 WARN position. internal position was not set. taught inthe
Reduce thenumber
properof
ACAL-047 WARN Too many points used. Too many points are used. detect points.
Make sure the correct
ACAL-048 WARN Solution failed. The solution failed to complete. number of points are
This is a motion limit error. The detect Move the robot away
ACAL-049 WARN Motion limit error. motion failed due to a limit error for from the joint limit, or
Try to run the TCP
Calibration instruction
ACAL-050 WARN TCP Cal is not loaded. TCP Cal is not loaded. without the TCP Cal
Try to run the Cell
Calibration instruction
ACAL-051 WARN Cell Cal is not loaded. Cell Cal is not loaded. without the Cell Cal
Robot Cal is not loaded. The robot tried Perform a Controlled
ACAL-052 WARN Robot Cal is not loaded. to run the robot Calibration instruction start, and load the Robot
No calibration software. The robot tried Perform a Controlled
ACAL-053 WARN No calibration software. to run a detect instruction without start, and load one of the
Invalid Calibration Invalid Calibration program. The Check the teach pendant
ACAL-054 WARN program. calibration program type does not program's calibration start
Too Many Parallel Searches have Teach more searches, or
Too Many Parallel occurred. More than three parallel change the excess parallel
ACAL-055 WARN Searches. searches occurred when the total searches to be in a
The robot executed an UPDATE FRAME UPDATE FRAME only
instruction in a non-Cell calibration works in Cell Calibration
ACAL-056 WARN Skip Update Frame Inst. program. programs with Uframe
Residual maximum calibration has Verify solid tooling and
ACAL-057 WARN Large Calibration Error exceeded the limit allowed by the good contact is made
UFRAME Change Not The UFRAME was changed during Use the same UFRAME for
ACAL-058 WARN All
Allowed
Positions Not UTOOL calibration and this is not all points
Record allduring the initial
necessary
ACAL-059 WARN Recorded All required positions are not recorded. positions, and retry the
Repair the tool so that the
Excessive Accumulated The accumulated offset exceeds the TCP is closer to the
ACAL-060 WARN offset tolerance specified in the schedule. reference TCP, or increase
A UFrame mismatch has occurred. The Change the current user
current MNUFRAME number does not frame number to match
ACAL-061 WARN UFrame mismatch. match the program's uframe. the program's user frame
Too many moves in a Too many moves have been attempted Limit the number of move
ACAL-062 WARN program. in a program. The Calibration porgram instructionz in a
Failed to update master The master data failed to update. The Abort the robot motion
ACAL-063 WARN data master count cannot be updated when and then press the
A UTool mismatch has occurred. The Change the current tool
ACAL-064 WARN UTool Mismatch. current MNUTOOL number does not number
Review theto match theerror
previous
ACAL-065 STOP TCP calibration failed The TCP calibration failed to complete. to identify
Review thethe cause.error
previous
ACAL-066 STOP Cell calibration failed Cell calibration failed to complete. to identify the cause.
The circle fit error exceeds the Check for a loss fixture or
ACAL-067 WARN Circle fit error %s threshold. tool, or change the fit
Check for a lost fixture or
ACAL-068 WARN Radius err %s Circle radius error exceeds threshold. tool, or change the radius
Auto Update is on therefore the frame
ACAL-069 WARN Auto Update is ON. has been updated automatically. An update is not required.
No update on record points. The teach
pendant program has a different Manually record positions
No update on record number of DETECT instructions than to create the calibration
ACAL-070 WARN points. expected. The positions cannot program.
The axis number specified in the Change the axis number
ACAL-071 WARN Invalid joint number. DETECT Joint instruction is invalid. to a valid one.
Invalid joint sensor The Detect Joint instruction cannot use Change sensor type to
ACAL-072 WARN type. TOS WRIST sensor type for contact either IO or TOS all axes in
The Detect Joint
The Detect Joint instruction is not valid instruction is for ROBOT
ACAL-073 WARN Skip Detect Joint for TCP or CELL calibration. calibration only. Change
No motion before No motion exists before the DETECT Add a MOVE instruction
ACAL-074 WARN DETECT. instruction. Detect instructions require before the DETECT
Mixed Detect instructions have
occurred. The Detect Joint instruction Delete the other DETECT
Mixed Detect cannot be used with other Detect instrucion from the
ACAL-075 WARN instructions. instructions within the same Calib Start - program.
More than one Detect Joint instruction
More than one Detect exists. Only one Detect Joint instruction Delete the extra DETECT
ACAL-076 WARN Joint. is allowed between Calib Start and JOINT instructions.
No Detect Joint should exist in Initial Run the program from the
No Detect Joint in Init. Calibration. The Detect Joint instruction robot master recovery
ACAL-077 WARN Cal does not apply to the initial robot menu.
Skip Update Tool Execute the Update Utool instruction in Update Tool only works in
ACAL-078 WARN instruction a non-TCPCal program. TCP Calibration programs
Large approach angle The search start position's appraoch Touch up the search start
ACAL-079 WARN error. vector does not align with the plate's position so that the
Failed to update TPE Failed to update the teach pendant Make sure there is not
ACAL-080 WARN program
Destination %s Limit program's search start position.
The recorded position is too close to system
Re-teach fault
thebefore
position
ACAL-081 WARN Error the joint limit. away from joint limit.
Tool is 180 degree off in The Tool approach vector is 180 Change the system
ACAL-082 WARN Z degrees off in Z from the search variable $cb_vars.$z_out
Invalid teach pendant calibratino The teach pendant
ACAL-083 WARN Invalid TPE instruction. instruction. program memory might
Failed to access Karel Failed to access the calibration Cold start the controller. If
ACAL-084 WARN vars. program's KAREL variables. the problem persists, re-
Set UFrame to be the
The specified UFrame is zero or small, precision calibration
ACAL-085 WARN UFrame is too small and Calibrate UFrame is disabled. fixture location or enable
Set UTool to be the
The specified UTool is zero or small, precision calibration
ACAL-086 WARN UTool is too small and the Calibrate UTool is disabled. fixture location or enable
Modify calibration points
Joint[%s^1] rotation is to provide more motion
ACAL-087 WARN small The joint angle motion is too small. on the specified axis. Or,
Three or more points with the same Reteach one of the points
ACAL-088 WARN Points are colinear search direction are colinear or nearly so that the points are not
There must be at least three different Add more search points or
search directions that are close to reteach existing points to
perpendicular to each other. There have sufficient search
Not enough search must also be at least three non-colinear directions and a sufficient
ACAL-089 WARN direction points in one search direction and at number of points in the
Identify the cause of the
large correction. If the
robot joint angle is
actually off by that large
amount, then you can
either increase the
tolerance in the schedule
or manually remaster the
robot to reduce the error
and touchup the
calibration points and
rerun the calibration. If
the calibration result is
incorrect, then check that
Large joint angle Calibration joint angle correction Calibrate UFrame is TRUE
ACAL-090 correction exceeds the limit unless you are doing
UFrame orienation not Use a UFrame with WPR
ACAL-091 WARN zero The UFrame orientation must be zero. values where all are set to
Position close to joint The search destination position is too Re-teach the position
ACAL-092 limit close to the joint limit. away from joint limits.
The Coordinate Motion Pair number is Check the CD pair setup to
ACAL-093 Invalid CD pair number invalid. make sure the CD pair has
Invalid Process Sync Check the Process Sync
ACAL-094 Setup Invalid Process Sync Set up setup to make sure the
No Coordinate Motion The CD pair calibration requires Load the Coordinate
ACAL-095 software
No Process Sync Coordinate
Robot Motion Software.
Link calibration requires Robot Motion
Load thesoftware on the
Robot Link
ACAL-096 software Link Software. software on the
The user is trying to run the MultiCal Perform a Control start
ACAL-097 MultiCal is not loaded. instruction without MultiCal software. and load the MultiCal
Bar method is not Calibration Bar is not support in the The calibration bar
ACAL-098 supported V7.20 MultiCal Release. method will be supported
Positioner is not Positioner calibration is not supported The positioner calibration
ACAL-099 supported in the V7.20 MultiCal release. will be supported in
Program Group The read in the program group does Use the FCTN key to
ACAL-100 Mismatch not match
The maximumthe current
alignment default motion
distance was change
Fix the Alignment
the TCP current and
ACAL-101 TCP Alignment error exceeded. run TCPCal again.
Process is not yet Cannot execute current step without Complete all steps leading
ACAL-102 completed completing previous steps. to the current step.
There is no associatedAnalog data file Copy the analog data file
ACAL-104 No Analog
Option doesport
notdata file RobotCal
in FRS: forand
theMultiCal
specifieddoes
analog
notport to the aFRS:
Select directory
different and
sensor
ACAL-105 support AIN support analog sensor. type in the detection
No analog sensor The Detect Circle and Detect Joint Select a different sensor
ACAL-106 support instructions do not support an analog type in the detection
Select a different AIN port
ACAL-107 Invalid AIN port number The AIN port number is not valid. number that has its data
Dynamic UFrame setup Dynamic Uframe seting require cd pair Set the cd pair number in
ACAL-108 error setting in its schedule. the schedule or change
Standard UFrame setup The schedule used by UFrame has a Select a new schedule or
ACAL-109 error turn off single
Please cd_pair set. change
Press the
the cd_pair
STEP key to
ACAL-110 step Disable single step mode. disable single step.
Joint position not TP program has position with joint 1. Exit High Accuracy
ACAL-115 allowed
Joint motion not representation.
Joint motion is not Thisallowed
is is notinallowed
High in Mode 2.motype
Change Move tototheLinear
ACAL-116 allowed
UTool change not Accuracy
UTool Mode
change is not allowed in High or exit
Exit High
High Accuracy
Accuracy Mode
ACAL-117 allowed Accuracy Mode before changing UTool
WJNT motion is not allowed in High Exit High Accuracy Mode
ACAL-118 Wristjoint
Remote TCP notnot
allowed Accuracy Mode
RTCP motion is not allowed in High before using
Exit High WJNT Mode
Accuracy
ACAL-120 allowed
Coord motion not Accuracymotion
COORD Mode is not allowed in High before
Exit using
High RTCP motion.
Accuracy Mode
ACAL-121 allowed Accuracy Mode before using COORD
Gravity comp. not Gravity compensation is not allowed Disable Gravity
ACAL-122 allowed with HighisAccuracy
Softfloat not allowed in High Compensation
Exit Go through
High Accuracy Mode
ACAL-123 Softfloat not allowed
High Acc Mode not Accuracy Mode
High Accuracy Mode failed to be before using Softfloat.
Check alarm history and
ACAL-124 entered
Problem with Sec. entered encoder mode failed to be
Secondary correctalarm
Check problem
history and
ACAL-125 Encoders entered correct problem
Information status. High Accuracy
ACAL-126 High Acc. Mode entered Mode successffully entered No action necesary
Information status. High Accuracy
ACAL-127 High Acc. Mode exited
Already in High Acc. Mode successffully
Information status. exited
Already in High No action necesary
ACAL-128 mode Accuracy Mode.
Information status. Not in High No action necesary
ACAL-129 Not in High Acc. mode Accuracy Mode. No action necesary
ACAL-130 Filter not empty Motion is still active Use FINEany
Remove termtype
motion
ACAL-131 Invalid motion change Motion changed options on the TP motion
TCP and UFrame cannot
ACAL-132 Invalid Selection Invalid Signature Setting be both FALSE for UFrame
Mismatch measure The number of measured points does Please re-do the
ACAL-133 ABORT. points not match the number of command calibration.
APPL-002 G
ABORT. AX is alredy entered Same AX is already registered. Check
At firstentry AMR data.
you should register
APPL-003 G entryAMR isisrequired
Application not Some request is received before entry. AX.
APPL-004 WARN plugged
Specified application is Application softpart isisnot
Specified application notplugged.
selected
APPL-005 WARN
ABORT. not selected now now Send setupAMR to work
APPL-011 G
ABORT. setupAMRsetupAMR
Unknown is required Some request is received before setup. AX. Check setupAMR
APPL-012 G received Unknown setupAMR is received. parameter.
startAMR recieved in StartAMR is received but requestAMR Check start and cancel
APPL-021 WARN
ABORT. IDLE
executedAMR recieved is not in the APPLICATION.
executedAMR sequence.
is received but AX does executedAMR maybe
APPL-022 G
ABORT. in IDLE
plannedAMR recieved not work.
plannedAMR is received but AX does illegal. Check
plannedAMR maybeit.
APPL-023 G
ABORT. in IDLE
executedAMR recieved not work.
executedAMR is received but AX is illegal. Check it.maybe
executedAMR
APPL-031 G
ABORT. in PLAN
other plannedAMR planning.
plannedAMR is received but AX is illegal. Check it.
plannedAMR maybe
APPL-032 G
ABORT. received in PLAN
executedAMR recieved planning other AMR.
executedAMR is received but AX is illegal. Check it.
executedAMR maybe
APPL-041 G
ABORT. in WTSTART recieved
plannedAMR waiting start. is received but AX is
plannedAMR illegal. Check it.
plannedAMR maybe
APPL-042 G in WTSTART
startAMR recieved in waiting start. illegal. Check it.
startAMR is received but AX is waiting startAMR maybe illegal.
APPL-051 WARN
ABORT. WTPLAN
executedAMR recieved planned AMR. is received but AX is
executedAMR Check it.
executedAMR maybe
APPL-052 G in WTPLAN waiting plannedAMR illegal. Check it.
ABORT. other plannedAMR plannedAMR is received but AX is plannedAMR maybe
APPL-053 G recieved inrecieved
stopAMR WTPLAN in waiting other
StopAMR plannedAMR.
is received illegal. Check
but AX is waiting stopAMR it. illegal.
maybe
APPL-054 WARN
ABORT. WTPLAN
other executedAMR planned AMR. is received but AX is
executedAMR Check it.
executedAMR maybe
APPL-061 G
ABORT. recieved
plannedAMRin EXEC
recieved executing other AMR
plannedAMR is received but AX is illegal. Check
plannedAMR maybeit.
APPL-062 G in EXEC executing AMR illegal. Check it.
startAMR recieved in start AMR is received but AX is stopping If necessary, you keep this
APPL-071 WARN STOP process. Packet race problem occered. startAMR and resend it
stopAMR recieved in stopAMR is received but AX is stopping Almost case, this warning
APPL-072 WARN
ABORT. STOP executedAMR
other process
executedAMR is received but AX is is ignorable. Because
executedAMR maybe AX
APPL-073 G
ABORT. recieved in STOP
other plannedAMR stopping other AMR
plannedAMR is received but AX is illegal. Check
plannedAMR maybeit.
APPL-074 G
PAUSE. recieved inpacket
Unknown STOP stopping other AMR illegal. Check it.
APPL-081 G
ABORT. recieved Unknown packet is recieved.
The AMR is received which is sent to Check this packet.
sp_index, dev_no,
APPL-082 G AX is not registered not registered AX. sub_id in AMR.
stopAMR is received. But specified AMR
is not in APPLICATION. The packet race Check the stopAMR.
APPL-083 WARN No AMR to stop problem occered. The stopAMR is Check the stop timing.
startAMR is received. But specified
AMR is not in APPLICATION. The packet Check the startAMR.
APPL-084 WARN
PAUSE. No AMR to start race problem occered. The startAMR is Check the stop timing.
APPL-085 G
ABORT. AMGR
AX is freezed
recieved an illegal AMGR is locked by the FATAL error. Please cold start.
APPL-087 G
ABORT. packet
AX recieved an illegal AX received an illegal packet. Check the packet.
APPL-088 G AMR is stopped by AX
Thereceived
process an
wasillegal AMR.
stopped by some Check the AMR.
APPL-090 WARN ERROR error. Check AX task sequence.
APPL-091 WARN AX is busy AX is busy. system error
APPL-092 WARN
PAUSE. There is nointernal
APEXPLAN packet system error system error
APPL-093 G
PAUSE. error
APMKCHND internal system error system error
APPL-094 G
ABORT. error system error system error
APPL-151 G APLIB internal error System error in APLIB. system error.
APSH-000 WARN %s General status messages. N/A
A MACRO was called without a Check the MACRO call in
APSH-001 WARN %s missing parameter that must be entered. the TP program.
A MACRO was called with a parameter Check the MACRO call in
APSH-002 WARN %s Illegal type that is illegal. The parameter has the the TP program.
An zone number less that 1 or greater Use an event number
APSH-003 WARN %s Illegal zone number than $IZONEIO.$NO_ZONES was used. from 1 to
The robot has requested an If the cell controller does
Waiting for interf. zone interferance zone, but has not been not give control of an
APSH-004 WARN %s given permission to enter by the cell interferance zone to the
The robot has received permission to Used to clear the waiting
APSH-005 WARN Entering interf. zone %s enter the interferance zone. for interferance zone
This warning indictates that the Warning only. Delete any
amount of free memory in the CMOS unneeded data. Contact
memory partition has gotten your FANUC
dangerously low. If the PERM memory representative with this
APSH-006 WARN PERM memory is low runs out, you will experience strange error. You will probably
This warning indicates that the amount Warning only. Delete any
of free memory in the TEMP memory unneeded data. Contact
partition has gotten dangerously low. If your FANUC
TEMP DRAM memory is the TEMP memory runs out, you will representative with this
APSH-007 WARN low experience strange MEMO errors and error. You will probably
A fault has ocurred, so the operation Clear the source of the
APSH-008 WARN FAULT must be reset requested cannot be performed. fault, and press FAULT
Program already The shell detected a start signal but a Re-issue start request
APSH-009 WARN running program is already running. when current program is
A UOP CYCLE START or DI[Initiate Style]
was detected when a non- production None is required. The next
(i.e. test cycle) program was paused. production start signal will
APSH-010 WARN %s aborted
Cannot access This current
The paused $MNUFRAMENUM[]
program was abortedisfor start
Go tothe current
FRAME style.
menu to
APSH-011 $MNUFRAME. incorrect. select a valid user frame.
The robot's REMOTE condition is TRUE, Disable the REMOTE
REMOTE switch must so the remote operating device (PLC) condition by turning the
APSH-012 WARN be on LOCAL currently has motion control over the REMOTE keyswitch on the
Verify that the following
The REMOTE condition is currently conditions are true in
false, so the robot is not under the order to put the robot
Place robot into control of the remote operating device into the REMOTE
APSH-013 WARN REMOTE state (PLC). condition: 1. UOP inputs
There is an active fault, which prevents Clear the source of the
APSH-014 WARN RESET Failure the reset request from executing fault (usually en external E-
Step mode must be Step mode is enabled, which prevents Disable step mode by
APSH-015 WARN disabled the run request from executing pressing the STEP
The UOP is not the master device, Turn SOP REMOTE/LOCAL
Robot is not under PLC which prevents the run request from keyswitch to REMOTE.
APSH-016 WARN control executing Make sure all UOP signals
Running with process This is a warning to notify the user that
APSH-017 WARN disabled a production job is running with the None needed.
WARNING - Machine This is a warning to notify the user that
APSH-018 WARN lock is on a production job is running with None needed.
The job queue cannot accept the next Manually edit the job
APSH-019 WARN Job queue is full job because it is full. queue to delete any
Check the external device
A request to run the next job in the to make sure that a job
APSH-020 WARN Job queue is empty queue came in, but the queue is empty. number was correctly sent
Robot motion and/or program Check UOP I/O setup. UOP
APSH-021 WARN Raise UOP ENBL input execution cannot occur unless UOP input 8 (ENBL) must be
The safety fence input
APSH-022 WARN Safety fence is open The safety fence input is LOW. must be ON to resume
No EXEC at Single Step Cannot execute AccuCal2 program in Please Turn off Single Step
APSH-023 Mode. Single Step Mode. before executing iRCal
The program name that the shell was Check PLC->Robot style
requested to run is not loaded on the communication. Verify
APSH-024 WARN Program %s not loaded controller. that specified JOB name
This is a warning to notify the user that None needed.
WARNING - Running at a production job is running at less than Dispensetool can increase
APSH-025 WARN < 100%% 100% speed. override. the override speed to
No CALIB END AccuCal2 program does not have a Add CALIB END instruction
APSH-026 instruction. FIND END instruction. at the end of the frame
Press FAULT RESET In order to resume normal production Perform the action stated
APSH-027 WARN button operation, Dispensetool requires that in the error message
Increasing speed to This is a warning to notify the user that None needed. To disable
APSH-028 WARN 100%% Dispensetool in increasing the this feature, you may
The robot must be at the HOME
position in order to perform the
requested operation. This error is Move the robot to the
APSH-029 WARN Robot must be at home usually posted when the PLC sends a home position.
The GIN[style_in] is set to an invalid
Check the GIN[style_in]
APSH-030 WARN Style code %s is invalid number. value as well as the Group
Place holder error, used to keep Check the GIN[style_in]
APSH-031 WARN %s documentaion for errors from value as well as the Group
Dispensetool has detected that the This is a status message to
robot servos have been disabled make sure the user is
APSH-032 WARN Robot Servos Disabled manually. aware that the robot
Increase communication
PLC comm error - A communication sequence took too timeout value in PNS Cell
APSH-033 WARN timeout long to complete. Communication setup
The User Operator Panel output group Set up the UOP Outputs in
APSH-034 WARN No UOP output defined has not been defined. the UOP I/O menu and
Robot is in Bypass The MODE input is low, forcing the Set the MODE switch to
APSH-035 WARN mode robot into BYPASS mode. The robot will ON. The robot will then re-
If the REMOTE condition
The current JOB has been paused. This is TRUE, the fault recovery
often happens if the HOLD input is menu will appear and give
User JOB has been turned ON or the UOP ENBL signal is set the user the appropriate
APSH-036 WARN paused to OFF. recovery options. If the
The User Operator Panel input group Set up the UOP Inputs in
APSH-037 WARN No UOP input defined has not been defined. the UOP I/O menu.
No style input group The group which carry the style code in Set up a STYLE SELECT
APSH-038 WARN defined to the controller has not been defined. group in the Cell I/O and
The style acknowlege strobe, which is Set up a Style Ack Strobe
No style ack strobe needed with the current in the Cell Output I/O
APSH-039 WARN defined communication configuration, has not menu and restart the
The backup input group, which is Set up a Backup Style
No backup input group needed with the current Select group in the Cell
APSH-040 WARN defined communication configuration, has not output I/O and GROUP
The style strobe, which is needed with Set up a PNS Strobe in the
No style input strobe the current communication Cell Input I/O menu and
APSH-041 WARN defined configuration (queue enabled), has not restart the robot.
Place holder error, used to keep Set up a PNS Strobe in the
APSH-042 WARN %s documentaion for errors from Cell Input I/O menu and
The style acknowlege group, which is Set up a Style Ack Group
No style ack group needed with the current in the Cell output I/O and
APSH-043 WARN defined communication configuration, has not GROUP I/O menus and
The current job has been held by Release the HOLD button
APSH-044 WARN A user program is HELD pressing the HOLD button or setting and raise the UOP HOLD
No program setup for No program number has been set up Enter a program number
APSH-045 WARN style %s for this RSR input. for this RSR input in the
This is a notice that the robot is leaving
Robot is in Automatic BYPASS mode and entering
APSH-046 WARN mode AUTOMATIC mode, where it can None needed.
This is a warning, telling the user that The shell requires the
Shell will not run the UOPs have not yet been set up, so UOPs to run. Once the
APSH-047 WARN without UOPs the shell will wait for the UOPs to be UOPs have been set up,
The backup style group is not the 1's Verify that the PLC is
PLC comm error - invert complement (inverse) of the style input sending the correct invert
APSH-048 WARN check group. style to the correct group.
Place holder error, used to keep Verify that the PLC is
documentaion for errors from sending the correct invert
APSH-049 WARN %s Drastically changing. style to the correct group.
Signals which are required for this cell Check the messages
IO configuration have not been posted previous to the in
APSH-050 WARN Cell IO setup is invalid configured. the error log for the
Connect or deassign The robot cannot move while the UOP You must either wire UOP
APSH-051 WARN UOP inputs inputs are in this state. inputs #1, #2, #3, and #8
UOP inputs #1 (IMSTP), #2 (HOLD), See remedy for APSH-051,
Critical UOP inputs are #3(SFTYFNC), #8 (ENBL) are all LOW. Connect or deassign UOP
APSH-052 WARN LOW These must all be HIGH for normal inputs.
Try to run detect instruction without Do Control start and load
APSH-053 No calibration software. Calibration software. one of the Calibration
In order to resume normal production Perform the action stated
APSH-054 PAUSE Release SOP E-STOP operation, Dispensetool requires that in the error message
APSH-055 PAUSE Raise UOP IMSTP input operation, Dispensetool requires that in the error message
APSH-056 PAUSE Release SOP E-STOP operation, Dispensetool requires that in the error message
APSH-057 PAUSE Release TP E-STOP operation, Dispensetool requires that in the error message
This error is posted by
This error is posted to simulate a PAUSE Dispensetool during
APSH-058 PAUSE Pause forced by shell error. normal operation, but
This error is posted by
This error is posted to simulate a Dispensetool during
APSH-059 PAUSE Abort forced by shell ABORT error. normal operation, but
This is not a fault. This error is posted In most cases, this fault
when the robot is sent a cycle start can be ignored. This fault
from the cell controller, but the robot is was put in to assist in
Cycle start ignored-not either in BYPASS mode (set from Soft debugging problems with
APSH-060 WARN in AUTO Panel menu) or in MANUAL mode, but the soft panel in
In most cases, this fault
can be ignored. This fault
Place holder error, used to keep was put in to assist in
documentaion for errors from debugging problems with
APSH-061 WARN %s Drastically changing. the soft panel in
In most cases, this fault
can be ignored. This fault
Place holder error, used to keep was put in to assist in
documentaion for errors from debugging problems with
APSH-062 WARN %s Drastically changing. the soft panel in
The current job has been paused by Release the HOLD button
APSH-063 PAUSE A HOLD input is active pressing the HOLD button or setting and raise the UOP HOLD
Place holder error, used to keep Release the HOLD button
APSH-064 PAUSE %s documentaion for errors from and raise the UOP HOLD
APSH-065 PAUSE %s documentaion for errors from and raise the UOP HOLD
APSH-066 WARN %s documentaion for errors from and raise the UOP HOLD
Check for loss fixture or
APSH-067 Circle fit error %s Circle fit error exceeds threshold. tool or change the fit
Check for loss fixture or
APSH-068 Radius err %s Circle radius error exceeds threshold. tool or change the radius
Auto Update is on. The frame has been
APSH-069 Auto Update is ON. updated automatically Update is not required.
The error handler was unable to Disable all E-Stops and
continue the task named when the user release HOLD buttons. If it
requested that all tasks be continued is not desired that the
APSH-070 PAUSE Failed to continue %s This is probably due to one of the E- task named be continued,
The task which the error
A Karel PAUSE_TASK() command failed handler tried to pause
Failed to pause robot to pause a task which the error handler was probably a system
APSH-071 PAUSE task believes should be paused. utility, and is not allowed
Failed to abort robot Cold start the robot
APSH-072 PAUSE Servos
task Locked-out, A Karel ABORT_TASK() command failed. controller, then manually
APSH-073 WARN enable servos Robot servos are locked out. Enable robot servos.
APSH-074 WARN Disable Teach Pendant operation, Dispensetool requires that in the error message
The following error occured when a the Verify that this TPE
Error in accessing data associated with a TPE program program exists. Go into
APSH-075 WARN TPE:%s was accessed. the DETAIL pages under
Make sure the program
exists and it is not already
The shell tried to execute a program, running or paused. Use
but was stopped by the operating the PROGRAM STATUS
APSH-076 WARN Shell could not run:%s system. display to make sure you
If you need to use the AT
PERCH, AT PURGE, or AT
This TPE did not contain a position to SERVICE outputs, teach
APSH-077 WARN No positions in %s represent HOME, SERVICE, or PURGE. the positons you need in
Make sure the program
exists and it is not already
The shell tried to execute a program, running or paused. Use
Shell could not run but was stopped by the operating the PROGRAM STATUS
APSH-078 WARN program system. display to make sure you
No Auto/Bypass input has been Set a Auto/Bypass input in
APSH-079 WARN No DIN for Auto/Bypass defined, but one was expected. the Cell I/O Input menu
The robot is currently waiting for This is a warning to inform
Waiting for Cancel or continue (Wet or Dry) or a the person at the teach
APSH-080 WARN Cancel/Continue HOME input from the PLC. pendant that the PLC has
The robot is currently waiting for a This is a warning to inform
cancel input from the PLC. The current the person at the teach
JOB has had a fault so severe that it pendant that the PLC has
APSH-081 WARN Waiting for Cancel cannt recover and must be aborted or been given exclusive
No $ERROR_PROG has been defined for Use the TPE ERROR_PROG
this JOB. This fault will only appear if command, under Program
No $ERROR_PROG the Karel variable Control, to set up a Error
APSH-082 WARN defined [SLERROR]POST_NO_ERRP is set to Program for this JOB. This
Use the TPE
No $RESUME_PROG No $RESUME_PROG has been defined RESUME_PROG
APSH-083 WARN defined for this JOB. command, under Program
The robot is running a style program Verify that all simulated
WARNING - simulated with one or more I/O ports simulated. I/O points should be
APSH-084 WARN I/O Unexpected motions and actions may simulated. Un-simulate all
Set UFrame to be the
Specified UFrame is zero or small and precision calibration
APSH-085 UFrame is too small Calibrate UFrame is disabled. fixture location or enable
Set UTool to be the
Specified UTool is zero or small and precision calibration
APSH-086 UTool is too small Calibrate UTool is disabled. fixture location or enable
Modify calibration points
Joint[%s^1] rotation is to provide more motion
APSH-087 small Joint angle motion is too small on the specified axis. Or
Three or more points with same search Reteach one of the points
APSH-088 Points are colinear direction are colinear or nearly colinear so the points are not
There must be at least three different Add more search points or
search directions that are close to reteach existing points to
perpendicular to each other. There have sufficient search
Not enough search must be at least three non-colinear directions and sufficient
APSH-089 direction points in one search direction and at number of points in the
Place holder error, used to keep Verify that all simulated
documentaion for errors from I/O points should be
APSH-090 WARN %s Drastically changing. simulated. Un-simulate all
Place holder error, used to keep Verify that all simulated
documentaion for errors from I/O points should be
APSH-091 WARN %s Drastically changing. simulated. Un-simulate all
Site-specific alarm caused by changes Please consult FANUC
APSH-092 WARN %s made for customer regarding specific changes
APSH-100 WARN %s made for customer regarding
Fix specific changes
TCP Alignment and run
APSH-101 TCP Alignment error Maximum alignment distance exceeded iRcal TCP again
Process is not yet Cannot execute current step without Please complete all steps
APSH-102 completed completing
Cannot stepsthe
re-apply before.
calibrated result leading to the current
APSH-103 Update already applied again. None.
There is no associated Analog data file Copy the analog data file
APSH-104 No Analog port data file in FRS: for the specified analog port to the FRS: directory and
Option does not iRCal Mastering and iRCal TCP do not Select a different sensor
APSH-105 support AIN support analog sensor. type in the detection
No analog sensor Detect Circle and Detect Joint Select a different sensor
APSH-106 support instruction do not support analog type in the detection
Select a different AIN port
APSH-107 Invalid AIN port number The AIN port number is not valid. number that has its data
Dynamic UFrame setup Dynamic Uframe seting require cd pair Set the cd pair number in
APSH-108 error setting in its schedule. the schedule or change
Standard UFrame setup The schedule used by UFrame has Select a new schedule or
APSH-109 error cd_pair set. change the cd_pair
The READ IO MACRO was called
READ IO parm %s without a parameter that must be Check the MACRO call in
APSH-110 WARN missing entered. READ IO(signal name string, the TP program.
READ IO parm %s is The READ IO MACRO was called with Check the MACRO call in
APSH-111 WARN wrong type illegal parameters. READ IO(signal the TP program.
The READ IO MACRO was called but the
signal could not be found. READ Check the MACRO call in
APSH-112 WARN signal %s does not exist IO(signal name string, integer register the TP program.
APSH-113 WARN can't fetch signal type IO(signal name string, integer register the TP program.
can't fetch signal signal could not be found. READ Check the MACRO call in
APSH-114 WARN number IO(signal name string, integer register the TP program.
APSH-115 WARN can't read signal %s IO(signal name string, integer register the TP program.
Check if the register is
APSH-116 WARN Reg %s could not be set Register operation failed defined, if it is between 1-
APSH-117 WARN Register not defined %s This is just a debug message N/A
The WRITE IO MACRO was called
WRITE IO parm %s without a parameter that must be Check the MACRO call in
APSH-118 WARN missing entered. WRITE IO(signal name string, the TP program.
The WRITE IO MACRO was called with
WRITE IO parm %s is illegal parameters. WRITE IO(signal Check the MACRO call in
APSH-119 WARN wrong type name string, integer value to write) the TP program.
The WRITE IO MACRO was called but
the signal could not be found. WRITE Check the MACRO call in
APSH-120 WARN signal %s does not exist IO(signal name string, integer register the TP program.
The WRITE IO MACRO was called but
the signal could not be found. WRITE Check the MACRO call in
APSH-121 WARN can't write signal %s IO(signal name string, integer register the TP program.
The GET IO MACRO was called without
GET IO PORT parm %s a parameter that must be entered. GET Check the MACRO call in
APSH-122 WARN missing IO(signal name string, integer port the TP program.
GET IO PORT parm %s is The GET IO MACRO was called with Check the MACRO call in
APSH-123 WARN wrong type illegal parameters. GET IO(signal name the TP program.
The GET IO MACRO was called but the
signal could not be found. GET IO(signal Check the MACRO call in
APSH-124 WARN signal %s does not exist name string, integer port number) the TP program.
It was detected that the Process was - Don't choose to FORCE
DISABLED at the start of this the process enable. -
production program. A choice (or setup Change Prog Select-
APSH-125 WARN Forcing Process Enabled selection) has indicated that the Production Check Process
APSH-126 PAUSE %s Robot is paused Status message
The joint velocity limit has changed.
Repower to activate This parameter change requires you to Turn off the controller,
APSH-127 WARN change. cycle controller power in order to take then turn it on again.
Tryout mode state has CHANGED from
disabled to enabled. This is only a
status message, it is not a fault. Note: Disable tryout mode, if
APSH-128 WARN Tryout mode enabled tryout mode is a test function - part desired.
Tryout mode state has CHANGED from
enabled to disabled. This is only a
status message, it is not a fault. Note: Enable tryout mode, if
APSH-129 WARN Tryout mode disabled tryout mode is a test function - part desired.
Cannot access FR: %s Error occurred while accessing the FR: .DT files must exist on the
APSH-130 WARN *.DT files device. No .dt files found. FR: device.
I/O port defined wrong: Illegal type, .DT file on the FR: device
APSH-131 WARN I/O data error: %s Default data is used. must be corrected.
The program name that the shell was Check PLC->Robot style
Selected Prog %s not requested to run is not loaded on the communication. Verify
APSH-132 WARN loaded controller. that specified Program
Move the robot back to
The robot has been jogged away from the position where the
Not in safe starting the position where the teach pendant teach pendant was
APSH-133 WARN position was enabled. enabled, abort the
the position where the teach pendant teach pendant was
APSH-141 PAUSE %s was enabled. enabled, abort the
WARNING - System is in This is a warning to notify you that a
APSH-142 WARN dry run production job is running with the None is required.
Robot motion is not Robot motion and/or program Check UOP I/O setup. UOP
APSH-143 WARN enabled execution cannot occur unless UOP input 8 must be ON.
WARNING - Process A 'Force Process Complete' was This is just a warning to let
APSH-144 Complete manually performed from the Soft Panel the operator know that
Gun operation is A production job is running with the
APSH-150 WARN NOSTROKE
Weld operation is gun set to NOSTROKE.
A production job is running with weld None.
APSH-151 WARN NOWELD set to NOWELD. None.
Robot mode must be The robot must be in full automatic Go to the SOFT PANEL
APSH-152 WARN AUTO mode with the PLC before production menu and set Robot
Must press SHIFT key The shift key must be pressed when
APSH-153 WARN too accessing this teach pendant hardkey. Press the shift key.
Because the system is currently
configured for one equipment with a
single gun, there is no need to set the
APSH-154 WARN Only one gun defined equiopment that that GUN and None is required
1. Go to the SETUP menu.
The HOME position has not been 2. Select Reference
HOME position not recorded yet. The HOME position is Position from the [TYPE]
APSH-155 WARN recorded contained in Reference Position menu. menu. 3. Jog the robot to
Go to the SETUP menu,
The HOME position has not been select Reference Position
Specify Home in Ref Pos recorded yet. The HOME position is from the [TYPE] menu. Jog
APSH-156 WARN Menu contained in Reference Position menu. the robot to the HOME
Teach pendant must be The teach pendant must be enabled
APSH-157 WARN enabled when accessing this teach pendant Enable the teach pendant.
Go to the Weld Intface
Output menu, and edit
The group output that contains the the index of the Weld
No group output for weld schedule has not been configured Schedule I/O point. Make
APSH-158 WARN weld sched yet. sure the group output has
The servos are not ready, so operation When resetting a fault,
APSH-159 WARN Servos are not ready requested cannot be performed. wait for the servos to click
Robot not at POUNCE The robot is not at the POUNCE Re-issue this request
APSH-160 WARN position position, so the operation requested when the robot is AT
No production program The robot is not currently running a Re-issue the request when
APSH-161 WARN is running production style, so the operation the robot is running a
Go to the Spot Equipment
Intface Output menu, and
The group output that contains the edit the index of the Valve
No group output for setting for the multi-pressure valving pressure I/O point. Make
APSH-162 WARN multi-pressure has not been configured yet. sure the group output has
No motion can occur because the gun
is closed. This prevents the user from
No motion allowed-- jogging or running a program while the
APSH-163 WARN gun closed gun is closed, and damaging parts Open the gun.
Go to the Cell Setup menu
and either check the
The HOME I/O program as specified name of the HOME I/O
Home I/O program %s from the Cell Setup menu does not macro name menu item.
APSH-164 WARN not loaded exist and was not run. Make sure the file
Proceed to the Spot
Equipment I/O setup
There I/O configuration for the proper screen and configure the
Invalid Studgun studwelding gun has not been digital inputs Gun Present
APSH-165 WARN Selection initialized. = On/Off, Gun in Nest =
Studgun Change The robot was aborted or interrupted Manually change the stud
APSH-166 WARN Unsuccessful during the studgun change sequence. guns and move the robot
To resume production the
Move robot home & The stud gun change program was robot must be manually
APSH-167 WARN cycle start interrupted. returned home and cycle
Go to the Spot Equipment
Intface Output menu, and
The group output that contains the edit the index of the Equal
setting for the equalization pressure pressure I/O point. Make
APSH-168 WARN No GO for EQP pressure has not been configured yet. sure the group output has
Proceed to Spot
Equipment Menu under
Uninitialized Stud A macro program to dropoff or pickup MENUS-SETUP and
APSH-169 WARN Macros studgun 1 or 2 has not been initialized. initialize the studwelding
Check Nest/Changer The inputs on the studwelder nest do Verify on the Spot Equip
APSH-170 WARN Inputs not appear to be set up correctly. I/O menu that the Head in
HOME_IO has not HOME_IO has not completed Check HOME_IO and see
APSH-171 completed running successfully,
An SCR overtempso new program
signal cannot be Check
has been if it is looping
the SCRonforsome
APSH-174 WARN SCR
Req.overtemp
Press. Notdetected
mapped received.
The Request Pressure digital input is overheating.
Map request pressure
APSH-175 WARN for WC:%s not mapped. input on Weld Interface
GIN For Weld Press. Not The GIN for Weld Pressure is not Map Weld Pressure
APSH-176 WARN mapped for WC:%s mapped. pressure input on Weld
Read Press. Not Read pressure input is not mapped on Map read pressure input
APSH-177 WARN Map
mapped
I/O for WC:%s
in Weld weld interface Menu. on Weld Interface Menu.
APSH-178 WARN Interface Menu There is not cause, this is a help code No rememdy required.
Upd. Press. timeout The weld controler did not set Read Check if weld controler is
APSH-179 WARN WC:%s Pressure input in time. functioning correctly, or
Could not communicate Could not read any I/O from the Weld Check if weld controler is
APSH-180 WARN Automatic
to WC. Collision controller. Device may
Automatic Collision be offline.
recovery is functioning correctly, or
APSH-201 WARN Recovery beginning. None.
Recovery Program not Automatic Collision recovery was Make sure the program is
APSH-202 WARN found attempting to run the recovery loaded, and retry the
Check the associated error
APSH-203 WARN Error running %s The task could not run or continue. message for the task error
Running recovery prog Automatic Collision recovery is about to
APSH-204 WARN %s run the recovery program. None.
Running original prog Automatic Collision recovery is about to
APSH-205 WARN %s run the original program. None.
The group specified to get_home does Verify the specified group
APSH-206 WARN Invalid Group Specified not
The exist.
reference position specified to number exists, and
Verify specified retry
Reference
APSH-207 WARN Invalid Ref Pos Specified get_home. position exists.
This error is related to production Press F6,REDO and cycle
setup check screen. This item should power to update items.
APSH-208 WARN Failed to check %s not be checked on the present 3.1.3 ARC Alarm Code
Fault Disabled: single This is a warning message to log that
APSH-209 cycle. the user chose to disable fault checking None.
Fault Disabled: multiple This is a warning message to log that
APSH-210 cycles. the user chose to disable fault checking None.
Illegal arc equipment An attempt was made to add or use
ARC-001 WARN config more equipment than permitted. To Be Determined
PAUSE. Illegal arc schedule An arc instruction contained an illegal Change the schedule
ARC-002 L
PAUSE. number
No (%s^4,%d^5)
gas flow schedule
No number.
gas flow was detected during an arc number to one shown in
ARC-003 L (%s^4,%d^5) start. Check the gas supply.
Gas flow after weld The gas fault input was not ON after Check the gas valve and
ARC-004 WARN (%s^4,%d^5)
PAUSE. the
A gas
gas output
fault inputwas
wasset to OFF. during the gas flow switch.
detected
ARC-005 L Gas fault (%s^4,%d^5) welding. Check the gas supply.
PAUSE. A wire fault input was detected during
ARC-006 LPAUSE. Wire
Waterfault
fault(%s^4,%d^5)welding.
A water fault input was detected during Check the wire supply.
ARC-007 L
PAUSE. (%s^4,%d^5)
Power supply fault welding.
A power fault input was detected Check the water supply.
ARC-008 LPAUSE. (%s^4,%d^5)
Wire stick detected during welding. Check
Securethe
thepower supply.
robot and
ARC-010 L (%s^4,%d^5) A wire stick has occured. equipment. Cut the wire.
A wirestick was detected and wirestick
reset was not performed. Wirestick
PAUSE. Wire stick, not reset reset may be disabled. Wirestick reset Secure the robot and
ARC-011 L (%s^4,%d^5) is not done during TIG welding or if equipment. Cut the wire.
PAUSE. Wire stick reset(s) failed A wirestick was detected and the Secure the robot and
ARC-012 L (%s^4,%d^5) automatic wirestick reset failed to equipment. Cut the wire.
Check the wire and weld
PAUSE. Arc Start failed The arc detect input did not stabilize equipment. Adjust the
ARC-013 L (%s^4,%d^5) during an arc start. weld schedule and/or
Teach pendant is The weld enable or a wire inch hardkey
ARC-014 WARN disabled was pressed with the teach pendant Enable the teach pendant.
The weld enable or a wire inch hardkey Try again while holding
ARC-015 WARN Press shift with this key was pressed without holding the shift the shift key.
A program executing from the teach Disable the arc for testing
PAUSE. Weld by Shift FWD is pendant attempted an Arc Start with from the teach pendant or
ARC-016 L disabled welding from the teach pendant change the Weld System
Welding can be enabled
using the teach pendant
Arc Start was disabled An Arc Start instruction was executed arc enable key or the
ARC-017 WARN (%s^4,%d^5) with welding disabled. remote arc enable input.
PAUSE. Lost arc detect The arc detect signal was lost during a Check the wire feeder.
ARC-018 LPAUSE. (%s^4,%d^5)
Can't read arc detect weld. Check the welding
process I/O
ARC-019 L
PAUSE. input
No (%s^4,%d^5)
plan data area The arc detect
Insufficient input exists
memory could not be read.
to plan an board
Try connection.
reducing the number
ARC-020 L available arc instruction. of programs.
ABORT. Program aborted while Check if the program ends
ARC-021 L welding (%s^4,%d^5) A program was aborted while welding. without an Arc End
Weld AO scaling limit The programmed analog output is Modify the weld
ARC-022 WARN
PAUSE. used
Illegal(%s^4,%d^5) beyond
arc schedule type the equipment
The arc instruction limits.
register is not an parameters
Use a registerused
thatinisthe
an
ARC-023 L (%s^4,%d^5)
Invalid equipment integer
The type. min to max range is too
equipment integernew
Enter type.
min or max
ARC-024 WARN range small. values for the equipment.
Invalid A/D or D/A The binary range data for the A/D or Modify the correct system
ARC-025 WARN range D/A is too small. variable fields within
Cannot scale AIO while An analog scaling limit was modified Turn off the controller
ARC-026 WARN welding while welding. The scaling was not and turn it on again.
Arc log failed: Device Free space on Memory Device is Arrange the contents of
ARC-027 full insufficient, so cannot save the log file Memory Device and get
%d arc log files auto Free space on Memory Device is Arrange the contents of
ARC-028 delete insufficient, so auto deletion of log files Memory Device and get
Illegal num of weld The number of weld I/O is illegal; more Set up weld I/O again at
ARC-029 I/O(%s)
Wire stick is still than
A wiremaxmum, less
stick is still than minimum
detected after a or controlled
Secure the start.
robot and
ARC-030 WARN detected (%s^4,%d^5) system RESET. equipment. Cut the wire.
Motion has stopped longer than If no motion is needed
$arc_los_tim while welding. Motion has during welding, increase
stopped longer than the time specified the arc loss time in the
PAUSE. No motion while in weld schedulle and weld setup while Weld Equipment SETUP
ARC-031 L welding (%s^4,%d^5) welding. screen or disable arc loss
PAUSE. Weld stopped by single Welding was stopped by entering single To continue welding you
ARC-032 L step (%s^4,%d^5) step mode after welding began. must exit single step
PAUSE. Override must be Set the speed override to
ARC-033 L 100%% to weld The speed override is less than 100%. 100% to weld or disable
A task which does not have weld Allow the task which has
PAUSE. Task does not control control attempted to execute an Arc weld control to end or
ARC-034 L welding (%s^4,%d^5) Start or an Arc End instruction. Only abort before attempting
PAUSE. Equipment number isn't The arc instruction does not have the Please set the equipment
ARC-035 L set (%s^4,%d^5) equipment number number to the program
PAUSE. Such equipment mask An attempt was made to add or use
ARC-036 L isn't supported more equipment than permitted. To Be Determined
Another equipment is Another equipment is wire inching Please stop wire inching
ARC-037 WARN inching now now. for another equipment by
PAUSE. Already held another This program( task ) has already held Please control the
ARC-038 L equipment the another equipment A task can only equipment by the another
PAUSE. %s^1 AO[%d^2] is not The named weld analog output signal is Adjust the weld analog
ARC-039 L scaled (%s^4,%d^5) not scaled properly. output scaling in the Weld
Verify the I/O hardware is
PAUSE. Missing I/O: %s^1 The named weld I/O signal is not connected and the signal
ARC-040 L (%s^4,%d^5) detected or configured properly. is assigned a port number
The weld equipment has been Add the DeviceNet option
configured to use DeviceNet by setting or choose a weld
the fields $VENDOR_ID, $DEV_TYPE, equipment model which
PAUSE. Weld EQ needs and $PROD_CODE in the system does not require
ARC-041 L DeviceNet option variable $AWEPRR to non-zero values. DeviceNet. If the weld
The weld equipment has been Add the Explicit
configured to use DeviceNet by setting Messaging option or
the fields $VENDOR_ID, $DEV_TYPE, choose a weld equipment
PAUSE. Weld EQ needs Expl and $PROD_CODE in the system model which does not
ARC-042 L Msg option variable $AWEPRR to non-zero values. require DeviceNet. If the
The weld equipment has been Add DeviceNet hardware
configured to use DeviceNet by setting or choose a weld
the fields $VENDOR_ID, $DEV_TYPE, equipment model which
PAUSE. Weld EQ needs and $PROD_CODE in the system does not require
ARC-043 L DeviceNet board variable $AWEPRR to non-zero values. DeviceNet. If the weld
The weld equipment has been You can add a DeviceNet
configured to use DeviceNet by setting definition for this product
the fields $VENDOR_ID, $DEV_TYPE, or if the weld equipment
PAUSE. Weld EQ needs and $PROD_CODE in the system you are using does not
ARC-044 L DeviceNet defn. variable $AWEPRR to non-zero values. support DeviceNet you
ArcTool attempted to communicate Verify the Weld
Weld EQ Device is with the Welding Equipment using the Equipment is ON. Verify
ARC-045 WARN OFFLINE DeviceNet network, but could not the DeviceNet cable is
There was a communication error Verify the Weld
Weld EQ detected between ArcTool and the Equipment is ON. Verify
ARC-046 WARN communication error Weld Equipment. the DeviceNet cable is
Not allowed during a An operation was attempted which is Try the operation after
ARC-047 WARN weld not permitted while a weld is executing the program ends or is
Auto AI/O setup is Auto AI/O setup for the mounted I/O Verify mounted I/O
ARC-048 WARN unsupported module is not supported. So module and set system
Process %d switch to The weld power supply
ARC-049 WARN %d failed ArcTool failed to switch weld processes. may be OFF,
ArcTool failed to find this process on Enter a different number
ARC-050 WARN Process %d NOT found the weld power supply. or use the SEARCH
ArcTool is communicating with the This message is for
ARC-051 WARN Weld EQ ONLINE: %s weld power supply.
The indicated The version
parameter is out of notification and within
Enter a number
ARC-052 WARN Bad %s %s Prc %d range. range.
No ramp at process Ramping is not allowed when switching Complete the process
ARC-053 WARN switch
PAUSE. (%s^4,%d^5)
No motion while arc weld processes. switch first, then ramp
ARC-054 G welding
No sync Eq An Arc Start instruction specified Determine why the sync
ARC-055 STOPL (%s^4,%d^5) synchronizing with an Equipment that Equipment is not starting,
Check the synchronization
equipment number
An Arc Start instruction specified specified in the Arc
Invalid sync synchronizing with an Equipment that instruction or in the
ARC-056 STOPL (%s^4,%d^5) is not also synchronized. specified weld schedule
The Arc process ramping cannot
execute because the delay (t1) to Increase
Cannot ramp t1=%d > communicate with the welder is larger $aweramp[eq].$time_fact
ARC-057 t2=%dstick is still
Wire than
A wirethe ramping
stick is still loop timeafter
detected (t2). This
a or by 1.the robot and
Secure
ARC-058 detected system RESET. equipment. Cut the wire.
If you want to use Arc
Welding Monitor without
The voltage or current command do voltage and current
not exist, so Arc Welding Monitor command, please set
cannot decide the WARN and STOP ABS(V,A) to Monitoring
ARC-060 PAUSE. Cmd
Illegal%s NOT found
instruction Limit range. Method and input the
ARC-061 L
PAUSE. (%s^4,%d^5)
ARC-062 LPAUSE. Unknown
Weld timerfunction
alreadycode
in
ARC-063 LPAUSE. use
Illegal arc detect
ARC-064 LPAUSE. command
ARC-065 LPAUSE. Unknown
Resume is softpart index
not an arc
ARC-066 LPAUSE. start
ARC-067 LPAUSE. Illegal arc start state
ARC-068 LPAUSE. Illegal motion timer
ARC-069 LPAUSE. Failed to create packet
ARC-070 LPAUSE. Illegal motion state
ARC-071 L Illegal SSC packet
PAUSE. Sometimes this error
ARC-072 L
PAUSE. Illegal AMR packet Internal error. requires cycling the
ARC-073 LPAUSE. Illegal weld state
ARC-074 LPAUSE. Illegal MMR number
ARC-075 LPAUSE. Failed to send packet
ARC-076 LPAUSE. Failed to delete monitor
ARC-077 LPAUSE. Illegal gas flow state
ARC-078 LPAUSE. Illegal
Receivedaout state
unknown
ARC-079 LPAUSE. AMR
Stopped AMR pre-
ARC-080 LPAUSE. planning
ARC-081 LPAUSE. Failed to create
The common monitor
data can't
ARC-082 LPAUSE. be foundPX is using this
Another
ARC-083 LABORT. equipment
Application process is Please change the
ARC-084 LPAUSE. changed
Incomplete during
of welding Application is changed during
Imcomplete the analog signal welding. program.
ARC-085 L conversion factor setup conversion factor. Please set it.
PAUSE. Invalid of binary data in The binary
ARC-086 L conversion factor data($AWEPRR.$io_min/max_bin) is Please set correct value.
The conversion factor data is invalid. It
PAUSE. Invalid conversion must be filled more than 2 tables at Please set conversion
ARC-087 L factor data least. But the value of the second table factor more than 2 tables
PAUSE. Over selected AO factor The selected number of AO conversion Please select the correct
ARC-088 LPAUSE. No. factor data is over the number of the number of AO conversion
ARC-089 L Invalid PX ID
In this situation, the welding is
disalbled by the following reason 1: In
Single step mode 2: In Machine lock Please remove the
Weld disable by mode 3: In Dry run mode 4: No I/O specified reason to
ARC-090 WARN reason[%d] board exist 5: No I/O assignment for perform the welding.
An Arc End weld schedule specified a
time of 99.0 seconds. This time value is Use a different weld
sometimes used with Arc Starts to schedule for the Arc End
Arc End cannot ramp to indicate ramping during an entire or change the time value
ARC-091 STOPL position (%s^4,%d^5) motion. This type of ramping is not to a smaller value.
PAUSE. SVT: Unsupported Wire The selected wire material is not Please select the correct
ARC-100 L
PAUSE. material
SVT: supported
Unsupported Wire The forwire
selected Servo Torch.
size is not supportedwire materal.
Please select the correct
ARC-101 L size for Servo Torch. wire size.
SVT: Unsupported The selected unit of inching speed is Please select the correct
ARC-102 WARN speed unit not supported for Servo Torch. unit of inching speed
If another alarm is also
PAUSE. SVT: WFS conversion Failed to convert weld schedule to wire occured at the same time,
ARC-103 L failed feed speed command for Servo Torch. please check it and
PAUSE. SVT: Invalid sequence Internal error. Invalid sequence mode Internal error. Cycle
ARC-104 L mode command is sent to Servo Torch. power to recover.
Confirm which type of
PAUSE. Cannot read WSTK Cannot received WSTK signal from weld equip is used.
ARC-105 L input signal serial communication power supply. Confirm the connection
Configuration of Roboweld was invalid. Remove all Robowelds by
Config of Roboweld is So data for Robowelds were set selecting other equip in
ARC-106 WARN
PAUSE. invalid
Roboweld internal inappropriately. weld equip select screen.
ARC-107 L Error(%d) RoboWeld internal error. Cycle power to recover.
Wire touching before Wire touching before Touch Retract Check the wire touches to
ARC-108 TRS seq Start sequence starts. the work at the arc start
Feedback voltage fell down to Remove the cause of
displayed value over Arc Loss Error lower voltage. If the weld
Time. Therefore, robot judges that arc has no problem, the
ARC-109 Arc Lost: Voltage < %d V is lost. voltage threshold for arc
Feedback current fell down to Remove the cause of
displayed value over Arc Loss Error lower current. If the weld
Arc Lost: Current < %d Time. Therefore, robot judges that arc has no problem, the
ARC-110 A is lost. voltage threshold for arc
ServoTorch I/O assignment is invalid. Please confirm the
Assignment of SVT I/O This assignment is automatically assignment of signals for
ARC-111 invalid executed after cycle power. arc welding.If you find a
Enable/Disable Sim Necessary signals for Simulation mode Verify that AI/O and
ARC-120 WARN mode failed cannot be detected. WDI/O signals are
Weld not Simulation mode is enabled. So actual This is not an error. There
ARC-121 WARN performed(Sim mode) welding is not performed. is no need to do anything.
Cannot I/O signals were not set to sim/unsim Verify that AI/O and
ARC-122 WARN SIM/UNSIM(%s,Id:%d) appropriately when Simulation mode WDI/O signals are
SYSTE Memory size is too Memory size is too small to get Change memory module
ARC-123 M small memory area for necessary data. into the one which has
The weld equipment has reported an Refer to the weld
ARC-124 WARN EQ%d E:%d %s error. equipment manual for
An Arc Stitch instruction was executed Edit the program so the
while welding. Stitch welds begin with Arc Stitch instruction is
Cannot start stitch in a an Arc Stitch and end with an Arc End. not between an Arc Start
ARC-125 weld Arc Stitch cannot execute between Arc and Arc End.
An Arc Stitch instruction could not Modify the stitch weld
Bad stitch weld or pitch execute because the stitch weld length length or pitch length.
ARC-126 length or the pitch length were invalid or the $aweupr[eq].$st_weld_le
An Arc Stitch instruction could not Edit the program so the
Cannot change stitch execute because a stitch weld was Arc Stitch instruction does
ARC-127 schedules
J motion during stitch already executing.
Joint motions Stitch
are not welds cannot
permitted in a not follow an Arc Stitch.
ARC-128 weld Stitch Weld. Edit the motion type.
Term-type is changed to FINE Please choose FINE term-
ARC-130 Term-type is corrected automatically type when an arc end
Weld procedure %d The weld procedure number entered in Enter the number of an
ARC-131 NOT found a Weld Start or a Weld End instruction existing weld procedure
The weld schedule number entered in a Enter the number of an
Weld schedule %d NOT Weld Start or a Weld End instruction is existing weld schedule or
ARC-132 found not found on the controller. increase the number of
This error is reported after ARC-57 Resume the program. If
Cannot ramp t1 > t2. ARC-133 indicates the ARC-57 error occurs
the variable $aweramp[1].$time_factor without an ARC-133 error
Adjusted time_factor was automatically increased to remedy the $awscfg.$loop_time
ARC-133 %d to %d a ramp timing problem. The weld can may need to be increased.
This error is related to Production Refer to the manual for
ARC-134 EQ%d E:%d %s Monitor operation. details on the specific
This error is related to Production Refer to the manual for
ARC-135 %s^7 Monitor macro operation. details on the specific
execute because the delay (t1) to Resume the program. If
communicate with the welder is larger the ARC-136 error occurs
Cannot pulse t1=%d > than the pulsing loop time (t2). This without an ARC-133 error
ARC-136 t2=%d may occur with Low-Frquency pulse the $awscfg.$loop_time
Low-Frequency Pulse Welding is Adjust Pulse Frequency or
Clamp pulse, %3.1fHz, clamped because pulse waveform Pulse Duty Cycle for Low-
ARC-137 %3.1f%% exceeds the available range. Frequency Pulse Welding
Contact tech support for
Intenal error of ArcTool software. further investigation.
ARC-138 Internal error: ID = %d Normally this is not occurred. Then, don't forget to
Weld ID %d is already The specified Weld ID has already been Enter other Weld ID which
ARC-139 SYSTE used I/O parameter
MCC used inparameter
Setup the current
forTPMMC
program.
I/O has not been used in this
ARC-140 M wrong(E:%d,
MCC stick %d) assignment
The MCC wasare wrong.
stuck but has been Check the parameters
ARC-141 STOP detected(E:%d)
MCC monitor turned ON.
MCC is OFF even though the MCC Check the MCC .and signal
ARC-142 STOP abnormal(E:%d) request is ON. line for MCC.
PS internal com- In the Power supply, the Cycle power of the power
ARC-143 STOP disconnect(E:%d) communication between GABANA CPU supply by pressing E-STOP
PS internal com- In Power supply, the communication Cycle power of the power
ARC-144 STOP error(E:%d) alarm between GABANA CPU and Main supply by pressing E-STOP
PS internal abnormal In the Power supply, the Cycle power of the power
ARC-145 STOP com-data(E:%d) communication data between GABANA supply by pressing E-STOP
Set pulse mode to
disabled in the weld
Can't use Pulse in In CO2 setup, you cannot use Pulse schedule detail menu. If
ARC-146 STOP CO2(E:%d) mode. you use the direct
Set pulse mode to
Can't use Pulse in this In CO2 setup, you cannot use Pulse schedule detail menu. If
ARC-147 STOP setup(E:%d) mode. you use the direct
Set pulse mode to
In CO2 setup, you cannot use Pulse schedule DETAIL menu. If
ARC-148 STOP Can't use Pulse in CO2 mode. you use the direct
Set pulse mode to
Can't use Pulse in this In CO2 setup, you cannot use Pulse schedule detail menu. If
ARC-149 STOP
PAUSE. setup op. in
Invalid mode. invalid signal operation in
Detect you use
Reset andthetrydirect
again after
ARC-150 G
PAUSE. weld(0x%X)(E:%d) welding. Arc OFF.
ARC-151 G
PAUSE. Invalid wire
weld size(E:%d) Detect invalid wire size. Set proper wire size.
welding
ARC-152 G
PAUSE. process(E:%d)
Invalid wire Detect invalid welding process. process.
ARC-153 G
PAUSE. material(E:%d)
Invalid Arc Loss Detect invalid wire material. Set proper wire material.
ARC-154 G Time(E:%d) Arc loss time is invalid range. Set proper arc loss time.
PAUSE. Communication with RoboWeld power Confirm port setup and
ARC-155 G
SYSTE Comm. Timeout(E:%d)
RoboWeld Error(0x%X, source is timeout. connection cable.
ARC-156 M
PAUSE. %d)
Receive RoboWeld internal
Receive invalid dataerror.
from Power Please
Confirmcall FANUC service.
noise
ARC-157 G
PAUSE. error(0x%X)(E:%d) Source. environment and cable.
ARC-158 G
PAUSE. 1st currency (E:%d) Detect 1st currency abnormal. Check currency.
ARC-159 G
PAUSE. 2nd currency
Temperature (E:%d) Detect 2nd currency abnormal. Check currency.
ARC-160 G
PAUSE. alaram(E:%d) Detect temperature abnormal. Check overload.
ARC-161 G
PAUSE. High voltage(E:%d) Detect high voltage. Check voltage.
ARC-162 G
PAUSE. Low voltage(E:%d) Detect low voltage. Check voltage.
ARC-163 G
PAUSE. Start signal
Power error(E:%d) Detect 3-phase
source start signal abnormal.
power source start signal.
Check 3-phase power
ARC-164 G
PAUSE. error(E:%d) abnormal. source.
ARC-165 G EQ is detached(E:%d) RoboWeld is detached. Confirm port setup.
PAUSE. Comm. stopped in Communication with RoboWeld power Confirm another error
ARC-166 G
SYSTE weld(E:%d)
I/O asginment source stopped
I/O space in welding.
for RoboWeld is already in message and port,
Confirm another I/Ocable
ARC-167 M
SYSTE overlap(%d)(E:%d) use. device and
Confirm $IO_START
another I/O in
ARC-168 M
PAUSE. I/O error(%d)(%d, E:%d) Detect
I/O initialization
invalid wireerror.
FWD/BWD device and
Confirm wire$IO_START
control in
ARC-169 G
PAUSE. Invalid wire op.(E:%d) operation. sequence.
Confirm welding device
ARC-170 G
PAUSE. Detect Arc
Unified dataOFF(E:%d)
RCV Detect ARC off. and workpiece
Confirm status.
port setup, noise
ARC-171 G error(%d,0x%X)(E:%d)
Warning, Failed
Receivetoinvalid
receivecommand
unified data.
from power environment,
Confirm noise cable
ARC-172 WARN Rcv(0x%X)(E:%d)
Warning, source.
Retry to send the command to power environment,
Confirm noise cable
ARC-173 WARN Retry(0x%X)(E:%d)
Warning, NAK source. environment,
Confirm noise cable
ARC-174 WARN
PAUSE. for(0x%X)(E:%d)
Signal change is Receive NAK from
Communication power
with powersource.
source is environment,
Confirm welding cable
setup,
ARC-175 G ignored(E:%d)
No sysvar $RBWLD for stopped.
Sysvar $RBWLD is not setup for new EQ cable connection,
Confirm $RBWLD and then
ARC-176 WARN E:%d
RoboWeld(E:%d) reset number. $RBWLD_CFG
Arc setup.
welding is now
ARC-177 WARN complete RoboWeld reset sequence is complete. available.
Confirm that the RS-422
communication line is
working properly. After
Power supply com A Power supply communication error checking it, try the
ARC-179 STOP alarm(E:%d) has occurred. operation again. If the
Check the wire feeder
motor. After check try the
Wire feeder motor speed is over the operation again. If the
ARC-180 STOP Gabana alarm(E:%d) limited speed. same alarm occurs,
Wire feeder motor sensor line was Check the wire feeder
ARC-181 STOP Encoder alarm(E:%d) connected off or wire feeder motor did motor sensor line. After
While the motor should stop, the If the motor was rotated
ARC-182 STOP Motor alarm(E:%d) motor rotation was detected. actually, the control board
External emergency An ESTOP signal was input from an Turn off controller power,
ARC-188 STOP input(E:%d) external source. remove the cause for the
An Exernal1 hold signal was input from Turn off controller power,
ARC-189 STOP External input1(E:%d) an external source. remove the cause for the
An Exernal1 hold signal was input from Turn off controller power,
ARC-190 STOP External input2(E:%d) an external source. remove the cause for the
Turn off the power then
ARC-191 STOP Memory alarm(E:%d) Power supply control memory error try again. If the same
Perform a Cold start: 1.
Turn off the robot. 2. On
the teach pendant, press
A Weld power supply CPU error has and hold the SHIFT and
ARC-192 STOP CPU alarm(E:%d) occurred. RESET keys. 3. While still
By turning off the Torch
The Torch switch was turned ON but switch, the alarm will
ARC-193 STOP Arc start alarm(E:%d) the arc could not started within 4sec. disappear. Confirm that
Check the setup of
Not support weld The specified weld type has not been process type, wire size,
ARC-195 STOP type(E:%d)
Loading weld type supported
Loading fortype
weld this power supply.
data now. Please wire material in weld
ARC-196 WARN ...(E:%d) wait for a moment.
Check the setup of
The specified weld type has not been process type, wire size,
ARC-198 STOP This
Not support
weld EQweld
isn't type The
supported for this
connected weldpower supply.is not
equipment wire material
Check in weld
the weld
ARC-199 WARN supported(E:%d) supported. equipment.
Arclink ch%d heartbeat The welding equipment connected on Check the power and
ARC-200 WARN timeout the Arclink is not responding to Arclink connections to the
Arclink ch%d obj #%d A welding equipment component on Check the power and
ARC-201 WARN no resp the Arclink failed to respond to a Arclink connections
Arclink ch%d obj #%d A welding equipment component Turn the controller and
ARC-202 WARN error resp returned an error in response to a welding equipment off
Arclink ch%d reset by The Arclink network was reset by a None. This usually
ARC-203 WARN master request from the welding equipment. happens as a result of an
This is an informational message
indicating that the Arclink network has
ARC-204 WARN Arclink ch%d available been initialized and is ready for normal None.
The high speed event message The Arclink network is
Arclink ch%d h/s event expected during welding failed to arrive automatically reset. If this
ARC-205 lost in time. error persists, it indicates
The Arclink CAN interface is detecting a Check all Arclink
Arclink ch%d too many high rate of errors on the connection to connections and wiring to
ARC-206 WARN errors the welder. This is usually caused by eliminate the electical
The Arclink interface on the controller Make sure that all Arclink
cannot detect any power or other connections are properly
equipment on the network made and that the
Arclink ch%d no bus connections. This indicates that there is connected welding
ARC-207 WARN power no Arclink network connected, or that equipment is also
Check to make sure that
Arclink ch%d no nodes No other equipment can be detected the Arclink network is
ARC-208 WARN on bus on the Arclink network. properly connected and
The Arclink interface is detecting Check all Arclink
unexpected errors on the network, connections and wiring to
indicating possible electrical noise oreliminate the source of
ARC-209 WARN Arclink ch%d bus errors other interference. If these errors the noise.
The Arclink interface on the controllerReduce the message
Arclink ch%d network is unable to communicate due to too traffic by running fewer
ARC-210 WARN flooded many messages flooding the network. utility program sessions to
Arclink ch%d comm An unexpected communications error Check all Arclink
ARC-211 WARN error %d has occurred on the Arclink CAN connections and wiring,
A CANbus card has been detected for Assign the Ethernet
Arclink ch%d CAN-Enet an Arclink communications channel connection to a different
ARC-212 conflict that has already been assigned as an channel to make this
After the weld ended the process activeIncrease the process
Process active ON after input remained ON longer than the active timeout on the
ARC-250 weld specified maximum time. robot
After the weld ended the arc detect Increase the process
Arc detect ON after input remained ON longer than the active timeout on the
ARC-251 weld specified maximum time. robot
Constant Deposition ramping could not Check that the constant
be used. This is because the constant deposition option is
No CDep %s E%d P%d deposition option is not loaded or loaded. If not, turn off
ARC-252 S%d because of using incompatible features CDep ramp in the weld
The argument for Adjust Start Height Use an integer value for
ARC-300 Argument is not integer macro is not an integer. the Adjust Start Height
The specified equipment number for Specify the existed
ARC-301 Invalid EQ number Arc Start Height Adjust is invalid. equipment number by
Invalid robot group The specified robot group number for Specify the proper robot
ARC-302 number Arc Start Height Adjust is invalid. group number in Arc Start
The specified I/O assignment for Arc Specify the proper I/O
ARC-303 Invalid I/O assignment Start Height Adjust is invalid. assignment in Arc Start
In Arc Start Height Adjust function, You
Use different PR number
Cannot use same PR cannot use same PR number for both for Touch Command
ARC-304 number Touch Command Signal and Touch Signal and Touch Detect
Other task adjusts Other task has already start Arc Start Do not perform Arc Start
ARC-305 height Height Adjust for the specified Height Adjust for one
Arc Start Height Adjust is ignored Release Single Step or Dry
because of Single Step, Dry Run. Or Run or set Weld Enabled
because of Weld Disabled when to perform Arc Start
Start Height Adjust is $AWSTHOF.$CHK_WLD_ENB is TRUE. If Height Adjust. If you are
ARC-306 ignored Lincoln welder is used, ArcLink may be using Lincoln welder,
Perform Arc Start Height
Adjust at the position
Contact has already detected before which the torch never
search is started for Arc Start Height touch the work. If you
ARC-307 Contact before search Adjust function. want to continue Arc Start
Contact is not detected during the Perform search motion
ARC-308 Contact is not detected search motion for Arc Start Height from closer position
Confirm that the settings
for Arc Start Height Adjust
Start Height Adjust Arc Start Height Adjust is failed by is proper. If other alarm is
ARC-309 failed some reason. posted at the same time,
If Arc Start Height Adjust
Too long adjust motion The motion for Arc Start Height Adjust is performed with very
ARC-310 time function is too long. low override, the alarm
The end of the file was found before Fix syntax errors within
ASBN-001 End of File parsing is complete. the file.
Error occurred during An unspecified error occurred while Fix the syntax errors
ASBN-002 load loading the file. within
Fix the the file.error
syntax The cause
on
ASBN-003 File line %4d A syntax error was detect on this line. this line.
An error occurred while loading this Fix the syntax errors
ASBN-008 file '%s' file. within the file. The cause
A syntax error was detected at the
ASBN-009 on line %d,
Memory column %d There
allocation specified linesufficient
is not and column.
free memory toFix thepower
Cycle syntaxonerror.
the
ASBN-010 error
Cannot read ASCII process this file. controller.
ASBN-011 source file The POS section of the file is missing. Fix the syntax of the file.
Fix the syntax error. The
ASBN-012 Invalid character
Unable to open source An invalid character was found. cause
The filecode
doesmay
nothave
exist or
ASBN-013 file The source file could not be opened. is corrupt.
The weld enable or a wire inch hardkey Try again while holding
ASBN-015 Press shift with this key was pressed without holding the shift the shift key.
A program executing from the teach Disable the arc for testing
Weld by Shift FWD is pendant attempted an Arc Start with from the teach pendant or
ASBN-016 disabled welding from the teach pendant change the Weld System
Welding can be enabled
using the teach pendant
Arc Start was disabled An Arc Start instruction was executed arc enable key or the
ASBN-017 (%s^4,%d^5) with welding disabled. remote arc enable input.
Lost arc detect The arc detect signal was lost during a Check the wire feeder.
ASBN-018 (%s^4,%d^5)
Can't read arc detect weld. Check the welding
process I/O
ASBN-019 input (%s^4,%d^5) The arc detect input could not be read. board connection.
Invalid section An unexpected section was detected Fix the syntax error. The
ASBN-020 encountered within the file. cause code may have
A required [ was not found in this Add [] to this register
ASBN-021 WARN Expecting a '[' context. reference, application
An index or value was specified that is Fix the syntax error. The
ASBN-022 Out of range not within acceptable bounds. cause code may have
The configuration string for the Fix the syntax error. The
ASBN-023 Configuration error position is malformed. cause code may have
ASBN-024 Expecting a comma A comma is expected. cause code may have
ASBN-025 Expecting a '=' An equal character, '=' is expected. cause code may have
ASBN-026 Expecting a ']' A ']' character is expected. cause code may have
ASBN-027 Expecting a '(' A '(' character is expected. cause code may have
ASBN-028 Expecting a ')' A ')' character is expected. cause code may have
ASBN-029 Expecting ';' A ';' character is expected. cause code may have
ASBN-031 Expecting ':' A ':' character is expected. cause code may have
Expecting a real A real floating point number is Fix the syntax error. The
ASBN-032 number expected. cause code may have
ASBN-033 Expecting an integer An integer value is expected. cause code may have
ASBN-034 Expecting 'mm' ‘mm’ is expected. cause code may have
ASBN-035 Expecting 'mm/sec' ‘mm/sec’ is expected. cause code may have
ASBN-036 Expecting 'sec' ’sec’ is expected. cause code may have
ASBN-037 Expecting 'deg' ‘deg’ is expected. cause code may have
An invalid motion group has been Fix the syntax error. The
ASBN-038 Invalid group number specified. cause code may have
Invalid combination of AND/OR operators cannot be mixed Fix the syntax error. The
ASBN-039 AND/OR within a single instruction. cause code may have
Invalid operator + and - operators cannot be mixed with Fix the syntax error. The
ASBN-040 combination * and / operators. cause code may have
Too many AND/OR A maximum of 4 AND/OR operators can Fix the syntax error. The
ASBN-041 operator be used per line. cause code may have
Too many arithmethic A maximum of 5 +,- or *,/ operations Fix the syntax error. The
ASBN-042 operator can be used per line. cause code may have
ASBN-046 Expecting a unit A unit declaration is required. cause code may have
String argument too Fix the syntax error. The
ASBN-047 long The string specified is too long. cause code may have
Auto AI/O setup is Auto AI/O setup for the mounted I/O Verify mounted I/O
ASBN-048 unsupported module is not supported. So module and set system
Process %d switch to The weld power supply
ASBN-049 %d failed ArcTool failed to switch weld processes. may be OFF,
Invalid name in /PROG The program name does not match the
ASBN-050 sectionsubtype /PROG filename or has invalid characters.
Invalid Fix the syntax error.
ASBN-051 section TP subtypeparameter
The indicated specified is out
not of
valid. Fix theasyntax
Enter number error.
within
ASBN-052 Bad %s %s Prc %d range. range.
No ramp at process Ramping is not allowed when switching Complete the process
ASBN-053 switch (%s^4,%d^5) weld processes. switch first, then ramp
No motion while arc Motion has stopped longer than the If no motion is needed
ASBN-054 welding time specified in weld schedulle and during welding, increase
No sync Eq An Arc Start instruction specifies Determine why the sync
ASBN-055 (%s^4,%d^5) synchronizing with an Equipment that Equipment is not starting
Invalid sync An Arc Start instruction specifies Edit the synchronization
ASBN-056 (%s^4,%d^5) synchronizing with an Equipment that data.
Arc process ramping cannot execute
because the delay (t1) to communicate Increase
Cannot ramp t1=%d > with the welder is larger than the $aweramp[eq].$time_fact
ASBN-057 t2=%dstick is still
Wire ramping
A loop
wire stick is time (t2). Thisafter
still detected may aoccur Secure
or by 1.the robot and
ASBN-058 detected system RESET. equipment. Cut the wire.
The gas purge operation by the teach Allow the gas purge to
pendant key was stopped by either complete before doing
ASBN-059 Gas purge stopped disabling the teach pendant, running a any of the actions listed to
The program header is invalid or Repair or provide a valid
ASBN-060 WARN Invalid attribute syntax missing /ATTR section. Print a
ASBN-061 No /ATTR section in file The /ATTR section is required. Fix the syntax error.
Invalid application The /APPL section has a general syntax Fix the syntax error. The
ASBN-070 syntax error. cause code may have
The /APPL section is required for this Fix the syntax error. The
ASBN-073 No /APPL section in file program but none was found. cause code may have
Duplicated Position A position register has been defined Make sure that each entry
ASBN-080 WARN data twice. in the /POS section has a
P[(number)] is referenced somewhere Define P[(number)] in
ASBN-081 WARN Unused Position data but is not defined in the /POS section. /POS section.
Syntax error in position The position data is not correctly Fix the syntax error. The
ASBN-082 data formated. cause code may have
Invalid data in /POS The data in the /POS section is not in Fix the syntax error. The
ASBN-083 section the correct format. cause code may have
The joint units in the file do not match Fix the syntax error. The
ASBN-084 Mismatch unit of joint the units for one or more joints of the cause code may have
Mismatch number of Number of joints specified in the Fix the syntax error. The
ASBN-085 joint position do not match the robot cause code may have
Invalid of binary data in The binary
ASBN-086 conversion factor data($AWEPRR.$io_min/max_bin) is Please set correct value.
The conversion factor data is invalid. It
Invalid conversion must be filled more than 2 tables at Please set conversion
ASBN-087 factor data least. But the value of the second table factor more than 2 tables
Over selected AO factor The selected number of AO conversion Please select the correct
ASBN-088 No. factor data is over the number of the number of AO conversion
ASBN-090 Undefined macro The macro is not defined. cause code may have
The instruction is not defined. Either Fix the syntax error. The
ASBN-092 Undefined instruction the instruction is invalid or not used cause code may have
Expecting integer or A direct or indirect index is expected. Fix the syntax error. The
ASBN-093 Register An integer constant or register type is cause code may have
Load or enable the
relevant feature. Delete
Instruction not Instruction is not supported on this the instruction if
ASBN-095 WARN supported robot as configured. unnecessary. Modify the
An error occured that was not Fix the syntax error. The
ASBN-097 Internal error anticipated. cause code may have
ASBN-098 Invalid encoding of line There is a syntax error within the line. cause code may have
The message is posted at the timing of
Some Bead Exceeds program abort after ARC-095 is posted Please perform the
ASBN-099 STOP Limit EQ%d during welding. This prevents the remedy of ARC-095.
Invalid data in robot Fix the syntax error. The
ASBN-100 configuration
Could not open file, rerun Data
robot Robotinconfiguration
robot configuration is invalid.
file could not because
Confirmcode may have
robot
ASBN-107 configuration file opened. configuration file.
Wire touching before Wire touching before Touch Retract Check the wire touches to
ASBN-108 TRS seq Start sequence starts. the work at the arc start
Feedback voltage fell down to Remove the cause of
displayed value over Arc Loss Error lower voltage. If the weld
Time. Therefore, robot judges that arc has no problem, the
ASBN-109 Arc Lost: Voltage < %d V is lost. voltage threshold for arc
ASBN-110 CS without CD CS is only valid with CD or CNT100 cause code may have
ServoTorch I/O assignment is invalid. Please confirm the
Assignment of SVT I/O This assignment is automatically assignment of signals for
ASBN-111 invalid executed after cycle power. arc welding.If you find a
AutoZone Mastering This is a warning message, Interference This is a warning message,
ASBN-115 may be needed Avoidance AutoZone mastering may be Interference Avoidance
Undefined pallet Fix the syntax error. The
ASBN-120 number Pallet number is invalid. cause code may have
ASBN-121 Wrong route position Route position is wrong. cause code may have
Duplicated Palletizing Fix the syntax error. The
ASBN-122 data Palletizing data is duplicated. cause code may have
ASBN-123 Duplicated pattern Palletizing pattern is duplicated. cause code may have
Undefined pattern Fix the syntax error. The
ASBN-124 number Pattern number is invalid. cause code may have
Wrong route position Fix the syntax error. The
ASBN-125 type Route position is wrong. cause code may have
Wrong route position Fix the syntax error. The
ASBN-126 number Route position number is wrong. cause code may have
Wrong bottom position Fix the syntax error. The
ASBN-127 count Bottom position count is wrong. cause code may have
Pallet register already Fix the syntax error. The
ASBN-128 used Pallet register is already used. cause code may have
ASBN-129 Expecting 'WID' 'WID' is expected. cause code may have
ASBN-130 Invalid Backup option Stroke condition is invalid. cause code may have
ASBN-131 Invalid Pressure option Pressure condition is invalid. cause code may have
Invalid Equipment Fix the syntax error. The
ASBN-133 number Equipment number is invalid. cause code may have
ASBN-135 Expecting 'BU' ‘BU’ is expected. cause code may have
ASBN-136 Expecting 'P' ‘P’ is expected. cause code may have
ASBN-137 Expecting 'S' ‘S’ is expected. cause code may have
SpotTool not Fix the syntax error. The
ASBN-142 configured SpotTool is not cofigured. cause code may have
ASBN-144 Expecting WC ‘WC’ is expected. cause code may have
Expecting OPEN, CLOSE, Fix the syntax error. The
ASBN-145 or * ‘OPEN’, ‘CLOSE’ or ‘*’ is expected. cause code may have
Expecting OPEN or Fix the syntax error. The
ASBN-146 CLOSE ‘OPEN’ or ‘CLOSE’ is expected. cause code may have
ASBN-147 Expecting SV ‘SV’ is expected. cause code may have
ASBN-148 Expecting SN 'SN’ is expected. cause code may have
ASBN-149 Invalid number Number is invalid. cause code may have
Invalid Equalization Fix the syntax error. The
ASBN-150 Pressure Equalization Pressure is invalid. cause code may have
ASBN-152 Expecting 'EP' 'EP’ is expected. cause code may have
ASBN-154 Expecting unit Unit is expected. cause code may have
ASBN-155 Expecting 'ED' 'ED’ is expected. cause code may have
ASBN-156 Expecting 'SD' ‘SD’ is expected. cause code may have
Invalid distance Fix the syntax error. The
ASBN-157 schedule Tip distance schedule is invalid. cause code may have
ASBN-158 Expecting 'SEL' SEL’ is expected. cause code may have
ASBN-159 Expecting ’t’ ‘t’ is expected. cause code may have
ASBN-163 Start signal
Power error(E:%d)
source start signal
Detect 3-phase abnormal.
power source start signal.
Check 3-phase power
ASBN-164 error(E:%d) abnormal. source.
ASBN-165 EQ is detached(E:%d) RoboWeld is detached. Confirm port setup.
Comm. stopped in Communication with RoboWeld power Confirm another error
ASBN-166 weld(E:%d)
I/O asginment source
I/O spacestopped in welding.
for RoboWeld is already in message and port,
Confirm another cable
I/O
ASBN-167 overlap(%d)(E:%d) use. device and
Confirm $IO_START
another I/O in
ASBN-168 I/O error(%d)(%d, E:%d) I/O initialization
Detect error.
invalid wire FWD/BWD device and
Confirm $IO_START
wire control in
ASBN-169 Invalid
Warning,wire op.(E:%d) operation.
Receive invalid command from power sequence.
Confirm noise
ASBN-172 Rcv(0x%X)(E:%d)
Warning, source.
Retry to send the command to power environment,
Confirm noise cable
ASBN-173 Retry(0x%X)(E:%d)
Warning, NAK source. environment,
Confirm noise cable
ASBN-174 for(0x%X)(E:%d)
Signal change is Receive NAK from
Communication power
with powersource.
source is environment,
Confirm welding cable
setup,
ASBN-175 ignored(E:%d)
No sysvar $RBWLD for stopped.
Sysvar $RBWLD is not setup for new EQ cable connection,
Confirm $RBWLD and then
ASBN-176 E:%d
RoboWeld(E:%d) reset number. $RBWLD_CFG
Arc setup.
welding is now
ASBN-177 complete RoboWeld reset sequence is complete. available.
1.If this alarm occurred
This alarm is occurred when with ARC-143, please
communication between the welding perform the remedy for
Power supply com equipment control board and the robot ARC-143. 2.If this alarm is
ASBN-179 alarm(E:%d) controller stops. still occurred after
ASBN-191 Memory alarm(E:%d) Power supply control memory error try again. If the same
ASBN-192 CPU alarm(E:%d) Weld power supply CPU error try again. If the same
- By turning off Torch
Torch switch was turned ON but the arc switch, the alarm will be
ASBN-193 Arc start alarm(E:%d) could not started within 4sec. disappeared. - Confirm
Tool frame number The tool frame number in /MN is Use the same tool frame
ASBN-195 mismatch different from that in /POS. number in both /MN and
Same position ID has been used twice Make sure that each entry
ASBN-196 Duplicated
Too Position ID
many Positions in /MN.
are More than 9999 positions are taught in in the /MN
Reduce the section
numberhas of a
ASBN-197 teached
Too many I/Os are the program.
More than 64 I/Os are specified in one teach positions
Reduce in theI/Os
the specified
ASBN-198 specified
This weld EQ isn't line.connected weld equipment is not
The in the line.
Check the weld
ASBN-199 supported(E:%d) supported. equipment.
The Arclink bus master did not respond Check the Arclink
Arclink ch%d heartbeat to a heartbeat request within the connections and the weld
ASBN-200 timeout maximum time period. The channel has controller devices that are
A device on the Arclink did not respond Check the Arclink
Arclink ch%d obj #%d to a request within the maximum time connections and the weld
ASBN-201 no resp period. The channel has been reset. controller devices that are
A device on the Arclink sent and Check the Arclink
Arclink ch%d obj #%d unexpected error response to a request connections and the weld
ASBN-202 error resp message. The channel has been reset. controller devices that are
The Arclink bus master has detected an If this is unexpected, then
error or other condition that requires check the connections
Arclink ch%d reset by the Arclink network to be reset. This and other devices on the
ASBN-203 master may be a normal event if a new device Arclink network.
The Arclink reset and initialization The Arclink network is
ASBN-204 Arclink ch%d available sequence is complete. ready for welding.
The high speed event message The Arclink network is
Arclink ch%d h/s event expected during welding failed to arrive automatically reset. If this
ASBN-205 lost in time. error persists, it indicates
The Arclink interface detected too
Arclink ch%d too many many errors on the CANbus network. Check Arclink network
ASBN-206 errors This is usually caused by noise or bad connections and shielding.
The Arclink interface detected too
Arclink ch%d no bus many errors on the CANbus network. Check Arclink network
ASBN-207 power This is usually caused by noise or bad connections and shielding.
The Arclink interface is not detecting Check the Arclink cable
Arclink ch%d no nodes any other devices on the CANbus connections and make
ASBN-208 on bus network. sure that the welding
The Arclink interface is detecting a high Check the Arclink cable
number of errors on the network. This connections and noise
ASBN-209 Arclink ch%d bus errors is not fatal right now, but indicates sources.
Arclink ch%d network The Arclink interface is unable to send Cycle power on the robot
ASBN-210 flooded messages due to too much traffic on controller and weld
Arclink ch%d comm The Arclink interface has detected a If this problem persists,
ASBN-211 error %d fatal error condition and has reset the contact tech support.
A CANbus card has been detected for Assign the Ethernet
Arclink ch%d CAN-Enet an Arclink communications channel connection to a different
ASBN-212 conflict that has already been assigned as an channel to make this
Check Arclink I/O
assignment on DI/DO
%s: Invalid Arclink I/O assignment screen or
ASBN-213 EQ%d The assignment of Arclink I/O is wrong. AI/AO assignment screen.
After the weld ended the process active Increase the process
Process active ON after input remained ON longer than the active timeout on the
ASBN-250 weld specified maximum time. robot
After the weld ended the arc detect Increase the process
Arc detect ON after input remained ON longer than the active timeout on the
ASBN-251 weld specified maximum time. robot
The argjment for Adjust Start Height Use integer value for
ASBN-300 Argument is not integer macro is not integer. Adjust Start Height macro.
The specified equipment number for Specify the existed
ASBN-301 Invalid EQ number Arc Start Height Adjust is invalid. equipment number by
Invalid robot group The specified robot group number for Specify the proper robot
ASBN-302 number Arc Start Height Adjust is invalid. group number in Arc Start
The specified I/O assignment for Arc Specify the proper I/O
ASBN-303 Invalid I/O assignment Start Height Adjust is invalid. assignment in Arc Start
In Arc Start Height Adjust function, You Use different PR number
Cannot use same PR cannot use same PR number for both for Touch Command
ASBN-304 number Touch Command Signal and Touch Signal and Touch Detect
Other task adjusts Other task has already start Arc Start Do not perform Arc Start
ASBN-305 height Height Adjust for the specified Height Adjust for one
Arc Start Height Adjust is ignored Release Single Step or Dry
because of Single Step, Dry Run. Or Run or set Weld Enabled
because of Weld Disabled when to perform Arc Start
Start Height Adjust is $AWSTHOF.$CHK_WLD_ENB is TRUE. If Height Adjust. If you are
ASBN-306 ignored Lincoln welder is used, ArcLink may be using Lincoln welder,
Perform Arc Start Height
Adjust at the position
Contact has already detected before which the torch never
search is started for Arc Start Height touch the work. If you
ASBN-307 Contact before search Adjust function. want to continue Arc Start
Contact is not detected during the Perform search motion
ASBN-308 Contact is not detected search motion for Arc Start Height from closer position
Confirm that the settings
for Arc Start Height Adjust
Start Height Adjust Arc Start Height Adjust is failed by is proper. If other alarm is
ASBN-309 failed some reason. posted at the same time,
If Arc Start Height Adjust
Too long adjust motion The motion for Arc Start Height Adjust is performed with very
ASBN-310 time function is too long. low override, the alarm
Attach group global variables are not Perform a Controlled start
ATGP-001 WARN No global variables loaded. and initialize motion
No joint motion allowed with an attach Change motype to Linear
ATGP-002 STOP Joint motion not allow group option. or Circular before
Wrist Joint motion not No wrist joint motion allowed with the Remove the wrist joint
ATGP-003 STOP allow attach group option. instruction
Set before
the current uframe
ATGP-004 STOP UFRAME must be zero Uframe number is not set to zero. number to zero.
Calibration internal AutoZone internal error. Cause: Power off to recover. If
ATZN-001 error. AutoZone internal error. problem persistes, please
Name not found in HDR Name not found in HDR Table Cause: Internal error. Please call
ATZN-002 Table Program name not found in AutoZone customer service.
Name not found in PRG Name not found in PRG Table Cause: Internal error. Please call
Name not found in REC Name not found in REC Table Cause: Internal error. Please call
Name not found in REQ Name not found in REQ Table Cause: Internal error. Please call
AZ HDR Table is full Cause: Internal Internal error. Please call
ATZN-006 AZ HDR Table is full AutoZone header table is full. customer service.
AZ PRG Table is full Cause: Internal Internal error. Please call
ATZN-007 AZ PRG Table is full AutoZone program table is full. customer service.
AZ REC Table is full Cause: Internal Internal error. Please call
ATZN-008 AZ REC Table is full AutoZone recording table is full. customer service.
AZ REQ Table is full Cause: Internal Internal error. Please call
ATZN-009 AZ REQ Table is full AutoZone request table is full. customer service.
Check master flag in both
Master flags not in sync Cause: Master main and sub program
flags in main and sub program header header, ensure that
ATZN-010 Master flags not in sync are not synchronized. master flags are
% start mastering Cause: Program start This is a warning message
ATZN-011 %s start mastering mastering process. to indicate that mastering
% end mastering Cause: Program end This is a warning message
ATZN-012 %s end mastering mastering process. to indicate that mastering
Not calibrated w.r.t. Not calibrated w.r.t. ZMGR Cause: Calibrate the robot w.r.t.
ATZN-013 ZMGR Robot is not calibrated w.r.t. zone zone manager in
G:%d AZ Jog close to G:%d AZ Jog close to target Cause: This alarm will stop the
ATZN-014 target Robot is close to target during Jogging. Jogging motion.
Resend G:%d AZ Jog request Cause: This is a warning message
Resend G:%d AZ Jog AutoZone jog request has not received to indicate that the
ATZN-015 request a response for a period of time. AutoZone jog request will
Prg needs re-master(mdf tim) Cause: Re-master the program
Prg needs re- Program modification time retrieved is will synchronize the
ATZN-016 master(mdf tim) different between program mastering program modification
%s Append Mode enabled Cause: This is a warning message
%s Append Mode Append mode has been enabled. The to indicate that the
ATZN-017 enabled new mastering data file will be merged append mode is enabled
Space setup not Space setup not initialized Cause: Space Configure the space and
ATZN-018 initialized has not been configured and enabled in enable it in AutoZone
No AutoZone CD No AutoZone CD Jogging Cause: Disable AutoZone jogging
ATZN-019 Jogging AutoZone does not support from AutoZone test-run
Constant Path not Constant Path not enabled Cause: Enable Constant Path and
ATZN-020 enabled Constant Path is not enabled. Cold Start to take effect.
Re-teach TP programs to
Exceed max DP comb Exceed maximum Deadlock Prevention reduce number of
ATZN-021 zone(%d) zone per DP combination analysis. Deadlock Prevention
Re-teach TP programs to
Exceed max DP total Exceed maximum Deadlock Prevention reduce number of
ATZN-022 zone(%d) total zones. Deadlock Prevention
Minimum 2 prog for DP Minimum of 2 TP programs required Modify setup of Deadlock
ATZN-023 analysismax DP total
Exceed for Deadlock
Exceed Prevention
maximum analysis.
Deadlock Prevention Prevention
Internal schedule.
error. Please call
ATZN-024 space(%d) total spaces. customer service.
Complete the Deadlock
Program space data is not available for Prevention analysis prior
ATZN-025 No %s space data the request. to program space data
Overlap space data is not available for Prevention analysis prior
ATZN-026 No overlap space data the request. to overlap space data
Robot space data is not available for Prevention analysis prior
ATZN-027 No robot space data the request.
Invalid Voxel Id during individual voxel to robot error.
Internal space Please
data call
ATZN-028 Invalid Voxel Id query. customer service.
Duplicated host name and program Use a unique host name
ATZN-029 Dup prg %s schd %d name in specified Deadlock Prevnetion and program name in
Same motion group
Same motion group number found in number can not be shared
ATZN-030 Same grp in %s %s specified TP programs. by two TP programs with
The first motion point of the TP Re-teach the TP program,
program is inside the Deadlock enable the Deadlock
ATZN-031 %s first pt in DP zone Prevention zone. Prevention analysis, and
The last motion point of the TP Re-teach the TP program,
program is inside the Deadlock enable the Deadlock
ATZN-032 %s last pt in DP zone Prevention zone. Prevention analysis, and
The hostname and the group number is Configure the hostname
ATZN-033 %s %d not in MASH not found in MASH main setup menu. and the corresponding
There are no application process Manually insert Bump
instructions in the program. Automatic schedule Line numbers in
BBOX-020 No %ss in the program detection of Bump schedule Lines the schedule.
1. Select a Bump
Cannot bump from TP schedule, go to the
BBOX-021 when I/O enabled TP is enabled when Bump DI is input. DETAIL screen, scroll to
Bump Group input value is out of Change the value of the
BBOX-022 Invalid bump schedule range. Group input to select a
Invalid Bump Group Bump schedule Group input is not Configure the Bump
BBOX-023 Input Bump Digital
Invalid configured
Bump correctly.
inputs are not configured Schedule Group
Configure input to
the Bump
BBOX-024 Inputs correctly. inputto valid digital
Invalid acknowledge Bump Acknowledge offset output is not Configure the Bump
BBOX-025 output DO configured correctly. Acknowledge offset
Bump Limit error output is not Configure the Bump Error
BBOX-026 Invalid error output DO Bump
configured correctly.
schedule Lines in the are not output
Set validtoLine
a valid digitalin
numbers
BBOX-027 Invalid line numbers correct. the Bump schedule.
1. Review part placement
BBOX-028 Bump2 limit
First exceeded
positions are too Bump offset limit has been reached. or Reteach
1. part specification.
one or more 2. of
BBOX-029 close Two sequential
Bump schedule points arename
Program too close.
does the positions.
Use a correct Porgram
BBOX-030 Program does not exist not exist. name in the Bump
Need 2 positions to The Bump schedule Program has only 1 1. This program cannot
BBOX-031 determine offsets point. use Bumpbox. 2. Add
Program is write Bump schedule Program has the write Edit the Bump schedule
BBOX-032 protected protect attribute ON. Program header to disable
Bump schedule is The selected Bump schedule has no 1. Use a valid Bump
BBOX-033 uninitialized Program name assigned. schedule. 2. Insert a
The Bump schedule Group number is Set the Bump schedule
BBOX-034 Invalid group number not correct. Group number to a valid
The Bump schedule Group number is Change the Bump
BBOX-035 Group is not a robot not a Robot group. schedule Group number
Group is not in group The Bump schedule Group number Set the Bump schedule
BBOX-036 mask
Cannot bump COORD does not exist
The Bump in theProgeam
schedule Bump program.
has Group
Remove number to a valid
the coordinated
BBOX-037 motion coordinated motion. motion.
1. Define a CD_PAIR that
There is no CD_PAIR that matches the includes the leader and
BBOX-038 CD leader not found Bump Program group mask. follower in the program.
CD leader and follower The leader group and the follower are Bump operation is not
BBOX-039 are robots robots. permitted for robot to
CD leader grp change in The leader group in a coordinated Change the Bump
BBOX-040 bump program
BBOX path did not motion program is changed. schedulethe
Contact lines to exclude
FANUC
BBOX-041 load start line is circle
Bump A program
Bump lines file is missing
do not Support
include circle START Set hotline 'Lines' to
the schedule
BBOX-042 VIA point include the START point
CD unit vector CD and NON-CD positions are used to Edit program so the first 2
BBOX-043 calculation failed calculate unit vector positions are both CD or
Program position Train the position, or
BBOX-044 number UNINIT
Preview operation Position number value is uninitialized See insert a number
cause alarm value in
for more
BBOX-045 failed The prescan operation failed information
Position regester will Replace position register
BBOX-046 not be
Too bumped
many positions in Position
Bump regesterinwill
positions thisnot be bumped
schedule with position
exceed Reduce the Line if this point
BBOX-047 Bump Lines
COORD[ldr] value is not maximum.
The group in COORD[ldr] or parameter to
Change the value include
to a
BBOX-048 correct. COORD[R[#] is not correct. valid coordinated leader
The TCP Mate motion was aborted
Alarm Code Cal Mate because of an unexpected change of
CALM-000 WARN motion aborted. menu, or it was aborted by the user. Start the motion again.
Turn off the controller
A Form Operation Error occurred and turn it on again. If the
CALM-001 WARN Form Operation Error. because the dictionary was not found. Use errorthe
stillSETUP
exists,menu to
CALM-002 WARN Fail
System is not
to run initalized.
CalMate system
The TCP Mateis not fully cannot
motion initalized.
be set upall
Clear allthe
required
errors before
CALM-003 WARN Motion started. running TCP Mate motion.
Please record all Not all positions in the reference menu Verify that all the
CALM-004 WARN position are recorded. positions in the menu
Do reference motion TCPMate cannot be executed without Display the reference
CALM-005 WARN first. mastering the TCP first. menu, and press MASTER
Record positions in the
CALM-006 WARN Point is not initialized. The position is not initialized. reference menu first.
The position cannot be recorded since Calibrate the robot. Then,
CALM-007 WARN Robot is not calibrated. the robot is not calibrated. try the operation again.
Record home position The home position must be recorded Record the home position.
CALM-008 WARN first before recording other positions. Then, try the operation
Keep same WPR as These positions require to have the Keep the same orientation
CALM-009 WARN home pos. same WPR as the home position. (WPR) when recording
CALM-010 WARN Please press SHIFT key. SHIFT key was
The destination not pressed.
position is not Press the aSHIFT
Re-teach new key.
starting
CALM-011 WARN Position is not in range. reachable. position.
The robot cannot compute the circle Check and correct robot's
CALM-012 WARN Singular solution. due to a singularity. mastering, and check the
The robot cannot converage to a Check and correct the
CALM-013 WARN Cannot converge. solution. robot's mastering. Check
The recorded positions are too close to Points should be at least
CALM-014 WARN Points are too close. each other. 10 mm apart. Reteach the
The robot was in contact with the part Reteach the starting
CALM-015 WARN Contact before search. before starting a search motion. position so that the robot
No contact was made during the Make sure the sensor and
CALM-016 WARN No contact detected. TCPMate motion. software are installed
Undefined program The enter/exit program names are not Display the SETUP menu
CALM-017 WARN name. defined. to select teach pendant
An internal teach pendant program and turn it on again. If the
CALM-018 WARN TPE operation error. errorcircle
The has occurred.
fitting error is greater than error still
Check exists,
hareware/tooling
CALM-019 WARN Circle Fitting error: %s. expected. or increase the fit
The search motion can not be executed Display the SETUP menu
CALM-020 WARN No DIN support.
Cannot continue withtout
The robotTOS sensor.
cannot continue the paused and select
Abort TOS in the
the paused motion
CALM-021 WARN motion. motion. and re-run TCPMate
and turn it on again. If the
CALM-022 WARN Cal Mate internal error. A CalMate internal error has occurred. error still exists,
Dictionary is not and turn it on again. If the
CALM-023 WARN loaded.
No saved reference Thesaved
No dictionary file isdata
reference not loaded.
exists for the error
Set still
the exists, motion
reference
CALM-024 WARN data. current tool. for thethe
Check current
path tool.
and file
CALM-025 WARN File open error: %s The output file cannot be opened. name of the output file.
CALM-026 WARN No recorded Utool. No recorded utool exists to save. Record a new utool.
Display the TCPMATE
The teach pendant program does not main menu. TCPMate will
have enough stack size to run TCPMate update your teach
CALM-027 ABORT Not
Cannot compute new automatically.
enough TPE stack. TCPMate cannot complete its operation pendant
Check forprogram
a severelystack
bent
CALM-028 ABORT TCP. successfully. tool, or for loose
Please record all Not all positions in the SETUP menu are All positions in the menu
CALM-029 WARN position recorded. must be recorded. Check
The center position is not within Re-teach a new center
CALM-030 WARN Position is not in range. CalMate joint limits. position with all joints
The new tcp mode has not been Set the adjust mode to
CALM-031 WARN Run newpoint
Surface tcp mode
not first. performed. the new
Check fortcp and run bent
a severely it
CALM-032 ABORT measured No Z points were measured. tool orfor
Check loose hardware.
a severely loose
CALM-033 ABORT Large fit error. The Fit error is greater than expected. tool or for loose
The number of positions measured is Record positions away
CALM-034 ABORT Insufficient
Search points.
distance <= less than
The moverequired.
distance is set to less than 10 from joint
Enter limits
a value and than
greater
CALM-035 ABORT 10mm mm. 10mm for the move
Invalid data restore Move the cursor to a valid
CALM-036 ABORT index There is no data to restore. data line, and press the F3
Orientation not The orientation point was not Check and repair any
CALM-037 WARN calculated
Invalid measured correctly and orientation will loose server
Calmate resettools or loose
CALM-038 WARN $MNUTOOLNUM. $MNUTOOLNUM is invalid. $MNUTOOLNUM=1. 3.2.2
Coordinated Motion global variables Perform a controlled start
CD-001 WARN No global
Unable to variables
allocate are
A not loaded.
failure occurred while allocating and initialize
Check amountmotion
of memory
CD-002 WARN memory memory. being used by the system.
PAUSE. Follower recv invalid Leader segment MMR number does not
CD-003 G segment match that of the follower Call FANUC Robotics.
PAUSE. Illegal leader INTR point
Illegal Leader Interpolated Point Data is
CD-004 G data detected when trying to convert it to a Call FANUC Robotics.
PAUSE. Non-coordinated group Coordinated Motion is used for a group Check motion statement.
CD-005 G detected which has not been SETUP for Perform Coordinated
PAUSE. Illegal follower joint JOINT MOTYPE was used for a follower Use LINEAR or CIRCULAR
CD-006 G
PAUSE. motion motype not
Circular during coordinated
CIRCULAR motion.
MOTYPE Not Implemented MOTYPE
Use instead
LINEAR MOTYPE
CD-007 G supported Yet instead
PAUSE. There is no leader in the coordinated Check motion statement.
CD-008 G No leader motion Perform Coordinated
PAUSE. There is more than one leader in the Check motion statement.
CD-009 G
PAUSE. More than one leader
Invalid angle in point coordinated motion Perform Coordinated
Internal Error, call FANUC
CD-010 G
PAUSE. data in flushing CD
Error Invalid Angle detected in Point Data Robotics.
CD-011 G mailbox Error in reporting mailbox status COLD START.
PAUSE. Leader single group motion after Issue non-coordinated
CD-012 G Illegal leader motion coordinated motion not allowed motion involving the
Jog group is not a Attempt to perform coordinated jog Select leader group for
CD-013 WARN leader with a non-leader group coordinated jog
Jog group has multi Attempt to perform coordinated jog Select only one
CD-014 WARN follower with a leader group which has multiple leader/follower pair
PAUSE. Wrist joint is not WRIST JOINT Motion is not supported Delete Wjnt motion
CD-015 G supported with coordinated motion instruction
PAUSE. INC motion is not INCREMENTAL motion is not supported
CD-016 G supported with coordinated motion Delete INC instruction
PAUSE. INDEP motn is not Independent motion is not supported Change Independent
CD-017 G supported with coordinated motion motion to Simultaneous
PAUSE. Calibration for coordinated motion is Execute calibration of
CD-018 G No calibration for CD not done coordinated motion in
PAUSE. Number of follower is zero or two or Set number of follower
CD-019 G Illegal follower setting greater on this motion correctly or set group
Not reach relative Follower can not reach relative speed Teach follower and leader
CD-020 WARN speed in program position again to reach
PAUSE. No kinematics in CD Attempt to perform coordinated Initialize robot library
CD-021 G group motion with non-kinematics robot correctly
PAUSE. Prev term type is not Term type before coordinated motion Change term type before
CD-022 G FINE is not Fine or CNT0 coordinated motion to
PAUSE. Setting of coordinated motion is not Check setting of
CD-023 G Illegal CD setting correct coordinated motion in
Calibration was Teaching points is incorrect or Leader's Check the mechanics and
CD-024 WARN inaccurate
PAUSE. mechanics is inaccurate reteach the points
CD-025 G Can't
PAUSE. Illegalconvert position System can't convert
Illegal transition positionor
(nonCD->CD properly
CD- Call
Add FANUC Robotics.
or remove motion
CD-026 G transition:nonCD<->CD >nonCD) happens. option COORD.
PAUSE. Illegal follower Transition from one CD pair to another Insert non coordinated
CD-027 G
PAUSE. transition happens.
Speed of TCPBut or
same follower
Face group is T1
Plate exceeded motion between
Specify slower speed or
CD-028 G T1 speed limit(G:%d^2) speed limit. change to AUTO mode.
Cannot switch leader group while in Use the same leader
CD-029 Illegal to switch leader coordinated motion. group number. Change
CD_XF update fail. G%d Cannot update CD_XF while robot is Let robot comes to stop
CD-034 moving moving first before trying to
CD Pair %d Copy %d is Not a problem. Information only. Not a problem.
CD-035 used%d Copy %d is
Pair CD_PAIR CD_XF is dynamically updated Information only.
CD-036 invalid Invalid copy number. Use valid copy number.
CD-037 CD_XF is invalid CD_XF copy is invalid. Use valid copy of CD_XF.
coordinated
CD-038 is invalid
CD PAIR %d Copy %d Coordinated
CD_XF pair isminvalid.
of CD PAIR Copy n successfully pair.
Not a problem.
CD-039 updated updated
The leader position type is not a legal Information onlyerror.
Internal system
CD-040 Illegal Leader pos type type Notify FANUC.
Check the device and path
The specified directory can not be that you entered. If none
CMND-001 WARN Directory not found found. entered, check the system
Check to make sure the
file has been spelled
CMND-002 WARN File not found specified
The file fileexists
already couldand
notcould
be found.
not be correctly
Make sureand
thethat it exists.
overwrite
CMND-003 WARN File already exists overwritten. option has been specified.
Change the name of the
CMND-006 WARN Self copy not allowed A file cannot be copied to itself. destination file so it is
Source type code is The source variable was not a position The valid postion types
CMND-010 WARN invalid type when converting between a are POSITION, JOINTPOS,
Destination type code is The destination variable was not a The valid postion types
CMND-011 WARN invalid position type when converting between are POSITION, JOINTPOS,
Type codes do not The requested type code doesn't match Internal error. Insure that
CMND-012 WARN match the passed variable type. the type code matches
Representation An attempt was made to compare two Both positions must be
CMND-013 WARN mismatch positions that are not the same type. the same type. Convert
The two positions were
Positions are not the Two positions were compared and not equal within the
CMND-014 WARN same found not to be equal. specified tolerance. This
Both arguments to ATAN2 were zero or If calling ATAN2, insure
Both arguments are an internal error occurred when that both arguments are
CMND-015 WARN zero attempting to convert a POSITION to not zero. If converting a
This is an internal error.
CMND-016 WARN Division by zero An attempt was made to divide by zero. Insure that the divisor is
Make sure that the
CMND-017 WARN Angle is out of range The rotational angle is to great. rotational angle is no
An invalid device or path has been that you entered. If none
CMND-018 WARN Invalid device or path specified. entered, check the system
The operation was cancelled because
CMND-019 WARN Operation cancelled CTRL-C or CTRL-Y was pressed. Repeat the operation.
This is a notification. You
CMND-020 WARN End of directory The directory listing is finished. do not have to do
The destination file name contained Use only alphanumeric
CMND-021 WARN Cannot rename file both alphanumeric characters and the characters or a single
PAUSE. Time motion with dist A time-based motion was specified Do not use these options
CMND-022 G before along with distance before. in combination.
No destination device No device or path has been specified that was provided. If
CMND-023 WARN or path for the destination. none, provide a
The indicated system variable has Change the system
CMND-024 %s invalid entry invalid information. See the cause code variable entry, or provide
%d FILE programs not This system has programs of FILE Please back up these files
CMND-025 saved storage type. FILE programs are not via another mechanism
Continuous Turn global variables are Perform a controlled start
CNTR-001 WARN No global variables not loaded. and initialize motion
Perform a cold start on
CNTR-002 WARN No MIR pointer This is an internal system error. the controller.
CNTR-003 WARN No sysvar pointer This is an internal system error. the controller.
Perform a controlled start
CNTR-004 WARN No cnir pointer This is an internal system error. and initialize the motion
The continuous turn axis that was Check Continuous turn
Wrong CN Axis/N1 or selected is not a valid cont. turn axis, or axis, cn_gear_n1, and
CNTR-005 WARN Unable
N2(G:%d^2)
to Allocate cn_gear_n1
A or cn_gear_n2
failure occured have a zero
while allocating cn_gear_n2
Check amount Select
of memory
CNTR-006 WARN Memory
PAUSE. Serious Internal error memory. being used by the system.
Record error and report
CNTR-007 G (G:%d^2) Internal Continuous Turn error to hotline
Invalid destination angle during linear Check compatibility of
PAUSE. Invalid dest. angle, motion. Incompatibility with motion options. Remove
CNTR-008 G (G:%d^2) Continuous Turn and other options. other options.
Warn-Cont Vel too Continuous turn axis velocity is too Lower contaxisvel. This
CNTR-009 WARN high(G:%d^2) high. cn_turn_no will not be valid warning may be ignored if
PAUSE. Ind.EV option not Continuous turn is not compatible with Remove Ind.EV option or
CNTR-010 G allowed. independent extended axes The Ind.EV disable continuous turn
Programmed motion exceeds the speed Lower the speed either
PAUSE. Axis speed exceeds limits on the continuous turn axis. through KAREL or Teach
CNTR-011 G lim(G:%d^2) Speed limit is 180 degrees per ITP time Pendant
Continuous Rotation must
PAUSE. Ending Cont Rot on Rel Attempted to end Continuous Rotation be ended with an
CNTR-012 G
SYSTE Motion with a Relative Motion absolution motion Use an
COMP-000 M
PAUSE. Unknown error
COMP-001 G
PAUSE. Retry count over
COMP-002 G
PAUSE. over(Hardware)
Retry count
COMP-003 G
PAUSE. over(Undefind TCC)
COMP-004 G
PAUSE. Retry count over(Parity)
COMP-005 G
PAUSE. over(Interval)
DSR off when
COMP-006 G
PAUSE. transmission
COMP-007 G
PAUSE. Invalid data format
COMP-008 G Response time over
Condition does not Check for condition
COND-001 WARN exist Specified condition does not exist statements to verify if the
Condition handler The specified condition number already This is just a notification,
COND-002 WARN superseded exists in the system, and has been and you do not have to do
Already enabled, no The specified condition is already This is just a notification,
COND-003 WARN change enabled. No change has been made. and you do not have to do
Already disabled, no The specified condition is already This is just a notification,
COND-004 WARN change
No more conditions disabled.
No No change are
more conditions hasdefined
been made.
for the and you do not have to do
COND-005 WARN defined
Task is exiting due to specified task. No action is required.
COND-006 WARN error
COND-007 WARN request
Invalid cond received
type
COND-008 WARN received
Break point
COND-009 WARN encountered Break point has been encountered. No action is required
Specified condition already exists. Either renumber the
Cond exists, not Condition was not superseded. May condition handler or avoid
COND-010 WARN superseded indicate two condition handlers for the re-defining the same
There are too many conditions defined. Reduce the number of
COND-011 WARN Scan time took too long It took too long to scan them all. conditions defined.
COND-100 WARN Class changed
NOPAUSE or NOABORT
COND-101 WARN action
The system was not able to setup the System probably out of
COPT-001 WARN Send_PC error message packet to send to the PC. memory. Cold start.
Add PC Uninit prog or An ADD PC buffer built-in was called All parameters must have
COPT-002 WARN var name with a parameter that is uninitialized. a value when calling the
The variable requested in the ADD Check program and
Add PC Variable not Byname or Send SysVar routines does variable name spellings.
COPT-003 WARN found not exist. Check variable data type.
The variable requested in
the ADD Byname or Send
SysVar routines is of a
Add PC Var type not data type that is not
COPT-004 WARN supported supported. Check variable
An ADD PC buffer built-in
was called with the index
Add PC illegal index into parameter set too big or
COPT-005 WARN buffer too small. Set the index
The data could not be copied to the Make sure the data buffer
Add PC buffer overflow - data buffer because the buffer is too is big enough for your
COPT-006 WARN parm %s small. data. If there is too much
Add PC Un-initialized An ADD PC buffer built-in was called All parameters must have
COPT-007 WARN parameter %s with a parameter that is uninitialized. a value when calling the
A Send PC built-in was
Send_PC Un-initialized called with a parameter
COPT-008 WARN parameter that is uninitialized. All
Send_PC Illegal event An event number less that 0 or greater Use an event number
COPT-009 WARN number
Send_PC Illegal wait than 255 was used. from 0 to 255.
COPT-010 WARN flag
Send_PC Onlymaximum
Buffer too big The wait flags data
of 0 or 1 aresize
buffer allowed. wait flag.
Use a legal data buffer
COPT-011 WARN for packet supported is 244 bytes. size.
A system error occurred when trying to Check other alarms in
COPT-020 WARN Send_PC builtin failed send the data buffer to the PC. alarm log for details.
A Send to PC MACRO was
Send_PC event parm %s called with a parameter
COPT-021 WARN error that is illegal. The
Status message only. A controller task Check PC
COPT-022 WARN Still waiting for %s is waiting for an event flag back from communications.
A controller task waited too long for an Check PC
COPT-023 WARN Abort wait for %s event flag from the PC. The controller communications.
Status message only. A
controller task was
waiting for an event flag
COPT-024 WARN Continuing without %s back from the PC. The PC
Status message only. The PC set the
COPT-025 WARN Received answer for %s event flag and the controller task is N/A
Wait timer cannot be A system timer cannot be created or
COPT-026 WARN set set for this controller task. Cold start
Register operation failed This is just a Check if the register is
COPT-027 WARN Reg %s could not be set debug message defined and if it has the
COPT-028 WARN Register %s not defined
Macro Table too small The MACRO table must have at least 60 Increase the MACRO table
COPT-029 WARN for send option elements for the SEND PC MACRO size.
Check other alarm log
COPT-030 WARN Parameter %s error Send PC Macro data error. errors for more details.
Send Macro - no data to The Send Data PC MACRO was not Check MACRO
COPT-031 WARN send
Send_n_wait - Illegal given any data to send.
The wait action parameter must be 0 parameters.
Check MACRO
COPT-032 WARN action through 3. parameters.
Send_n_wait - Uninit A send PC MACRO was
COPT-033 WARN parm %s called with a parameter
A MACRO was called
without a parameter that
COPT-034 WARN %s missing An error occurred in the TP program. must be entered. Check
COPT-035 WARN Aborting TP program
A MACRO was called with
a parameter that is illegal.
COPT-036 WARN %s Illegal type The parameter has the
The system might have
An internal error occurred in the been corrupted. This
Constant Path PLAN module. This class might have been caused
Internal PLAN error (G: of error should not be encountered by any of a number of
CPMO-001 ABORT %d^2) during normal operation. reasons including:
An internal error occurred in the been corrupted. This
Constant Path INTR module. This class might have been caused
Internal INTR error (G: of error should not be encountered by any of a number of
CPMO-002 ABORT %d^2) during normal operation. reasons including:
been corrupted. This
An internal CP error occurred. This class might have been caused
SERVO Internal CP error (G: of error should not be encountered by any of a number of
CPMO-003 2 %d^2)
Feature not Supported during normal operation. reasons including:
Disable the feature and
CPMO-004 ABORT (G: %d^2) CP does NOT support this feature. try the operation again.
CP ran out of memory during Check the
CPMO-005 Out of memory
Simulated Hold (G: initialization.
A Constant Path (CP) simulated Hold $CP_PARAMGRP
Reset the error andvariables
CPMO-006 %d^2)
Simulated E-Stop (G: has
A occurred.
Constant Path (CP) simulated E-Stop perform
Reset theaerror
Cycleand
Start.
cycle
CPMO-007 %d^2) has occurred. start the controller.
SERVO Cycle power:JBF size (G: The data struture is not large enough Cycle power to increase
CPMO-010 2 %d^2) with either JBF size or Ext JBF size. the size of either jbf_size
An Internal INTR error has occurred. might have been caused
SERVO JBF INTR_T < Ts (G: This class of error should not be by any of a number of
CPMO-011 2 %d^2) encountered during normal operation. reasons including:
SERVO This class of error should not be by any of a number of
CPMO-012 2 JBF Len<0 (G: %d^2) encountered during normal operation. reasons including:
CPMO-013 2 JBF Len=0 (G: %d^2) encountered during normal operation. reasons including:
CPMO-014 2 JBF NULL PTR (G: %d^2) encountered during normal operation. reasons including:
CPMO-015 2 JBF Ts>itp (G: %d^2) encountered during normal operation. reasons including:
CPMO-016 2 JBF Ts != 0 (G: %d^2) encountered during normal operation. reasons including:
SERVO JBF INTR_T != itp (G: This class of error should not be by any of a number of
SERVO JBF nitp_time < 1 (G: This class of error should not be by any of a number of
SERVO JBF INTR_T > itp (G: This class of error should not be by any of a number of
JBF MEMORY ALLOC This class of error should not be by any of a number of
CPMO-020 ABORT ERROR encountered during normal operation. reasons including:
CPMO-021 2 JBF Index < 0 (G: %d^2) encountered during normal operation. reasons including:
Internal INTR error. This class of error might have been caused
SERVO JBF Ptout > Ptin (G: should not be encountered during by any of a number of
CPMO-022 2 %d^2) normal operation. reasons including:
SERVO JBF Ptout != Ptin (G: This class of error should not be by any of a number of
might 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:
- Perform a Cold start. -
Perform an Init start and
set up the robot again -
An Internal INTR error has occurred. Confirm that any options
JBF (Ptin-Ptout)>itp (G: This class of error should not be or additional software not
CPMO-024 %d^2) encountered during normal operation. on the original software
CPMO-025 2 JBF Ts < 0 (G: %d^2) encountered during normal operation. reasons including:
CPMO-026 2 JBF Ts != 0 (G: %d^2) encountered during normal operation. reasons including:
CPMO-027 2 JBF Ts > itp encountered during normal operation. reasons including:
SERVO JBF TS, Ptin & Ptout This class of error should not be by any of a number of
CPMO-028 2 mismatch encountered during normal operation. reasons including:
CPMO-029 2 JBF Index > 1 (G: %d^2) encountered during normal operation. reasons including:
SERVO JBF Ptout > npts (G: This class of error should not be by any of a number of
CPMO-031 2 JBF Len <= 0 (G: %d^2) encountered during normal operation. reasons including:
SERVO JBF Set not empty (G: This class of error should not be by any of a number of
SERVO JBF not empty (G: This class of error should not be by any of a number of
SERVO JBF len mismatch (G: This class of error should not be by any of a number of
SERVO JBF set not main (G: This class of error should not be by any of a number of
SERVO JBF set not valid (G: This class of error should not be by any of a number of
CPMO-037 2 JBF not valid (G: %d^2) encountered during normal operation. reasons including:
Press RESET. If the error
SERVO NonZero JBF Internal INTR error: A empty JBFset has still exists, document the
CPMO-038 2 Remainder(G: %d^2) non-zero remainder events that led to the
SERVO NonZero Chn Internal INTR error: A empty Channel and hold the SHIFT and
CPMO-039 2 Remainder(G: %d^2) has non-zero remainder RESET keys. 3. While still
GTF not empty (G: This class of error should not be by any of a number of
CPMO-040 ABORT %d^2) encountered during normal operation reasons including:
GTF no main filter (G: This class of error should not be by any of a number of
CPMO-041 ABORT %d^2) encountered during normal operation. reasons including:
GTF fout too big (G: This class of error should not be by any of a number of
GTF num_tf != 1 (G: This class of error should not be by any of a number of
Cycle power to
SYSTE Cycle power: GTFsize automatically increase
CPMO-044 M (G: %d^2) An allocated time filter size is too small. time filter size.
The difference between channel Press RESET and try the
Local Hold error (G: previous input and current input is not operation again. If the
CPMO-045 ABORT %d^2) eligible under local hold. problem still persists,
Press RESET and try the
ChnI != ChO + CIF (G: operation again. If the
CPMO-046 ABORT %d^2) Chn Input != Chn Output + CIF problem still persists,
GTF dynamic acc (G: Velocity or acceleration change too Disable
CPMO-047 %d^2) large when dynamic time filter $CPCFG.$COMP_SW2 &
No System Variables (G: This class of error should not be by any of a number of
No Data Structure (G: This class of error should not be by any of a number of
Stack Underflow (G: This class of error should not be by any of a number of
This class of error should not be by any of a number of
CPMO-053 ABORT No Stack (G: %d^2) encountered during normal operation. reasons including:
Stack Overflow (G: This class of error should not be by any of a number of
CPMO-055 ABORT Stack Not Full (G: %d^2) encountered during normal operation. reasons including:
CPMO-056 ABORT Corrupt data (G: %d^2) encountered during normal operation reasons including:
Wrong MT or OT (G: This class of error should not be by any of a number of
Cycle power on the
controller to increase
SYSTE Cycle power: CHNs (G: There are not enough CHANNELs to number of CHANNELs
CPMO-058 M %d^2) continue motion. automatically.
Cycle power on the
SYSTE Cycle power: JBFSETs There are not enough JBFSETs to number of JBFSETs
CPMO-059 M (G: %d^2) continue motion. automatically.
Cycle power on the
SYSTE Cycle power: JBFs (G: There are not enough JBFs to continue number of JBFs
CPMO-060 M %d^2) motion. automatically.
SYSTE Cycle power: TFs (G: There are not enough time filters to Cycle power on the
CPMO-061 M %d^2) continue motion. controller to increase the
Cycle power on the
SYSTE Cycle power: RSINFOs There are not enough RSINFOs to number of RSINFOs
CPMO-062 M (G: %d^2) continue motion. automatically.
SYSTE MAINCHN is NULL (G: and hold the SHIFT and
CPMO-063 M %d^2) Internal Error: Main Channel is NULL RESET keys. 3. While still
Press RESET. If the error is
SYSTE MAINCHN is Unknown Internal Error: Main Channel is neither not cleared, document
CPMO-064 M (G: %d^2) JBF nor JF the events that led to the
MultiGrp RSM STOPPOS Internal Error: At resume stoppos mis- still exists, document the
CPMO-065 ABORT MisSyn synch among groups events that led to the
MultiGrp RsmType Internal Error: resume_type mis-synch still exists, document the
CPMO-066 ABORT MisSyn among groups events that led to the
MultiGrp RsmInfo Internal Error: num of rsinfo still exists, document the
CPMO-067 ABORT Mismatch mismatches among groups events that led to the
Step mode enabled (G: Step mode was enabled after a None. This is normal
CPMO-069 STOP %d^2) constant path hold. The path will vary behavior.
Channel not empty (G: This class of error should not be by any of a number of
Channel not main (G: This class of error should not be by any of a number of
Can't resume same Resume motion cannot continue on a Press RESET and cycle
CPMO-072 ABORT path (G: %d^2) constant path. This error was posted start the controller to
CPMO-073 ABORT path (G: %d^2) constant path. This error was posted start to continue. The
Hold and resume motion cannot occur Use the Jerk Blending
Can't resume blend on a constant path when there is Filter Type for all motion
CPMO-074 WARN path (G: %d^2) blending between different filter types. segments.
CPMO-075 WARN %s This is only a warning. None.
CPMO-076 WARN path (G: %d^2) constant path. This error is posted by start to continue. The
Can't resume same The resume motion cannot continue on the teach pendant, press
CPMO-077 WARN path (G: %d^2) a constant path. and hold the SHIFT and
The system is ready to start next Increase the ITP time if
segment, but none are available. The the processor loading is
path might deviate from the normal high. The alarm can be
path. The segment might be delayed by disabled by setting
CPMO-078 WARN Seg Overrun (G: %d^2) processor loading or by statements $cp_paramgrp[].$warnme
The system is ready to start the next Press RESET and cycle
segment, but planning was cancelled. start the controller to
CPMO-079 WARN Preplan fail (G: %d^2) The path might deviate from the continue. The path might
SERVO EXTChannel not empty This class of error should not be by any of a number of
CPMO-080 2 (G:%d^2) encountered during normal operation. reasons including:
An Internal INTR error. This class of might have been caused
SERVO EXT JBFSet not empty error should not be encountered by any of a number of
CPMO-081 2 (G:%d^2) during normal operation. reasons including:
SERVO EXT JBF not empty This class of error should not be by any of a number of
SERVO EXT JBF len mismatch This class of error should not be by any of a number of
by any of a number of
reasons including:
Incorrect loading and
setup loading
- Perform a Cold start. -
Perform an Init start and
set up the robot again -
An Internal INTR error has occurred. Confirm that any options
EXT JBFSET NULL PTR This class of error should not be or additional software not
CPMO-084 (G:%d^2) encountered during normal operation. on the original software
SERVO EXT JBF NULL PTR This class of error should not be by any of a number of
Cycle power on the
SYSTE Cycle power: EXT JBFs There are not enough EXTJBFs to number of EXT JBFs
CPMO-086 M (G:%d^2) continue motion. automatically.
EXT pt.valid.ext=0 by any of a number of
CPMO-087 ABORT (G:%d^2) Internal error: EXT pt.valid.ext=0 reasons including:
Invalid MainChn ID (G: Internal Error: Main Channel Id is by any of a number of
CPMO-090 ABORT %d^2) invalid. reasons including:
Invalid JBF MainChn ID Internal Error: JBF Main Channel Id is not cleared, document
CPMO-091 ABORT (G: %d) invalid the events that led to the
JF NewLastAng Internal Error: JF new last angles are not cleared, document
CPMO-092 ABORT Mismatch (G: %d^2) incorrect the events that led to the
JB NewLastAng Internal Error: JF filter new last angles still exists, document the
CPMO-093 ABORT Mismatch (G: %d^2) mismatch events that led to the
Invalid JBF New ChnId Internal Error: JBF new main channel id still occurs, document the
CPMO-094 ABORT (G: %d^2) is invalid events that led to the
Increase
$cp_paramgrp[].$jnt_vel_l
im[],
$cp_paramgrp[].$jnt_acc_
Too Large Jnt Cmd The motion command exceeds joint lim[], or
CPMO-095 SERVO (G:%d A:%d) velocity, acceleration, or jerk limits. $cp_paramgrp[].$jnt_jrk_l
Abort the program and try
Error: ChnNewAng (G: the operation again.
CPMO-096 SERVO Forward
%d^2) Resume Offset Thedoes
CP motion
not command is too large.
support forward resume Document
Use the resume
backward events that
CPMO-100 WARN (G: %d^2) offset. offset only.
Rsm Ofst Buffer Limit Could not reach the desired resume Try the following: *
CPMO-101 WARN (G: %d^2) offset because the distance exceeded Reduce resume offset. *
Resume Offset Limit (G: Could not reach desired resume offset - Increase
CPMO-102 %d^2) because the distance exceeded the $CPCFG.$RSM_OFST_ITP. -
Could not reach the desired resume Try the following: *
Resume Offset Gp Limit offset because the offset was limited by Remove the limitation on
CPMO-103 WARN (G: %d^2) another group. the other group. * Reduce
A prior resume offset position was None. This prevents
Resume prior Offset (G: reused because a second hold occurred indefinite resume offsets
CPMO-104 WARN %d^2) before the prior stop position was with repeated
The coordinated groups for resume
Rsm Ofst Coord Sync offset could not be synchronized. The
CPMO-105 WARN Fail G: %d^2 path might deviate from the taught None.
Document the events that
T1 speed > 250 (G: T1 speed exceeds 250 mm/sec for this led to the error, and call
CPMO-130 STOP %d^2)
NO CR allowed in this group. Region is not allowed in this
Corner your FANUC
Remove Robotics
Corner Region
CPMO-135 region
NO PSPD allowed in this block.
Process Speed is not allowed in this and use CNT.
Remove the PSPD
CPMO-136 region
NO mspd allowed in application block.
max_speed is not allowed in this (Processthe
Change Speed) option. to
max_speed
CPMO-137 this region application block. mm/sec.
NO LD allowed in this AP_LD and RT_LD are not allowed in Remove the AP_LD or
CPMO-138 region this application block. RT_LD option.
The specified CR value was too big to
achieve since the actual CR value is Use a higher programmed
Can't maintain CRval limited by either CNT100 corner path speed, or use ACCxx,
CPMO-139 L:%d^5
NO CD allowed in this or half-distance
Corner Distance of involved
is not segments.
allowed in this xx<100.
CPMO-140 region block. Remove CD and use CNT
Wrong CP State (G: CP internal state was wrong at resume By pressing RESET, the
CPMO-150 %d^2)
No Stoppos at OrgRsm Please log debug
CP detected data
that at and report
resume the
stoppose state
Resetshould be reset
the system and try
CPMO-151 (G:%d^2) was not initialized again
NotSupport CP does NOT support Simultaneous GP Either remove
CPMO-199 Simul/Indep GP L:%d^5 or Independent GP motions. Simultaneous GP
TorchMate has found that the offset of Determine if the Torch
the torch from the original TCP is needs to be replaced at
CUST-000 WARN Offset is out of range beyond the offset limits in the SETUP this time. Replace it if
The wire is in contact with the touch REMEDY 1: Shorten the
plate or is grounded prior to executing wire stickout before
the touch move; CAUSE 1: The wire TorchMate execution by
Sensor is ON before stickout is too long; CAUSE 2: The retracting the wire or
CUST-001 WARN search starting position for the touch move is clipping the wire; REMEDY
Cause 1:The TorchMate sensor circuit Remedy 1: Decrease the
indicates the wire is in contact with the stickout, increase the
touch plate before the search move search start distance, or
Sensor failed during (too much stickout-the search start replace the bent torch.
CUST-002 WARN search distance is too small.) Cause 2: An Remedy 2: Contact the
This error indicates that Z
compensation was disabled while Disable Z compensation in
mastering and enabled during the TorchMate SETUP
CUST-003 WARN Z offset is not mastered TorchMate adjustment. TorchMate screen.
Program paused while Mastering was stopped by releasing the Select the MASTER
CUST-004 WARN mastering SHIFT key. softkey to execute
Reassign the TorchMate
output signal to the
WO[1] is not available The TorchMate output signal has been welder's touch sense
CUST-005 WARN for output assigned to the Weld Start output. circuit, or to an external
Override must be 100 The speed override must be 100% Set the override to 100%,
CUST-006 WARN %% during both mastering and TorchMate
TorchMate does not function if DRY and execute
Display mastering
the Test Cycle or
CUST-007 WARN Dry run is not allowed RUN is turned on. menu, and turn DRY RUN
CAUSE 1: TorchMate Adjustment was
attempted before mastering CAUSE 2:
TorchMate Ajustment has Z offset Calibrate the TCP correctly
TorchMate is not enabled, but the mastering was done before using TorchMate
CUST-008 WARN mastered with Z offset disabled. CAUSE 3: Adjustment.
The automatic setup of macros during The Macro teach pendant
installation cannot find an unused program will be loaded on
Macro number. No macro table entry the controller. Remove an
No unassigned MACRO will be automatically assigned to unused Macro from the
CUST-009 WARN is available TM_ADJST, TM_ADJ2, TM_ADJ3. Macro table, and assign
An attempt was made to run On the affected
TorchMate adjust or mastering in T1 controllers, change the
mode on a CE or Control reliable Teach mode to T2 and
Cannot run TorchMate controller. This error applies to rerun mastering or
CUST-010 WARN in T1 Mode TorchMate and TorchMateII on R-J, R- TorchMate adjustment.
Multiple equipment is TorchMate mastering or TorchMate Set up multiple
CUST-011 WARN not defined adjustment has been attempted on an equipment prior to
System Utool is not The UTOOL that you are trying to Set up your UTOOL using
CUST-012 WARN defined adjust or master is not defined. the six-point method.
On the ATFLASH release
media for your robot,
The hidden programs used by locate the the programs
%s is corrupt or does TorchMate have become corrupted. PRODUCT\TORCHMAT\T
CUST-013 WARN not exist This is an extremely rare occurrence. MTMPLT.TP and
During TorchMate mastering, the Abort the PAUSED or
MOVETO operation in the TorchMate RUNNING program prior
Abort program using SETUP screen, or TorchMate to executing any of these
CUST-014 WARN G:%s adjustment was attempted on a motion functions.
TorchMate mastering or TorchMate REMEDY 1: Select for
adjustment was used on a motion jogging a motion group
group that is not associated with the that is associated with the
G:%s does not support robot(s) in your system. CAUSE 1: At robot(s) in your system.
CUST-015 WARN TorchMate mastering, the group is determined by REMEDY 2: Correct the
This indicates that the TorchMate This is cleared by pressing
Touchup Monitor has been turned the ENTER key. It is
on(Touchup monitor value is > 0.0 recommended that you
Run TorchMate before Hrs.), that the program contains a execute TorchMate adjust
CUST-016 WARN edit robot motion group(s), and that a for the motion group(s) in
This indicates that the TorchMate This alarm causes a
collision monitor has been turned on prompt box to be
Collision! Run and that it has detected that a displayed. Press the
CUST-017 WARN TorchMate "collision detect" alarm, a "disturbance ENTER key to clear the
CVIS-000 Success None. None.
First, make sure your RD:
drive is not unnecessarily
large. If so, reduce the size
of it. If you continue to
Not enough memory to Not enough memory is available to encounter the error, cycle
CVIS-001 process process the request. power on your controller.
Bad arguments to the Document the events that
CVIS-002 function Internal error. led to the error and
Check to make sure you
have entered the correct
Cannot find specified filename. If the file is
CVIS-003 file The specified file cannot be found. supposed to be on a
Change the file name or, if
CVIS-004 The file already exists The specified file already exists. using removable media
Make sure you are
attempting to access the
correct file. If the file is on
CVIS-005 File access is denied File access is denied. media which has a
Not enough space on Free up space on the
CVIS-006 the disk Not enough space exists on the media. existing media by deleting
Invalid/unsupported The BMP file is corrupted, or its format Convert your image to a
CVIS-007 BMP file is not supported. different format such as
Bad vector/matrix Document the events that
CVIS-008 dimensions Internal error. led to the error and
CVIS-009 The matrix is not square Internal error. led to the error and
CVIS-010 The matrix is singular Internal error. led to the error and
CVIS-011 The objects are parallel Internal error. led to the error and
The quadratic is a Document the events that
CVIS-012 parabola Internal error. led to the error and
The quadratic is a Document the events that
CVIS-013 hyperbola Internal error. led to the error and
Not enough points for Document the events that
CVIS-014 fitting Internal error. led to the error and
Too few calibration The number of points is not enough to Check if the calibration
CVIS-015 points compute the calibration. points are found properly.
Cannot calibrate the Calibration cannot be computed from Check if the calibration
CVIS-016 camera the given point set. points are found properly.
Check if the file name
contains unusable
characters. Note that the
controller only supports
CVIS-017 Invalid file name The specified file name is invalid. DOS file names (8-
Please notify FANUC of
the conditions (program
CVIS-018 The mask size is bad Internal error executed, operation
CVIS-019 The window size is bad The specified window is bad. Change the window size.
Big circles cannot be Determine if the
CVIS-020 distinguished Big circles could not be distinguished. calibration plate is tilted
Not enough vision pool is available to
Exceed VisPool(%d process the request. So the main pool Increase the size of vision
CVIS-021 Bytes) was temporarily used to process the pool.
The system may have
been corrupted. This may
have been caused by any
of a number of reasons
including: Incorrect
loading and setup loading
1. Perform a cold start. 2.
Perform an init start and
setup the robot again 3.
Confirm that any options
Internal INTR error. This class of error or additional software not
JBF Ptout > Ptin (G: should not be encountered during on the original software
CVIS-022 %d^2) normal operation distribution media is the
The system may have
JBF Ptout != Ptin (G: should not be encountered during on the original software
The system may have
JBF (Ptin-Ptout)>itp (G: should not be encountered during on the original software
The system may have
should not be encountered during on the original software
CVIS-025 JBF Ts < 0 (G: %d^2) normal operation distribution media is the
The system may have
CVIS-026 JBF Ts != 0 (G: %d^2) normal operation distribution media is the
The system may have
CVIS-027 JBF Ts > itp normal operation distribution media is the
The system may have
JBF TS, Ptin & Ptout should not be encountered during on the original software
CVIS-028 mismatch normal operation distribution media is the
The system may have
CVIS-029 JBF Index > 1 (G: %d^2)
The model pattern is normal operation distribution media
Train the model is the
pattern,
CVIS-030 not trained. The model pattern is not trained. and retry the operation.
There are not enough Use another part of the
features in the training There are not enough features in the image as the model. Or,
CVIS-031 window. image to train the model pattern. teach a model using
led to the error and
CVIS-032 Bad arguments. Internal error contact your FANUC
In the Geometric Pattern
Match (GPM) Tool Setup
screen, check if you have
the Orientation, Scale, or
Aspect Ratio degrees of
freedom enabled. If so,
reduce the maximums
and/or increase the
minimums and try to find
again. If it still fails,
disable one or more
degrees of freedom.
The operation has The system could not find the object Increase the allowable
CVIS-033 timed out. within the time limit. processing time.
The emphasis area is Train the emphasis area,
CVIS-034 not
The trained.
emphasis area is The emphasis area is not trained. or configure
Train a smaller thearea
toolasnot
the
CVIS-035 too large. The emphasis area is too large to train. emphasis area.
The emphasis area is The emphasis area is too small and Train a larger area as the
CVIS-036 too small. does not contain enough features to emphasis area.
For a non-rotatable model, an attempt The model origin of a non-
The model pattern is was made to have the model origin rotatable model cannot
CVIS-037 not symmetrical. automatically set by clicking the Center be set Geometric
In the automatically by
Pattern
Match (GPM) Tool SETUP
the Orientation, Scale, or
Aspect Ratio degrees of
freedom enabled. If so,
reduce the maximums
and/or increase the
There is not enough memory to minimums and try to find
perform the detection with the again. If it still fails,
Too many candidates to specified condition. The image has too disable one or more
CVIS-038 process. many candidate patterns to find. degrees of freedom. Make
The mask doesn't fit the Document the events that
CVIS-039 model pattern. Internal error. led to the error and
The mask doesn't fit the the conditions (program
CVIS-040 search window. Internal error executed, operation
This error indicates there
is no way to convert the
file to use on this robot
The version of the file is too new to controller. To use this file,
CVIS-041 File version error. load.
The GPM tool data in the file is you will either need to
CVIS-042 File is
The corrupted.
search corrupted.
window is The specified search window is too None.
Set the search area larger,
CVIS-043 too small.
Cycle power: GTFsize small to process. and retry
Reboot the operation.
controller for
CVIS-044 (G: %d^2) Allocated time filter size is too small. larger time filter size
Local Hold error (G: The difference between channel Report the problem and
CVIS-045 %d^2)
ChnI != ChO + CIF (G: previous input and current input is not then
Report reset
the problem and
CVIS-046 %d^2) Chn Input != Chn Output + CIF then reset
GTF dynamic acc (G: Velocity or acceleration change too Disable
CVIS-047 %d^2) large when dynamic time filter $CPCFG.$COMP_SW2
Set it in the range from&
CVIS-050 Exposure is invalid The exposure time is out of range. 0.04 ms to 250 ms.
Re-teach a measurement
area. The minimum
No laser measurement area has been allowable laser
set up or a set laser measurement area measurement area is 8
CVIS-051 Laser window is invalid is too small. pixels in both height and
Calibration data is not Make sure that 3D laser
CVIS-052 perspective The calibration data is improper. sensor calibration data
The probable causes are
that the calibration data is
Calculation is not Measured laser spots did not converge incorrect, or within the
CVIS-053 converged. at one point. measurement range the
First, adjust the setting of
exposure so that an
appropriate laser image
can be obtained. Next,
make sure that the laser
measurement area was
taught properly. If the
pattern match model
No straight line was found from a string origin is changed after the
CVIS-054 Laser line is not found. of laser spots. laser
First, measurement areaof
adjust the setting
exposure so that an
pattern match model
origin is changed after the
laser measurement area
has been taught, it is likely
Not enough laser points The number of found laser spots is not that the laser
CVIS-055 for calculation. larger than the threshold. measurement area may
exposure so that an
pattern match model
Laser plane is not No plane was found during laser origin is changed after the
CVIS-056 found. measurement. laser measurement area
Zero vector is used in This is an internal error found during the conditions (program
CVIS-057 calculation. laser measurement. executed, operation
Input data is out of This is an internal error found during the conditions (program
CVIS-058 range. laser measurement. executed, operation
During 3D measurement, it was found If this tilting of the
that the workpiece had been tilted workpiece is permissible,
Leaning angle exceeded more than the setting, as compared increase the setting.
CVIS-059 limit. when the reference data was obtained. Otherwise, eject the
Check that your field of
CVIS-060 No features in image No features are found in the image. view is well-lit, and your
Parameter is not Vision Shift error. This is an internal Document the events that
CVIS-061 initialized error. led to the error and
Vision Shift error. Unable to find a Adjust the Rotation Angle
Target is rotated too target in a image because the rotation parameter in the Vision
CVIS-062 much angle of the target is larger than the SETUP screen.
The distance between a
Vision Shift error. Unable to find a camera and a target might
target in a image because the target in be shorter than the
CVIS-063 Target is too close the image is too large. allowable distance limit.
camera and a target might
Vision Shift error. Unable to find a be longer than the
target in an image because the target in allowable distance limit.
CVIS-064 Target is too far away the image is too small. Check the distance
Vision Shift error. Unable to find a camera and a target may
Target is tilted too target in a image because the target in be longer than allowable
CVIS-065 much an image is too small. distance limit. Check the
The image contrast may
be lower than the image
Vision Shift error. Unable to find a contrast threshold. Check
target in an image because the image the image and adjust
CVIS-066 Contrast is too low contrast is low. camera and lighting
The score of geometrical
Vision Shift error. Unable to find a feature matching between
target in an image because the the target and the taught
CVIS-067 Target is not clear detection score is low. model might be less than
Mastering calculation is An internal Vision Shift error has led to the error, and
CVIS-068 failed occurred. contact your FANUC
The specified vision data
might be created by
Data is not for vision Vision Shift error. The specified vision iRVision setup. Rename or
CVIS-069 shift data is not for vision shift. delete the currently
Vision Shift cannot run when the vision Remove the vision board
CVIS-070 Remove Vision Board board is plugged in. temporarily while running
The system may have
Channel not main (G: should not be encountered during on the original software
CVIS-071 %d^2) normal operation distribution
Please ABORT media is the
and move
the robot to a safe
position or Backward one
line to avoid the same
error message NOTE: (1)
When this error message
is posted, the system no
longer maintains constant
path (path would change)
at resume (2) If you
Path Changed: Need Resume motion can't continue on a ABORT the program, then
CVIS-072 BWD (G:%d^2) constant path. the cursor
Please will and
ABORT not stay
moveat
the robot to a safe
position or Backward one
line to avoid the same
error message NOTE: (1)
When this error message
is posted, the system no
longer maintains constant
path (path would change)
at resume (2) If you
Path Changed: Need Resume motion can't continue on a ABORT the program, then
CVIS-073 BWD (G:%d^2) constant path. the cursor will not stay at
Can't resume blend Hold and resume motion can't occur on Use the Jerk Blending
CVIS-074 path (G: %d^2) a constant path when there is blending Filter
Take aType
closefor all motion
look at the
CVIS-075 %s This is only a warning issue
Can't resume same Resume motion can't continue on a Reset and cycle start to
CVIS-076 path (G: %d^2) constant path. continue. The path may
Can't resume same Resume motion can't continue on a Reset and cycle start to
CVIS-077 path (G: %d^2) constant path. continue. The path may
Resume motion can't continue on a Reset and cycle start to
CVIS-078 Seg Overrun (G: %d^2) constant path. continue. The path may
Resume motion can't continue on a Reset and cycle start to
CVIS-079 Preplan fail (G: %d^2) constant path. continue. The path may
The camera is busy and cannot respond
CVIS-080 The camera
Invalid is busy
camera type to the request. None.
Select the current camera
CVIS-081 specified The specified camera type is invalid. type.
Invalid image object led to the error and
CVIS-082 passed
Exposure time is out of Internal error
The specified exposure time is out of contact
Select anyour FANUCtime
exposure
CVIS-083 range camera port
Invalid range. within arange.
Select correct camera
CVIS-084 specified The invalid camera port is specified. port.
Internal error. The image cannot be Document the events that
CVIS-085 time
Camera is notout
3D laser acquired
The within
specified the time
camera limit.
is not led to the error
the 3D laser Configure and to
the camera
CVIS-086 sensor sensor. be 3D laser sensor.
Images could not be captured by a USB Document the events that
CVIS-087 DEPICT error camera. led to the error and
Vision FPGA version The FPGA version is too old to work Contact FANUC to update
CVIS-088 error with vision. your hardware to the
Check that the camera
cable is securely
CVIS-089 Camera is not initialized The camera is not initialized. connected to both the
Check that the camera
cable is securely
connected to both the
A DMA transfer error occurred during camera and the robot
CVIS-090 Vision
The autoDMA error
exposure the
The image acquisition.
auto exposure setting has not been controller.
Train the autoCycle power on
exposure
CVIS-091 setting
The autois exposure
not trained trained. setting.the auto exposure
Lower
CVIS-092 setting is too bright
The auto exposure The auto exposure setting is too bright. setting.
Raise the auto exposure
CVIS-093 setting
The autois exposure
too dark The auto exposure setting is too dark. Re-train
setting. the auto
CVIS-094 setting is bad The auto exposure setting is bad. exposure setting.
This Board has no The main CPU board currently in the
CVIS-095 CAMERA I/F controller does not have a camera Change the Main Board.
Multi exposure Exposure times calculated
exceeded the limit. for the multi-exposure
Number of exposures Multi exposure exceeded the limit. The function exceeded the
will be modified at number of exposures will be modified limit of the exposure time
CVIS-096 execution
Area is not trained. at execution. available
Train the with the camera.
multi-exposure
CVIS-097 Area is reset.is
The camera The multi-exposure scale is not trained. scale area.
CVIS-098 disconnected
Not support this config The camera is disconnected. Connect
Please the camera.
change the congif
CVIS-099 ofvision
A MUX data file with Not support this config of MUX of MUX another name for
Specify
CVIS-100 that name data
The vision already
file does The specified vision data already exists. the Use vision data. vision data
an existing
CVIS-101 not exist. The specified vision data does not exist. name.
Invalid vision data Document the events that
CVIS-102 pointer
The vision data file is Internal
The error.
vision data file is already opened led to the
Close the setup
error and
window
CVIS-103 already open for for writing. for this vision data file.
No more vision data Internal error. No more vision data Document the events that
CVIS-104 found exists. led to the error and
Cannot delete the Cannot delete the vision data because Close the vision data
CVIS-105 vision data file because it is opened for setup. before performing the
Cannot rename the Cannot rename the vision data because Close the vision data
CVIS-106 vision data file because it is opened for setup. before renaming.
Cannot save the vision Cannot save the vision data because it Close the vision data
CVIS-107 data file because it is is opened for setup. before performing the
The vision data included a vision tool Order the option for the
CVIS-108 Tool type not found that this controller does not support. vision tool.
CVIS-109 Interface not supported Internal error. led to the error and
CVIS-110 Double registration Internal error. led to the error and
The corrupted data file
The vision data file is cannot be recovered. If
CVIS-111 corupted. The vision data file is corrupted. you have a backup of the
Parent camera view not Document the events that
CVIS-112 found Internal error. led to the error and
The vision data file is The vision data is too old, and this Contact FANUC to obtain
CVIS-113 too old to load. version of controller cannot load it. an updated version of
The vision data file is The vision data is too new, and this file to use on this robot
CVIS-114 too newvision
Invalid to load.
data version
The of controller
vision data namecannot load it.
might contain controller.
Check To usefor
the name this file,
CVIS-115 name invalid characters. invalid characters.
There is not enough There is not enough space on the disk Delete any unnecessary
CVIS-116 space on the disk. to save the vision data. vision data, and try the
The 3DL vision process
allows only laser
measurement tools of the
CVIS-117 CannotController
Target insert thishas
tool The selected tool cannot be inserted. same type
Select to be added.
the correct robot If
CVIS-118 no vision The target controller has no vision. and retry the operation.
The vision program can The vision program can not output this Select a valid vision
CVIS-119 not output this vision vision
The parameter.
vision log could not be recorded to parameter
Change theid.
new memory
CVIS-120 Could not log data the log file. card, or delete files on the
Vision log function error. The logged Insert a new memory card
CVIS-121 Could not log image image could not be recorded. into the controller, or
The log file is corrupted and cannot be None. The log file is not
CVIS-122 Log file is corrupted read. recoverable. Select a new
Unknown tag specified An internal error of the vision log Document the events that
CVIS-123 to log function occurred. led to the error and
An internal error of the vision log Document the events that
CVIS-124 Bad log file open mode function occurred. led to the error and
CVIS-125 Log record is full function occurred. led to the error and
No more elements in An internal error of the vision log Document the events that
CVIS-126 log record function occurred. led to the error and
CVIS-127 Invalid index specified function occurred. led to the error and
CVIS-128 Specified tag not found function occurred. led to the error and
file to use on this robot
Unknown tag found in The log file is too new, and this version controller. To use this file,
CVIS-129 log free
No file disk space to of the is
There system cannotspace
not enough read it.
to write the you will the
Change either need to
memory card,
CVIS-130 log log file. or delete some files.
CVIS-131 Resumelog
Cannot data loggingof
because logging be
Data cannot is resumed.
logged because of bad None.
CVIS-132 bad clock setup clock setup. Set the clock properly.
CVIS-133 Missing my work area Missing my work area Please train the line data
CVIS-134 Line data
Please is not
enter trained
a valid The line data has not been trained. Train the line data.
CVIS-136 robot
The IP address.
robot name '%s' or IP address
The specified robot nameisisnot valid.
already Enter a valid IP address.
CVIS-137 ip address is already in being used. Enter a new robot name.
The robot name must The specified robot name contains
start with a letter, invalid characters. Invalid characters Enter a robot name that
contain no spaces, not are: backslash, forward slash, colon, does not contain any of
CVIS-138 contain the characters asterisk, question mark, double quotes, these characters.
Some programs have
been designed to prevent
The specified tool cannot be deleted the number of command
CVIS-139 Cannot delete this tool. from the tree window. tools from being set
The value %s is out of Specify a value within the
CVIS-140 range.
The The
tool valid'%s'
name range
is is The specified value is out of range. range.
CVIS-141 already in use. The specified name is already in use. Specify another name.
The tool name must
start with a letter,
CVIS-142 contain no spaces, not The specified name is invalid. Specify a valid name.
The image display is in An attempt was made to perform Complete the setting of
CVIS-143 the Graphic Edit another operation while a window or the window or mask
The name has been The specified tool name is too long and If truncating the tool
CVIS-144 truncated to '%s'. therefore truncated to a valid length. name poses a problem,
The image display is in An attempt was made to perform Complete the live mode
CVIS-145 live mode.\n (Exit mode another operation while an image was display before performing
An attempt was made to teach a model Snap an image or read a
CVIS-146 There is no image. using a pattern match when there was saved image file.
CVIS-147 Load failed for %s. The tool failed to be loaded. None.
There are no found No part was found. Either no part Adjust the exposure so
CVIS-148 results. exists, or it could not be found. that an appropriate image
The image display is in Before trying to perform
CVIS-149 Continuous S+F Continuous location is running. another operation, press
Camera view index out The camera view index specified in the Type the correct camera
CVIS-150 of range RUN_FIND
The command
vision process hasisno
out of range.
more vision view index for the vision
CVIS-151 No more
Failed vision
to set ref.offsets offsets. None.the results before
Find
CVIS-152 position The object has not been found. setting the reference
Ref. position has not The reference position has not been Execute the
CVIS-153 been set set. SET_REFERENCE
Reference data does Reference data for the found model ID Create a reference data,
CVIS-154 not exist does not exist. set the model ID, and set
Bad vision process The vision process with the specified Check if the specified
CVIS-155 name name does not exist. vision process exists, and
Vision process was not The vision process with the specified Check if the specified
CVIS-156 found name does not exist. vision process exists, and
The camera set up with the specified Check if the specified
CVIS-157 Camera does not exist name does not exist. camera setup exists, and
Camera calib. does not The camera calibration with the Check if the specified
CVIS-158 exist specified name does not exist. camera calibration exists,
Do not use this request
Inappropriate request The vision tool cannot work for the for the specified vision
CVIS-159 to tool given request. tool in this case. You
Find has not been Execute the RUN_FIND
CVIS-160 executed
No camera setup is Findcamera
The has notsetup
been has
executed.
not been command or press the
CVIS-161 selected
No camera calibration The selected.
camera calibration has not been Select a camera setup.
CVIS-162 selected selected. calibration.
In case of the tool offset, the robot
No reference robot position is needed to train the Set the reference position
CVIS-163 position for tool offset reference position. But the reference for the tool offset.
In the case of robot a mounted camera,
the robot position is needed to
No robot position for compute the part position. However, Snap the image from a
CVIS-164 robot mounted camera the robot position is not set. Maybe the camera.
In case of tool offset, the robot position
No robot position for is needed to compute the part position. Snap the image from a
CVIS-165 tool offset However, the robot position is not set. camera.
In order to continue using
iRVision, you must restart
the controller in
Controlled Start mode,
enter the Option menu,
and enter the necessary
PAC code(s) for the
iRVision option(s) you
Vision Standard DEMO The 60-day use period of the iRVision require. NOTE: You MUST
CVIS-166 expiredController is too
Target demo
The version
target has expired.
controller is too old to also enter
Update thea software
PAC codeoffor
CVIS-167 old to communicate
Target communicate.
Controller is off- the target controller.
Check the target
CVIS-168 line The target controller is off-line. controller power and
Object is not found in The offset cannot be computed Modify parameters to find
CVIS-169 some camera view(s). because the object is not found in the object properly, then
Calculating a compensation value Check the found result of
resulted in the misalignment becoming each camera view and
Combine error exceed equal to or greater than the make sure that no mal-
CVIS-170 the limit. must be
Calibration permissible value. detection
Use occurred.
a perspective If no
camera
CVIS-171 perspective. Camera calibration is not perspective. calibration.
Robot Pos(Z) is different The robot position(Z) is different from The robot position(Z)
CVIS-172 from Calib Pos. the position to calibrate the camera. must be the same as the
Robot Pos(WP) is The robot position(WP) is different The robot position(WP)
CVIS-173 different from Calib from the position to calibrate the must be the same as the
Robot Pos(Z) is different The robot position(Z) is different from The robot position(Z)
CVIS-174 from Reference Pos. the position to set the reference data. must be the same as the
Robot Pos(WP) is The robot position(WP) is different The robot position(WP)
CVIS-175 different from from the position to set the reference must be same as the
Application-Z has been Application-Z has been changed after Set the reference data
CVIS-176 changed after SetRef. setting the reference data. again.
Error occurred in Check another error
CVIS-177 Camera View %d. An error occurred in this camera view. posted at the
Select the same time,
application
CVIS-178 Not Available No application data has been selected. data.
The specified application data was not Check whether the
CVIS-179 Not Available found. specified application data
No images were found for image Verify that the log folder
playback for the selected date. If you corresponding to the
No images found for have selected to use only images for selected date contains the
CVIS-180 image playback. the current vision process, there might images you are expecting.
Image Playback has reached the end Document the events that
CVIS-181 End of image playback. date/time limit. This is an internal led to the error and
Change the VOFFSET type.
Verify if your teach
CVIS-182 VOFFSET
Vision typedoes
Board is wrong.
not The VOFFSET type is wrong. pendant program or
CVIS-183 exist. The Vision Board does not exist. Install the Vision Board.
Check the teach pendant
GET_OFFSET command GET_OFFSET command is conflicted. program logic. Document
CVIS-184 is conflicted. This is an internal error. the events that led to the
No visual tracking Order the visual tracking
CVIS-185 option No visual tracking option is ordered. option.
Order the line tracking
CVIS-186 No line tracking offset)
VOFFSET(frame option No line tracking option is ordered. option.the index value and
Check
CVIS-187 is duplicated
VOFFSET(tool offset) is VOFFSET(frame offset) is duplicated. offset
Check type
indexofvalue
VR.[]and
CVIS-188 duplicated VOFFSET(tool
Vision registeroffset)
is also is duplicated.
locked by LOCK offset type
Unlock of register
vision VR[]. to
CVIS-189 Vision Register is locked PREG command. use UNLOCK PREG
Only 1 vision tool (GPM, The error proofing vision process
Histogram, etc.) accepts only one command tool to be Delete the existing tool
CVIS-190 allowed at this level. inserted. before adding a new one.
The comment string has The specified comment string was too Review the truncated
CVIS-191 been truncated to '%s'. long, and has automatically been comment string and edit,
The system is low on The amount of temporary memory Please contact FANUC
temporary memory and available on the robot is currently low,
America Corporation if
cannot open the vision so the specified vision setup page wasyou receive this error.
CVIS-192 process setup page. not opened. Notify FANUC of the
The maximum number Close any vision setup
of setup pages are You have opened the maximum pages that do not need to
CVIS-193 already open. A vision allowed number of vision setup pages. remain open.
The sorting parameters The sorting parameters have not been Select and specify all of
CVIS-194 are not completely completely defined for the vision the available sorting
The sorting parameters
CVIS-195 are now invalid.\n They The specified name is invalid. Specify a valid name.
Another setup page '%s' You have tried to enable live mode in a
is already in live setup page when another setup page Stop live mode in the
CVIS-196 mode.\n Exit live mode was already in live mode. Live mode is other setup page first.
The vision tool with the specified name Check if the specified
CVIS-197 This tool
Layer was not found
threshold doescalculated
The not exist. layer value exceeded vision tool
Adjust exists,tolerance
the layer and
CVIS-198 exceeded limitnumber is
Layer output threshold
Layer outputlimit.
number is used by parameter.
Change the layer output
CVIS-199 usedcamera
The elsewhere
calibration measurement
The output. has not been
camera calibration number.
Train the camera
CVIS-200 tool camera
The is not trained.
calibration trained.
The calibration data might be calibration.
Create a new calibration
CVIS-201 tool is corrupted. corrupted. data.
The camera calibration No calibration points have been found Find the calibration
CVIS-202 tool is corrupted. on one or more calibration planes. points.
Invalid calibration plane An invalid calibration plane number is Enter the correct plane
CVIS-203 number. passed to the CAMERA_CALIB number to the
Either camera or fixture Either the camera or fixture needs to Mount either the camera
CVIS-204 needs to be mounted be mounted on a robot for 2-plane or fixture on a robot, and
Both camera and Both the camera and fixture should not Fix either the camera or
CVIS-205 fixture should not be be mounted on robots. fixture on a table or other
No robot position for The position of the robot holding the You need to snap an
CVIS-206 robot mounted camera. camera is unknown. image from the camera
No robot position for The position of the robot holding You need to snap an
CVIS-207 robot mounted
No robot fixture.
position for fixture is unknown.
The index of the calibration point is out image
Type a from theindex
correct cameraof
CVIS-208 robot mounted fixture. of range. the calibration point.
The calibration points Simple 2-D calibration error. Calibration
are too close to each data cannot be calculated because the Teach two points that are
CVIS-209 other. two calibration points are too close to farther apart.
The robot position is needed when the
The calibration points fixture is mounted on a robot. Snap the image from a
are too close to each However, the robot position is not set. camera to use a real-
CVIS-210 other. This alarm might occur when you are world image.
The calibration points The plane specified in the Enable the calibration
CVIS-211 are too close to each CAMERA_CALIB is disabled. plane, or pass another
You cannot use an image
No robot position for The robot position at calibration is file for calibration of robot-
CVIS-212 robot mounted camera. needed for the robot-mounted camera. mounted camera. Snap a
Robot positions for two The calibration points must be set with Do not move the robot
CVIS-213 points must be the the same camera position. holding the camera during
No calibration data was calculated for
CVIS-214 Laser calibration fails. the 3D laser sensor. Perform calibration again.
Laser frame cannot be No calibration data was calculated for
CVIS-215 calculated.
Laser window is not the laser
No 3D laser sensor. area has been Set
measurement Perform
up thecalibration
measurementagain.
CVIS-216 trained. set up. area.
Snap an image using the
CVIS-217 No laser image. No laser image was taken. Snap button.
Check whether the target
No found pose of The parent tool of the associate tool is within the camera view.
CVIS-218 parent locator tool. has not been found. Adjust the parent tool
Histogram tool is not There is a histogram tool yet to be Teach all histogram tools
CVIS-219 trained. taught. or delete the unnecessary
Histogram tool: Fail to An internal histogram tool error has led to the error, and
CVIS-220 get reference position. occurred. contact your FANUC
Histogram tool: Fail to An internal histogram error has led to the error, and
CVIS-221 set reference position. occurred. contact your FANUC
CVIS-222 Sub tool is not trained. A child tool is not trained. Train all of the child tools.
Conditional Execution: Document the events that
Fail to set An internal histogram tool error has led to the error, and
CVIS-223 measurement. occurred. contact your FANUC
Camera is not parallel The camera is not parallel to the Z axis Adjust the camera
CVIS-224 to Z axis of UF.
Conditional Execution is of
Thethe User Frame.
conditional execution tool is not orientation.
Train the conditional
CVIS-225 not trained trained. execution tool.
Conditional Execution: Measurements are not set, or an Train measurements on
CVIS-226 Fail to get value. invalid measurement is set. the Conditional Execution
An attempt to find a
parent tool failed. Adjust
No found pose of A condition judgment tool error has the exposure setting so
CVIS-227 parent
The locator tool.
calibration planes occurred. that calibration
The an appropriate image
planes
CVIS-228 are too close. The calibration planes are too close. must be apart from each
The Model ID of a found part is Place a part for the model
CVIS-229 Model ID mismatch.
Reference data is not different from the one of the selected SetID inthe
view of the camera.
reference scales in
CVIS-230 set. No reference scales are set. advance.
Identical reference Two reference scales must be different Set reference scales with
CVIS-231 values exist for for different application Z values. the different application Z
No robot position is set for the Set reference scale with
No robot position for reference scale. The current reference the camera on the robot
CVIS-232 reference scale is set. scale would be set with the camera on enabled.
Robot pose must not be The robot position must be the same as Run the vision process
CVIS-233 changed. the one when you set the reference with the same robot
Robot-mounted camera A Robot-mounted camera is not Change the camera setup
CVIS-234 is not supported. supported in visual tracking. to use a fixed camera.
Encoder count is not The encoder count is not consistent
CVIS-235 consistent with the with the current image. Perform the snap again.
Encoder count of this The encoder count of this robot is Turn all of the robots off
CVIS-236 robot is different
The points are toofrom
close different from one of the other robots.
The points are too close together to and
Touch then on again.
points that are
CVIS-237 together to calculate calculate the frame. farther apart.
Double GetQueue from GET_QUEUE is executed twice in the Modify your teach
CVIS-238 the robot. programs. pendant programs not to
Invalid timing mode for Check that the correct
CVIS-239 visual tracking. The specified timing mode is incorrect. timing mode was specified
Vision overtimes The vision location was not completed Make the conveyor slower
against conveyer before the conveyor moved through or the conveyor travel
CVIS-240 movement. the specified distance. distance longer in the
No found pose of The parent location tool for an Adjust the parameter and
CVIS-241 parent locator
Caliper tool.
tool is not associate
There is a tool hasmeasurement
length not been found.
tool yet model all
Teach so length
that the parent
CVIS-242 trained. to be taught. measurement tools.
Caliper tool: Fail to get Document the events that
CVIS-243 reference position. Internal error. led to the error and
Caliper tool: Fail to set Document the events that
CVIS-244 reference position. Internal error. led to the error and
Blob Locator tool: Fail Document the events that
CVIS-245 to get reference Internal error. led to the error and
No found pose of The parent location tool failed to find Modify parameters of the
CVIS-246 parentare
There locator
not anytool.blobs
the part.
There are not any blobs in the training parentanother
Train locationpart
toolof the
CVIS-247 in the training window. window. image, or use another
The register number is not specified so Set the register number in
CVIS-248 Invalid register number. the software cannot get the application which the application Z
CVIS-249 GetQueue is timeout. GET_QUEUE has timed out. Adjust the waittime.
This robot received This robot received a packet from a Use the same software
CVIS-250 packet from robot with robot with a different software series. series for all robots.
The distance between The distance between reference Change the Minimum
CVIS-251 reference positions is positions is too small. distance between
The range maximum You have entered a maximum value for Enter a maximum value
CVIS-252 value must be greater the range that is less than the minimum that is greater than the
The range minimum You have entered a minimum value for Enter a minimum value
CVIS-253 value must be less than the range that is greater than the that is less than the
AckQueue with invalid The returned part is different from the The last part retrieved by
CVIS-254 vision register
No found posenumber
of part which was in the queue previously. the GET_QUEUE
Adjust parameters of the
CVIS-255 parent locator tool. No found position of the parent tool. parent tool.
GPM Locator tool: Fail Document the events that
to get reference A failure to get the reference position led to the error, and
CVIS-256 position. has occurred. contact your FANUC
The camera %s must be The Floating Frame vision process is Open the camera setup in
CVIS-257 a robot-mounted
Measurement referencing
Output is The a camera
conditional setuptool
execution whose
is not the iRVision
Train Setup and
this conditional
CVIS-258 not trained trained. execution tool.
The parent tool or
Measurement Output: iRVision Measurement Output: Fail to another child tool could
CVIS-259 Fail to get value. get value. not find the part. Check
Measurement Output: iRVision Measurement Output: No Parent location tool could
CVIS-260 No found pose of found pose of parent location tool. not find any part. Please
Invalid work area An invalid register number was set for Input a valid register
CVIS-261 specified. the gripper index. number.
Input the valid gripper
CVIS-262 Invalid line specified An invalid
The gripper
register numberindex
for was set.
the gripper index.
Set the register number
CVIS-263 tray specified
Invalid track schedule index is not set. for the
Set the gripper
gripper index
index
CVIS-264 specified
This model ID is already The gripper index is not initialized. correctly.
Enter a different model
CVIS-265 used
There is a robot which This
A model
robot ID has
is using already been
a different used.
allocation ID. the same allocation
Use
CVIS-266 uses a different mode. mode for each robot.
Part with invalid model The number of robots which have the Input the correct number
CVIS-267 ID is pushed into queue same model id is invalid. of the robots which has
Input the correct
CVIS-268 Unknown
Applicationfunction code
UF is not The allocation mode is invalid. allocation mode.
CVIS-269 selected The application UF is not set. Set the application UF.
The calibration grid The frame indicating the position of the Set the frame indicating
CVIS-270 frame is not selected calibration grid fixture is not set. the position of the
User tool number is not The utool frame in which you perform Set the utool frame that
CVIS-271 selected the tool offset is not set. you perform the tool
The parent location tool The parent location tool of the multi- Adjust the parameters of
CVIS-272 failed to find anything. locator tool failed to find anything. the parent location tool.
The multi-locator tool is The multi-locator tool has not been Add and train one or
CVIS-273 not
The trained.
location tool index trained.
The location tool index register index is more
Selectchild location
a valid tools
index for the
CVIS-274 register index is invalid. invalid. location tool index
The location tool index The location tool index register value is Set the location tool index
CVIS-275 register value is invalid. invalid. register to a value
A child location tool of A child location tool of the multi- Train all of the child
CVIS-276 the multi-locator tool is locator tool is not trained. location tools.
The parent location tool The parent location tool of the multi- Adjust the parameters of
CVIS-277 failed to find anything. window tool failed to find anything. the parent location tool.
The multi-window tool Add and train a child
CVIS-278 is
Thenot trained.index
window The multi-window tool is not
window index register index istrained. location tool and
Select a valid setfor
index the
the
CVIS-279 register index is invalid. invalid. window index register.
The window index The window index register value is Set the window index
CVIS-280 register value is invalid. invalid. register to a value
The child location tool The child location tool of the multi- Train the child location
CVIS-281 of thelocator:The
Blob multi-window
search window tool has not been trained.
The specified search window is too tool.
CVIS-282 window is too small. small to process. Set a larger search area.
The sum of sorting The sum of sorting priority weights is Enable some of the
CVIS-283 priority weights is zero. zero. sorting priority weights
Check the measurements
The vision process is The Error Proofing vision process has configuration to make
CVIS-284 not trained. not been fully trained. sure that no invalid
To overwrite position To overwrite postion and angle, two or Set two or more child
CVIS-285 and angle, two or more more child location tools must be set. location tools.
Any child location tools No child location tools have been set Set some location tools on
CVIS-286 are not setpose
No found on the
of setup on the setup screen. the setup
Adjust screen. of the
parameters
CVIS-287 parent
A child locator
locationtool.
tool Nochild
A found position
lcation toolof the parent
failed to find tool. parent parameters
Adjust tool. of the
CVIS-288 fails to find anything. anything. child location tool.
Position Adjust tool is The Position Adjust tool has not been Set some child location
CVIS-289 not trained. set. tools and set a reference
Invalid ACK status in Modify the call to
CVIS-290 AckQeueu Invalid ACK status has occurred. AcqQueue in your
AckQueue before AckQueue is called before a part is Modify your teach
CVIS-291 GetQueue allocated in GetQueue. pendant program to call
No AckQueue before AcqQueue is not called before the next Modify your teach
CVIS-292 next GetQueue GetQueue. pendant program to call
The GetQueue request is canceled Do not call GetQueue
CVIS-293 Work area is disabled because the work area is disabled. until the work area is re-
The exposure time plus typical system
The DVM snap interval overhead to snap a picture exceeds the Increase the interval or
CVIS-294 is too
The short.
DVM log path is interval
DVM timenot
could specified in the
access the logschedule.
path reducethat
Verify the the
exposure time.
specified
CVIS-295 invalid. specified. log media exists and is not
A system error is inhibiting Diagnostic Document the events that
DVM internal error Video Monitoring (DVM) from enabling led to the error and
CVIS-296 #%d. a schedule. contact your FANUC
%s specified for DVM Diagnostic Video Monitoring (DVM) Check your I/O
CVIS-297 event %d cannot be cannot read the specified I/O signal. configuration.
There is not TEMP Diagnostic Video Monitoring (DVM) Reduce the number of
memory to run DVM at needs more TEMP memory than is pictures in the video loop.
CVIS-298 this time. currently available. If the state of the
Verify that there is
Snap camera port %d An error occured while acquiring an acamera connected to the
CVIS-299 failed. Code %d. image from the camera. port. If the connection
The value of Light The specified value of Light Output Specify a value of Light
CVIS-300 Output Signal Number Signal Number is out of range. Output Signal Number
Edge pair is not Select one edge pair from
CVIS-301 selected. Select found The edge pair is not selected. a list view in the result
Part is not selected. Select one part from a list
CVIS-302 Select found item from The part is not selected. view in the result page.
This function is This function is obsolete and not led to the error and
CVIS-303 obsolete. available on your controller. contact your FANUC
No work area in the No work area is added in the line, so Add one or more work
CVIS-304 line.more line can be
No the required operation cannot be areas inunused
Delete the line.
lines
CVIS-305 created.
No more area can be No more lines can be created. before creating
Delete unused work a newareas
CVIS-306 created. No more work areas can be created. before creating a new
No more tray pattern Delete any unused tray
CVIS-307 can be created. No more tray patterns can be created. patterns before creating a
No more cell can be Delete any unused tray
CVIS-308 added to the tray. No more tray patterns can be created. patterns before creating a
Visual tracking system led to the error, and
CVIS-309 error. Visual tracking system error. contact your FANUC
Invalid name is The specified name is too long, or an Correct the name and try
CVIS-310 specified.
Specified name is unacceptable character was used. the
Enteroperation
another again.
name and
CVIS-311 already in use. The specified name was already used. try the operation again.
The specified data cannot be deleted or Close the setup window of
CVIS-312 Specified data is in edit. renamed, because it is in edit. the data before trying to
No custodianship for Another controller on the network has Close the setup window
CVIS-313 that operation.
Parameters for scale custodianship
Some parameters for that operation.
for scale conversion on
Setthe controller that
all parameters for has
the
CVIS-314 conversion are not
Miss-measured dataset.
is are not set.measured data has been
Incorrectly scale conversion.
Select non-zero length
CVIS-315 selected. selected. data in a list view.
CVIS-316 HDI is not set up. HDI is not set up. Set up
theHDI.
correct trigger
CVIS-317 Invalid trigger type. An invalid trigger type has occurred. type.
Some controllers are Visual tracking configuration of the Use the SYNC button on
CVIS-318 offline. offline controllers are inconsistent. the visual tracking main
The IP address of could The iRVision software could not set the Use the vendor utility to
CVIS-319 not be set on this IP address of the selected GiGe Camera. set up the IP address for
The IP address is in use The IP address is assigned to another Use a different IP address
CVIS-320 by another
Any locatordevice.
tools are computer or other device on the for this camera.
CVIS-321 not set.
Any child locator tools Locator tools are not set. locator
Set some child tools.
locator
CVIS-322 are not
The modelset.pattern is Any child locator tool is not set. tools.
Train the model pattern,
CVIS-323 not trained. The model pattern is not trained. and retry the operation.
In the Curved Surface
Match (CSM) Tool Setup
the Orientation or Scale
degrees of freedom
enabled. If so, reduce the
maximums and/or
increase the minimums
and try to find it again. If
it still fails, disable one or
The operation has The system could not find the object more degrees of freedom.
CVIS-324 timed out. within the time limit. Increase the allowable
Use another part of the
There are not enough image as the model or
features in the training There are not enough features in the teach a model using
CVIS-325 window. image to train the model pattern. another image by taking it
Saved laser image and The saved laser image and laser Change the laser number
CVIS-326 laser Locator:
CSM number are not
No found number
No pose are not consistent.
(position) of the parent tool in the setup
Adjust page.
the parameters of
CVIS-327 pose of parent locator was found. the parent tool.
CSM Locator: Fail to get Failed to get the reference pose led to the error, and
CVIS-328 reference
CSM position.
Locator: The (position).
The specified search window is too contact your FANUC
CVIS-329 search
CSM Locator: A is
window too
child small to process. Set the search area larger.
CVIS-330 tool is not trained. A child tool is not trained. Train all of the child tools.
When the search window
is too small, set the search
The search window is area larger. When the
too small or set to the The specified search window is too search window is set to
CVIS-331 outside of the image. small or set to the outside of the image. the outside of the image,
Cannot control the Please check the
CVIS-332 sensor power Cannot control the sensor power. multiplexer type, the
The found positions are The found positions are too close to Train fundamental data
CVIS-333 too close to each other. each other. again so that fundamental
All found positions are Train fundamental data
CVIS-334 on a same line. All found positions are on a same line. again so that fundamental
The fundamental data The fundamental data are too close to Train fundamental data
CVIS-335 are too close to each each other. again so that fundamental
All fundamental data All fundamental data are on a same Train fundamental data
CVIS-336 are
The on a same line.data
fundamental line.
The fundamental data have not been again
Set thesofundamental
that fundamental
data
CVIS-337 have not been set. set. in camera view set-up
The application user The numbers of application user frames Set the same application
CVIS-338 frames in calibration in calibration data of each camera view frame number to the
The distance between The distance between camera and Select the calibration data
CVIS-339 camera and target has target has not been set. that is trained and
exposure so that an
pattern match model
The cylinder is not No cylinder was found during laser origin is changed after the
CVIS-340 found. measurement. laser measurement area
The cylinder is not Train the laser window,
CVIS-341 trained. The cylinder is not trained. the cylinder direction or
No 2D measurement Make 2D measurement
CVIS-342 result. There is no 2D measurement result. successful. If no 2D
exposure or min laser
Fail to initialize the There are too few laser slit points or contrast so that an
CVIS-343 cylinder calculation. too many noisy points. appropriate laser image
The max fit error is too small. Or there max fit error. Second,
The cylinder calculation are too few laser slit points or too adjust the setting of
CVIS-344 did
Therenotare
converge.
too few many noisy points. exposure
Add manyorcalibration
min laser
CVIS-345 calibration
There are nopoints.
target There are too few calibration points. points.
CVIS-346 position. There are no target position. Train target position.
This configuration This camera-target configuration is not Change camera or target
CVIS-347 between camera and supported. configuration .
The camera that is The camera that is connected to other
CVIS-348 connected to other controller is not supported. Change robot name.
CVIS-349 Too long string. Too long string. Truncate string.
Initial measurement Set an initial measrement
CVIS-350 position is not set.
Invalid motion group Initial measurement position is not set. position
Set a validinto the data
number as of
CVIS-351 number.
The two found Invalid motion group number. motionset
Please group.
trigger offset 1
CVIS-352 positions are too close. The two found positions are too close. and trigger offset 2
Window shift tool does Window shift tool does not exist or Insert a window shift tool,
not exist, or failed to failed to find, so some command tools or train its child locator
CVIS-353 find. could not shift their search window tool.
Window shift tool is not Insert a locator tool under
CVIS-354 trained. Window shift tool is not trained. the window shift tool, and
No vision logs exist in No vision logs exist in the directory Set system variable
CVIS-355 the specified directory. specified by $VISION_CFG$LOG_PATH Run $VISION_CFG$LOG_PATH
operation one more
CVIS-356 Operation
Log file hascancelled.
read-only Operation cancelled. time.
Remove read-only
CVIS-357 attribute.
Vision override is not Log file
The hasoverride
vision read-only attribute.
is not trained attribute
Verify from
if the a log file.
vision
CVIS-358 trained
Count toolproperly.
is not properly. override is trained
CVIS-359 trained.
Arithmetic calculation Count Tool Calculation
Arithmetic is not trained.
Tool is not Count Tool.
Train the Arithmetic
CVIS-360 tool is not trained.
Geometric calculation trained. Calculation Tool is not
Geometric Calculation
Train Tool.
the Geometric
CVIS-361 tool is not trained.
Statistic calculation tool trained. Calculation Tool.
Train the Statistic
CVIS-362 is not trained. Statitic Calculation Tool is not trained. Calculation Tool.
Edge histogram tool is There is a edge histogram tool yet to be Teach all edge histogram
CVIS-364 not trained. taught. tools or delete the
Edge histogram: Fail to Please notify FANUC of
CVIS-365 get reference position Fail to get the reference pose. the conditions in which
Edge histogram: Fail to the conditions (program
CVIS-366 set reference
Found result isposition.
not set Internalresult
Found errorisofnot
a edge
set tohistogram tool. Please
the specidied executed,set operation
found result to
CVIS-367 to the specified vision vision register. the spedified vision
Position data is not set Position data is not set to the specifid Please set position data to
CVIS-368 to the specified position position register. the spedified position
Type of the specified Type of the specified position register is Type of the specified
CVIS-369 position register is not not supported. position register must be
Place a grid pattern plate
in the camera field of view
CVIS-370 Scale factor
Cannot find not set.
evaluation Scale factor is not trained. and teach
Create theevaluation
a new scale factor
CVIS-371 tool. Evaluation tool does not exist. tool under the vision
Cannot add multiple Add evaluation conditions
CVIS-372 evaluation tools.not
Evaluation tool Cannot add multiple evaluation tools. in the evaluation tool.
CVIS-373 trained. Evaluation tool is not trained. Train evaluation tool first.
Check the vision log to
investigate whether the
The 3-D fit error The GET_OFFSET command failed part was wrong or
CVIS-374 exceeds the limit. because the 3-D fit error was too high. damaged. If the part
Not enough targets The GET_OFFSET command failed Check the vision log to
were found to compute because not enough targets were investigate whether the
CVIS-375 the 3-D offset. found during the RUN_FIND part was wrong or
A target was discarded to lower the fit Check the vision log to
One of the targets was error. The 3-D offset was recomputed investigate whether the
CVIS-376 discarded. without that target, and is still valid. discarded target has a
No more targets can be The maximum allowed number of To add a new target, you
CVIS-377 added. targets has already been added to the must delete another one
There is no image Create image register by
CVIS-378 register. There is no image register. changing system variable
The image register is Increase the size of image
CVIS-380 too small. The image register is too small. register by changing
The image register has Store the data to the
CVIS-381 no data. The image register has no data. image register by
The user frame is The user frame is different from that of The user frame must be
CVIS-382 different from that of the image register. same as that of the image
The tool frame is The tool frame is different from that of The tool frame must be
CVIS-383 different from that of
The robot is different the
The image register.
robot is different from that of the same as that
The robot of the
must image
be same
CVIS-384 from that of the image image register. as that of the image
The condition of The condition of detection
detection is different The condition of detection is different must be same as that of
CVIS-385 from that of the image from that of the image register. the image register. Check
Image register index is The image register index specified in Enter the correct image
CVIS-386 out of
The rangeis different The
camera the IRVSNAP
camera isordifferent
IRVFINDfrom
command
that ofisthe register
The index.
camera must be same
CVIS-387 from that of the image
There is no part with image register.
There is no part with the specified as
Please confirmimage
that of the the
CVIS-388 the specified work_id in work_id in queue. specified work_id.
CVIS-389 Invalid
No more data is specified.
position to Internal
No moreerror
position to avoid the executed, operation
CVIS-390 avoid the interference. interference. None.
Interference setup the conditions (program
CVIS-391 system error. Interference setup system error. executed, operation
Specified data cannot be deleted or Close the setup window of
CVIS-392 Specified data is in edit renamed, because it is in edit. the data before delete or
No more interference No more interference setup Delete unused
CVIS-393 setup data(system) can data(system) can be created. interference setup
CVIS-394 setup data(robot) can data(robot) can be created. interference setup
CVIS-395 setup
No data(condition)
more object can be data(condition) can be created. interference
Delete unusedsetup
object
CVIS-396 created. No more object can be created. before created a new one.
Invalid name is Specified name is too long, or un-
CVIS-397 specified. name is
Specified acceptable character is used. Enter correct name.
CVIS-398 already
Specified object shape Specified name is already used.
in use. Enter
Changeanother name.
the object size or
CVIS-399 is invalid. Specified
A object
zero vector hasshape
been isused
invalid.
in positions.
CVIS-400 Zero vector. calculation. None.
CVIS-401 Invalid vertex index. A vertex index is invalid. None.
CVIS-402 direction edge
Invalid segment index. A direction index is Invalid. None.
CVIS-403 index.
Invalid half line edge A segment edge index is invalid. None.
CVIS-404 index.
Invalid number of A half line edge index is invalid. None.
CVIS-405 edges.
Illfitted vertices on number ofofedges
The sequence is invalid.
vertices on polygon isNone.
CVIS-406 polygon.
Illfitted vertices on illfitted.
The sequence of vertices on surface is None.
CVIS-407 surface. illfitted. None.
CVIS-408 Invalid group number. A group number is invalid. None.
CVIS-409 Invalid utool number. A utool number is invalid. None.
If no limit check operation
The GET OFFSET operation has found should be executed,
The computed offset an offset that fails the configured limit deselect the configured
CVIS-412 failed a limit check. check operation. Limit Check Tool in the
Limit check failed, The Limit Check failed, causing the
CVIS-413 offset skipped. offset to be skipped. (For internal use.) None
Limit Check Tool is not Train the Limit Check Tool
CVIS-414 trained. The Limit Check Tool is not trained. first by enabling at least
The selected Limit The Limit Check Tool that was Select a new Limit Check
CVIS-415 Check Tool no longer previously selected has been removed Tool or select 'None
The setting of opening CONS was Make it enabled to open
CVIS-416 CONS was not opened. disabled. Or, it was failed to open CONS. And, select
There are too many There were too many divided points of Reduce the divide number
CVIS-417 divided points of the measurement. for the measurement.
Incorrect camera pos. The setting values of the camera Input the correct values of
CVIS-418 setting
%s is out of range(%d- position was not correct. the camera position.
CVIS-420 %d). The setting values is not correct. Input the correct values.
CVIS-421 %s may be invalid path. The setting value is not correct. Input the correct values.
Barcode library is not The barcode library has not been Attempt the operation
CVIS-422 initialized.
Barcode library is initialized.
The barcode library has already been again. If the error
This message is foroccurs
CVIS-423 already initialized. initialized. informational purposes
Barcode lib: memory The barcode library was unable to Attempt the operation
CVIS-424 allocation
Barcode lib: error.
parameter allocate required memory. again. If the error
This message is foroccurs
CVIS-425 out of range.
Barcode lib: invalid A parameter is out of range. internal
This use only.
message is for
CVIS-426 parameters.
Barcode lib: invalid Invalid parameters are being used. internal
This use only.
message is for
CVIS-427 image.
Barcode lib: invalid data An invalid image is being used.
data buffer has been internal use only.
This message is for
CVIS-428 buffer. lib: invalid
Barcode detected.
An invalid grayscale variable is being internal
This use only.
message is for
CVIS-429 grayscale
Barcode lib:variable. used. internal use only.
This message is for
CVIS-430 incompatible
Barcode image1D
lib: invalid The image buffers are incompatible. internal
This use only.
message is for
CVIS-431 structure.
Barcode lib: invalid 1D Barcode
The specified structure
number is invalid.
of calculation internal
This use only.
message is for
CVIS-432 calculation lines.
Barcode lib: invalid lines is invalid. internal use only.
This message is for
CVIS-433 result structures. The result structures are invalid. internal use only.
Reposition the part and
Barcode lib: barcode The barcode was not found in the try again. If the barcode
CVIS-434 not found. image. still cannot be found,
Barcode lib: error There was an error calculating the try again. If the barcode
CVIS-435 calculating orientation. barcode orientation. still cannot be found,
Barcode lib: error There was an error calculating the try again. If the barcode
CVIS-436 calculating location.
Unknown error from barcode
Unknown error returned from barcode still
location. Thiscannot
messagebeisfound,
for
CVIS-437 barcode library. library. internal use only.
Relative limit check is This vision process does not support Change the limit check
CVIS-447 not supported
Vision for this
measurement relative limit checks, because there is type topush
Don't absolute, or select
key while
CVIS-448 was aborted.
Override value is out of Vision measurement was aborted. executing.
CVIS-449 range. Override value is out of range. Input valid value.
No more big dot can be When the number of found big dots is When the number of
CVIS-450 deleted. conversion is
Millimeter less than four, the big dots can't be correctly
Enable found big dots is
millimeter
CVIS-451 disabled. Millimeter conversion is disabled. conversion checkbox.
Please contact FANUC
America Corporation if
you receive this error.
CVIS-452 Divided by
Camera zeroiserror
setup not Zero denominator division occurred. Notify FANUC of the
CVIS-453 trained.
Camera communication The camera setup is not trained.
communication error Train the camera setup.
CVIS-454 error. occurs. Check the camera cables.
Comm port for camera The communication port for the Initialize the
CVIS-455 is notcamera
This initialized.
is not camera is not initialized. communication port for
CVIS-456 supported. This camera is not supported. Change camera.
View the binary image on
A Matrix Code could the setup page to verify
not be found in the A Matrix Code could not be found in that the threshold is
CVIS-457 image. the image. correct. Check the search
the setup page to verify
that the threshold is
correct. Check the search
The Matrix Code window on the setup page
CVIS-458 geometry is bad. The Matrix Code geometry is bad. to verify that the matrix
the setup page to verify
The Matrix Code is too The Matrix Code is too damaged to that the threshold is
CVIS-459 damaged to read. read. correct. Check the search
None. Please save the
Matrix Code reader An internal software error occurred in image and the vision
CVIS-460 internal
Illegal softwarefound
character error. theillegal
An Matrixtext
Code reader. was found in
character processthat
Verify thatthe
caused this
Matrix
CVIS-461 in Matrix Code. the Matrix Code. Code is not damaged.
The Matrix Code reader The Matrix Code contains an
CVIS-462 does not support Base unsupported feature. None.
CVIS-463 does not support FNC1 unsupported feature. None.
CVIS-464 does not support unsupported feature. None.
CVIS-466 does not support
The Matrix Upper
Code reader unsupported feature.
The Matrix Code contains an None.
CVIS-467 doesMatrix
The not support 05
Code reader unsupported
The feature.
Matrix Code contains an None.
CVIS-468 does not support 06 unsupported feature. None.
CVIS-469 does not support ANSI unsupported feature. None.
The String Output Tool The String Output Tool has not been Open the setup page for
CVIS-472 is not trained. properly configured. the String Output Tool.
Invalid model ID is Specify the model ID for
CVIS-473 specified.
Specified load balance Invalid model ID is specified. that youload
Specify want to change
balance in a
CVIS-474 is over range.
Specified parameter is Specified load balance is over range. range. supported
Specify
CVIS-475 not supported. Specified parameter is not supported. parameter.
Look at previous CVIS
CVIS-476 RUN FIND
Invalid failedof tools
Number Vision Find failed error for remedy to reset
Use SETUP>GUN
CVIS-477 for Gun Tool Number must be 1 or 2 number of tools.
Make sure that the vision
GET OFFSET wrong GET OFFSET Not all model IDs found at process edge point tool's
CVIS-478 model ID View 1 for 1st wire search window includes
GET OFFSET VP 2 Wire Make sure the Search
1:Not all model IDs GET OFFSET Not all model IDs found at window includes the wire
CVIS-479 found View 2 for 1st wire. and only the wire in the
GET OFFSET VP 1 Wire The second wire was not found by Make sure both wires are
CVIS-480 2:Not all model IDs vision at the first view position. in the search window and
GET OFFSET VP 2 Wire Make sure the VP search
2:Not all model IDs The 2nd wire was not found in the window encloses both
CVIS-481 found second view. wires and only the wires.
GET OFFSET Invalid The number of tools per gun must be Uee SETUP>Guns to set
CVIS-482 Number of tools one or two. the number of tools to
Make sure that view 1 and
view 2 differ in yaw,
normally it is a 90 degree
difference in yaw. This
Wire1:Two views are error can be caused by
CVIS-483 parallel The Two view positions are the same. using the same position
Wire2:Two views are The two robot views are nearly the Adjust one of the view
CVIS-484 parallel same position. positions by rotating the
Use SETUP>TOOLS to
The Z axis is defined to be dominant. define the base Z and end
Tool Z End or Base Therefore the base and end model IDs Z to be non zero. MOst
CVIS-485 cannot be 0 must both be non zero weld guns can be easily
The X axis is the dominant axis. The Use SETUP>TOOL to
Tool X End or Base Base X and End X model IDs cannot be define the Base X and End
CVIS-486 cannot be 0 zero. X model IDs. The standard
Multiple consecutive warnings on Determine what is causing
automatic retry have occurred without the previous alarm log
Element exceeds success. Once the retry threshold has warnings and fix the
CVIS-487 Warning threshold been exceeded, an error is posted problem. Chose RETRY to
The tool or the wire has
deviated more than the
The element (X, Y, Z, W, P, or R) has allowable error threshold
Element exceeds Error exceeded the error threshold for values. This is a safety
CVIS-488 threshold change in the UTOOL. check to make sure the
The irtUtiltiy program for getting the The usual cause is an
focal point has failed. The same error invalid vision process
can occur using the FLAG screen to get name or an invalid camera
CVIS-489 Get Focal Point Failed the focal point position. calibration name in the
This is probably cause by
not enough wire in the
search window. Change
Model 1 and Model 3 The top of the wire #1 and the bottom the search window so that
CVIS-490 same point of wire #1 are too close (same point). it includes more wire. The
The vision process search
window may be too small
Model 4 and Model 6 Wire 2 top and bottom point are the and chopping off part of
CVIS-491 same point same point or within 1.0 mm. the wire. The wire may be
6th parameter not Gun The call to irtmain requires a sixth Change or add a sixth
CVIS-492 No parameter for this function. The parameter. The gun
6th parameter not Tool The call to irtmain requires a sixth Change or add a sixth
CVIS-493 No parameter for this function. The parameter. The tool
2nd parameter not VP The call to irtmain requires a second Change or add a second
CVIS-494 Name parameter for this function. The parameter. The vision
6th parameter not View The call to irtmain requires a sixth Change or add a sixth
CVIS-495 No parameter for this function. The parameter. The view
The call to irtmain requires a fourth Change or add a fourth
4th parameter not PR parameter for this function. The parameter. The position
CVIS-496 index parameter is a position register index. register index should be 1
Use the irtUtility TP
program to perform the
Get Focal function. The
Focal point is not The focal point has not been calculated user may also use the
CVIS-497 initialized for irtmain. SETUP>FLAGS screen to
Use the irtUtility TP
program to perform the
Get Focal function. The
The focal point has not been calculated user may also use the
CVIS-498 Focal point is NILPOS for irtmain. SETUP>FLAGS screen to
3rd parameter not The call to irtmain requires a second Change or add a second
CVIS-499 Status Register parameter for this function. The parameter. The status
6th parameter not The call to irtmain requires a sixth Change or add a sixth
CVIS-500 Group No parameter for this function. The parameter. The group
Failed to set the status register Make sure the second
CVIS-501 SET_INT_REG failed containing the return code parameter is a valid
IrTorchMate
automatically retries
Num. consecutive The maximum number of consecutive warnings the maximum
warnings exceeds warnings has been exceeded and an retry count. If there is no
CVIS-502 threshold Response :
Operator erroroperator
The to this effect has been
has selected posted.
the ABORT success, this error is
CVIS-503 ABORT
Operator Response : recovery option
The operator has selected the IGNORE none
CVIS-504 IGNORE Response :
Operator recovery
The option
operator has selected the RETRY none
CVIS-505 RETRY recovery option none
Posture W and P can Enable aspect in GPM
CVIS-506 not be calcurated. Posture W and P can not be calcurated. locator tool of robot-
Move area is limited in Move area is limited in the Make sure to check
CVIS-507 the measurement
Calibration data is of
not measurement of robot-generated grid accuracy of measured
CVIS-508 selected. Calibration data is not selected. Select calibration data.
One or more targets One or more non-required targets were Check the vision log to
CVIS-509 were not found. not found. The 3-D offset was investigate whether the
No vision offset server could be found Make sure that this robot
No vision offset server on the RIPE network. Either there are and the vision server have
CVIS-510 was found. no robots has_vision variable set to RIPE set up, that they
The vision result has failed one or more Adjust the parameters, or
CVIS-511 Limit Check: %s parameters set in the configured Limit adjust the target.
CVIS-512 %s isisdirectory
Log on process to Directory is not supported. Specify
Wait forfile.
completion of
CVIS-513 export Log is on process to export. process to export
RUN_FIND_OFFSET The RUNOFFST program had a vision Adjust part, check
CVIS-514 failed is not
Camera error in GET_OFFSET. lighting, clean camera
CVIS-515 connected Camera is not connected. Connect a camera.
The 2-D Barcode reader The 2-D Barcode is QR Code Model 1.
CVIS-516 does not support QR This code is is old and is not supported. None.
The RUNPASSF program had a vision Adjust part, check
CVIS-517 Error Proof Failed error in GET_PASSFAIL lighting, clean camera
The RUNPASSF program had a vision The Parent part was not
CVIS-518 Error Proof Inconclusive error in GET_PASSFAIL. found. Test is
Operator Selected The operator has selected a custom None this is a log of how
CVIS-519 Custom Recovery recovery option after a vision error. an error was handled.
Operator Retried The operator has Retried the process None this is a log of how
CVIS-520 Operation
Operator Ignored after a vision error.
The operator has Ignore the vision an
Noneerror
thiswas
is ahandled.
log of how
CVIS-521 Operation error. an error was handled.
Check measuring group
number are same as
CVIS-522 Failed to detect motion. Motion of axis failed to be detected. selected group number on
Check measuring group
number are same as
Failed to align to ref. Target mark can't be aligned to selected group number on
CVIS-523 pos. position is
Robot reference position. uif. Checkthe
Reteach measuring axis
position and
CVIS-524 invalid.
Master image is not Robot position is invalid. try the operation again.
CVIS-525 trained Master image is not trained. Train master image first.
Wrong master image The size of image to add does not Either capture or load an
CVIS-526 size coincide with the size of master image. image with the size of
Master image reference Window Shift Tool is inserted before Train master image for
CVIS-527 pose is not
Shading set
coefficients are Surface Flaw Inspection Tool. static master
Train removalimage
again.for
CVIS-528 not set Shading coefficients are not set. shading removal first.
Shading coefficients Not enough pixels are available to Re-edit the run-time mask
CVIS-529 cannot be calculated calculate the shading coefficients. for shading background
Image is not suitable for The image is not suitable for teaching Use another image
CVIS-530 teaching shading shading removal. preprocess, or mask the
CVIS-531 Buffer is full. Internal error executed, operation
Make the vision data
CVIS-532 Vision data
Cannot is toothis
remove big. Vision data is too big to handle. smaller.
CVIS-533 tool.
This camera is not color The
A command
grayscale tool cannot
camera is used be
forremoved.
color None.
CVIS-534 camera. image operation. Use a color camera.
Multi-Exposure cannot Multi-exposure function cannot be Use it in the single
CVIS-535 be used with color used with a color camera. exposure mode.
Auto-Exposure cannot Auto exposure function cannot be used Use it in the fixed
CVIS-536 be used with color with a color camera. exposure mode.
Cannot find specified The tool specified as the input image is Select a proper tool, or
CVIS-537 tool.
Image Filter tool is not not found in the vision process. add an image filter tool.
CVIS-538 trained.
Color Extract tool is not The Image Filter tool is not trained. Train the Image Filter tool.
CVIS-539 trained.
Work area is too Color Extract tool is not trained. Train
Set upColor
properExtract tool
boundaries
CVIS-540 narrow Specified work area is too narrow. of work area.
Fail to calculate the conditions (program
CVIS-541 parameter Internal Error executed, operation
Robot cannot move to the conditions (program
CVIS-542 the destination Internal Error executed, operation
CVIS-544 Target
This is not found
operation is not Internal
This Error is not allowed in
operation executed,
Please operation
enable TP or
CVIS-545 allowed during production. change mode to T1 or T2.
In Bin Picking, an internal error has the conditions (program
CVIS-546 Internal error. %s occurred. executed, operation
In Bin Picking, a KAREL program has Please enter the correct
CVIS-547 No argument. %s been executed with an argument argument.
In Bin Picking, a KAREL program has Please enter the correct
CVIS-548 Bad argument. %s been executed with an argument argument.
In Bin Picking, the Parts List ID specified Please enter the correct
CVIS-549 No Parts List. %s as an argument of a KAREL program Parts List ID.
In Bin Picking, Part Data which has
been popped by IMPOP.PC or is
specified as an argument does not
exist. In the case that no Part Data is Please confirm the TP
specified, IMPOP.PC has not been program to enter correct
CVIS-550 No Part Data. %s executed or the popped Part Data has Part Data ID.
In Bin Picking, the Parts List Manager's Please complete the
CVIS-551 Not trained. %s setup referred by a KAREL program is setup.
The setup is invalid. In Bin Picking, FINE vision process and Please set FINE Position ID
CVIS-552 Please set FINE Position FINE position refers each other in a and FINE VP correctly.
Wizard process has In Bin Picking, a wizard process has the conditions (program
CVIS-553 timed out. timed out. executed, operation
In Bin Picking, the type of a Position Please make the type
CVIS-554 Bad PR type. %s Register which has been referred by a Cartesian.
In Bin Picking, a Position Register which Please initialize the
CVIS-555 Uninitialized PR. %s has been referred by a KAREL program Position Register.
Model ID does not In Bin Picking, the Model ID of Part Please correct the Part ID
CVIS-556 match between FIND Data does not corresponds with that of or the setup.
Vision process does not In Bin Picking, the vision process of Part Please correct the Part ID
CVIS-557 match between FIND Data does not corresponds with that of or the setup.
Please check the Camera
CVIS-558 Snap Retry Occurs%s Snap Retry Occurs. and Cables.
There is no suitable In Interference Avoidance, there is no This alarm does not mean
candidate from the tilt suitable candidate because of the tilt of a serious problem. If it
CVIS-559 of the Z-axis. the Z-axis. persists, please tune
Another Camera is Please don't use Analog
CVIS-560 runningvertices are too
Taught Another Camera is running. Camera when Digital
CVIS-561 near
All taught vertices are Taught vertices are too near. Reteach vertex.
CVIS-562 on a same line.
Inspection interval is All taught vertices
Inspection intervalare on long
is too a same line. Change
with Reteachinspection
vertex. interval
CVIS-563 too long with respect to respect to bead line. or reteach vertex.
This is an alarm of 3D Area Sensor. The
buffer to store 3D map was reserved Don’t try to acquire 3D
for writing. This alarm can occur when map on the setup page
CVIS-564 3D map write
Projector error
is already run-time process and-setup time duringsure
Make production.
not to control
CVIS-565 used. Projector unit is already controlled. projector unit at a same
CVIS-566 Projector setting error Projector setting is not correct. Correct projector settings.
CVIS-567 Projector
3D control
map buffer error
is not Projector control error Check
Set projector
number of 3Dsettings.
map
CVIS-568 found 3D map buffer is not found. buffer.
Intersect point the conditions (program
CVIS-569 calculation error Internal error. executed, operation
Subpixel calculation the conditions (program
CVIS-570 error Internal
No 3d points are measured within the executed, operation
error.
CVIS-571 No 3D points area. Set up projector
Check proper parameters.
settings.
CVIS-572 Projector timeofout
Temperature Projector time out Check
Use projector
projector at and
more
CVIS-573 projector increases.
Projector temperature Temperature of projector increases. intervals.
CVIS-574 error Projector temperature error Cool down projector.
CVIS-575 Projector
All fanare
cameras error
not Projector
All cameras fanare
error Change projector
not calibrated based on Calibrate all camera unit.
based
CVIS-576 calibrated
Projector based on same UF. on same UF.
CVIS-577 communication error. Projectorlayout
Camera communication
is wrong. Orerror.
same Check cables.
CVIS-578 Camera layout error. camera cannot select. Check camera layout.
CVIS-579 3D map buffer3D
Unsupported time
mapout 3D map buffer time out None.
CVIS-580 file
Wait for cooling down Unsupported 3D map file None.
Interval of 3D snap
CVIS-581 projector %d ms Interval
Invalid image size is selected in camera becomes more longer.
of 3D snap is too short.
CVIS-582 Invalid image size setup. Select valid image size.
This is an alarm of 3D Area Sensor. The Document the events that
firmware version of the projector unit led to the error and
CVIS-583 Projector version error. is too old. contact your FANUC
The dimension of Ref. The dimension of Ref.Pos is invalid
CVIS-584 Pos is invalid.
Window shift tool because the
Window shiftsetup of window
tool doesn't shift
have 3d tool Use
Teachthecontainer
result of shape.
vision
CVIS-585 doesn't have 3D result. result. register in window shift
Confirm that the size of
The size of log image is log image and the setting
CVIS-586 wrong. The size of log image is wrong. of [Use Shrink Image] on
Area Sensor Preprocess Tool does not Train Area Sensor
CVIS-587 No 3D Map Mask. have 3D Map Mask. Preprocess Tool or select
The number of 3D points in the Depending on the causes,
measurement area is less than the adjust or re-teach the
threshold. There may be the following following items. 1.
causes. 1. The position or size of the [Measurement Area] and
Not enough 3D points measurement area is not appropriate. [Window Mask] 2. The
CVIS-588 for calculation. 2. The 3D Map is sparse. 3. The settings of 3D Area
No plane was found during plane Depending on the causes,
measurement. There may be the adjust or re-teach the
following causes. 1. The position or size following items. 1.
Suitable plane for 3D of the measurement area is not [Measurement Area] and
CVIS-589 Map is not found. appropriate. 2. The 3D Map is sparse. 3. [Window Mask] 2. The
Valid 3D points in the measurement Depending on the causes,
area did not converge at one point. adjust or re-teach the
There may be the following causes. 1. following items. 1.
The height of a part of a workpiece [Measurement Area] and
differs largely from that of another part [Window Mask]. 2. [Z
within the measurement area or the Range]. 3. The settings of
Center of gravity of 3D position or size of the measurement 3D Area Sensor or the
Map cannot be area is not appropriate. 2. The range setting of camera
CVIS-590 calculated.
USB Camera isn't where valid 3D points belong
USB camera isn't connected to is not calibration.
Connect USB camera to
CVIS-591 connected.
USB Camera system iPendant. iPendant.
Please tell the last number
CVIS-592 error. USB camera system error happens. of this error to FANUC.
Fail to calculate the conditions (program
CVIS-593 parameter Internal Error executed, operation
Robot cannot move to the conditions (program
CVIS-594 the destination Internal Error executed, operation
Size of model is too The size of model is too large with Please retrain the smaller
CVIS-595 large respect to search window. model or reset the lager
CVIS-596 Target is not found Internal Error executed, operation
When offset type is tool Offset type is tool offset on the vision Change the offset type to
CVIS-597 offset, window shift process or the vision register. fixed frame offset.
When robot-mounted When robot-mounted camera is used, Select locator tool for
CVIS-598 camera is used, window window shift tool can't use other VP mode on window shift
Frame number is Select a same offset frame
different on vision Frame number is different on vision number on two vision
CVIS-599 proccess and vision proccess and vision register. process, one is what has
Do the following
operation. VP1 is the
vision process that has the
window shift tool, and
VP2 is the vision process
Because of the soft that makes the result for
update, window shift the window shift. 1. On
tool must be taught Because of the soft update, window VP2, select the same
CVIS-600 again. shift tool must be taught again. number of Offset Frame
Camera type has been Reteach model of pattern
changed after teaching The type of the camera has been matching, or set the type
CVIS-601 model. changed after teaching model. of the camera which was
Reference data Reference data corresponding to the Check to make sure that
CVIS-602 corresponding to the specifiedmodel
External modeltrain
ID is file
not tag
found. the vision
nesting is Check andprocess has
fix the model
CVIS-603 Tag nesting too deep. too deep. train file format.
External model train the conditions (program
CVIS-604 datanot
Tag is broken.
supported by Externaltool
Current model train
type doesfilenot
is broken. executed,
support the Check andoperation
fix the model
CVIS-605 the current tool type. specified tag. train file format.
This tag cannot be This tag cannot be a child element of Check and fix the model
CVIS-606 specified here. the current parent tag. train file format.
Specified vision tool not A vision tool with the specified tool Check and fix the model
CVIS-607 found. name does not exist. train file.
No model info in No information about the model is Check and fix the model
CVIS-608 external model train specified in the external model train train file format.
Check and fix the model
Invalid image for train file format. Write
CVIS-609 external model
Insufficient datatrain.
to train Image name
Required specified
data does not
is insufficient exist.a Check
to train SNAP to andsnap a new
fix the model
CVIS-610 model. model. train file format.
Model train mode Cannot use both an image and graphics Check and fix the model
CVIS-611 conflict. to train
The a model.
value specified is invalid for this train file
Check andformat.
fix the model
CVIS-612 Invalid value. tag. attribute specified is invalid for this Check
The train file
andformat.
fix the model
CVIS-613 Invalid attribute. tag. train file format.
Dynamic window not External model train is not supported Choose another tool, or
CVIS-614 supported. for tools with a dynamic search remove the window shift
The specified points may be too close, Check and fix the model
CVIS-615 Cannot form an arc. or the radius is too small. train file.
Trained model exceeds The model specified with graphics does Check and fix the model
CVIS-616 image
Model size.
is not trained not fit in the image. train
Train file.
the model using an
CVIS-617 with antrain
Model image.
file error. The model is not trained with an image. image.
See the cause and remedy
CVIS-618 (Line: %s) Bad model train file format. for the following error
External model train Specified vision process does not
CVIS-619 not supported. support external model train. Train the model from UIF.
Exceeded external Exceeded external model train daily Increase the limit by
CVIS-620 model trainfunction
The strobe daily limit.
of limit.
The strobe function of the digital changing
Please disable strobe
CVIS-621 the digital camera is camera is enabled. function of the digital
User frame number is User frame number is different from Set the correct user frame
CVIS-622 different
Tool numberfromisthe one the
Toolone whenisteaching.
number different from the one number.
Set the correct tool
CVIS-623 different from the one when teaching. number.
CVIS-624 Invalid position type. Internal Error executed, operation
Not supported with this Executed a vision program with a Check the type of the
CVIS-625 vision data. wrong vision data type. selected vision data.
Parent aspect DOF must Parent aspect DOF result must be Disable the aspect DOF of
CVIS-626 be 100%%. found with 100%% for static the parent command tool.
Parent DOF result does Parent DOF result must match the Disable the DOF of the
CVIS-627 not match the master master data for static background parent command tool.
To use this file, you will
Master file is too old to The master file is too old, and this either need to find a
CVIS-628 load. version of controller cannot load it. controller with older
Master file is too new The master file is too new, and this Contact FANUC/FANUC
CVIS-629 to load. version of controller cannot load it. America Corporation to
CVIS-630 Master file is broken.
does not Master file is broken. the
Use conditions
an existinginmaster
which
CVIS-631 exist. file is not
Master Master file does not exist. name. master file using
Specify
CVIS-632 specified. Master file is not specified. prepared Karel program.
Too small circle exists in Please notify FANUC of
CVIS-633 master file. Too small circle exists in master file. the conditions in which
Too sharp angle exists Please notify FANUC of
CVIS-634 in master file. Too sharp angle exists in master file. the conditions in which
Measurement range is On the 3D Area Sensor Vision Prcocess
CVIS-635 not set setup page, the [Range] is not set. Please set the [Range].
Reference plane is not Confirm that the specified
CVIS-636 found.
LED channel is out ofReference
The plane
specified LEDischannel
not found.
is out of plane measurement
Specify an LED channeltool
CVIS-637 range range.
LED intensity is out of
The specified LED intensity is out of within range.
Specify an LED intensity
CVIS-638 range
LED range.
is not supported in
LED is not supported in this within range.
Please check the
CVIS-639 this configuration configuration hardware
Go configuration
to UTILITY screen and
DIAG-000 Execute CREATE
Freq. Power limitfirst
_DIAG
(G:%d TP program doesn't exist. execute CREATE function
Primiary frequencies power is over the Please schedule service
DIAG-001 A:%d) threshold maintenance.
Group is not supportedCurrent running porgam includes the Check suuported robot
DIAG-002 (G:%d) non-supported robots. models and make sure TP
Data collection/processing stops may Make sure TP program
DIAG-003 Data process stops cause by program paused run successfully.
Aggressive motion Use iRDiagnostics Motion
DIAG-004 (G:%d A:%d L:%d P:%s) Motion is aggressive Profiler to identify the
Reducer load excess Use iRDiagnostics Motion
DIAG-005 (G:%d A:%d L:%d P:%s) Motion is too aggressive Profiler to identify the
Aggressive motion Use iRDiagnostics Motion
DIAG-006 (G:%d A:%d L:%d P:%s) Motion is aggressive Profiler to identify the
Reducer load excess Use iRDiagnostics Motion
DIAG-007 (G:%d A:%d L:%d P:%s) Motion is too aggressive Profiler to identify the
Baseline prog changed TP program used to generated the Please re-master baseline
DIAG-008 (G:%d A:%d) baseline data has changed data using
Perform the data
prompted
DIAG-009 G%d %s in %dhr Maintenance is prompted maintenance
Dictionary already A dictionary cannot be reloaded if it Load into a different
DICT-001 WARN loaded was loaded into FROM. language and use KCL SET
Not enough memory to There is no more permanent memory Clear all unnecessary
DICT-002 WARN load dict available in the system to load another programs, dictionaries or
No dict found for There are no dictionaries loaded for the Use the DEFAULT
DICT-003 WARN language specified language. language or a language in
Use KCL LOAD DICT to
DICT-004 WARN Dictionary not found The specified dictionary was not found. load the dictionary into
Dictionary element not Check the dictionary or
DICT-005 WARN found The dictionary element was not found. element number to be
Only five levels of dictionary elements Fix the dictionary text file
DICT-006 WARN Nested
Dictionary not opened can be nested.
level too deep to include
Remove thefewer
closenested
DICT-007 WARN by task The dictionary was never opened. operation.
The dictionary element was truncated Increase either the size of
Dictionary element because the KAREL string array is not the string or the number
DICT-008 WARN truncated large enough to hold all the data. of strings in the array.
DICT-009 WARN End of language list The language list has completed. do not have to do
DICT-010 WARN End of dictionary list The dictionary list has completed. do not have to do
Dict opened by too Only five dictionaries can be open by Load the dictionary to
DICT-011 WARN many tasks one task at one time. memory or close an
Not enough memory exists in TEMP This is a notification of
Not enough memory to pool on the controller. The dictionary insufficient memory
DICT-012 WARN load dict was not loaded. resources on the
Cannot open dictionary The dictionary file does not exist on the Select the proper
DICT-013 WARN file specified device or in the specified device/directory and try
Expecting $ in The dictionary text incorrectly specifies Make sure all dictionary
DICT-014 WARN dictionary file an element without a $. elements begin with $.
Reserved word not A reserved word was not recognized in Check for misspelling or
DICT-015 WARN recognized the dictionary text. look up the correct word
Make sure all dictionary
text is surrounded by
The dictionary text incorrectly specifies double quotes. Use a
DICT-016 WARN Ending quote expected
Expecting element an element without
A reference using
to another quotes.
element is backslash if you want
Use the element an
number
DICT-017 WARN name or num expected. to reference the element.
The cursor position is specified Make sure the cursor
DICT-018 WARN Invalid cursor position incorrectly or the values are outside position is valid. For
ASCII character code A series of digits are expected after the Remove the # or look up
DICT-019 WARN expected # to specify an ASCII character code. the ASCII character code
Reserved word An identifier is expected after the & to Remove the & or look up
DICT-020 WARN expected specify a reserved word. the reserved word in the
An unexpected character was found in Make sure all dictionary
DICT-021 WARN Invalid character the dictionary text file. text is correct.
Dict already opened by The dictionary is already open by the This is a notification. You
DICT-022 WARN task task. do not have to do
Dict does not need to Dictionaries loaded to memory do not Do not try to open the
DICT-023 WARN be opened need to be opened. dictionary file.
Dictionaries loaded to FROM cannot be Do not try to remove a
Cannot remove removed or a dictionary cannot be dictionary loaded to
DICT-024 WARN dictionary file- internal
Invalid state removed if another task has it opened. FROM. Remove the
DICT-025 WARN error
DICT-026 WARN
DICT-027 WARN
Not enough memory exists in TEMP This is a notification of
Not enough memory to pool on the controller. The dictionary insufficient memory
DICT-028 WARN load dict was not loaded. resources on the
Check the dictionary to be
sure the help dictionary
The help dictionary element was not element was specified
DICT-029 WARN Help element not found found. correctly. The help
Check the dictionary to be
sure the function key
Function key element The function key dictionary element element was specified
DICT-030 WARN not found was not found. correctly. The function
%4s-%03d $%8lX, no The dictionary containing the error Refer to the System
DICT-031 WARN message found message could not be found. Reference Manual for the
%4s-%03d, see posted The error message was posted to the See error window or the
DICT-032 WARN error error log. Alarms menu for the error
Expecting element num The dictionary text incorrectly specifies Make sure all dictionary
DICT-040 WARN after $ an element number. elements begin with $
Expecting element The dictionary text incorrectly specifies Make sure all dictionary
DICT-041 WARN name after , an element name. elements are specified as
Expecting add constant The dictionary text was specified Make sure all dictionary
DICT-042 WARN name incorrectly. elements are specified as
Element number out of The dictionary text was not specified in Make sure all dictionary
DICT-043 WARN sequence sequence. elements are specified in
Warning - large hole in The dictionary text has a large gap Reduce the gap in the
DICT-044 WARN ele seq between
The element
dictionary textnumbers.
was specified element
Verify sequence.
that each .LITEach
is
DICT-045 WARN .LIT or .ENDalready
Command mismatch incorrectly.
The dictionary text was specified matchedthe
Remove with a .END.
extra
DICT-046 WARN encountered incorrectly. command.
Use the .etx file extension
The dictionary compressor expects a for error text, the .utx file
DICT-047 WARN File extension required file extension. extension for
Use the .etx file extension
The dictionary compressor did not for error text, the .utx file
DICT-048 WARN Invalid file extension recognize
The the file
dictionary extension.expects a
compressor extension
Specify forname after
a file
DICT-049 WARN Expecting file name file name. the command.
Expecting facility The dictionary compressor expects a Specify the facility
DICT-050 WARN number facility number in the .KL command. number after the file
Symbol invalid for An invalid command was specified for Check the command and
DICT-051 WARN dictionary type
Expecting .ENDFORM this
The type of dictionary
dictionary text wasfile.
specified if a form
Verify is used,
that verify the
each .FORM is
DICT-052 WARN Cannot
symbol open include incorrectly. matched
Make surewith a file
a valid
DICT-053 WARN file The include file could not be created. name has been specified.
The form you are trying to compress is Abort the KAREL program
DICT-054 WARN Form is being displayed currently being displayed. that is displaying the
End the KANJI string with
%% not allowed in a single quote. Use double
DICT-055 KANJI string %% is not allowed in KANJI string quotes around the format
DJOG-000 WARN Unknown error (DJ00)
DJOG overtravel System internal error Notify GMFanuc
DJOG-001 WARN violationcontrol prog
Motion DJOG overtravel Release overtravel
DJOG-002 WARN aborted Program abort during DJOG enable Run theall
Engage program
the brakes and
DJOG-003 WARN Manual brake enabled manual brake enabled reset
Disable TP, RESET, resume
DJOG-004 WARN TP enabled
Prog has MCTLduring DJOG
of DJOG TP enabled during DJOG Prog
Disable DJOG, RESET,
DJOG-005 WARN group
Robot not clear for DJOG attempt on attached group resume
Move robot or disable
DJOG-006 WARN DJOG station fence Robot not clear of DJOG cell DJOG
Insert fence connector,
DJOG-007 WARN open Fence safety violation RESET
Reset limit value if
DJOG-008 WARN DJOG axis limit
Max group number DJOG Axis limit reached required
Reduce number of DJOG
DJOG-009 WARN exceeded
Max input number Max group number exceeded groups
Reduce starting point
DJOG-010 WARN exceeded
Max output number Max input number exceeded number
Reduce starting point
DJOG-011 WARN exceeded Max output number exceeded number
DJOG-012 WARN
DJOG-013 WARN
DJOG-014 WARN
DJOG-015 WARN
DJOG-016 WARN
DJOG-017 WARN
DJOG-018 WARN
DJOG-019 WARN
ABORT. Unexpected DJOG
DJOG-020 G
ABORT. packet
Bad data in DJOG System internal error Notify GMFanuc
DJOG-021 G
ABORT. packet System internal error Notify
InspectGMFanuc
I/O and/or I/O
DJOG-022 G
ABORT. Uninitialized DJOG I/O Uninitialized I/O setup
DJOG-023 G
ABORT. Uninitialized DJOG data Uninitialized variable Inspect DJOG vars
DJOG-024 G
ABORT.
DJOG-025 G
ABORT.
DJOG-026 G
ABORT.
DJOG-027 G
ABORT.
DJOG-028 G
ABORT.
DJOG-029 G
PAUSE. Motion control taken Abort program or disable
DJOG-030 G
PAUSE. by prog Program
Run program while same group djog is DJOG
attempt to get MCTL
DJOG-031 G
PAUSE. DJOG enabled enable Disable DJOG
DJOG-032 G
PAUSE.
DJOG-033 G
PAUSE.
DJOG-034 G
PAUSE.
DJOG-035 G
PAUSE.
DJOG-036 G
PAUSE.
DJOG-037 G
PAUSE.
DJOG-038 G
PAUSE.
DJOG-039 G Adjust mode canceled
DMDR-001 SERVO G:%d
MasterM:%d
gets selected
DMDR-002 SERVO G:%d gets
Slave M:%dselected
DMDR-003 SERVO G:%d M:%d
Wrong adjust
DMDR-004 SERVO number(G:%d
Large position M:%d)
gap
DMDR-005 SERVO (G:%dcommand
Large M:%d) gap1
DMDR-006 SERVO (G:%dcommand
Large M:%d) gap2
DMDR-007 SERVO (G:%d M:%d) gap3
Large command
DMDR-008 SERVO (G:%d M:%d)
Large synch errror
DMDR-009 SERVO (G:%d
InvalidM:%d)
dual axis
DMDR-010 WARN config(G:%d)
Selected adjust mode
DMDR-021 SERVO G:%d M:%d
DMDR-031 WARN Fail to get memory area
DMER-000 WARN UNUSED ERROR CODE
DMER-001 WARN
PAUSE. Unknown instruction
DMER-002 LPAUSE. phase type
Unknown translation
DMER-003 G
PAUSE. alarm
DMER-004 LPAUSE. Illegal resume
Permanent data doesn't
DMER-005 G
PAUSE. exist
This SLC2cycle isn't
DMER-006 G
PAUSE. supported
DMER-007 G
PAUSE. Pointer is NULL
DMER-008 G
PAUSE. System timer
Receive is strange
unknown
DMER-009 G packet
PAUSE. (%s^4, Internal data does not exist at Check the available size of
DMER-010 L
PAUSE. %d^5)Uninitialized
(%s^4, %d^5)Already data execution
A of Sample
Sample Start Start/End.
instruction permanent
has already
Remove thememory.
duplicate
DMER-011 L sampling been executed. Sample Start instruction.
PAUSE. (%s^4, %d^5)Other task Sampling has already been started bySample with one task at a
DMER-012 L sampling another task. time when using multiple
Edit the Data Monitor
schedule specified in the
PAUSE. The executing Data Monitor schedule program. Correct all
DMER-013 LPAUSE. Invalid item number specifies
The item an invalid
type is notitem number.
supported for monitored items which do
DMER-014 L Unsupported item type sampling. Change the item type.
PAUSE. Invalid schedule The sampling schedule references an Change the item number
DMER-015 L number invalid item number. in the sampleing schedule.
PAUSE. The register n referenced by the Change the register type
DMER-016 L Invalid register type Sample Start[R[n]] instruction is not a in the DATA screen.
The Data Monitor functions is checking Examine the system for
DMER-017 WARN Warn Limit item (%d) this item. The item is past the warning problems.
PAUSE. The Data Monitor functions is checking Examine the system for
DMER-018 L Pause Limit item (%d) this item. The item is past the pause problems.
PAUSE. Data Monitor cannot save data to the Check the if the device
DMER-019 L Data cannot be saved specified device. listed in the schedule is
PAUSE. The Data Monitor record buffer Decrease the record
DMER-020 L Record buffer limit became full. frequency or increase the
The device specified in the Data Use a memory card or
PAUSE. Not enough device Monitor schedule does not have floppy disk with more
DMER-021 LPAUSE. memory free enough file space available. memory available or
DMER-022 L Invalid file size
DMER-023 WARN File is incomplete Data Monitor is not saving data to the Verify the device listed in
DMER-024 WARN Data is not saved specified device. the schedule is available.
PAUSE. Data item type The type specified for a Data Monitor Correct the item type in
DMER-025 L mismatch item does not match the type of the the Data Monitor screen.
Not enough memory There is not enough memory to Select a smaller size for
DMER-026 WARN for pipe allocate the size of the requested pipe. the pipe, or select a
Reallocate the pipe by
Data Monitor was not able to write changing the pipe size or
DMER-027 WARN Failed to write to pipe data to the pipe. device using the system
Data Acquisition task is not active on Make sure the Data
DMER-031 WARN DAQ task not available the system. Acquisition option has
The Data Acquisition system has Contact FANUC Robotics
DMER-032 WARN DAQ system failed encountered a critical failure. for assistance.
The Data Acquisition system failed to Contact FANUC Robotics
DMER-033 WARN DAQ initialization failed initialize properly. for assistance.
DMER-034 WARN Pipe tag invalid
The Data Acquisition pipe you are Unregister the pipe and
DMER-035 WARN Pipe already registered attempting to register has already been attempt the operation
The Data Acquisition pipe you are DAQ pipes must be
DMER-036 WARN Pipe not registered attempting to use has not been registered by a controller
You are attempting to activate a Data
DMER-037 WARN Pipe already active Acquisition pipe which is already active. Deactivate the pipe first.
Cannot allocate global No global files are available to be used Close a global file before
DMER-038 WARN FD by the Data Acquisition system. re-attempting this
Pipe %d could not be The pipe you have attempted to use Check all parameters of
DMER-039 WARN activated could not be activated for some reason. the activation call.
The pipe you are attempting to access Activate the pipe before
DMER-040 WARN Pipe not active has not been activated. attempting this operation.
The Data Acquisition system has run Remove programs to free
DMER-041 WARN DAQ ran out of memory
Invalid DAQ output out
You of memory.
have specified an invalid output controller
Check the memory,
device then
DMER-042 WARN device device. parameter you have
DAQ output mode The output operation you are Check the parameters of
DMER-043 WARN mismatch attempting cannot be performed using your output operation.
DAQ output file not No output file has been defined for the Define an output file for
DMER-044 WARN defined requested operation. the pipe, then re-attempt
The specified Data Acquisition monitor Correct your monitor
DMER-045 WARN DAQ monitor not found could not be located. parameter for the
DAQ monitor already You are attempting to add a Data Use the existing monitor,
DMER-046 WARN exists Acquisition monitor
No client device tagswhich already for
are available or remove the
Deallocate oneexisting
or more
DMER-047 WARN No client tags available use. client tags before
The specified client tag is not being Check the client tag
DMER-048 WARN Client tag not used used. parameter to make sure
DAQ data size A mismatch has been detected Check the specified data
DMER-049 WARN mismatch between the specified data size and the size.
A bad parameter has been detected in Check all parameter
DMER-050 WARN DAQ: Bad parameter the routine call. values before making the
DAQ: monitors still Monitors are still active when you Remove monitors from
DMER-051 WARN activeBad parameter: attempted the current operation.
DAQ: the pipeabefore
Specify valid memory
DMER-052 WARN mem type
DAQ: Bad parameter: The memory type parameter is invalid. type.
DMER-053 WARN pipe
DAQ: Bad parameter: The pipe
size size name
program parameter is invalid.
parameter is Specify a valid pipe size.
program
DMER-054 WARN prog name
DAQ: Bad parameter: invalid. name.
Specify a valid variable
DMER-055 WARN var name
DAQ: Bad param: The variable name parameter is invalid. name.
Specify a valid output
DMER-056 WARN output mode The output mode parameter is invalid. mode.
The specified task ID does not match Unregister the pipe only
DMER-057 WARN DAQ task ID mismatch the task ID used to register the pipe. from the task in which the
Check the name of the
DMER-058 WARN Invalid DAQ pipe name The specified pipe name is invalid. pipe for a null string or
Buffer index $DMONBUF specifed by Set the index properly,
DMER-100 STOPL error(Item:%d) $DMONITEM.$BFFV_INDEX does not and retry the operation.
Confirm whether the
A KAREL variable has been specified variable name is correct.
DMER-101 STOPL [%s]%s doesn't exist that does not exist. Confirm if specified
The KAREL variable for the data output
DMER-102 STOPL [%s]%s isn't array must be an array. Use an ARRAY variable.
The KAREL variable to store the number Use a variable that is not
DMER-103 STOPL [%s]%s is array of record must not be an array. an array.
Change the setup for the
The KAREL variable for data output is array to accomodate all
DMER-104 STOPL [%s]%s is full used up. records. Or increase the
The KAREL variable for data output is Change setup for the
DMER-105 WARN [%s]%s is full used up. array to accomodate all
[%s]%s is multiple The KAREL variable for data output Use a single dimension
DMER-106 STOPL dimension array must be a single dimension array. array.
Edit the Data Monitor
The Data Monitor item to be sampled Item to be sampled to
DMER-107 STOPL Invalid axis number specifies an invalid axis number. specify the correct axis
INIT start and reload the
DeviceNet Interface
The system device definition file is option. If the error still
DNET-001 WARN No system device file missing from the system. exists, document the
INIT start and reload the
DeviceNet Interface
PAUSE. No application device The application device definition file is option. If the error still
DNET-002 G file missing from the system. exists, document the
Turn off controller power.
There are too many DeviceNet Disconnect one of the
PAUSE. Too many DNet motherboards connected to the robot DeviceNet motherboards.
DNET-003 G motherboards controller. Re-connect any DeviceNet
Make sure the board
PAUSE. The specified board has failed to parameters are correct.
DNET-004 G Board init failed: Bd %d initialize. Make sure the board is
The text based device definition is Correct the text based
User dev def Err, invalid. It is missing one of the required device definition and then
DNET-005 WARN line:%d fields or the values specified are invalid. use it. Refer to the header
SYSTE Document the events that
DNET-006 M System error: %d A system error has occurred. led to the
Please error
check and call
syntax in
DNET-007 Invalid device definition An
Invalid Entry
invalid in MD:DNDEF.DG
board index has been MD:DNDEF.DG
Specify a board index
DNET-008 WARN Invalid board
MAC Id:index
Bd %d specified. between
Specify a 0MACandId3.between
DNET-009 WARN MAC %d An invalid MAC Id has been specified. Take 0 andthe63 board
inclusive.
off-line
DNET-010 WARN Board already online The specified board is already on-line. Put before
theattempting
board on-linethe
DNET-011 WARN Board not online The specified board is not on-line. before attempting the
Take the device off-line
DNET-012 WARN Device already online The specified device is already on-line. Put before
theattempting the
device on-line
DNET-013 WARN Device not online The specified device is not on-line. before attempting the
The attempted DeviceNet command Check all network
DNET-014 WARN Request timed out request has timed out. connections. If all
The specified board has not been Initialize the board by
DNET-015 WARN Board not initialized initialized. attempting to put it on-
Cold start the system. If
the problem persists, INIT
SYSTE The DeviceNet Interface system has start or reload the system.
DNET-016 M System failed failed. If the problem continues
The specified board was not found in Make sure the daughter
DNET-017 WARN Board not found the system. boards are properly
The specified board has failed the initial Cold start the system. If
DNET-018 WARN Memory test failed memory test. the problem persists, INIT
The code file required to initialize the Cold start the system. If
DNET-019 WARN Code file open failed board cannot be accessed. the problem persists, INIT
The code file required to initialize the Cold start the system. If
DNET-020 WARN Code file read failed board cannot be read. the problem persists, INIT
Cold start the system. If
the problem persists, INIT
start and reload the
Code file checksum There is a problem with the DeviceNet DeviceNet Interface
DNET-021 WARN error scanner code file. option. If the problem
Turn the controller off.
Make sure the
motherboard is correctly
Board initialization The board initialization routine has seated on the back plane.
DNET-022 WARN timeout timed out. Cold start the controller. If
Cycle power to the
controller. If the problem
persists, turn the
Board initialization An error has occurred in the board controller off and check
DNET-023 WARN error initialization process. the motherboard
Turn the controller off
A data mismatch has occurred such and cold start the
that the system cannot find a device controller. If the problem
No device assigned for assigned for the specified board persists, delete the board
DNET-025 WARN Bd/MAC number and MAC Id. from the Board List
Check the selected device
type on the Device List.
The system cannot find the specified Next, check the Defined
No match on dev type device type in its list of defined device Device List and the
DNET-026 WARN look-up types. Standard Device
Make sure the device is
properly connected to the
The device at the specified board network. Check the
PAUSE. Dev online err: Bd %d number and MAC Id cannot be brought device's MAC Id and baud
DNET-027 G MAC %d on-line. rate configuration. Check
Make sure the board is
PAUSE. The specified board cannot be brought network. Check that
DNET-028 G Board online err: Bd %d on-line. network power is being
Too many deferred The system has received the maximum Attempt to remedy any
DNET-029 WARN errors number of DeviceNet errors it can errors that are displayed,
PAUSE. Std dev file fmt err: Line There is an error in the format of the Contact your FANUC
DNET-030 G %d specified device definition file, on the Robotics technical
PAUSE. App dev file fmt err: There is an error in the format of the Contact your FANUC
DNET-031 G Line %d specified device definition file, on the Robotics technical
When a device has been added to a Cycle power to the
PAUSE. Device not ready: Bd scan list, it cannot be brought online controller. You will then
DNET-032 G %d MAC %d without cycling power to the controller. be able to bring the
An unknown keyword has been found Contact your FANUC
DNET-033 WARN Unknown keyword in the device definition files. Robotics technical
The user must turn power off and on to Cycle power to the
Cycle power to bring the controller to bring online a newly- controller. You will then
DNET-034 WARN online added device to a board's device list. be able to bring the
Bad format or out of An integer value in the device definition Contact your FANUC
DNET-035 WARN range files is incorrect. Robotics technical
No NINPUTS or The specified line was not found in a Contact your FANUC
DNET-036 WARN NOUTPUTS line device definition file. Robotics technical
The specified line was not found in a Contact your FANUC
DNET-037 WARN No PDTCODE line device definition file. Robotics technical
No MODULE lines with The specified lines were not found in a Contact your FANUC
DNET-038 WARN MULTIMOD device definition file. Robotics technical
Too many MODULE The specified lines were incorrect in a Contact your FANUC
DNET-039 WARN lines device definition file. Robotics technical
MODULE specified w/o A definition was incorrect in a device Contact your FANUC
DNET-040 WARN MULTIMOD definition file. Robotics technical
A definition was incorrect in a device Contact your FANUC
DNET-041 WARN Required field missing definition file. Robotics technical
No DEVTYPE line The specified line was not found in a Contact your FANUC
DNET-042 WARN supplied device definition file. Robotics technical
No VENDORID line The specified line was not found in a Contact your FANUC
No PRODCODE line The specified line was not found in a Contact your FANUC
No I/O mode line The specified line was not found in a Contact your FANUC
No PDTCODE line The specified line was not found in a Contact your FANUC
PAUSE. DeviceNet The DeviceNet motherboard is not and make sure the
DNET-047 G motherboard not found plugged into the back plane. motherboard is properly
The device definition file has too many Remove the DEFAULT
Multiple DEFAULT I/O access modes designated as designation from all I/O
DNET-048 WARN modes; ignored DEFAULT. Only one mode should be access modes except one.
Supply a device name
along with the device
Text based device definition does not definition and then use
DNET-049 WARN Device Name not found have the device name for the device. the text based device
An problem has occurred with the
specified daughter board or the Refer to the next DNET
DeviceNet network connected to it. The alarm posted in the alarm
Board or network problem is not severe enough to log for specific alarm
DNET-050 WARN warning: Bd %d disrupt communications, but should be recovery information.
The DeviceNet scanner has detected an Check your network
abnormal number of communications topology to ensure
errors on the network. This message is conformance with
Netwk comm errors: a warning that the scanner may go DeviceNet standards.
DNET-051 WARN Bus warning offline if errors continue to occur at an Check that your network
The specified line was incorrect in the Contact your FANUC
DNET-052 WARN Data line too long device definition file. Robotics technical
Check the Standard
Device Definition List to
Line above DEVICE line An extraneous line was found in a see if device types have
DNET-053 WARN ignored device definition file. been properly loaded. If
Contact FANUC Robotics
to report the problem.
All space in shared RAM There is no space left in the DeviceNet Provide all details of the
DNET-054 WARN used I/O buffer. DeviceNet network,
An error has occurred with the Refer to the Cause and
PAUSE. Board or network error: specified daughter board or the Remedy of the cause code
DNET-055 G Bd %d DeviceNet network connected to it. (displayed immediately
Check the cable
Power has been removed from the connecting the daughter
DNET-056 WARN Network power lost DeviceNet network. board to the DeviceNet
Check that the board's
baud rate corresponds to
A network communications error has that of the devices. Check
Network occurred on the network connected to cable connections to both
DNET-057 WARN communications error the specified board. the board and devices.
The problem may be
momentary; attempt to
The board has received more messages bring the board on-line
DNET-058 WARN Message queue overrun than it can handle at one time. again. If the problem
The problem might be
momentary; attempt to
The board has missed a message over bring the board on-line
DNET-059 WARN Message lost the DeviceNet network. again. If the problem
Check that the board
The traffic on the DeviceNet network is baud rate agrees with the
Xmit timeout: Network too heavy for the board to baud rate of the devices.
DNET-060 WARN flooded communicate with the devices. If no baud rate problem
Check cable connections
All of the devices expected by the to the board and to the
No other nodes on board to be on the network appear to devices. If a device has
DNET-061 WARN network be disconnected to the network. been disconnected,
Check that the baud rate
of the board and of the
The board is not communicating to the devices is the same. Make
Bus off due to comm network because there are too many sure that power is
DNET-062 WARN errors errors. connected to the
An error has occurred with the device Refer to the Cause and
PAUSE. Device error: Bd %d at the specified board number and Remedy for the cause
DNET-063 G MAC %d MAC Id. code (displayed directly
of the device agrees with
the board baud rate.
An error has occurred when attempting Check that the device is
DNET-064 WARN Connection error connection to the specified device. properly connected to the
Delete the device from
The vendor Id for the device, as the Device List. Check the
specified in the device definition, is device documentation for
DNET-065 WARN Incorrect vendor Id incorrect. the correct vendor Id.
The product code for the device, as the Device List. Check the
DNET-066 WARN Incorrect product code incorrect. the correct product code.
The device type for the device, as the Device List. Check the
DNET-067 WARN Incorrect device type incorrect. the correct device type.
Check the device's
connection to the
The connection to the specified device network. Make sure the
DNET-068 WARN Device timeout has timed out. device baud rate agrees
PAUSE. Unknown error code An unknown error has occurred with led to the error and call
DNET-069 G %d the specified device. your FANUC Robotics
of the device agrees with
the board baud rate.
Connection allocation An error has occurred when attempting Check that the device is
DNET-070 WARN error connection to the specified device. properly connected to the
Re-configure the DIP
You have two or more DeviceNet switches on your daughter
PAUSE. Dup dbrd: Bd:%d daughter boards with the same board boards so that you no
DNET-071 G Mbd:%s number configuration. longer have duplicates.
This cause code is posted together with
DNET-071 above to allow the user to Please see the Remedy
Found dupl. DNet easily identify the duplicate daughter text for DNET-071 to fix
DNET-072 WARN daughterboard board. Please see the Cause text for this problem.
View the module list for
the device and delete or
The system could not find the module change the module in
No match on mod type type corresponding to a module on the question. If this module
DNET-073 WARN look-up specified device. was previously functional,
An I/O configuration file (.IO file)
PAUSE. containing DeviceNet configuration Reload the .IO file at
DNET-074 G Load only
arsize mismatin
ctrl start data was loaded at COLD START. The controlled start.
DNET-075 WARN dntkmary.copy_array
$DN_DEV_DEFS array is There is no more room in the Defined Delete any unneeded
DNET-076 WARN full Device List system variable. device definitions from
DNet I/O inactive at At controlled start, I/O data assigned to This message is for
DNET-077 WARN CTRL start DeviceNet devices is not active. informational purposes
If there are devices which
are off-line, delete these
No room for more The system variable for storage of devices unless they are
DNET-078 WARN devices devices is full. required to be kept on the
This error occurs during
the I/O restore. Cold start
PAUSE. Unknown dev type: Bd The device type used by this device is the controller, add a new
DNET-079 G %d MAC %d currently unknown to the system. device definition
PAUSE. The previous I/O configuration contains Make sure you have the
DNET-080 G Loaded config too large too many modules, devices, or device same memory
This message appears when a board Pressing RESET will
automatically restarts communication attempt reconnection
with a DeviceNet network, but some or with the non-
Press RESET to all devices are not designated as communicating devices
DNET-082 WARN reconnect autoreconnecting. Pressing RESET will and clear this message.
A board which was previously in error This message is intended
Board %d auto- state has automatically restarted for user notification only
DNET-083 WARN restarted communications with the DeviceNet and does not indicate the
Refer to the Cause and
PAUSE. Board reset failed: Bd The command to reset the specified Remedy for the cause
DNET-084 G %d board has failed. code (displayed directly
PAUSE. Dev reset failed: Bd %d The command to reset the specified Remedy for the cause
DNET-085 G MAC %d device has failed. code (displayed directly
The specified board is unable to Check DeviceNet
PAUSE. Stop scan cmd failed: acknowledge the stop-scanning connection to the board,
DNET-086 G Bd %d command. as well as DeviceNet
Check DeviceNet
PAUSE. Bd offline cmd failed: The board is not acknowledging the connection to the board,
DNET-087 G Bd %d command to take it off-line. as well as DeviceNet
Make sure the device
The system does not recognize the definition data files are
PAUSE. Ignored: Bd %d MAC %d module type of the module being the same between the
DNET-088 G Slot %d loaded. current system being
Can't specify POLL and The data file contains lines which Contact FANUC Robotics
DNET-089 WARN STROBE specify both POLL access and STROBE to obtain the correct
Can't STROBE w/ num The device definition file specifies a Contact FANUC Robotics
DNET-090 WARN outs > 0 strobed-access device but the number to obtain the correct
The number of inputs specified in the Delete the device, correct
device definition for this device does the device definition, then
DNET-091 WARN Input size error not match the number expected by the re-add the device to the
The number of outputs specified in the Delete the device, correct
device definition for this device does the device definition, then
DNET-092 WARN Output size error not match the number expected by the re-add the device to the
The scanner board encountered an Check that the device
DNET-093 WARN Error reading vendor ID error while trying to read the device's baud rate matches the
Error reading device The scanner board encountered an Check that the device
DNET-094 WARN type error while trying to read the device's baud rate matches the
Error reading product The scanner board encountered an Check that the device
DNET-095 WARN code error while trying to read the device's baud rate matches the
The scanner board encountered an Check that the device
Error setting packet error while trying to set the baud rate matches the
DNET-096 WARN rate communication packet rate for this board baud rate. Check
The board was unable to achieve Check that the device
synchronization in the connection with baud rate matches the
DNET-097 WARN Connection sync fault the specified device. board baud rate. Check
Check that the board
DNET-098 WARN BROWSE
NULL cmdfailed
error ret'd by The BROWSE operation failed. status is ONLINE. Check
DNET-100 WARN board
CMD cmd error ret'd by
DNET-101 WARN board
Check the Board Detail
screen to see if the
board's MAC Id is
The board's MAC Id is not between 0 between 0 - 63, inclusive.
DNET-102 WARN Invalid board MAC Id and 63. If it is not, change the
Check the Board Detail
screen to see if the
board's baud rate is one
The board's baud rate is not one of: of the above values. If it is
DNET-103 WARN Invalid board baud rate 125 KB, 250 KB, or 500 KB. not, change the baud rate
Check that no other
devices have the same
MAC Id, particularly those
The specified device has the same MAC connected to a different
DNET-104 WARN Duplicate MAC Id error Id as another device on the network. master on the same
If the desired device is
There was an attempt to add a device already on the network
to the board's device list that was a and a second one is not
DNET-105 WARN Duplicate device error duplicate of a device already on the list. being added, you may
Check that the device is
connected to the
network. Check that the
A device expected to be on the device baud rate matches
DNET-106 WARN Device not found error network was not found. the board baud rate.
Press RESET on the teach
pendant to attempt to
The board could not perform an bring the board on-line. If
DNET-107 WARN Bus offline error operation because the bus was off-line. the problem persists,
The board could not perform an Take the board off-line
DNET-108 WARN Scanner active error operation because the it is actively and re-attempt the
DNET-109 WARN Bus not offline error operation because the bus is not off- and re-attempt the
DNET-110 WARN Error: board scanning operation because the it is actively and re-attempt the
Error: board not The board could not perform an Bring the board on-line
DNET-111 WARN scanning operation because the it is not actively and re-attempt the
An attempt to bring the board on-line Wait ten seconds and re-
Board not ready; pls. was unsuccessful because the board attempt to bring the
DNET-112 WARN wait
OFFSET cmd err ret'd by was busy. board on-line. If the
DNET-113 WARN board
of the board matches the
The board has detected a fault on the baud rate of all devices on
DeviceNet network, and cannot the network. Also, check
DNET-114 WARN Bus fault error detected communicate with devices. that power is being
Invalid I/O connection A device does not support the Check the device
DNET-115 WARN Invalid
attemptexp. msg. buffer requested I/O connection(s). and documentation to ensure
DNET-116 WARN size
Invalid strobe buffer
DNET-117 WARN size
Invalid connect path
DNET-118 WARN buffer
Check it the Interface is
not the only node on the
PAUSE. Ack Fault-No acknowledge received network. Check the
DNET-119 G Dup. MAC Ack Fault during Duplicate MAC ID sequence. baudrate of the interface
Make sure the device is
The device at the specified board network. Check the
Dev online err: Bd %d number and MAC Id cannot be brought device's MAC Id and baud
DNET-120 WARN MAC %d on-line. rate configuration. Check
When a device has been added to a Cycle power to the
Device not ready: Bd scan list, it cannot be brought online controller. You will then
DNET-121 WARN %d MAC %d without cycling power to the controller. be able to bring the
An error has occurred with the device Refer to the Cause and
Device error: Bd %d at the specified board number and Remedy for the cause
DNET-122 WARN MAC %d MAC Id. code (displayed directly
Dev reset failed: Bd %d The command to reset the specified Remedy for the cause
DNET-123 WARN MAC %d device has failed. code (displayed directly
This message appears when a board Pressing RESET will
automatically restarts communication attempt reconnection
with a DeviceNet network, but some or with the non-
Device not autorec: Bd all devices are not designated as communicating devices
DNET-124 WARN %d MAC %d autoreconnecting. Pressing RESET will and clear this message.
The slave connection of the specified Make sure the remote
board is idle The remote Master has Master is online and
DNET-125 WARN Slave Conn. Idle: Bd %d not yet connected to the slave configured properly.
PAUSE. An invalid parameter has been Refer to the cause code to
DNET-130 G Invalid parameter specified for a DeviceNet KAREL built- determine which
Make sure the board
DNET-131 WARN Invalid board number The specified board number is invalid. number is an integer
Make sure the MAC ID is
DNET-132 WARN Invalid MAC ID The specified MAC ID is invalid. an integer between 0 and
This indicates that there is a user device
definition on the system that matches
the one supplied using text-based This error is for display
definitions except for the I/O size. A only. No action is
DNET-133 WARN I/O Size mismatch match is indicated by name, vendor id, required.
The text-based device definition has
matched with an existing user This error is for display
definition on the robot except for the only. No action is
DNET-134 WARN Mode mismatch mode of operation. A match is required.
There is a user defintion on the system
that matches one of the entries in the
text-based user definition except the
size of analog input/outputs. A match is This is for display only. No
DNET-135 WARN Analog size mismatch indicated by name, vendor id, product action is
Please required.
check
DNET-136 Name does not match Please check MD:DNDEF.DG MD:DNDEF.DG
The text-based device definition
matches one that exists on the This error is for display
controller, except for the name and only. No action is
Name and Analog do number of analog points. Any entry required. 3.3.6 DX Alarm
DNET-137 WARN not match that has the same vendor id, product Code
A DevicNet channel has been
configured for safety. A safety Use DN4 DeviceNet
IDNS unsupported DeviceNet channel requires DN4 hardware or disable safety
DNET-138 H/W, Bd %d hardware. The detected hardware is on this channel.
Please check the 1st
DTBR-001 host name is null string Specified host name is null string. argument. If SR is used,
Communication with specified host Please make sure
DTBR-002 RPC Call timed out took time and timeout happend. newtwork is working
Ethernet connection to specified host Please make sure
DTBR-003 Connection failed failed newtwork is working
Bad variable or register Specified register or position register Please check parameter.
DTBR-014 index (%s^7) does not exist on remote host. Please check valid range
Illegal group Specified group does not exist on Please check parameter.
DTBR-015 PAUSE. number(%s^7) remote host. Please check valid range
DX-000 G Unknown error (DX00)
PAUSE. The Delta Tool/Frame global variables Check the application
DX-001 G
PAUSE. No global
Error variables
allocating data have NOT been properly loaded. installation manual for the
DX-002 G memory
Check the application
PAUSE. Delta Tool/Frame system variables (e.g. installation manual for the
DX-003 G No system variables $DXSCH[]) not found. proper installation
Check all schedule
PAUSE. Invalid Delta Tool/Frame schedule numbers used within the
DX-004 G Illegal schedule number number. specified program to
Schedule already Requested Delta Tool/Frame schedule Use END_OFFSET or abort
DX-005 WARN enabled number has already been enabled. program to disable
Check to see if the
Try to disable a schedule which has not requested schedule has
DX-006 WARN Schedule not enabled been enabled. been disabled before, or
Check to see if the
PAUSE. Try to apply offset to a schedule which requested schedule has
DX-007 G
PAUSE. Schedule not enabled Internal
has not been
error:enabled.
cannot find dxfndofs been disabled before, or
DX-008 G Internal error schedule. Notify FANUC Robotics.
PAUSE. Wrong packet was sent to INTP to
DX-009 G Internal error signal completion of updating $DXMOR Notify FANUC Robotics.
PAUSE. DeltaJ DeltaT/F Attempt to enable deltajoint with Do not enable deltajoint
DX-010 G incompatible deltatool and/or deltaframe in a with deltatool and/or
PAUSE. DeltaT DeltaF Attempt to enable deltatool with Do not enable deltatool
DX-011 G incompatible deltaframe in a schedule. with deltaframe in a
PAUSE. Specified group already The specified motion group has been Abort the enabled DX
DX-012 G
PAUSE. enabledrobot link group already enabled by DX function.
Invalid function before this start.
DX-013 G tracking
PAUSE. Invalid offset The calculated offset orientation of this Decrease the speed of the
DX-014 G orientation time is out of range specified by Master robot or Check the
PAUSE. The calculated offset distance of this Decrease the speed of the
DX-015 G
PAUSE. Invalid offset distance time is out of range specified by Masterchange
Don't robot UT
or Check
of the
DX-016 G UT is changed UT of master robot is changed. master during robot link.
DX-040 WARN Notify FANUC Robotics
Check Memory usage
DX-042 WARN and Delta Tool/Frame
ELOG-000 WARN error parameter is
ELOG-001 WARN losted
ELOG-002 WARN out buffer size is short
ELOG-003 WARN parametersize
parmeter sizeover
is long
ELOG-004 WARN packet sizesize over
parmeter
ELOG-005 WARN packet size
ELOG-006 WARN typecodenot
severity is illegal
included in
ELOG-007 WARN error
ELOG-008 WARN
Perform a cold start: 1.
and hold the SHIFT and
ELOG-009 WARN call a service man A system
This is theerror has error
internal occurred.
code for clear RESET keys. 3. While still
ELOG-010 WARN error message. NONE
Power off, if you want A system error has occurred. A system and hold the SHIFT and
ELOG-011 WARN to recover. error has occurred. RESET keys. 3. While still
A system error has A system error has occurred A system and hold the SHIFT and
ELOG-012 WARN been occurred.
PAUSE. error has
Failed occurred.
to get the pointer of a system RESET keys.
Record error3.and
While still
report
ELSE-001 G Failed to VMGTSYSV variable. to hotline.
PAUSE. Failed to OSCONTSK Record error and report
ELSE-002 G
PAUSE. with
FailedPUMN
to OSRCVPKT Failed to connect
receive awith PUMN
packet fromtask.
LNTK to hotline.
ELSE-003 G
PAUSE. from LNTK
Failed to OSSNDPKT to softpart. to hotline.
ELSE-004 G
PAUSE. PUMN
Failed to OSRCVPKT Failed to send a packet
receive to from
a packet PUMN task.
PUMN to hotline.
ELSE-005 G
PAUSE. from PUMN
Illegal OSRCVPKT from task.
Received a illigal packet from PUMN to hotline.
ELSE-006 G
PAUSE. PUMN task. to hotline.
ELSE-007 G Failed
UNUSED to ERROR
OSDLTPKT Failed to delete a packet. to hotline.
FIG-000 WARN
PAUSE. CODE(FCT00)
Receive an unkown
FIG-001 LPAUSE. packet
Execution by inactive
FIG-002 LABORT. PXNN
Can't create FCT
FIG-003 LABORT. programs
Can't delete FCT
FIG-004 LABORT. programs
Can't create FCT work
FIG-005 LPAUSE. data
Fail to execute Fig
FIG-006 LPAUSE. statement Case: Motion statment of program has
FIG-010 L Parameter error not parameter Set up parameter
PAUSE. Case: L1 and L2 is differ L2
FIG-011 L L1,L2 is different is longer than L1 This
Case: Length and Width is
PAUSE. Length,Width is differ Width is longer than
FIG-012 L different length This figule don't
PAUSE. Case: R is longer than
FIG-013 L R is different Width This figule don't
PAUSE. Case: L1 is too short BRC is
FIG-014 L L1 is short differ This figule don't
PAUSE. Case: Length is too short
FIG-015 L Length is short BRC is differ This figule
PAUSE. Case: L1 is too long BRC is
FIG-016 L L1 is long differ This figule don't
PAUSE. Case: Length is too long
FIG-017 L Length is long BRC is differ This figule
PAUSE. Case: L2 is too short BRC is
FIG-018 L L2 is short differ This figule don't
PAUSE. Case: Width is too short
FIG-019 L Width is short BRC is differ This figule
PAUSE. Case: L2 is too long BRC is
FIG-020 L L2 is long differ This figule don't
PAUSE. Case: Width is too long
FIG-021 L Width is long BRC is differ This figule
PAUSE. Case: $FCMIN_INTR is too
FIG-022 L $FCMIN_INTR is short short $FCMIN_INTR is
PAUSE. Case: $FCMIN_INTR is too
FIG-023 L
PAUSE. $FCMIN_INTR is long long $FCMIN_INTR
Case: is
BRC is differ Change
FIG-024 LPAUSE. BRC is short BRC
Case: BRC is long BRC is
FIG-025 LPAUSE. BRC is long differ MJ
Case: Change BRC then
is longer
FIG-026 LPAUSE. MJ is different circuitMJ
Case: MJisisshort
differMJ
Change
is
FIG-027 LPAUSE. MJ is short differ Change MJ
Case: This figule don't
FIG-028 L Figure not write write confirm each
Case: Cutting time turn
FIG-029 WARN
PAUSE. Don't effective Lof
Index value code is out
Case:long,
Thisindata
the number
case
FIG-030 LPAUSE. different don't set up
FIG-031 L Speed value is different Changesetup
Case: Group speedisvalue
FIG-032 WARN Group setup is wrong wrong
PAUSE. Case: Speed unit don't set
FIG-033 L
PAUSE. Speed unit is different up SetMJ
Case: upisspeed
long MJunitisin
FIG-034 L MJ is long differ Chang MJ
PAUSE. Case: Diameter is too long
FIG-035 L Diameter is long BRC is differ This figule
Check if the device is
FILE-001 WARN Device not ready Specified file device is not ready. mounted and ready to
Device is full. There is no more space to Delete any unnecessary
FILE-002 WARN Device is Full store data
Device on the device.
is protected. So, you cannot files or change
Release to a new
the device
FILE-003 WARN Device is protected write to the device. protection.
Device is not assigned to the LUN. The
FILE-004 WARN Device not assigned specified device is not recognized by System error.
Device is not mounted. You should Mount the correct file
FILE-005 WARN Device not mounted mount the device before using it. device.
Device is already You tried to mount the device which
FILE-006 WARN mounted had been already mounted. Mount device only once.
This is an internal error.
FILE-007 WARN Illegal device number Illegal device
Device number isanused.
name contains illegal the validity
Check spelling andof the
validity
FILE-008 WARN Illegal device name character. of device name.
Illegal logical unit This is an internal error.
FILE-009 WARN number Illegal LUN is used. Check the validity
validity of the
of directory
FILE-010 WARN Directory not found Specified directory does not exist name.
Directory is full. You tried to create a
file in the root directory which Delete unnecessary files in
FILE-011 WARN Directory full execeeded
You tried tothe maximum
write number
to a write of
protected the rootthe
Release directory.
protection to
FILE-012 WARN Directory is protected directory.
Directory name contains an illegal the directory.
Check spelling of directory
FILE-013 WARN Illegal directory name character. name.
Check that the file exists
FILE-014 WARN File not found The specified file was not found. and thatthe
Release theprotection
file name
FILE-015 WARN File is protected You tried to access a protected file. from file.
FILE-016 WARN File cannot expand You tried to access a file which is not Open the file before
FILE-017 WARN File not open open. accessing.
You tried to create/delete/rename a Close file before such
FILE-018 WARN File is already opened file
Youwhich
tried tois already
access aopened.
file which is operations.
FILE-019 WARN File is locked locked. Release file
Change the size
lock.to be
FILE-020 WARN Illegal file size File size is invalid. correct.
FILE-021 WARN End of file End of file was detected. do notspelling
Check have to of dofile
FILE-022 WARN Illegal file name File name contains an illegal character. name.
Use a valid file number
FILE-023 WARN Illegal file number File number is illegal. which is
Check thethe ID returned
spelling and
FILE-024 WARN Illegal file type File type contains an illegal character. Check
validityifof the
the file type.
protection
FILE-025 WARN Illegal protection code File protection code is illegal. code is correct.
Check if the access mode
FILE-026 WARN Illegal access mode File access mode
attribute is illegal.
in the SET_ATTRIBUTE is correct.
Check that attribute
FILE-027 WARN Illegal attribute request is illegal. specified is valid.
Data block is broken which is used in You should keep the data
FILE-028 WARN Illegal dataisblock
Command not FIND_NEXT request. block which
Check is returned
if the request code
FILE-029 WARN supported Illegal request command is specified. is corect.
Dismount any
FILE-030 WARN Device lun table is full Device
Path management
name contains an table is full.
illegal unnecessary
Check devices.
if the path name is
FILE-031 WARN Illegal path name character. correct.that all parameters
Check
FILE-032 WARN Illegal parameter Illegal parameter is detected. for the request are valid.
FILE-033 WARN System file buffer full File management buffer is full. Close unnecessary files.
Check that the file
FILE-034 WARN Illegal file position Illegal
You file to
tried position
accessisa specified.
unformatted positionthe
Format parameter from
device before
FILE-035 WARN Device not formatted device. using it.
You tried to rename a file to an already Change the new file name
FILE-036 WARN File already exist existing file name. to be unique or delete the
You tried to remove a subdirectory Remove all files and
FILE-037 WARN Directory
File lockednot by empty which are
too many There contains somelock
too many filesrequests
or to directories
Unlock any in the
unnecessary
FILE-038 WARN tasks same file. file lock requests.
You tried to create a sub-directory that Use a unique name for
FILE-039 WARN Directory already exists already exists. new sub-directory
You tried to read from a write only Open a file with correct
FILE-040 WARN Illegal file access mode opened file or tried to write to a read access mode.
You tried to unlock file which you had Don't unlock a file that is
FILE-041 WARN (File
thisnot locked
is an internal not locked. not locked.
This is not anYou can only
error.
FILE-042 WARN code) None System use only.
There are too many requests in File Retry request after other
FILE-043 WARN Context table is full System. File access management data access finished.
Not enough C-work System error. Try a COLD
FILE-044 WARN memory internal c-work memory is insufficient. start to recover c-work
need to set $FILE_MAXSEC has not been set and Set variable
FILE-045 WARN
PAUSE. $FILE_MAXSEC
Memory allocation must be be set before device can be $FILE_MAXSEC to valid
FILE-046 G
PAUSE. error send/recieve
Packet
FILE-047 G
PAUSE. error
FILE-048 G Internal phase error
A file operation has been attempted on Use a standard file device
FILE-049 WARN File is not%s
PChamp standard file PChamp
device NOT a file which is notdevice
output a standard file or
NOT ready (e.g., FR:
Check or RD:
device OR delete
FILE-050 WARN ready - device FULL FULL old files on device
A call to kread was made while a Do not call kread again
FILE-051 WARN NESTED kread issued WOULDBLOCK read was pending until the packet from the
Kread re-call with A call to kread was made following a Call kread with the same
FILE-052 WARN different buf_p WOULDBLOCK read with a different buf_p as was used in the
Memory Card (MC) has been inserted Start MC access after
FILE-053 WARN MC Inserted and
Memoryproperly
Carddetected
(MC) hasby the removed
been system receiving this message
Reinstall Memory Card if
FILE-054 WARN MC Removed from the system you wish to continue
Either the Memory Card (MC) is not Either insert a MC or
properly inserted or the Card that is exchange inserted card
FILE-055 WARN MC not detected inserted is not a Memory Card type with a MC
Modem Card has been inserted and Start Modem Card access
FILE-056 WARN Modem Card Inserted Modem properlyCard detected by the
has been system from Reinstall
removed after receiving
Modem thisCard if
FILE-057 WARN Modem Card Removed the system you wish to continue
Illegal Character in Remove any non alpha
FILE-058 WARN Name Name contains an illegal character. numeric character which
Try one of the following:
Not enough TEMP 1. Remove unnecessary
memory for file The TEMP memory is too low to files/programs from the
FILE-059 WARN operation complete the file operation. system. 2. Remove
Requested RD Size (Req) exceeds Max Adjust $FILE_MAXSEC
FILE-060 WARN Max %d,Req %d,Ac %d Available (Max). RD Left at Actual Size Memory Size (Req) to less
Requested RD Sz too The requested RD Size (Req)exceeds Adjust $FILE_MAXSEC
FILE-061 WARN big the Max Available (Max). RD Left at Memory Size (Req) to less
Backup files are not Try performing the file
FILE-062 WARN correct The backup file is not correct. backup operation to
The indicated file is not loaded when all Check cause code for
FILE-063 STOP (%s) is not loaded filesunusual
An are restored in Automatic
File System Software
error has more information.
occurred. This alarm should rarely
occur. The number after the error text
indicates: 50 -- Device was removed
and replaced before flush 51 -- Driver
reports that the device is not working Retry the operation. If the
52 -- Trying to access a drive that alarm consistently occurs
wasn't initialized 53 -- Driver reports then manually check that
that the device is empty 54 -- Driver the files were read,
reports that the device is not written, etc. Using a
recognized 60 -- No signature found in personal computer check
BPB (need to format) 61 -- No signature the media with a Check
found in MBR 62 -- Partition requested Disk or Error-checking
but none at that offset 63 -- IO error tool. If reporting the
reading MBR (note: MBR is first to be alarm to FANUC America
read on a new insert) 64 -- IO error Corporation, be sure to
Unspecified DOS system reading BPB (block 0) 65 -- IO error include the number that is
FILE-064 error:%d reading FAT32 INFO struc (BPB provided.
An unexpected internal File System Retry the operation. If the
error has occurred. This alarm should alarm consistently occurs
occur very rarely. The number after the then manually check that
error text indicates: 100 -- Unexpected the files were read,
block number encountered, use a written, etc. Using a
check disk 101 -- Unexpected cluster personal computer check
encountered, use a check disk 102 -- A the media with a Check
Internal DOS system specified path that must be a directory Disk or Error-checking
FILE-065 error: %d was not. 103 -- Unexpected condition, tool. If reporting the
The USB memory stick has been Start UDx: access after
FILE-066 WARN UD%d Ins %s %s inserted and properly detected by the receiving this message.
The USB memory stick has been Reinstall the memory stick
FILE-067 WARN UD%d Removed removed from the system. if you want to continue.
Either the USB memory stick is not Try removing and
FILE-068 WARN UD not detected properly inserted or the stick that is reinserting the memory
A USB hub was inserted and properly Start using the USB hub
FILE-069 WARN USB hub Ins %s %s detected by the system. after receiving
Reinstall thishub if
the USB
FILE-070 WARN USB vend:
hub Removed
%04x prod: A USB hub was removed. you want to continue to
FILE-071 WARN %04x USB device details
USB over current The attached USB devices are drawing Reduce the power draw
FILE-072 WARN detected more than 500mA of current. by removing some
FILE-073 WARN USB error %d General error
The USB device is not supported on this Document the events that
FILE-074 WARN USB not supported hardware. led to the error, and call
The appropriate media is not inserted Insert the appropriate
No media inserted or or properly inserted, or the media that media, such as a USB
FILE-075 WARN detected is inserted is not of the correct type. memory stick or a
%s invalid sector size The device has an invalid sector size
FILE-076 %d and can not be used by the file system. Try a different device.
FILE-077 Auto backup start (%s) Auto backup start. None.
FILE-078 Auto backup complete Auto backup was finished. None.
FILE-079 Error Auto backup %s Error occurred at Auto backup Check
FILE-080 Backup in progress Auto backup in progress Auto backup Check
The named file failed to be read and led to the error, and
FILE-081 Load fail %s (%d,%d) loaded correctly. contact your FANUC
This occurs with the alarm: Backup file Find this file in an older
Backup file not found: is not correct. This alarm indicates the backup or maybe on
FILE-082 %s file or one of the files that was not another controller and
This occurs with the alarm: Backup file Find this file in an older
A Backup file is empty: is not correct. This alarm indicates the backup or maybe on
FILE-083 %s file or one of the files that was found to another controller and
Retry the operation. If the
alarm consistently occurs
The format operation The device has some problem or is then try a different
FILE-084 failed worn out. device. Using a personal
CHKDSK has determined that the file Contact FANUC America
FILE-085 chkdsk %s device has an error. Corporation or FANUC
FILE-086 Failed to save MC: Failed to save MC:. This is just message.
FILE-087 Failed to save UD1: Failed to save UD1:. This is just message.
FILE-088 Failed to save UT1: Failed
USB to save
device keyUT1:.
board is installed and This
It is just message.
is possible to use USB
FILE-089 USB kb Ins %s %s detected. device key board.
Connect the USB device
FILE-090 USB kb Removed key board
USB device mouse is removed.
is installed and key
It is board
possibleagain if you
to use USB
FILE-091 USB mouse Ins %s %s detected. device mouse.
Connect the USB device
FILE-092 USB mouse Removed USB device mouse is removed. mouse again if you want
A parity error was detected in the USB led to the error, and
FILE-093 USB ram parity controllers ram. contact your FANUC or
An error occurred with DMA transfer Document the events that
from or to the USB controllers RAM. It led to the error, and
FILE-094 USB ram dma %d was then done without DMA. contact your FANUC or
FlexTool global variables are not Perform a controlled start
FLEX-001 WARN Fail to get
Invalid memory area loaded.
selected and initialize
Correct motion
selected axis
FLEX-002 SERVO axis(G:%d) Invalid selected axis number number
End of directory Your listing has reached the end of the This is a notification. You
FLPY-001 WARN reached directory. You do not have to do do not have to do
The file name you are trying to create Delete the file of this
FLPY-002 WARN File already exists already exists on this device. name or choose a
The file you are trying to open does not Open a file that does exist
FLPY-003 WARN File does not exist exist on this
Operation is device.
not supported on floppy on
Usetheonlydevice.
operations
FLPY-004 WARN Unsupported command disk. supported on floppy disk.
Delete some unneeded
FLPY-005 WARN Disk is full The disk filethe
end of capacity has
file was been reached.
reached while files
Do notor use a disktowith
attempt read
FLPY-006 WARN End of
Only filefile
one reached
may be reading.
An attempt was made to open more beyond
Do the end to
not attempt of open
a file.
FLPY-008 WARN opened than one file. more than one file at a
FLPY-009 WARN Communications error The protocol format was invalid. Retry the operation.
Write protection Remove write protection
FLPY-015 WARN violation disk has write
The directory protection
information enabled.
is corrupted fromanother
Try the diskdisk
or use
or a disk
FLPY-100 WARN Directory read error and unreadable. reformat the disk.
The checksum data is bad. Data is Try another disk, or
FLPY-101 WARN Block check error corrupted on disk and can not be read. reformat the disk
There is a bad sector or track on the Clean the disk drive, try
FLPY-103 WARN Seek error disk. another disk, or reformat
The drive did not respond to a Check the cable to the
FLPY-104 WARN Disk timeout command. drive and make sure drive
FLPY-105 WARN violation The disk has write protection enabled. from the disk or use a disk
Memory Card hardware Memory Card hardware error is Check Memory Card I/F
FLPY-106 WARN error detected. unit connection
Format the card or battery
with
FLPY-107 WARN Not formatted card The Memory Card is not formatted. UTILITY menu on FILE
PAUSE. 1. Turn the controller OFF.
FORC-001 G RISC board
Interface doesn't
board exist
doesn't Force control board doesn't exist. 2. Turn
1. Mount thethe force OFF.
controller
FORC-002 WARN exist
PAUSE. Force control error Force I/O board doesn't exist.
The error occurred from the force 2. Mount the force I/O
Refer to the manual for
FORC-003 G (F:%d^1, E:%d^2) control board. the force control board.
SYSTE The system cannot cammunicate with Please check the force
FORC-004 M Communication error the force control board. control board.
Force control board has been disabled Refer to the remedy of
FORC-005 WARN RISC board is disabled because of the alarm displayed at the the alarm displayed at the
Interface board is Force I/O board has been disabled Refer to the remedy of
FORC-006 WARN
PAUSE. disabled because
The of the
program alarmcontrol
cannot displayedtheat the Please
the alarm
checkdisplayed at the
the default
FORC-011 G
PAUSE. Force group mismatch specified motion group. motion groups in
Please check the force the
FORC-012 G Time out error occurred The system cannot start force control. control board.
PAUSE. The system cannot communicate with Please check the force
FORC-013 G
PAUSE. Communications error the force control board. control
Please setboard.
the correct tool
FORC-014 G Invalid tool number The tool number is set to 0. number.
PAUSE. Force sensor error As a result of the force sensor diagnosis
FORC-015 G exceed limit the error of the force sensor exceeded Replace the force sensor.
FORC-016 WARN Diagnosis normal end Force sensor is normal No action is required.
If you want to change the
PAUSE. Initial force sensor data already setting initial force sensor data,
FORC-017 G
PAUSE. Init data already set up up Please change
initializethethesystem
force
FORC-018 G
PAUSE. Uninitialized
Tolerance data
data is 0 or Initial force sensor data is uninitialized Please
sensor set
data.up the system
FORC-019 G
PAUSE. less error excess
Sensor Tolerance
The data is output
force sensor uninitialized
data is too variable
FORC-020 G (S:%d E:%X) large. Check the force sensor
PAUSE. Sensor index does not The force sensor which is specified by Please specified correct
FORC-021 G exist sensor index does not exist. sensor index.
An INSERTION instruction was executed Add an OFFSET
PAUSE. before an OFFSET CONDITION CONDITION instruction
FORC-022 G
PAUSE. Offsetsensor
Force value iserror
needed instruction. A position register was not Please before check
the INSERTION
the state of
FORC-023 G occurred Force sensor error has occurred. the force sensor.
PAUSE. Force control error The error occurred from the force Refer to the remedy of
FORC-024 G
PAUSE. occurred control board.
Cannot executeThe error jump
instruction is not
because the force
Select control alarm
appropriate
FORC-025 G Function type is unused Initial
Unused is selected.
force sensor data has been set function type.
FORC-026 WARN
PAUSE. Init data has been set now
Another tuning already Another tuning mode is already No actionanother
Remove is required.
tuning
FORC-027 G enabled enabled instruction
Please confirm the default
FORC-101 WARN incorrect The
Default data is not Selected default
default data data is not
still has notcorrect
been data ofselect
Please system thevariables
default
FORC-102 WARN selected selected data at the default
Please enter the index menu
FORC-103 WARN Index value is incorrect Index value is not correct value
Number of array is Number of array in selected default Please confirm the
FORC-104 WARN incorrect data is not correct number of array in the
The force group of program has not Please create this
FORC-105 WARN Force group is incorrect been existed in this system statement in this system
Mass data is out of The mass data which has been
FORC-106 WARN range calculated by entering data is out of Please enter proper data
Damper data is out of The damper data which has been
FORC-107 WARN range data is out of
Input calculated by entering data is out of Please enter proper data
FORC-108 WARN minimum
Input data is out of minimum range
The input data is out of maximum Please enter proper data
FORC-109 WARN maximum
Setting data is not range Please enter proper
confirm data
and enter
FORC-110 WARN enough The setting data has not been set yet proper the data
Number of array Mismatch the number of array data Please confirm the data
FORC-111 WARN mismatch
Program data is between
The forcethe
datasource data and
of selected default
program is and enter
Please proper
confirm thethe data
force
FORC-112 WARN incomplete
Specified data doesn't not complete data ofconfirm
Please selectedand
program
enter
FORC-113 WARN exist The specified data does not exist the proper data
Converted individual Because the ending condition switch is
FORC-114 WARN difference changed, the individual difference Verify the pushing depth
Modified bearing rotation axis or
Insert direction is groove direction is set to be the same Verify the insert direction
FORC-115 WARN changed as insert direction. This is impossible in in 'Basic Data'.
Bearing rot axis is groove direction is set to be the same Verify the bearing
FORC-116 WARN changed as insert direction. This is impossible in
rotation axis.
Cannot set phase match impedance Do auto tuning and set
FORC-117 WARN Auto tuning not done rate because auto impedance tuning is phase match impedance
Groove direction is Modified insert direction is the same as Verify the groove
FORC-118 WARN
PAUSE. changed groove direction. For this case, it direction.
Contact FANUC Robotics
FORC-130 G Illegal insert data index Software internal error. to report the error.
1. Move the robot to a
safe pose. 2. Turn the
controller OFF, then ON
PAUSE. F/S SLDM non response Communication with the I/O board again. If this alarm occurs
FORC-151 G error (F:%d^1) failed. again, go to the next step.
PAUSE. F/S SCL2 slave error Communication with the I/O board again. If this alarm occurs
FORC-152 G (F:%d^1) failed. again, go to the next step.
PAUSE. F/S SLC2 frmaing error Communication with the I/O board again. If this alarm occurs
FORC-153 G (F:%d^1) failed. again, go to the next step.
PAUSE. F/S SLC2 internal parity A parity error occurred on the interface safe pose. 2. Turn the
FORC-154 G error (F:%d^1) board. controller OFF, then ON
PAUSE. F/S SLC2 external parity A parity error occurred on the interface safe pose. 2. Turn the
PAUSE. F/S head data request The data request from the I/O board to again. If this alarm occurs
FORC-156 G error (F:%d^1) the sensor head failed. again, go to the next step.
PAUSE. F/S force data calc. safe pose. 2. Turn the
FORC-157 G overflow (F:%d^1) Software internal error. controller OFF, then ON
PAUSE. F/S gauge data overflow An output error occurred from the safe pose. 2. Turn the
FORC-158 G (F:%d^1) sensor head. controller OFF, then ON
1. Make sure that the
value of 'Insert Force' in
'Basic Data' is not too
PAUSE. F/S sensor limit An excessive load was put on the large. If not, go to the
FORC-159 G
PAUSE. overflow (F:%d^1) sensor head. next step. 2.orBad
Re-connect replace the
FORC-160 G F/S cable is cut (F:%d^1) Cable is cut. cable.
1. Turn the controller OFF,
then ON again. If this
PAUSE. F/S timeout error The force control board or the R-J3 alarm occurs again, go to
FORC-161 G (F:%d^1) main control board has failed. the next step. 2. Replace
PAUSE. F/S temperature data Temperature output error occurred in safe pose. 2. Turn the
FORC-162 G overflow (F:%d^1) the sensor head. controller OFF, then ON
PAUSE. F/S watch dog error Watchdog error occurred on the I/O again. If this alarm occurs
FORC-163 G (F:%d^1) board. again, go to the next step.
1. Check the temperature
around the sensor head. If
it is not low, go to the
PAUSE. F/S temp. lower limit The temperature measured at the next step. 2. Check the
FORC-164 G error (F:%d^1) sensor head is too low. sensor cable connectivity.
it is not high, go to the
PAUSE. F/S temp. upper limit The temperature measured at the next step. 2. Check the
FORC-165 G error (F:%d^1) sensor head is too high. sensor cable connectivity.
SYSTE SCRDY set error Contact the FANUC
FORC-167 M (F:%d^1) internal error service center and report
SYSTE HCRDY set error Contact the FANUC
SYSTE SCRDY reset error Contact the FANUC
SYSTE HCRDY reset error Contact the FANUC
1. Check the force sensor
output data on TP (Force
sensor status screen). The
PAUSE. F/S output data frozen The output data from the sensor head value must vary slightly
FORC-171 G (F:%d^1) is frozen (unchanging). over time due to sensor
PAUSE. F/S communication Communication failed between the again. If this alarm occurs
FORC-172 G error (F:%d^1) sensor head and the I/O board. again, go to the next step.
PAUSE. F/S external error Refer to the remedy of
FORC-173 G (F:%d^1) Error(s) occurred on the I/O board. the alarm displayed at the
1. Gradually increase the
PAUSE. F/S force differential The differential value of the force values of the 'Mass' and
FORC-175 G limit (F:%d^1) during force control is too large. 'Damper' impedance
PAUSE. F/S shard memory A parity error occurred on the interface safe pose. 2. Turn the
FORC-176 G parity error (F:%d^1) board. controller OFF, then ON
PAUSE. F/S local memory parity A parity error occurred on the interface safe pose. 2. Turn the
F/S SLC2 slave data Contact the FANUC
FORC-178 WARN error (F:%d^1) internal error service center and report
F/S SLC2 slave comm. Contact the FANUC
FORC-179 WARN error (F:%d^1) internal error service center and report
PAUSE. F/S ITP counter error Communication failed between the again. If this alarm occurs
FORC-180 G (F:%d^1) force sensor board and the I/O board. again, go to the next step.
There are two possible
robot poses which cause
PAUSE. Single singularity error The axis has approached a singularity this alarm: 1. The angle of
FORC-199 G (F:%d^1) point during force control. J5 is 0 degrees. 2. The sum
PAUSE. Complex singularity The robot has approached a singularity Force control must not be
FORC-201 G
PAUSE. error axis
Joint (F:%d^1)
limit error due to
One or the
morepositions
joint(s) of
hasJ1approached
and J6 during executed
its Force while
control J6 isnot be
must
FORC-203 G (F:%d^1) stroke limit. executed near a joint
PAUSE. Cool down fail in pause Contact the FANUC
FORC-205 G (F:%d^1) internal error service center and report
PAUSE. Pos. error limit at Hot Contact the FANUC
FORC-206 G Start (F:%d^1) internal error service center and report
PAUSE. Force error limit at Hot Contact the FANUC
FORC-207 G Start (F:%d^1) internal error service center and report
PAUSE. Hot Start after pause Contact the FANUC
FORC-208 G error (F:%d^1) internal error service center and report
1. Change the position
PAUSE. Jacobian matrix and orientation of the
FORC-209 G singurality (F:%d^1) Software internal error. robot. If this alarm occurs
Servo error occurred Refer to the remedy of
FORC-211 SERVO (F:%d^1) A servo error occurred. the alarm displayed at the
PAUSE. Force calc. timeout alarm occurs again, go to
FORC-215 G error (F:%d^1) Software internal error. the next step. 2. Replace
PAUSE. Ilegal end force control Contact the FANUC
FORC-223 G (F:%d^1) Software internal error service center and report
PAUSE. Not detect the touch Contact the FANUC
PAUSE. Not move specified Contact the FANUC
FORC-225 G distance (F:%d^1) Software internal error service center and report
PAUSE. Tool correction calc. Contact the FANUC
FORC-226 G error (F:%d^1) Software internal error service center and report
PAUSE. Unknown status from Contact the FANUC
FORC-227 G orbit func (F:%d^1) Software internal error service center and report
PAUSE. Unknown status from Contact the FANUC
FORC-228 G sub func (F:%d^1) Software internal error service center and report
1. Check the distance
betweent the approach
PAUSE. Approach timeout error The robot did not contact the work position and contact
FORC-263 G (F:%d^1) surface during a required time period. position - 5 mm or less is
1. The orientation of the
robot might have changed
too much during the force
PAUSE. Insertion timeout error Insertion did not complete during the control. If so, correct the
FORC-264 G (F:%d^1) required time. approach position. 2. The
1. Check that the
PAUSE. Angle change limit error The orientation change during the orientation of the
FORC-265 G (F:%d^1) insertion exceeded the limit value. insertion task is correct. 2.
PAUSE. Returning approach Contact the FANUC
FORC-266 G pos. failed (F:%d^1) Software internal error service center and report
PAUSE. Retry count exceeds Contact the FANUC
FORC-267 G limits (F:%d^1) Software internal error service center and report
PAUSE. Approach position error Contact the FANUC
PAUSE. Insert direction error The insertion direction acquired by the Execute the end condition
FORC-269 G (F:%d^1) end condition acquisition is wrong. acquisition again.
PAUSE. Insert length error The insertion length acquired by the Execute the end condition
FORC-270 G (F:%d^1) end condition acquisition is wrong. acquisition again.
The sign of the force command during Reverse the sign of 'Insert
PAUSE. Invalid teaching torque error acquisition is different Force' in Basic Data, or
FORC-271 G (F:%d^1) from the one during force control. execute the torque error
PAUSE. Invalid torque data is Contact the FANUC
FORC-272 G set (F:%d^1) Software internal error service center and report
PAUSE. Setting end cond. failed Contact the FANUC
1. Increase the value of
'Phase Match Rot Vel' in
Basic Data. 2. Increase the
PAUSE. Phase matching Insertion time exceeded the upper limit value of 'Phase Match
FORC-275 G timeout (F:%d^1) during the phase match insertion. Torque' in Performance
PAUSE. Recovering timeout Contact the FANUC
FORC-276 G (F:%d^1) software internal error service center and report
PAUSE. Approach angle limit Contact the FANUC
FORC-277 G (F:%d^1) software internal error service center and report
1. Check that the distance
between the approach
point and the Insertion
PAUSE. The object was inserted further than finishing point is
FORC-278 G Overrun error (F:%d^1) the specified length. appropriate. 2. Check that
SYSTE Illegal physical ITP Contact FANUC or FANUC
FORC-301 M (F:%d^1) Software internal error. Robotics and report the
SYSTE Illegal logical ITP Contact FANUC or FANUC
SYSTE Illegal axis module Contact FANUC or FANUC
FORC-303 M number (F:%d^1) Software internal error. Robotics and report the
SYSTE Illegal axis number Contact FANUC or FANUC
SYSTE Illegal axis order Contact FANUC or FANUC
SYSTE Illegal F/C axis number Contact FANUC or FANUC
SYSTE Illegal mech. parameter Contact the FANUC
FORC-317 M (F:%d^1) Software internal error. service center and report
SYSTE Illegal DH parameter Contact the FANUC
SYSTE Illegal motor parameter Contact the FANUC
PAUSE. Unfinished master Master the robot, then
FORC-320 G (F:%d^1) Robot is not mastered yet. turn the controller OFF,
SYSTE Unfinished quick Master the robot, then
FORC-321 M master (F:%d^1) Robot is not mastered yet. turn the controller OFF
SYSTE Unknown master type Master the robot, then
FORC-322 M (F:%d^1) Robot is not mastered yet. turn the controller OFF
SYSTE Illegal limit data Contact the FANUC
FORC-323 M (F:%d^1) Software internal error service center and report
Default values are:
Bad values for the system variables $CCI_GRP.$SJSW[1],[2],[4]
SYSTE Illegal joint singular $CCI_GRP.$SJSW[] and/or ,[6] = 0, $SJSW[3],[5] = 5
FORC-324 M (F:%d^1) $CCI_GRP.$SJSE[]. $CCI_GRP.$SJSE[1],[2],[4],
SYSTE Illegal F/S coord. system Contact the FANUC
Bad values for the system variables Default values are:
SYSTE Illegal F/S range $CCS_GRP.$RANGE_F[] and/or $CCS_GRP.$RANGE_F[1],[
FORC-326 M (F:%d^1) $CCS_GRP.$RANGE_T[]. 2],[3] = 40
SYSTE Illegal F/C motion group Contact the FANUC
SYSTE Illegal F/C motion group Contact the FANUC
FORC-328 M order (F:%d^1) Software internal error service center and report
SYSTE Timer variable init. Contact the FANUC
FORC-329 M error (F:%d^1) Software internal error service center and report
Program copy then ON again. If this
PAUSE. failed(ROM->RAM) alarm occurs again, go to
FORC-380 G (F:%d^1) Interface board initialization failed. the next step. 2. Replace
F/S SLC2 1. Turn the controller OFF,
PAUSE. error(STATERR) then ON again. If this
FORC-381 G (F:%d^1) Interface board initialization failed. alarm occurs again, go to
PAUSE. F/S SLC2 error(BITERR) then ON again. If this
FORC-382 G (F:%d^1) Interface board initialization failed. alarm occurs again, go to
PAUSE. Unestablished F/C data Contact the FANUC
PAUSE. Established F/C data at Contact the FANUC
FORC-413 G hot start (F:%d^1) Software internal error service center and report
PAUSE. Illegal basic data array Contact the FANUC
FORC-414 G num. (F:%d^1) Software internal error service center and report
PAUSE. Illegal Insert data array Contact the FANUC
FORC-415 G num. (F:%d^1) Software internal error service center and report
PAUSE. Unknown F/C mode Contact the FANUC
PAUSE. Illegal user frame(B/D) Contact the FANUC
PAUSE. Illegal tool frame(B/D) Contact the FANUC
PAUSE. Too much B/D number Contact the FANUC
PAUSE. Contact the FANUC
FORC-447 G Illegal B/D (F:%d^1) Software internal error service center and report
PAUSE. Exchange impedance Contact the FANUC
FORC-448 G data failed (F:%d^1) Software internal error service center and report
PAUSE. Exchange frequency then ON again. If this
FORC-449 G failed (F:%d^1) Software internal error. alarm occurs again, go to
PAUSE. Unknown F/C type Contact the FANUC
FORC-450 G (F:%d^1) Software internal error. service center and report
PAUSE. Unknown initializing Contact the FANUC
FORC-451 G status (F:%d^1) Software internal error. service center and report
PAUSE. Illegal cool down rate The value of 'Settling Rate'
FORC-452 G (F:%d^1) Settling rate is out of range. in Performance Data must
PAUSE. Illegal tool weight get Contact FANUC or FANUC
FORC-453 G time (F:%d^1) Software internal error. Robotics and report the
PAUSE. Tool weight is uninit Contact the FANUC
PAUSE. Illegal tool weight Contact the FANUC
PAUSE. Illegal I/D number Contact the FANUC
PAUSE. Contact the FANUC
FORC-477 G Illegal I/D (F:%d^1) Software internal error. service center and report
PAUSE. Illegal vision tool comp. Contact the FANUC
FORC-478 G
PAUSE. data (F:%d^1)
Illegal vision user comp. Software
Vision internal error.
compensated user frame is service center
Re-acquire theand report
offset data
FORC-479 G data (F:%d^1) wrong. with vision.
PAUSE. Unknown insertion Contact the FANUC
FORC-480 G mode (F:%d^1) Software internal error. service center and report
PAUSE. Illegal insertion Contact FANUC or FANUC
FORC-481 G direction (F:%d^1) Software internal error. Robotics and report the
PAUSE. Illegal end Contact the FANUC
FORC-482 G condition(approach) Software internal error. service center and report
PAUSE. Illegal retry number Contact the FANUC
PAUSE. Illegal insertion force The value of 'Insert Force' is smaller Make the absolute value
FORC-484 G (F:%d^1) than the lower limit (absolute value 0.5 of 'Insert Force' in Basic
distance between the
PAUSE. Setting torque error approach position and the
FORC-485 G failed (F:%d^1) Failed to acquire torque error data. contact position is not too
PAUSE. Setting end cond. Contact the FANUC
FORC-486 G failed(TEACH) (F:%d^1) Software internal error. service center and report
PAUSE. Setting end cond. Insertion direction acquired by the end Execute the end condition
FORC-487 G
PAUSE. failed(USE) (F:%d^1)
Display graph data on condition acquisition is wrong. acquisition again.
FORC-488 G debug console (F:%d^1) Display graph data on debug console No action is required.
The value of 'Individual Diff (-)' is Basic Make the value of
PAUSE. Illegal pushing depth Data is less than zero or larger than the 'Individual Diff (-)' positive
FORC-489 G (F:%d^1) value of 'Insert Depth (Design)' in Basic and smaller than the
PAUSE. Illegal rotation angle Contact FANUC or FANUC
FORC-490 G max (F:%d^1) Software internal error. Robotics and report the
PAUSE. Illegal decelerate time Contact FANUC or FANUC
FORC-491 G (F:%d^1) Software internal error. Robotics and report the
PAUSE. Illegal decel depth rate Contact FANUC or FANUC
PAUSE. Illegal rotation direction Contact FANUC or FANUC
PAUSE. Illegal initial Fd The sign of 'Initial Insert Force' in Make the sign of 'Initial
FORC-494 G (F:%d^1) Performance Data is different from the Insert Force' in
PAUSE. Illegal velocity adjust The value of 'Velocity Adjust Gain' in 'Velocity Adjust Gain'
FORC-495 G gain (F:%d^1) Performance Data is illegal. must be between 0 and 3.
PAUSE. Illegal starting rate The value of 'Starting Rate' in 'Starting Rate' must be
FORC-496 G (F:%d^1) Performance Data is illegal. larger than 12.5.
PAUSE. Illegal ending rate The value of 'Ending Rate' in 'Ending Rate' must be
FORC-497 G (F:%d^1) Performance Data is illegal. smaller than 95.
PAUSE. Illegal approach length Contact the FANUC
PAUSE. Illegal approach modify Contact the FANUC
FORC-499 G time (F:%d^1) Software internal error. service center and report
PAUSE. Illegal reduction ratio Contact FANUC or FANUC
PAUSE. Illegal velocity adjust Contact the FANUC
FORC-501 G
PAUSE. switchoverrun
Illegal (F:%d^1)length Software
The valueinternal error.Diff. (+)' in Basic
of 'Individual service center
'Individual Diff.and
(+)'report
must
FORC-502 G (F:%d^1) Data is illegal. be between 0 and 10000.
Modify the force control
parameters in the
AIT X direction An environmental characteristic in the following order; then
PAUSE. environment NG X direction could not be acquired in the execute the impedance
FORC-508 G (F:%d^1) impedance parameters auto tuning. parameters auto tuning
parameters in the
AIT Y direction An environmental characteristic in the following order; then
PAUSE. environment NG Y direction could not be acquired in the execute the impedance
execute the impedance
parameters auto tuning
AIT Z direction An environmental characteristic in the again. 1. The impedance
PAUSE. environment NG Z direction could not be acquired in the change for the
FORC-510 G (F:%d^1) impedance parameters auto tuning. environmental
parameters in the
AIT W direction An environmental characteristic in the following order; then
PAUSE. environment NG W direction could not be acquired in execute the impedance
FORC-511 G (F:%d^1) the impedance parameters auto tuning. parameters auto tuning
parameters in the
AIT P direction An environmental characteristic in the following order; then
PAUSE. environment NG P direction could not be acquired in the execute the impedance
parameters in the
AIT R direction An environmental characteristic in the following order; then
PAUSE. environment NG R direction could not be acquired in the execute the impedance
Correct the errors in the
The force in the X direction became following order; then
excessive while acquiring an execute the impedance
PAUSE. AIT X direction unstable environmental characteristic in the parameters auto tuning
FORC-514 G (F:%d^1) impedance parameters auto tuning. again. 1. Execessive force
The force in the Y direction became following order; then
PAUSE. AIT Y direction unstable environmental characteristic in the parameters auto tuning
The force in the Z direction became following order; then
PAUSE. AIT Z direction unstable environmental characteristic in the parameters auto tuning
The force in the W direction became following order; then
PAUSE. AIT W direction environmental characteristic in the parameters auto tuning
FORC-517 G unstable (F:%d^1) impedance parameters auto tuning. again. 1. Execessive force
The force in the P direction became following order; then
PAUSE. AIT P direction unstable environmental characteristic in the parameters auto tuning
The force in the R direction became following order; then
PAUSE. AIT R direction unstable environmental characteristic in the parameters auto tuning
If the prepared default
Force control is disabled in all data for the application is
PAUSE. AIT all switch OFF directions during the impedance used, this error should not
FORC-520 G (F:%d^1) parameters auto tuning. occur. Try to copy the
following order; then
PAUSE. AIT X direction fail Impedance parameters auto tuning in parameters auto tuning
FORC-521 G (F:%d^1) the X direction did not complete. again. 1. Stop any
PAUSE. AIT Y direction fail Impedance parameters auto tuning in parameters auto tuning
FORC-522 G (F:%d^1) the Y direction did not complete. again. 1. Stop any
PAUSE. AIT Z direction fail Impedance parameters auto tuning in parameters auto tuning
FORC-523 G (F:%d^1) the Z direction did not complete. again. 1. Stop any
PAUSE. AIT W direction fail Impedance parameters auto tuning in parameters auto tuning
FORC-524 G (F:%d^1) the W direction did not complete. again. 1. Stop any
PAUSE. AIT P direction fail Impedance parameters auto tuning in parameters auto tuning
FORC-525 G (F:%d^1) the P direction did not complete. again. 1. Stop any
PAUSE. AIT R direction fail Impedance parameters auto tuning in parameters auto tuning
FORC-526 G (F:%d^1) the R direction did not complete. again. 1. Stop any
PAUSE. AIT system error Contact FANUC or FANUC
PAUSE.Rotate angle limit The rotation angle exceeded the upper 'Phase Match Push F' in
FORC-542 G (F:%d^1) limit during the phase match insertion. Basic Data. 2. Make sure
PAUSE.AIT system error Contact FANUC or FANUC
Sensor board doesn't 1. Turn the controller OFF.
FRCE-001 WARN exist Force control board doesn't exist. 2. Mount the force
Sensor board doesn't 1. Turn the controller OFF.
FRCE-002 WARN Force
exist 2control error Force
The controlboard
error doesn't
occurred from theexist.
force 2. Mount
Refer themanual
to the force for
FRCE-003 (F:%d^1, E:%d^2) control board. the force control board.
SYSTE The system cannot cammunicate with Please check the force
FRCE-004 M Communication error the force control board. control board.
Sensor board is Force control board has been disabled Refer to the remedy of
FRCE-005 WARN disabled because of the alarm displayed at the the alarm displayed at the
Sensor board is Force board has been disabled because Refer to the remedy of
FRCE-006 WARN disabled 2 of the alarm displayed at the same the alarm displayed at the
There was an error at memory Turn off the robot. 2. On
initialization internally. Maybe, the teach pendant, press
Memory initialization memory is lack, or, the memory and hold the SHIFT and
FRCE-007 WARN error module is broken. RESET keys. 3. While still
FRCE-008 STOP Option is not loaded Option
The is not cannot
program loaded.control the Load the
Please option.
check the default
FRCE-011 STOP Force group mismatch specified motion group. motion groups
Please check the inforce
the
FRCE-012 STOP Time out error occurred The system cannot start force control. control board.
The system cannot communicate with Please check the force
FRCE-013 STOP Communications error the force control board. controlset
Please board.
the correct tool
FRCE-014 STOP Invalid tool number The tool number is set to 0. number.
Force sensor error As a result of the force sensor diagnosis
FRCE-015 STOP exceed limit the error of the force sensor exceeded Replace the force sensor.
FRCE-016 WARN Diagnosis normal end Force sensor is normal No action is required.
If you want to change the
Initial force sensor data already setting initial force sensor data,
FRCE-017 STOP Init data already set up
up change the
Please initialize thesystem
force
FRCE-018 STOP Uninitialized
Tolerance data
data Initial force sensor data is uninitialized
is 0 or sensor set
Please data. up the system
FRCE-019 STOP less
Sensor error excess Tolerance data is output
The force sensor uninitialized
data is too variable
FRCE-020 STOP (S:%d E:%X) large. Check the force sensor
Sensor index does not The force sensor which is specified by Please specified correct
FRCE-021 STOP exist sensor index does not exist. sensor index.
An INSERTION instruction was executed Add an OFFSET
before an OFFSET CONDITION CONDITION instruction
FRCE-022 STOP Force
Offsetsensor
value iserror
needed instruction. A position register was not before check
Please the INSERTION
the state of
FRCE-023 STOP occurred Force sensor error has occurred. the force sensor.
Force control error The error occurred from the force Refer to the remedy of
FRCE-024 STOP occurred control board.
Cannot executeThe error jump
instruction is not
because the force
Select control alarm
appropriate
FRCE-025 STOP Function type is unused Unused is selected.
Initial force sensor data has been set function type.
FRCE-026 WARN Another
Init data tuning
has been set now
already Another tuning mode is already No actionanother
Remove is required.
tuning
FRCE-027 STOP enabled enabled instruction
Customize tuning little There is a schedule whose DOF is bigger Execute tuning with a
FRCE-028 STOP DOF than executed one schedule of biggest DOF
Internal error(%d) led to the error, and
FRCE-029 occurred
Fixed sensor option is Software internal error. contact your FANUC or
FRCE-037 not ordered Fixed sensor option is not ordered Order Fixed sensor option
FRCE-038 Please set sensor frame Sensor frame for fixed sensor is not set Set Sensor frame
Please reboot controller in
FRCE-039 Pleaseexec.
Can't reboot
F/Ccontroller
with Sensorisframe
There has sensor
No force not beenforupdated
this robot order toattachment
Change update sensor type
FRCE-040 hand sensor to be attached of force sensor to FIXED
This controller isn't This robot with force sensor doesn't Contact FANUC America
FRCE-041 supported
Vision Register is not support this controller Corporation to report the
FRCE-042 set Vision Register is not set. Execute Vision.
ForceSensor can't be Do not execute a SENSOR
FRCE-050 connected Force Sensor can't be connected. CONNECT command while
ForceSensor can't be Do not execute a SENSOR
FRCE-051 disconnected Force Sensor cannot be disconnected. DISCONNECT command
ForceSensor A Force control was attempted while Attach the force sensor,
FRCE-052 disconnection the force sensor is disconnected. and retry the operation.
FS disconnect internal led to the error, and
FRCE-053 error An internal error has occurred. contactconfirm
Please your FANUC
the default
FRCE-101 WARN Default data is incorrect
not Selected default
The default data data is not
still has notcorrect
been data of system variables
Please select the default
FRCE-102 WARN selected selected data atenter
Please the default menu
the index
FRCE-103 WARN Index value is incorrect
Index value is not correct value
Number of array is Number of array in selected default Please confirm the
FRCE-104 WARN incorrect data is not correct number of array in the
The force group of program has not Please create this
FRCE-105 WARN Force group is incorrect been existed in this system statement in this system
Mass data is out of The mass data which has been
FRCE-106 WARN range calculated by entering data is out of Please enter proper data
Damper data is out of The damper data which has been
FRCE-107 WARN range
Input data is out of calculated by entering data is out of Please enter proper data
FRCE-108 WARN Input
minimum
data is out of minimum range
The input data is out of maximum Please enter proper data
FRCE-109 WARN Setting
maximum data is not range enter proper
Please confirm data
and enter
FRCE-110 WARN enough The setting data has not been set yet proper the data
Number of array Mismatch the number of array data Please confirm the data
FRCE-111 WARN mismatch
Program data is between
The forcethe
datasource data and
of selected default
program is and enter
Please proper
confirm thethe data
force
FRCE-112 WARN Specified
incompletedata doesn't not complete data ofconfirm
Please selectedand
program
enter
FRCE-113 WARN exist The specified data does not exist the proper data
Converted individual Because the ending condition switch is
FRCE-114 WARN difference changed, the individual difference Verify the pushing depth
Insert direction is groove direction is set to be the same Verify the insert direction
FRCE-115 WARN changed as insert direction. This is impossible in in 'Basic Data'.
Bearing rot axis is groove direction is set to be the same Verify the bearing
FRCE-116 WARN changed as insert direction. This is impossible in rotation axis.
Cannot set phase match impedance Do auto tuning and set
FRCE-117 WARN Auto tuning not done rate because auto impedance tuning is phase match impedance
Groove direction is Modified insert direction is the same as Verify the groove
FRCE-118 WARN changed groove direction. For this case, it direction.
Parent schedule's parent is child : Verify parent and child
FRCE-119 WARN infinit loop
Customize exceed rty- Infinit loop relationship
Parmitted And setofright
number child
FRCE-120 WARN child num exceed ins- There are two children for retry
Customize for retry is number
Parmitted only oneof child
FRCE-121 WARN child num exceed retry There are two children for insertion
Customize for insertion is only one
FRCE-122 WARN num Child for retry can't have child Prohibited operation
Customize syncro Parameters of customized schedules If you don't want to
FRCE-123 WARN change OK were synchronized changed synchronized chage, turn
Customize syncro Parameters of customized schedules If you want to
FRCE-124 WARN change NG were not synchronized changed synchronized chage, turn
FRCE-125 WARN Customize intr. TP err0 Software internal error. led to the error, and call
FRCE-126 WARN Customize intr. TP err1 Software internal error. led to the error, and call
FRCE-127 WARN Customize
Turn on Gain intr. TP err2
Auto Software
The switchinternal error.
of F.Ctrl. Gain Auto Modify led
Turntoonthe error,
the andofcall
switch
FRCE-128 WARN Modify is OFF. F.Ctrl. Gain Auto Modify.
Direction is same as ins. Input direction for the search menu is
FRCE-129 WARN dir. same as the insertion direction. Select
Contactthe otherRobotics
FANUC directions
FRCE-130 STOP Illegal insert data index Software internal error. to report the error.
Can not execute Gain Auto Gain Tuning was executed when Move the robot in any
FRCE-131 Tuning the robot is not prepared. directions and Execute
F/S FPGA version error Document the events that
FRCE-151 STOP (F:%d^1) The version of FPGA is old. led to the error, and call
F/S SCL2 slave error Communication with the sensor board again. If this alarm occurs
FRCE-152 STOP (F:%d^1) failed. again, go to the next step.
F/S SLC2 frmaing error Communication with the sensor board again. If this alarm occurs
FRCE-153 STOP (F:%d^1) failed. again, go to the next step.
F/S SLC2 internal parity A parity error occurred on the sensor safe pose. 2. Turn the
FRCE-154 STOP error (F:%d^1) board. controller OFF, then ON
F/S SLC2 external parity A parity error occurred on the sensor safe pose. 2. Turn the
F/S head data request The data request from the sensor again. If this alarm occurs
FRCE-156 STOP error (F:%d^1) board to the sensor head failed. again, go to the next step.
F/S force data calc. safe pose. 2. Turn the
FRCE-157 STOP overflow (F:%d^1) Software internal error. controller OFF, then ON
F/S gauge data overflow An output error occurred from the safe pose. 2. Turn the
FRCE-158 STOP (F:%d^1) sensor head. controller OFF, then ON
value of 'Insert Force' in
'Basic Data' is not too
F/S sensor limit An excessive load was put on the large. If not, go to the
FRCE-159 STOP overflow (F:%d^1) sensor head. next step. 2.orBad
Re-connect replace the
FRCE-160 STOP F/S cable is cut (F:%d^1) Cable is cut. cable.
F/S timeout error The force control board or the R-J3 alarm occurs again, go to
FRCE-161 STOP (F:%d^1) main control board has failed. the next step. 2. Replace
F/S temperature data Temperature output error occurred in safe pose. 2. Turn the
FRCE-162 STOP overflow (F:%d^1) the sensor head. controller OFF, then ON
F/S watch dog error Watchdog error occurred on the sensor again. If this alarm occurs
FRCE-163 STOP (F:%d^1) board. again, go to the next step.
it is not low, go to the
F/S temp. lower limit The temperature measured at the next step. 2. Check the
FRCE-164 STOP error (F:%d^1) sensor head is too low. sensor cable connectivity.
it is not high, go to the
F/S temp. upper limit The temperature measured at the next step. 2. Check the
FRCE-165 STOP error (F:%d^1) sensor head is too high. sensor cable connectivity.
SYSTE SCRDY set error Document the events that
FRCE-167 M (F:%d^1) Internal error led to the error, and call
SYSTE HCRDY set error Document the events that
SYSTE SCRDY reset error Document the events that
SYSTE HCRDY reset error Document the events that
1. Check the force sensor
output data on TP (Force
sensor status screen). The
F/S output data frozen The output data from the sensor head value must vary slightly
FRCE-171 STOP (F:%d^1) is frozen (unchanging). over time due to sensor
F/S communication Communication failed between the again. If this alarm occurs
FRCE-172 STOP error (F:%d^1) sensor head and the sensor board. again, go to the next step.
F/S external error Refer to the remedy of
FRCE-173 STOP (F:%d^1) Error(s) occurred on the sensor board. the alarm displayed at the
Try the following. -
F/S sensor limit warning An excessive load was put on the Reduce the velocity or
FRCE-174 (F:%d^1) sensor head. acceleration of the robot
1. Gradually increase the
F/S force differential The differential value of the force values of the 'Mass' and
FRCE-175 STOP limit (F:%d^1) during force control is too large. 'Damper' impedance
F/S shard memory A parity error occurred on the sensor safe pose. 2. Turn the
FRCE-176 STOP parity error (F:%d^1) board. controller OFF, then ON
F/S local memory parity A parity error occurred on the sensor safe pose. 2. Turn the
F/S SLC2 slave data Document the events that
FRCE-178 WARN error (F:%d^1) Internal error led to the error, and call
F/S SLC2 slave comm. Document the events that
FRCE-179 WARN error (F:%d^1) Internal error led to the error, and call
F/S ITP counter error Communication failed between the again. If this alarm occurs
FRCE-180 STOP (F:%d^1) sensor board and the force sensor. again, go to the next step.
- Move the robot to a safe
position. - Turn the
again. If this alarm occurs
again, go to the next step.
Force sensor type error The force sensor type has been - Check the sensor cable
FRCE-181 (F:%d^1) changed. connectivity. Check also
1. Check if Reg.No.Basis
Measure, Reg.No.Mass
Measure and
Reg.No.Mass Result are
different. 2. Check if
Mass Measure The settings of Mass Measurement are Reg.No.Basis Measure,
FRCE-183 execution error illegal. Reg.No.Mass Measure
1. Check the start timing
Mass Measure timeout Mass Measurement exceeded Max and end timing of Basis
FRCE-184 error Data Record Time. Measurement or Mass
Auto Tuning SW is Auto Impedance Tuning switch is tuned This is not error.If you
FRCE-188 turned off off. desire to execute tuning
There are two possible
robot poses which cause
Single singularity error The axis has approached a singularity this alarm: 1. The angle of
FRCE-199 STOP (F:%d^1) point during force control. J5 is 0 degrees. 2. The sum
Complex singularity The robot has approached a singularity Force control must not be
FRCE-201 STOP error axis
Joint (F:%d^1)
limit error due to
One or the
morepositions
joint(s) of
hasJ1approached
and J6 during executed
its Force while
control J6 isnot be
must
FRCE-203 STOP (F:%d^1) stroke limit. executed near a joint
Cool down fail in pause Document the events that
FRCE-205 STOP (F:%d^1) Internal error led to the error, and call
Pos. error limit at Hot Document the events that
FRCE-206 STOP Start (F:%d^1) Internal error led to the error, and call
Force error limit at Hot Document the events that
FRCE-207 STOP Start (F:%d^1) Internal error led to the error, and call
Hot Start after pause Document the events that
FRCE-208 STOP error (F:%d^1) Software internal error led to the error, and call
Inverse kinematics Error Document the events that
FRCE-209 STOP (F:%d^1) Software internal error led to the error, and call
Forward kinematics led to the error, record
FRCE-210 Error (F:%d^1) An internal error has occurred. the error status, and
Servo error occurred Refer to the remedy of
FRCE-211 SERVO (F:%d^1) A servo error occurred. the alarm displayed at the
led to the error, and
FRCE-212 Servo is not ready The servo is not ready. contact your FANUC or
Force calc. timeout Document the events that
FRCE-216 STOP X Force Limit (F:%d^1) the Force in X direction is too big. See the manual.
FRCE-217 STOP Y Force Limit (F:%d^1) the Force in Y direction is too big. See the manual.
FRCE-218 STOP ZWForce
MomentLimitLimit
(F:%d^1) the Force in Z direction is too
Moment about X direction is toobig. See the manual.
FRCE-219 STOP (F:%d^1)
P Moment Limit big. Moment about Y direction is too
the See the manual.
R Moment Limit big. Moment about Z direction is too
the See the manual.
FRCE-221 STOP (F:%d^1) big. See the manual.
Ilegal end force control Document the events that
Not detect the touch Document the events that
Not move specified Document the events that
FRCE-225 STOP distance (F:%d^1) Software internal error led to the error, and call
Tool correction calc. Document the events that
Unknown status from Document the events that
FRCE-227 STOP orbit func (F:%d^1) Software internal error led to the error, and call
Unknown status from Document the events that
FRCE-228 STOP sub func
Force (F:%d^1)
at the end is not Software internal error
Force at the end is smaller than led to the
Change error, andor
parameters call
FRCE-260 STOP ok (F:%d^1)
Torque at the end is not 'Minimum
Torque Force
at the endRate'
is larger than positionparameters
Change and retry or
FRCE-261 STOP ok (F:%d^1) 'Torque Upper Limit' position and retry
End Force and Torque is Force and Torque at the end doesn't Change parameters or
FRCE-262 STOP not ok (F:%d^1) satisfy 'Minimum Force position and retry
1. Check the distance
betweent the approach
Approach timeout error The robot did not contact the work position and contact
FRCE-263 STOP (F:%d^1) surface during a required time period. position - 5 mm or less is
1. The orientation of the
robot might have changed
too much during the force
Insertion timeout error Insertion did not complete during the control. If so, correct the
FRCE-264 STOP (F:%d^1) required time. approach position. 2. The
1. Check that the
Angle change limit error The orientation change during the orientation of the
FRCE-265 STOP (F:%d^1) insertion exceeded the limit value. insertion task is correct. 2.
Returning approach Document the events that
FRCE-266 STOP pos. failed (F:%d^1) Software internal error led to the error, and call
Retry count exceeds Document the events that
FRCE-267 STOP limits (F:%d^1) Software internal error led to the error, and call
Approach position error Document the events that
Insert direction error The insertion direction acquired by the Execute the end condition
FRCE-269 STOP (F:%d^1) end condition acquisition is wrong. acquisition again.
Insert length error The insertion length acquired by the Execute the end condition
FRCE-270 STOP (F:%d^1) end condition acquisition is wrong. acquisition again.
The sign of the force command during Reverse the sign of 'Insert
Invalid teaching torque error acquisition is different Force' in Basic Data, or
FRCE-271 STOP (F:%d^1) from the one during force control. execute the torque error
Invalid torque data is Document the events that
FRCE-272 STOP set (F:%d^1) Software internal error led to the error, and call
Setting end cond. failed Document the events that
'Phase Match Rot Vel' in
Basic Data. 2. Increase the
Phase matching Insertion time exceeded the upper limit value of 'Phase Match
FRCE-275 STOP timeout (F:%d^1) during the phase match insertion. Torque' in Performance
Recovering timeout Document the events that
Approach angle limit Document the events that
1. Check that the distance
between the approach
point and the Insertion
The object was inserted further than finishing point is
FRCE-278 STOP Overrun error (F:%d^1) the
A specified
HOLD or anlength.
EMERGENCY STOP appropriate.
Restart 2. Check that
the contouring
FRCE-279 WARN Contouring
F. Ctrl duringaborted aborted the contouring.
Force control occurred during process.
Abort contouring before
Contouring start contouring.
Force control occurred during you satrt
Abort force control.
contouring before
FRCE-281 WARN (F:%d^1)
Contouring normal end contouring. you start force control.
FRCE-282 WARN (F:%d^1) Contouring normal end. None.
A position error occurred during Reduce the velocity
Contouring limit error contouring which exceeded the limit command or increase the
FRCE-283 STOP (F:%d^1) value. value of the push distance
Order and install the
Contouring option. It is
Contouring option is The contouring option was not possible that backup data
FRCE-284 STOP not ordered ordered. which contained
Auto tuning is Auto tuning for contouring cannot be Do not attempt Auto
FRCE-285 STOP impossible done. tuning for contouring.
impedance ctrl. not cleared, document
FRCE-286 STOP impossible A parameter setting error has occurred. the events that led to the
An internal software error has and hold the SHIFT and
FRCE-287 STOP Contouring 07 (F:%d^1) occurred. RESET keys. 3. While still
FRCE-295 STOP Contouring
F. Ctrl during15 (F:%d^1) occurred. RESET Contouring
Abort keys. 3. While still
before
FRCE-296 (F:%d^1)
Contouring option is Force control during Contouring. you satrt
Order theforce control.
Contouring
FRCE-297 not ordered
Change Moving Vel. Contouring option is not ordered option
Check max. and min. val.
FRCE-298 Set.or
I/O error
Num.Reg. Change Moving Vel. Set. error. andI/O
Set other val.
or Num.Reg.
FRCE-299 number Push.
Change error Force Set. I/O or Num.Reg. number error. number properly.
FRCE-300 error Change Push. Force Set. error. Check max. and min. val.
SYSTE Illegal physical ITP Document the events that
FRCE-301 M (F:%d^1) Software internal error led to the error, and call
SYSTE Illegal logical ITP Document the events that
FRCE-302 M (F:%d^1) Software internal error led to the error, and call
SYSTE Illegal axis module Document the events that
FRCE-303 M number (F:%d^1) Software internal error. led to the error, and call
SYSTE Illegal axis number Document the events that
FRCE-304 M (F:%d^1) Software internal error. led to the error, and call
SYSTE Illegal axis order Document the events that
SYSTE Illegal F/C axis number Document the events that
SYSTE Illegal mech. parameter Document the events that
SYSTE Illegal DH parameter Document the events that
SYSTE Illegal motor parameter Document the events that
Unfinished master Master the robot, then
FRCE-320 (F:%d^1) The robot is not mastered yet. turn the controller OFF,
Unfinished quick Master the robot, then
FRCE-321 master (F:%d^1) The robot is not mastered yet. turn the controller OFF,
Unknown master type Master the robot, then
FRCE-322 (F:%d^1) The robot is not mastered yet. turn the controller OFF,
Illegal limit data led to the error, record
FRCE-323 (F:%d^1) An internal error has occurred. the error status, and
Default values are:
Bad values for the system variables $CCI_GRP.$SJSW[1],[2],[4]
SYSTE Illegal joint singular $CCI_GRP.$SJSW[] and/or ,[6] = 0, $SJSW[3],[5] = 5
FRCE-324 M (F:%d^1) $CCI_GRP.$SJSE[]. $CCI_GRP.$SJSE[1],[2],[4],
SYSTE Illegal F/S coord. system Document the events that
Bad values for the system variables Default values are:
SYSTE Illegal F/S range $CCS_GRP.$RANGE_F[] and/or $CCS_GRP.$RANGE_F[1],[
FRCE-326 M (F:%d^1) $CCS_GRP.$RANGE_T[]. 2],[3] = 40
SYSTE Illegal F/C motion group Document the events that
SYSTE Illegal F/C motion group Document the events that
FRCE-328 M order (F:%d^1) Software internal error. led to the error, and call
SYSTE Timer variable init. Document the events that
FRCE-329 M error (F:%d^1) Software internal error. led to the error, and call
Program copy then ON again. If this
failed(ROM->RAM) alarm occurs again, go to
FRCE-380 STOP (F:%d^1) Sensor board initialization failed. the next step. 2. Replace
F/S SLC2 1. Turn the controller OFF,
error(STATERR) then ON again. If this
FRCE-381 STOP (F:%d^1) Sensor board initialization failed. alarm occurs again, go to
F/S SLC2 error(BITERR) then ON again. If this
FRCE-382 STOP (F:%d^1) Sensor board initialization failed. alarm occurs again, go to
Unestablished F/C data Document the events that
FRCE-412 STOP (F:%d^1) Software internal error. led to the error, and call
Established F/C data at Document the events that
FRCE-413 STOP hot start (F:%d^1) Software internal error. led to the error, and call
Illegal basic data array Document the events that
FRCE-414 STOP num. (F:%d^1) Software internal error. led to the error, and call
Illegal Insert data array Document the events that
FRCE-415 STOP num. (F:%d^1) Software internal error. led to the error, and call
Unknown F/C mode Document the events that
Check the values of the
Search Retry Limit Retry number of the search exceeded following parameters
FRCE-420 STOP (F:%d^1) the limit. 1.the search range 2.the
Search Range over The robot moved beyond the search Check the parameter
FRCE-421 STOP (F:%d^1) range limit before finishing the search. 'search range' Make the
Set the values of the
search force or torque
Search Frc/Vel wrong Force or Velocity command of the other than zero. Set the
FRCE-422 STOP (F:%d^1) search direction is wrong. values of the velocity or
Search Vel order error The velocity order for the search Set the different value for
FRCE-423 STOP (F:%d^1) function is invalid. the different direction.
Search direction error Set different direction to
Search range param. Search
'search directions are invalid.
range' is smaller than the search
Make direction
'search range' 1>=and
FRCE-425 STOP error (F:%d^1) 'Clearance & Chamfer'. 'Clearance & Chamfer'.
Search velocity Calc. 'Search acc. time' or 'Clearance & Set the values 'Search
FRCE-426 STOP error (F:%d^1)
Search reverse SW Chamfer' are zero. frequency',
Set 'Search
the 'reverse range'
switch'
FRCE-427 STOP invalid (F:%d^1) The value of Reverse switch is wrong. ON.
The values of 'Search frequency', Reduce the value of
Search velocity MAX 'Search range' or 'Clearance & Chamfer' 'Search frequency'.
FRCE-428 STOP error (F:%d^1) are wrong. Reduce the value of
Illegal user frame(B/D) led to the error, record
Illegal tool frame(B/D) led to the error, record
Too much B/D number led to the error, record
FRCE-447 STOP Illegal B/D (F:%d^1) Software internal error. led to the error, and call
Exchange impedance led to the error, and
FRCE-448 data failed (F:%d^1) An internal error has occurred. contact your FANUC
- Turn the controller OFF,
Exchange frequency then ON again. - If this
FRCE-449 failed (F:%d^1) An internal error has occurred. alarm occurs again, go to
Unknown F/C type led to the error, and
FRCE-450 (F:%d^1) An internal error has occurred. contact your FANUC
Unknown initializing Document the events that
FRCE-451 STOP status (F:%d^1) Software internal error. led to the error, and call
Illegal cool down rate The value of 'Settling Rate'
FRCE-452 STOP (F:%d^1) Settling rate is out of range. in Performance Data must
Illegal tool weight get Contact FANUC or FANUC
FRCE-453 STOP time (F:%d^1) Software internal error. Robotics and report the
Tool weight is uninit Contact FANUC or FANUC
FRCE-454 STOP (F:%d^1) Software internal error. Robotics and report the
Illegal tool weight led to the error, and
Illegal I/D number led to the error, and
FRCE-477 Illegal I/D (F:%d^1) An internal error has occurred. contact your FANUC
Illegal vision tool comp. led to the error, and
FRCE-478 data (F:%d^1)
Illegal An internal
vision user comp. The error has occurred.
Vision compensated user frame is contact your
Re-acquire FANUC
the offset data
FRCE-479 data (F:%d^1) wrong. with vision.
Unknown insertion led to the error, and
FRCE-480 mode (F:%d^1) An internal error has occurred. contact your FANUC
Illegal insertion led to the error, and
FRCE-481 direction (F:%d^1) An internal error has occurred. contact your FANUC
Illegal end Document the events that
FRCE-482 STOP condition(approach) Software internal error. led to the error, and call
Illegal retry number Document the events that
Illegal insertion force Document the events that
distance between the
Setting torque error approach position and the
FRCE-485 STOP failed (F:%d^1) Failed to acquire torque error data. contact position is not too
Setting end cond. Document the events that
FRCE-486 STOP failed(TEACH) (F:%d^1) Software internal error. led to the error, and call
Setting end cond. Insertion direction acquired by the end Execute the end condition
FRCE-487 STOP failed(USE) (F:%d^1)
Display graph data on condition acquisition is wrong. acquisition again.
FRCE-488 STOP debug console (F:%d^1) Display graph data on debug console No action is required.
The value of 'Individual Diff (-)' is Basic Make the value of
Illegal pushing depth Data is less than zero or larger than the 'Individual Diff (-)' positive
FRCE-489 STOP (F:%d^1) value of 'Insert Depth (Design)' in Basic and smaller than the
Illegal rotation angle Document the events that
FRCE-490 STOP max (F:%d^1) Software internal error. led to the error, and call
Illegal decelerate time Document the events that
Illegal decel depth rate Document the events that
Illegal rotation direction Document the events that
Illegal initial Fd The sign of 'Initial Insert Force' in Make the sign of 'Initial
FRCE-494 STOP (F:%d^1) Performance Data is different from the Insert Force' in
Illegal velocity adjust The value of 'Velocity Adjust Gain' in 'Velocity Adjust Gain'
FRCE-495 STOP gain (F:%d^1) Performance Data is illegal. must be between 0 and 3.
Illegal starting rate The value of 'Starting Rate' in 'Starting Rate' must be
FRCE-496 STOP (F:%d^1) Performance Data is illegal. larger than 12.5.
Illegal ending rate The value of 'Ending Rate' in 'Ending Rate' must be
FRCE-497 STOP (F:%d^1) Performance Data is illegal. smaller than 95.
Illegal approach length Document the events that
Illegal approach modify Document the events that
FRCE-499 STOP time (F:%d^1) Software internal error. led to the error, and call
Illegal reduction ratio Document the events that
Illegal velocity adjust Document the events that
FRCE-501 STOP switch (F:%d^1)length
Illegal overrun Software
The valueinternal error.Diff. (+)' in Basic
of 'Individual led to the error,
'Individual andmust
Diff. (+)' call
FRCE-502 STOP (F:%d^1) Data is illegal. be between 0 and 10000.
parameters in the
AIT X direction An environmental characteristic in the following order; then
environment NG X direction could not be acquired in the execute the impedance
FRCE-508 STOP (F:%d^1) impedance parameters auto tuning. parameters auto tuning
parameters in the
AIT Y direction An environmental characteristic in the following order; then
environment NG Y direction could not be acquired in the execute the impedance
parameters in the
AIT Z direction An environmental characteristic in the following order; then
environment NG Z direction could not be acquired in the execute the impedance
parameters in the
AIT W direction An environmental characteristic in the following order; then
environment NG W direction could not be acquired in execute the impedance
FRCE-511 STOP (F:%d^1) the impedance parameters auto tuning. parameters auto tuning
parameters in the
AIT P direction An environmental characteristic in the following order; then
environment NG P direction could not be acquired in the execute the impedance
parameters in the
AIT R direction An environmental characteristic in the following order; then
environment NG R direction could not be acquired in the execute the impedance
The force in the X direction became
AIT X direction unstable excessive while acquiring an Please specified correct
FRCE-514 STOP (F:%d^1) environmental characteristic in the sensor index.
The force in the Y direction became following order; then
AIT Y direction unstable environmental characteristic in the parameters auto tuning
FRCE-515 STOP (F:%d^1) impedance parameters auto tuning. again. 1. Execessive force
The force in the Z direction became following order; then
AIT Z direction unstable environmental characteristic in the parameters auto tuning
The force in the W direction became following order; then
AIT W direction environmental characteristic in the parameters auto tuning
FRCE-517 STOP unstable (F:%d^1) impedance parameters auto tuning. again. 1. Execessive force
The force in the P direction became following order; then
AIT P direction unstable environmental characteristic in the parameters auto tuning
The force in the R direction became following order; then
AIT R direction unstable environmental characteristic in the parameters auto tuning
If the prepared default
Force control is disabled in all data for the application is
AIT all switch OFF directions during the impedance used, this error should not
FRCE-520 STOP (F:%d^1) parameters auto tuning. occur. Try to copy the
AIT X direction fail Impedance parameters auto tuning in parameters auto tuning
FRCE-521 STOP (F:%d^1) the X direction did not complete. again. 1. Stop any
AIT Y direction fail Impedance parameters auto tuning in parameters auto tuning
FRCE-522 STOP (F:%d^1) the Y direction did not complete. again. 1. Stop any
AIT Z direction fail Impedance parameters auto tuning in parameters auto tuning
FRCE-523 STOP (F:%d^1) the Z direction did not complete. again. 1. Stop any
AIT W direction fail Impedance parameters auto tuning in parameters auto tuning
FRCE-524 STOP (F:%d^1) the W direction did not complete. again. 1. Stop any
AIT P direction fail Impedance parameters auto tuning in parameters auto tuning
FRCE-525 STOP (F:%d^1) the P direction did not complete. again. 1. Stop any
AIT R direction fail Impedance parameters auto tuning in parameters auto tuning
FRCE-526 STOP (F:%d^1) the R direction did not complete. again. 1. Stop any
AIT system error Document the events that
Rotate angle limit The rotation angle exceeded the upper 'Phase Match Push F' in
FRCE-542 STOP (F:%d^1) limit during the phase match insertion. Basic Data. 2. Make sure
clutch ins. force lim. Force exceeded the limit during clutch decrease the amplitude of
clutch ins. & tuning ins. the search
auto tuningcheck if theins.
for clutch
FRCE-545 STOP (F:%d^1) tried to make auto tuning for clutch ins. is prohibitted
No custom cont. exe. Not customized force control were 1. Customize two force
FRCE-546 STOP (F:%d^1) continuously executed control schedule 2. Move
Customize no parent Previous executed force control was Execute child force
FRCE-547 STOP (F:%d^1) not parent force control control immediately after
Customize Position NG Final position of parent and initial Execute child force
FRCE-548 STOP (F:%d^1) position of child are different control immediately after
1. If you want to retry, set
Customize parent err Parent finished with error Child is for same frame number and
FRCE-549 STOP (F:%d^1) insetion reversed insert direction
Customize intr. err0 Document the events that
Customize intr. err1 Document the events that
Customize intr. err2 Parent finished with error Child is for Contact FANUC or FANUC
FRCE-552 STOP (F:%d^1) insetion Robotics and report the
Please confirm following
Force sensor is items: 1.Robot is
FRCE-631 abnormal Force sensor is abnormal. mastered. 2.Force sensor
Contact FANUC or FANUC
FRCE-632 Can't get variables Software internal error. America Corporation and
Contact FANUC or FANUC
FRCE-633 Can't set variables Software internal error. America Corporation and
Can't use WCG in case In case of fixed force sensor, Tool In order to use WCG,
FRCE-634 of fixed FS weight and center of gravity can't be Attach force sensor to
In case of this robot, there is no force In order to use WCG,
Can't use WCG with this sensor to be attached, Tool weight and change robot type that
FRCE-635 robot center of gravity can't be calculated. can have force sensor
Recording positions Recording positions failed. The real Please check the alarm
FRCE-641 failed cause is the alarm just below this one in history and then retry
Too many recorded Please reduce total
FRCE-642 positions Too many positions monitored monitoring time, or
No enough recorded Recording positions not finished, or NO Please finish monitoring
FRCE-643 positions enough monitored positions process, or increase total
Please run program
ImageToPoints Setting The setting of iRVision ImageToPoints PTPVINIT to initialize
FRCE-644 Error vision process is not right. iRVision Image To Points
Failed to run iRVision Image To Points Please check the setting of
FRCE-645 Image To Points failed vision process. iRVision ImageToPoints
iRVision Image To Points vision process (1) Please finish running
has not been executed or NOT enough iRVision ImageToPoints
FRCE-646 No enough edge points edge points detected. vision process. (2) Please
(1) Please check empty
Too many edge points Too many edge points detected by capacity of DRAM. (2)
FRCE-647 detected iRVision Image To Points vision process. Please check the setting of
Calculate initial data Failed to calculate initial data. The real Please check the alarm
FRCE-648 failed cause is the alarm just below this one in history and theninitial
Please calculate retry.
FRCE-649 No initial data No initial data data.
Generating TP program Generating TP program failed. The real Please check the alarm
FRCE-650 failed cause is the alarm just below this one in history and retry.
Please increase values of
FRCE-651 Too many teach points Too many teach points parameters Tolerant
(1) Please check the
message in the parameter
setting screen. (2) If alarm
FORC-656 occurred, check
FRCE-652 Parameter setting error Parameter setting error the setting of contouring
: (1)Please set user frame
so that camera view is in
+Z direction while
FRCE-653 Invalid UFrame setting Invalid User Frame setting snapping standard
NOT for robot with Ext Robots with extended axes are NOT Please change to robot
FRCE-654 axes supported. without extended axes to
(1) Please check the
Cannot find matched Cannot find edge line that matches to setting of iRVision
FRCE-655 edge line that of standard workpiece. ImageToPoints vision
Please refer to [8 Contour
The setting of contouring schedule data Sch Number] in [7.2.1
FRCE-656 Contour Schedule error is wrong. Parameter Setting] to set
The FROM disk does not have enough Delete all unnecessary
available memory to perform the files and then purge the
FRSY-001 WARN FROM disk is full specified command. device.
Format Ifthe
thedevice
devicebefore
is still
FRSY-002 WARN Device not formatted The device is not formatted. using it.
Verify all the parameters
FRSY-003 WARN Invalid parameter An invalid parameter is detected. for the requested
Copying a file to the FROM disk Mount the RAM disk
RAM disk must be requires that the RAM disk be mounted before specifying the
FRSY-004 WARN mounted with enough memory available to command.
Mount the device before
FRSY-005 WARN Device not mounted The device is not mounted. using it.
Device is already This is a notification. You
FRSY-006 WARN mounted The device is already mounted. do not have to do
FRSY-007 WARN Invalid device name The specified device is not valid. Verify the device name.
Delete the file first or
FRSY-008 WARN File already exists The specified file already exists. specify overwrite if
The maximum number of files is Either close one or more
FRSY-009 WARN Too many files opened already open. THerefore the requested of the files or set
An invalid file position is specified. The
FRSY-010 WARN Invalid file position position is beyond the end of the file or Check the file position.
Delete any unnecessary
No more files are allowed on the files or dismount and
FRSY-011 WARN Directory full device. remount MF: 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 Open the file with the
FRSY-012 WARN Invalid file access mode update or append to an existing file on proper access mode.
Delete all unnecessary
files and then purge the
The file cannot be created on the device. For more
Device is too device because not enough consecutive information on purging,
FRSY-013 WARN fragmented blocks are available. refer to the PURGE_DEV
Verify the file name and
FRSY-014 WARN File not found The specified file is not found.
file name contains an invalid the specified
Verify the fileor default
name is
FRSY-015 WARN Invalid file name character
The or is
file type blank. an invalid
contains correct.
Verify the file type is
FRSY-016 WARN Invalid file type character. correct.
File not open Open the
FRSY-017 WARN File not open The file is not open. file before accessing.
The requested command cannot be Close the file before
FRSY-018 WARN File is already opened performed because the file is already specifying the command.
Command is not The specified command is not This is a notification. You
FRSY-019 WARN supported supported for the device. do not have to do
The RAM disk does not have enough Delete all unnecessary
available memory to perform the files and then purge the
specified command. Note that copying device. For more
a file to the FROM disk requires that information on purging,
FRSY-020 WARN RAM disk is full the RAM disk be mounted with enough refer to the PURGE_DEV
This is a notification. Your
FRSY-021 WARN End of file The end of the file is detected. do not have to do
You must backup all your
The file identification number has files, reformat the device,
File ID exceeded reached the maximum number for the and restore the files. Refer
FRSY-022 WARN maximum device. to chapter 9, "File
If you require more
No blocks were purged for one of the blocks, you must backup
following reasons: 1) No garbage blocks all your files, reformat the
exist. 2) No spare blocks exist because device, and restore the
FRSY-023 WARN No blocks were purged the FROM disk is full. files. Refer to chapter 9,
Set $PURGE_ENBL to
TRUE and retry the purge
You are not allowed to purge the FROM operation. You may wish
FRSY-024 WARN Purge
Logicalisblock
disabled
already disk because purge is disabled. to set $PURGE_ENBL to
FRSY-025 WARN assigned
You should backup all
your files, reformat the
One or more files on the FROM disk are device, and restore the
corrupted. This may occur if the FROM files. Refer to chapter 9,
FRSY-026 WARN CRC check failed is wearing out. "File System", in the
FRSY-027 WARN Invalid logical block
The system will continue
%d out of %d bad to operate as long as
FRSY-028 WARN FROM
Attempt blocks
to cmprs w/o The FROM disk is wearing out. enough blocks are
FRSY-029 WARN u.c. data to dcmprs w/o
Attempt
FRSY-030 WARN cmp.does
File datanot have
FRSY-031 WARN headers
header not found in
FRSY-032 WARN readheader
r/w headernot at start
FRSY-033 WARN of file
Invalid compression
FRSY-034 WARN version no.
FRSY-035 WARN End of directory
A file parsing error has occurred. An Correct the model file and
FXTL-001 File parsing error error exists in one of the model files. copy it to the controller.
Not enough values on Not enough values on line. There are Correct the model file and
FXTL-002 line not enough values on a line in one of copy it to the controller.
Numeric conversion A numeric conversion error has Correct the model file and
FXTL-003 error occurred. A value on a line in a model copy it to the controller.
The output buffer is too small. A file Document the events that
FXTL-004 Output buffer too small output line exceeds the size of the led to the error, and
An unexpected internal library error Document the events that
FXTL-005 Internal library error has occurred. led to the error, and
An invalid unit number was specified in Specify a unit number that
FXTL-006 Invalid unit number a command or within a model file. is valid for the particular
Specify a CPU number
An invalid CPU number was specified in that is valid for this
FXTL-007 Invalid CPU number the mapping assignment. controller configuration.
Invalid motion group. An invalid motion Specify a motion group
group was specified in the mapping that is valid for this
FXTL-008 Invalid motion group assignment. controller configuration.
Loop number out of Loop number out of range. A LOOP Correct the model file and
FXTL-009 range number in a model program is out of copy it to the controller. A
Too many sensor There are too many offsets or no Correct the model file and
FXTL-010 offsets offsets specified on a SENSOR_READ copy it to the controller.
Maximum payload A payload was specified that exceeds Correct the model file and
FXTL-011 exceeded the maximum for the particular unit. copy it to the controller.
An invalid sensor slot was specified in Correct the model file and
FXTL-012 Invalid sensor slot an OFFSET line in a model file. copy it to the controller.
An invalid model name was specified in Correct the model file and
FXTL-013 Invalid model name a MODEL line in a model file. copy it to the controller.
An invalid model number was specified Correct the model file and
FXTL-014 Invalid model number in a MODEL_NUM line in a model file. copy it to the controller.
No NEWMODEL file: A NEWMODEL.PTS file was not found in Correct the model file and
FXTL-015 T%d the tray's root directory or could not be copy it to the controller.
Invalid NEWMODEL file: An invalid index file exists: T%d. An Correct the model file and
FXTL-016 T%d entry in the NEWMODEL.PTS file could copy it to the controller.
Memory allocation Memory for the tray data structures Document the events that
FXTL-017 error could not be allocated. led to the error, and
A file specified in the NEWMODEL.PTS Correct the model files
FXTL-018 File open error file could not be found and/or opened. and copy them to the
No cell data file exists: T%d. A cell data
file was not found in the tray's root Correct the model file and
FXTL-019 No cell data file: T%d directory or could not be opened. copy it to the controller.
No model program file exists: T%d. A
model program file that was specified
No model program file: in the NEWMODEL.PTS file was not Correct the model file and
FXTL-020 T%d found in the tray's root directory or copy it to the controller.
There was an error during processing Check the error log and
FXTL-021 Invalid model file set the set of model files for the tray. listing for more details
Invalid positioner An invalid mechanical unit type was Specify a supported
FXTL-022 variant specified in a command or within a variant type.
Error in cell data file: An error was found in the cell data file Check the error log and
FXTL-023 T%d for the tray. listing for more details
An unrecognized keyword was found Correct the model file and
FXTL-024 Invalid keyword in file when reading one of the model files. copy it to the controller.
No unit mapping file: The unit cpu/group mapping file was
FXTL-025 T%d not found in the tray's root directory or Correct or create the file.
Invalid unit mapping The unit cpu/group mapping file Check the error log and
FXTL-026 file: T%d contains incorrect entries and could listing for more details
Wrong number of units A model program has the wrong Correct the model file and
FXTL-027 in prog number of units vs. the number copy it to the controller.
Error in program file: A model program file has incorrect or Check the error log and
FXTL-028 T%d invalid lines and could not be listing for more details
Invalid model Model numbers must all be specified or Correct the model files
FXTL-029 assignment: T%d all set to the defaults. and copy them to the
Duplicate model More than one model program has the Correct the model files
FXTL-030 numbers: T%d same model number specified. and copy them to the
A POSITIONER_MOVE statement was Correct the model files
FXTL-031 Missing MOVE subkeys not followed by any move command and copy them to the
Duplicate BUILD_BEGIN More than one BUILD_BEGIN or Correct the model files
FXTL-032 or END BUILD_END line was found in a model and copy them to the
More than one LOOP_BEGIN/END Correct the model files
FXTL-033 Duplicate LOOP number statement specifies the same loop and copy them to the
Invalid A subkey following a Correct the model files
FXTL-034 POSITIONER_MOVE POSITIONER_MOVE is invalid or in the and copy them to the
A BUILD_BEGIN did not have a Correct the model files
Unmatched BUILD_END, a LOOP_BEGIN did not and copy them to the
FXTL-035 BUILD_BEGIN or loop have a LOOP_END, or there was some controller.
Error writing model file: An error occurred while creating or Check the error log and
FXTL-036 T%d writing a new version of one of the listing for more details
Tray has unmapped The tray has one or more units that Assign or correct the unit
FXTL-037 units: T%d have not been mapped to a CPU and mappings and restart.
The tray has one or more units that are
Tray has mapping mapped to the same CPU and the Assign or correct the unit
FXTL-038 conflict: T%d motion group as another unit on the mappings, and restart.
Unit not mapped: T%d The specified unit has not been Assign or correct the unit
FXTL-039 U%d mapped to a CPU and motion group. mappings and restart.
Mapping conflict: T%d The specified units have the same CPU Assign or correct the unit
FXTL-040 U%d and group mapping. mappings and restart.
There were errors in the assignment of Check the error log for
positioners to specific CPUs and motion more specific details, then
FXTL-041 Unit mapping error(s) groups. The specified units have the assign or correct the unit
Tray verification failed: Verification of the tray model files Check the error log for
FXTL-042 T%d failed due to an error in the files or in more specific details, then
Prog conversion An error occurred in the process of Check the error log for the
FXTL-043 process error converting the model programs to their specific details.
The mechanical variant type specified Correct the model files or
Variant type mismatch: in the cell data does not match the the physical unit
FXTL-044 T%d U%d actual positioner for the specified tray configuration.
The tray has one or more mismatches Check the error log for
Tray has variant of mechanical variants specified in the more specific details, then
FXTL-045 mismatch cell data file vs. the actual make the required
An error occurred while creating or Check the error log and
FXTL-046 Error writing TPP file writing a new TPP file for a model listing for more details
An invalid unit number was specified in Specify a tray number that
FXTL-047 Invalid tray number a command. is valid for the particular
Invalid program An invalid program number was Specify a program number
FXTL-048 number: T%d P%d specified in a command or by the PLC. that is valid for the
Program conversion err: An error occurred while converting the Check the error log and
FXTL-049 T%d P%d model program to the internal TPP listing for more details
No CPU RIPE communications exist. Verify that the internal
No CPU RIPE There are no internal network network connections and
FXTL-050 communications communication connections with one the Ethernet switch are
Program conversion timed out. A Turn off the controller
Program conversion request to convert a model program to and then turn it on again.
FXTL-051 timed out a TP program has taken too long to If the problem persists,
Program file transfer A TP program converted from a model Check the error log and
FXTL-052 failed program failed to be copied to its listing for more details
The model move command has Correct the command
FXTL-054 Invalid move command specified a program or step number data or the model
One or more units on the tray that are Enable all units and retry
FXTL-055 Not all units enabled required for the model move are not the operation.
The tray is not in a valid position in Check the positions of the
FXTL-056 Tray not in valid state order to do a legal model step move. units. Use the model
Move command out of The requested model move is out of Correct the command
FXTL-057 sequence sequence according to the model data or use the OVERRIDE
Move command The requested model move has been Check the error log for
FXTL-058 rejected: T%d rejected. The move was not initiated. more details on the exact
The command is rejected because the Wait for the tray to finish
tray or one or units on the tray are the previous operation,
FXTL-059 Tray is busy busy completing a previous operation and retry the operation
One or more units on the tray that are Initiate a full initialization
required for the model move do not or data verification for the
FXTL-060 Not all units verified have the proper programs loaded and tray.
The PLC interface has put the tray into Use the PLC to put the
FXTL-061 Tray is in AUTO mode AUTO mode and the requested tray into MANUAL mode,
The PLC did not clear the CR bit within Check and correct the PLC
FXTL-062 PLC CR not cleared: T%d the allowable time after the controller program.
An invalid axis number was specified in Specify an axis number
FXTL-063 Invalid axis number a command. that is valid for the
The specified positioner has been Undo the bypass or
FXTL-064 Unit is bypassed disabled or bypassed. change the unit number.
The tray is in a HOLD state because the Clear the HOLD condition
FXTL-065 Tray %d in HOLD state PLC NOHLD bit is OFF. from the PLC, and retry.
An invalid positioner group number Specify a valid group
FXTL-066 Invalid group number was specified in a GROUP statement. number in the range from
Duplicate group A duplicate positioner group number Edit the file so that each
FXTL-067 number was specified in a GROUP statement. GROUP specifies a unique
Invalid PLC command: The PLC sent a command that is invalid Correct the PLC logic to
FXTL-068 T%d or not supported. send only valid command
Invalid PLC data value: A data value sent by the PLC is not Correct the PLC logic to
FXTL-069 T%d valid, such as the unit number, send only valid command
Error state recovery is not possible for Put the tray into a valid
Tray %d ESR not this tray at this time. The previous state by using the model
FXTL-070 possible commanded state cannot be move override feature,
There is an invalid value assigned for Assign the correct rack
Invalid I/O the rack and/or slot number for the and slot for the fieldbus
FXTL-071 configuration fieldbus I/O device for the tray. interface that is actually
An invalid program step number was Use the correct step
Invalid program step specified. The step number is out of number for the specified
FXTL-072 number range or is not a valid step for the program.
A model file processing error occurred Check the other entries in
in the file as shown at the specified line the alarm log for the type
FXTL-073 Error %s line %d number. of error that was
A step number in the model file is out Correct the model file by
Step number sequence of sequence. Steps must be numbered fixing or renumbering the
FXTL-074 error sequentially with no missing numbers. cell step lines.
Invalid program An invalid program number was Specify a program number
FXTL-075 number specified. that is valid for the
A shim was calculated or specified that Specify a smaller shim
is out of range of the limits specified for value, change the limits in
FXTL-076 Shim value out of range this unit. the celldata.pts file, or use
Rotational shim not A forward/backward shim search Do not do a shim search if
FXTL-077 allowed cannot be done for a rotational shim. the current shim has a
A position that was specfied as IDLE in Shim the previous actual
the model points file cannot be directly move step and the IDLE
FXTL-078 Cannot shim IDLE move shimmed. position will also get the
One or more of the sub-CPUs did not Determine the reason for
start up or was not detected on the the CPU startup failure, or
internal network. The tray(s) that try cycling power on the
FXTL-079 Sub-CPU did not start depend on the positioners on that CPU controller.
The model files for the specified tray
have been successfully converted and
FXTL-080 Tray %d ready to run the tray is ready for manual or PLC None.
PATH_END without A PATH_END statement was found Make sure that
FXTL-081 PATH_BEGIN without a matching PATH_BEGIN PATH_BEGIN and
PATH_BEGIN without A PATH_BEGIN statement was found Make sure that
FXTL-082 PATH_END without a matching PATH_END PATH_BEGIN and
There must be at least three Make sure that there are
Not enough steps in POSITIONER_MOVE statements the correct number of
FXTL-083 PATH between a PATH_BEGIN and a steps within a path-move
Path command The requested path move has been Check the error log for
FXTL-084 rejected: T%d rejected. The move was not initiated. more details on the exact
A path move can only be
Requested step is not a The requested step is not a valid step made to the last step or
FXTL-085 path for a path move. first step within the path
All units on the tray must
The units are not at a valid position or be at a move step that is
Current position not in are not at a valid step for doing a path within the defined path
FXTL-086 path move. move block. Move the
Vision command The requested vision or sensor Check the error log for
FXTL-087 rejected: T%d command has been rejected. more details on the exact
A vision or sensor operation was Take action to start the
commanded, but there is no vision or vision or sensor
FXTL-088 app not running
Vision operation failed: sensor
The application
requested running.
vision The
or sensor application
Check whenlog
the error the
for
FXTL-089 T%d operation failed. more details on the exact
Vision application timed The vision or sensor user application Make sure that the
FXTL-090 out did not respond to the command in the program is running and is
A vision or sensor offset was specified Correct the vision offset
Vision offset out of that is out of range of the limits value, change the limits in
FXTL-091 range specified for this unit. the celldata.pts file, or use
A model move for a single unit or a Issue an override (MMO)
FXTL-092 Move requires override group of units requires the override command before trying
An invalid value was specified in a
LIN_SPEED, JNT_SPEED,
DEF_LIN_SPEED, or DEF_JNT_SPEED Correct the statement and
FXTL-093 Invalid speed specified statement. Linear speed must be from retry.
Sig File Copied. Cycle Signature file for wall mount units have Information only. Not a
FXTL-099 Power been copied. Cycle Power to take problem.
Wall mount units cannot find sig file in
its FR: Hex data: 00 00 00 00 has 4
bytes. only lower 3 bytes are used to Indentify which unit's sig
indicate status for cpu3 cpu2 cpu1 each file is missing. Copy sig file
bit is for a group in that cpu. LSB is G1 again in flextool setup
FXTL-100 Missing SIG File Hex:%x e.g. 00 00 04 00 indicates cpu2 G3 wall menu.
Error occurred during sig file checking. Check that sig files for all
CPU Hex:%x miss sig file CPU mask is in Hex. LSB is cpu1. e.g. wall mount units are
FXTL-101 chk CPU Hex:3 means CPU-2 and CPU-1 copied to FR: of each cpu
Warning indicating the available MBE Wait until MBE memory
MBE memory Low C:%d memory size is substantially low, and is comes back, or you may
FXTL-102 Free:%d affecting the performance. This may be need to cycle power if the
Some units are not ready for motion. Visit the error history
Unit not ready CPU%d The error text shows the CPU number page to find related servo
FXTL-103 G:%s and group number whose servo is not error. You may also need
FXTL-151 Press Shift key. The shift key is not pressed Press the shift key.
Use this menu to map a
FXTL-152 No unit assigned. No unit has been assigned. unit number with a
Unit(%d) invaild Check the hardware to
FXTL-153 mapping. The unit has invalid mapping. make sure the mapping is
FXTL-154 No tray is defined. No tray has been defined. Perform a data verify first.
Perform a data verify first,
FXTL-155 Invalid step number. The Step number is not valid. then select the valid step
Not all units are in the correct position Go to the model move
FXTL-156 Programcopy
Cannot is undefined.
file to for acannot
You model copy
move.a The Tray to
file back cannot
its menu and
Select move the
a different tray
device
FXTL-157 same dev device. for the file copy
No unit in the Tray. No unit is defined Check the unit mapping
FXTL-158 No unit in the Tray. for the tray. and Unit enable menu.
Check the model file
FXTL-159 Program has no step. The program has no motion step. offline and copy the file to
Zero mastering Non-Zero mastering has been applied. Move all axes to their zero
FXTL-160 required. Zero mastering must be performed mastering position.
Cannot read/write shim Cannot open shim log file in FR: Check memory status to
FXTL-161 log. directory. make sure space is
Shim cannot be Cannot restore this shim in the shim log
FXTL-162 restored. because it is no longer valid due to None.
An error has occurred in reading the The shim log file has been
FXTL-163 Invalid shim log entry. shim logshim
Invalid file.data. Cannot display the corrupted.
Select Load
a valid itemthe
onshim
the
FXTL-164 Invalid shim data. shim shim
New item.data is all zero. No shim is shim log.
FXTL-165 Zero shim data. applied. Enter non-zero shim data.
Move the units to the first
FXTL-166 Cannot switch program. Cannot change model program or lastthe
Move stepcursor
of thetomodel
a unit,
FXTL-167 No unit selected. The cursor is not on a unit. then press the ENTER key.
The jog keys are disabled in C-flex axis Exit from the C-flex axis
FXTL-168 Jog keys are disabled. jog or frame jog menu. jog or C-flex frame jog
FXTL-169 Jog keys
Teach are enabled.
Pendant is The jog keys are enabled. None.
Turn on the teach
FXTL-170 disabled. The teach pendant is disabled. pendant.
Invalid shim move has occurred. Yoc Use Model Move to move
cannot execute a shim move due to the units to the shim step
FXTL-171 Invalid shim move. mismatch of tray number, program before shimming the
Inverse Kinematic Error. The calibrated Jog the robot or teach the
inverse kinematics does not converge position away from the
FXTL-201 Inverse kinematic error. to a solution. The unit is close or at a singular
Turn position.
off/on the controller
FXTL-202 Invalid wrist type. The wrist type is not supported. to get correct wrist type.
The motion group is either not Make sure the group
FXTL-203 Invalid motion group. available or it is not a C-flex unit. number is valid.
The program is not in the model Make sure to do a data
FXTL-204 Invalid program name. program list. verify before running the
The teach pendant program has an Make sure to do a data
FXTL-205 Invalid TP position type. invalid position data type. verify before running the
The robot is close to a singularity point Jog the unit away from
FXTL-206 Singular position. where there is no solution for the singular
Make sureposition
the tooland
vector
FXTL-207 Invalid TOOL vector. Invalid TOOL vector exists. is defined.
GUID-000 WARN Rotation
Speed limit exceeded
speed limit speed exceeded
Command rotation limits.
speed exceeded Reduce sensor gain.
GUID-001 WARN exceeded
Excessive motion limits. Reduce sensor gain.
GUID-002 SERVO command Motion command exceeded limits. Reduce sensor gain.
Other source tried to execute motion
GUID-003 SERVO Teach Device
Limit error, Enabled
axis num while LeadThru device was enabled. Disable teach device.
GUID-004 WARN %d^3 limit, axis num
Torque Limit or singularity encountered. in other
Move away fromdirection.
object if
GUID-005 WARN %d^3 Motor torque disturbance detected. collision occurred.
GUID-006 SERVO Motion limit exceeded Software motion limit exceeded. Check SMON for details.
Excess command Reduce gains or velocity
GUID-007 SERVO torque %d^3 Command torque exceeded set limits. limit parameters to avoid
Excess joint velocity Reduce gains or velocity
GUID-008 SERVO %d^3 Joint velocity exceeded set limits. limit parameters to avoid
Reduce gains or velocity
GUID-009 WARN Joint velocity limit %d^3 Joint velocity exceeded set limits. limit parameters to avoid
ABORT. Automatic Motion A program attempted motion Automatic Motion
GUID-050 G Disabled commands while the IAD is in manual Disabled Manual mode
Liveman switch tied Liveman switch tied down or liveman Remove interfering
GUID-051 WARN down hardware
An failure.
unexpected fault occurred during object, instructions
Follow increase for
GUID-052 WARN Excessive
Tracking fault
Track%d^3
Speed. line tracking.
The line speed indicated by the indicated
Fix encoder fault number.
problem or
GUID-053 WARN L:%d^3 encoder is too fast. reduce line speed to safe
End of Travel Warning. The operator crossed the end of travel The line speed may be too
GUID-054 WARN L:%d^3 warning point while line tracking. fast to finish the cycle in
End of Travel Hold. The operator crossed the end of travel The line speed may be too
GUID-055 WARN L:%d^3 hold point while line tracking. fast to finish the cycle in
End of Travel Stop. The operator crossed the end of travel The line speed may be too
GUID-056 SERVO L:%d^3 stop point while line tracking. fast to finish the cycle in
Can't init tracking. Tracking won't start due to an Fix problem indicated on
GUID-057 WARN L:%d^3 initialization problem. Check SMON for SMON.
Queue overflow. Tracking queue overflowed: too many Set LEN, OUT_BOUNDS,
GUID-058 WARN L:%d^3 parts in the queue. The oldest queue and DETECT_DIST to
Current queue lost. Set LEN, OUT_BOUNDS,
GUID-059 SERVO L:%d^3 Lost queue entry was in use. and DETECT_DIST to
LT File R/W while Attempted to read or write logic table LT File R/W while moving.
GUID-060 WARN moving. text file while the IAD is in operation. Engage brakes before
GUID-100 WARN Unknown error An internal error has occured. Cold start the controller
Cannot run monitoring
Cannot run monitoring Cannot start the KAREL shell program task Abort
GUID-101 WARN task to monitor I/O events unwanted/paused KAREL
Cannot calibrate Cannot calibrate sensor.
GUID-102 WARN sensor. Cannot calibrate the force sensor. No lead thru teaching
This error occures when lead thru teach TPE operation error. Make
GUID-103 WARN TPE operation error. cannot access the TPE program. sure the TPE program
Invalid TPE program Invalid TPE program
GUID-104 WARN name. The TPE program does not exist. name. Make sure the TPE
Robot is not ready. Make
GUID-105 WARN Robot is not ready. Cannot
The leadmove
thru or record
teach a
software does not sure the
Lead Thrurobot is mastered
not loaded.
GUID-106 WARN Lead Thru is not loaded. load properly. Reload the lead thru
Invalid Single Step The lead thru teach software does not Invalid Single Step Mode.
GUID-107 WARN Mode. work in single step mode. Turn off the single step
No data read from AIN No data read from AIN
GUID-108 WARN port No data comes from the AIN ports. port Check AIN port
Analog ports are Analog ports are invalid.
GUID-150 WARN invalid. The analog port setting is invalid. Please check the DIO
Unusual force sensor load.
Unusual force sensor New force sensor zero setting exceeded Remove foreign object
GUID-151 WARN load. change limits during auto-zeroing. from operator controls or
Force sensor overload Force measurement exceeded allowed Force sensor overload
GUID-152 SERVO A:%d^3 limits. A:%d^3 Reduce force on
Copying a DSP program from ROM to Force sensor ROM error
GUID-153 SERVO Force sensor ROM error RAM failed (DSP init). Replace sensor head,
SLC-2 (Serial Link Controller-2) Force sensor SLC-2 init
GUID-154 SERVO Force sensor SLC-2 init initialization failed (DSP init). Replace sensor head,
SLC-2 (Serial Link Controller-2) Force sensor SLC-2 init
GUID-155 SERVO Force sensor SLC-2 init initialization failed (DSP init). Replace sensor head,
Force sensor data req Force sensor data req fail
GUID-156 SERVO fail
Force sensor outer Data request to sensor head failed. Replace sensor
Force sensor head,
outer parity
GUID-157 SERVO parity sensor inner
Force Parity error on FS I/F board outer RAM. Replace
Force interface
sensor innerboard.
parity
GUID-158 SERVO parity Parity error on FS I/F board inner RAM. Replace interface board.
Force sensor comm Force sensor comm failure
GUID-159 SERVO failure Communication failed on FS I/F board. Replace sensor head,
Force sensor comm Force sensor comm failure
GUID-160 SERVO failure Communication failed on FS I/F board. Replace sensor head,
Force sensor comm Communication failed on FS I/F board. Force sensor comm failure
GUID-161 SERVO failuresystem
F-bus (parity, framing,
Non-force sensorCRC, etc.)emergency
system Replace
F-bus sensor
system head,
emergency
GUID-162 SERVO emergency error on F-bus Correct source of error.
Force sensor watch dog
GUID-163 SERVO Force sensor shared
watch dog Force sensor interface watchdog alarm. Replace
Force sensor
sensor head,parity
shared
GUID-164 SERVO parity Parity error in shared memory. Replace interface board.
Force sensor local Force sensor local parity
GUID-165 SERVO parity Parity error in local memory. Replace interface board.
Force sensor SIR1 SLC-2
GUID-166 SERVO Force sensor SIR1 SLC-2 SLC-2, SLDM, or SLDS error. Replace sensor head,
Force sensor dist link Distributed link error between head Force sensor dist link
GUID-167 SERVO comm and interface. comm Replace sensor
TCP Mate motion The TCP Mate motion aborted due to TCP Mate motion
GUID-200 WARN aborted. unexpected change of of menu, or aborted. Please start
Form Operation Error.over.
GUID-201 WARN Form Operation Error. Dictionary not found. Please reload the
System is not initalized.
GUID-202 WARN System is not initalized. System not been fully initialized. Use the Setup menu to set
Fail to run TCPMate Fail to run TCPMate
GUID-203 WARN Motion Cannot start the TCP Mate motion. Motion Clear all the errors
Please record all Not all positions in the reference menu Please record all position
GUID-204 WARN position are recorded. All positions in the menu
Do reference motion Cannot execute the TCP mate without Do reference motion first.
GUID-205 WARN first. mastering TCP first. Please go to reference
Point is not initialized.
GUID-206 WARN Point is not initialized. Positionrecord
Cannot is not initialized. Please isrecord
position since the robot Robot positions in
not calibrated.
GUID-207 WARN Robot is not calibrated. is not calibrated Calibrate the robot first.
Record home position Please record approach point before Record home position first
GUID-208 WARN first record other positions Record home position.
Keep same WPR as These position require to have the Keep same WPR as home
GUID-209 WARN home pos. same WPR as the home position. pos. Keep the same
Press SHIFT key at the same time when Please press SHIFT key.
GUID-210 WARN Please press SHIFT key. this key is pressed Press SHIFT key to active
The current TCP and previous differs TCP differs by %s Check
GUID-211 WARN TCP differs by %s more than pre-defined threshold. for loose hareware or too.
TCPMate logs the previous TCP XYZ
GUID-212 WARN XYZ: %s value to error log for record keeping. XYZ: %s None.
TCPMate logs the previous TCP WPR
GUID-213 WARN WPR: %s valuedestination
The to error logposition
for record keeping.
is not None. is not in range. Re-
Position
GUID-214 WARN Position is not in range. reachable. teach a new starting pos.
Singular solution. Check
Cannot compute the circle due to and correct robot's
GUID-215 WARN Singular solution. singularity. mastering. Check
Cannot converge. Check
and correct robot's
GUID-216 WARN Cannot converge. Cannot converage to a a solution. mastering. Check
Recorded positions are too close to Points are too close.
GUID-217 WARN Points are too close. each other. Points should be at least
Robot is in contact with the part before Contact before search.
GUID-218 WARN Contact before search. starting a search motion. Reteach the starting
No contact is made druing the TCP No contact detected.
GUID-219 WARN No contact detected. Mate motionl. Make sure the sensor and
Undefined program The enter/exit program names are not Undefined program name.
GUID-220 WARN name. defined. Go to
TPE the setuperror.
operation menu to
GUID-221 WARN TPE operation error. Internal TPE program error. Please reload the
The circle fitting error is greater than Circle Fitting error: %s.
GUID-222 WARN Circle Fitting error: %s. expected. Check hareware/tooling
The search motion can not be executed No DIN support. Go to
GUID-223 WARN No DIN support. withtout TOS sensor. setup menu and select
Cannot continue Cannot continue motion.
GUID-224 WARN motion. Cannot continue the paused motion. Abort the paused motion
TCP Mate internal TCP Mate internal error.
GUID-225 WARN error.
Dictionary is not TCP Mate internal error. Power off to
Dictionary recover.
is not loaded.If
GUID-226 WARN loaded. Dictionary file is not loaded Please reload the
No saved reference No saved reference data for current No saved reference data.
GUID-227 WARN data. tool. Please
File do error:
open reference%s Check
GUID-228 WARN File open error: %s Cannot open output file. the recorded
No path and Utool.
file name.
GUID-229 WARN No recorded Utool. No recorded utool to save. Recorded a new utool.
Not enough TPE stack. Go
The TPE program does not have to the TCPMATE main
ABORT. enough stack size to run TCPMate menu, TCPMate will
GUID-230 G Not enough TPE stack. automatically. update your TPE program
ABORT. Cannot generate TCP TCPMate cannot complete it's Cannot generate TCP
GUID-231 G offset operation successfully. offset Check for sever tool
PAUSE. Collision, Axis %d^3 Collision (G:$d^2, A:%x^3
GUID-232 G (G:$d^2) Collision during motion Hex) Reteach
Software starting
loading error.
GUID-250 WARN Software loading error. Software loading error. Please reload the
Invalid data range. Please
GUID-251 WARN Invalid data range. The specified data range is invalid. check the max_value and
Invalid I/O Port setting.
GUID-252 WARN Invalid I/O Port setting. Cannot access to the specified I/O port. Please use the I/O menu
Cannot access to the specified system Invalid system variable.
GUID-253 WARN Invalid system variable. variable name. Check the
Invalid spelling
torque setup.of the
GUID-254 WARN Invalid torque setup. Cannot access to specified torque data. Please reload the
No contact with the
No contact with the Robot does not have a contact with the chuck. Increase the search
GUID-300 WARN chuck. chuck during search motion. distance under the setup
Cannot update prostion Cannot update the specific position Cannot update prostion
GUID-301 WARN reg register. reg Make sure the
Failed to run search Failed to run search motn.
GUID-302 WARN motn. Cannot start the motion task. Aborted paused KAREL
Another motion task is running cannot Other task is running.
GUID-303 WARN Other task is running. start a new motion. AbortedSoftWall:
Invalid the running task
%s Enter
GUID-350 WARN Invalid SoftWall: %s Invalid parameters in SoftWall correct SoftWall
Cone: Bad SoftWall Type
Cone[%d^2]: Bad Cone does not support SoftWall type %d^2 Use a supported
GUID-351 WARN SoftWall Type for limiting. SoftWall type.Too
Cone[%d^2]: Supported
short
GUID-352 WARN Cylinder[%d^2]:
Cone[%d^2]: TooToo
short Cone is too short. Define cone to be
Cylinder[%d^2]: Toolonger.
short
GUID-353 WARN short Cylinder is too short. Define cylinder to be
Spline[%d^2]: Too few Spline[%d^2]: Too few
GUID-354 WARN Spline[%d^2]:
points Too many Too few control points in spline. points Use at least
Spline[%d^2]: 3
Too many
GUID-355 WARN points Too many control points in spline. points Use correct n
Spline[%d^2]: Spline[%d^2]: Regressive
GUID-356 WARN Regressive Control points are regressive. Redefine control points or
Spline[%d^2]: Bad
Spline[%d^2]: Bad Cone does not support SoftWall type SoftWall Type Use a
GUID-357 WARN SoftWall Type for attach. supported SoftWall type.
Spline[%d^2]: Regr. Attached SoftWall causes spline Spline[%d^2]: Regr.
GUID-358 WARN SoftWall
Zone[%d^2]: Bad Zone regression. SoftWall Redefine
Zone[%d^2]: Bad Zonecontrol
GUID-359 WARN Type Invalid zone type. Type Use a valid zone
Zone[%d^2]: Bad Zone[%d^2]: Bad SoftWall
GUID-360 WARN SoftWall Type Invalid SoftWall type used in zone. Type Use a valid SoftWall
Cone[%d^2]: Bad radius
GUID-361 WARN Cone[%d^2]: Bad radius Invalid cone radius. Radius must be greater
Cone[%d^2]: Bad shape
GUID-362 WARN Cone[%d^2]: Bad shape Cone shape is undefined. Use a defined cone shape.
HIGH-000 WARN UNUSED ERROR CODE
ABORT. Specified HTdata The specified calibration data of height Please change index
HIGH-001 LPAUSE. doesn't exist sensor does not exist. number
Please setofaheight
propersensor
value
HIGH-002 L
PAUSE. $count_mesur is 0 $HSUSEDATA.$COUNT_MESUR
The is 0
sensing distance is out of effective to this check the position
Please
HIGH-003 L Distance is out of range range of work
Please calibrate the ration
PAUSE. Mesuring-pos doesn't The mesuring posistion DATA are not between the focal
HIGH-004 L exist correct position and the sensing
PAUSE. The calib-DATA isn't The specified calibration DATA is not Please calibrate this
HIGH-005 L effective effective calibration DATA in the
Please change current
tool frame refer to
PAUSE. The current tool frame is differnt from $HSINITCALB.$SUTOOL or
HIGH-006 L
ABORT. Tool frame
Height mismatch
sensor group is that when the calibration executed calibrate
Please the ration
change
HIGH-007 L illegal $HSMOGROUP is uneffective value $HSMOGROUP to
PAUSE. Distance to be moved is The corrected distance is too small The Please check height
HIGH-008 L small sensing seems not to be correct sensor and the position of
PAUSE. Distance to be moved is The corrected distance is too large The Please check height
HIGH-009 L large sensing seems not to be correct sensor and the position of
PAUSE. Moving_up distance is The move_up distance is different from Please change the
HIGH-010 L mismatch that when the calibration is executed move_up distance in
Motion from CALIB Condition of TP-motion is not filled or Please reset illegal status
HIGH-011 WARN screen
This faild
can't be taught Program
This is not aborted
statement can't be taught with or abort
You havecurrent program
to remove
HIGH-012 WARN with HEIGHT
HEIGHT can't be taught HEIGHT statement can't be taught with HEIGHT
You have to removefrom
statement
HIGH-013 WARN with OFST
HEIGHT can't be taught OFFSET statement can't be taught with
HEIGHT OFFSET
You havestatement
to removefrom
INC
HIGH-014 WARN with INC INC statement statement from this line
HEIGHT can't be taught HEIGHT statement can't be taught with You have to remove
HIGH-015 WARN with APPL Aplication statement Aplication statement from
End of directory Your listing has reached the end of the
HOST-001 WARN reached directory. You do not have to do This is a notification.
The file name you are trying to createDelete the file on this
HOST-002 WARN File already exists or copy to already exists on this device.
device or choose a
The file you are trying to open or copy
Open or copy a file that
HOST-003 WARN File does not exist does not exist on this device. exists on the device.
Illegal command The requested operation is not Use only supported
HOST-004 WARN received supported. operations, or check
Delete some unneeded
HOST-005 WARN Disk is full disk of
The end filethe
capacity has
file was been reached.
reached while Dofilesnot
or use a disktowith
attempt read
HOST-006 WARN End of file reached
Only one file may be reading.
An attempt was made to open more beyond the end of
Do not attempt to opena file.
HOST-008 WARN opened than one file. more than one file at a
iRConnect option not iRConnect option is not loaded or demo You may not use
HOST-009 loaded option expired. iRConnect features
iRConnect emails are Use the SETUP iRConnect
HOST-010 disabled All iRConnect emails are disabled. menu to enable all emails.
iRConnect To Addr not An attempt was made to send an Use the SETUP iRConnect
HOST-011 set iRConnect email when To Addr is not menu to set the To Addr.
iRConnect Alert Addr An attempt was made to send an Use the SETUP iRConnect
HOST-012 not set iRConnect alert when Alert Addr is not menu to set the Alert
iRConnect email An iRConnect email was not sent If possible, configure the
HOST-013 throttled because too many emails per minute emails so they are sent at
iRConnect email too An iRConnect email was not sent Try increasing
HOST-014 large because the size is too large. $RCMCFG.$SIZE_THROT.
Verify protocol field in the
HOST-100 WARN Communications error The protocol format was invalid. setup menu and retry the
The directory information is corrupted Clean the disk drive,try
HOST-101 WARN Directory read error and unreadable. another disk or reformat
The checksum data is bad. Data is Try another disk, or
HOST-102 WARN Block check error corrupted on the disk and can not be reformat the disk
There is a bad sector or track on the Clean the disk drive, try
HOST-103 WARN Seek error disk. another disk, or reformat
The drive did not respond to a Check the cable to the
HOST-104 WARN Disk timeout command. drive and make sure drive
HOST-105 WARN violation The disk has write protection enabled. from the disk or use a disk
$PROTOENT entry not Protocol Entry structure ($PROTOENT) Return Protocol Entry
HOST-106 WARN found is invalid. It should be reset to default structure to initial values
$SERVENT entry not Server Entry structure ($SERVENT) is Return Server Entry
HOST-107 WARN found invalid. It should be reset to default structure to initial values
Internet address not Set Internet Address in
HOST-108 WARN found Internet Address needs to be set. the Setup Host Comm
Set Host Name and
HOST-109 WARN Host name not found Host Name needs to be set. Internet Address in the
The Remote Node Name needs to be Set Remote Node Name in
HOST-110 WARN Node not found set. the Host Comm TCP/IP
Cycle power to use ER-1 or ER-2 Ethernet hardware is Turn off and then turn on
HOST-111 WARN Ethernet already running and can not be the controler.
The TCP/IP Stack has encountered a Copy ETHERNET.DG file
situation that may result in corruption from MD: and save it.
or disruption in normal network Note the PANIC string.
HOST-112 WARN PANIC: %s activity. Cycle power to the
This alarm generally
implies that either the
Proxy or the TCP/IP
interface is not set up
correctly. Verify network
connectivity to the robot
The robot controller Proxy was not able controller using the ping
HOST-113 PROXY: %s bind error to bind a TCP network socket. utility (on the robot, and
A new TCP/IP socket cannot be Check for abnormal
allocated because all system resources activity with all installed
HOST-114 WARN PROXY: %s socket error are in use. internet options. Obtain
implies that either the
Proxy or the TCP/IP
interface is not set up
correctly. Verify network
connectivity to the robot
The robot controller Proxy was not able controller using the ping
HOST-115 PROXY: %s listen error to listen on a TCP network socket. utility (on the robot, and
Configure the External
The External Proxy Server is not Proxy Server with a valid
PROXY: Remote proxy configured with a valid Hostname or IP Hostname or IP Address. If
HOST-116 error Address. the the
Set problem persists,
Ethernet address
HOST-117 WARN PROXY: PMON error
Invalid Ethernet The Ethernet address needs to be set. in Configuration Menu.
Set the Ethernet address
HOST-126 WARN address
Ethernet firmware not address
The Ethernet Board needs toisbe
firmware notset. in Configuration
Load the EthernetMenu.
Board
HOST-127 WARN loaded loaded. firmware in BMON.
Ethernet hardware not The Ethernet Board needs to be Install or reseat the
HOST-128 WARN installed reinitialized. Ethernet Board.
Data received from external device is The error can be cleared
HOST-129 WARN Receiver error invalid. Most likely caused by electrical by Stopping and Starting
A buffer was passed to the Serial Port Ensure program can run
HOST-130 WARN Buffer alignment wrong Driver which can not be accessed. on this version of
The Host Comm system can not Stop and Start the Host
HOST-131 WARN Wrong state execute the requested command in the Comm Tag in the Host
The Host Comm system can not Either add more memory
HOST-132 WARN Can't allocate memory allocate memory buffers for receiving to the controller or
The Host Comm system is receiving Correct port settings: data
HOST-133 WARN Wrong setup conditions messages but can not decode them. rate, data size, stop bits,
The Host Comm system is receiving Ensure that the external
HOST-134 WARN BCC or CRC error checksum errors on all messages. device is using the same
There has not been any network
activity on the Comm Tag for a period
HOST-135 WARN Timeout specified by Inactivity Timeout. The Restart the Comm Tag.
The remote device is connected but is Check cabling between
HOST-136 WARN Device not ready not responding to requests. the devices and/or insure
The remote device indicates the The cancel command was
HOST-137 WARN Request cancelled operation was successfully terminated. successful.
The remote device did not indicate The command might have
HOST-138 WARN Request aborted operation was terminated. been completed before
The Host Comm Protocol does not Check the Host Comm
HOST-139 WARN Invalid function support
The the device
remote requested function. but it is
is connected Protocol
Set to ensure
the remote the
device
HOST-140 WARN Device offline not online. online.
The Host Comm Protocol could not be Either use another Comm
Protocol Start/Stop started (Mounted) or stopped Tag or Stop and Undefine
HOST-141 WARN error (dismounted) on the selected comm the selected Comm Tag
The Host Comm Protocol could not Ensure both local and
establish communication with the remote are using
HOST-142 WARN Connection error remote device. Possible software compatible software
Power the controller OFF
Comm port cannot be The selected hardware port defined for and then ON and try
HOST-143 WARN closed the Comm Tag could not be closed. again. If the error occurs
The Comm Tag either does not have a DEFINE a protocol to the
HOST-144 WARN Comm Tag error protocol defined or if required does not Comm Tag or assign a
An attempt has been made either to If possible, close and
read a file opened for write access only reopen the file with the
HOST-145 WARN Permission denied or to write a file opened for read access correct access
Bad address for Comm Verify the tag has a
HOST-146 WARN Tag A bad address has been detected. supported protocol then
The selected protocol requires a device First ensure the Port has
HOST-147 WARN Block device required port.
Either the Comm Tag is STARTED or it is No UseSTOP
Either fromthe
PortComm
Init
HOST-148 WARN Mount device busy presently in use. Tag or select another Tag.
The passed Device Type is not a Comm Only Comm Tags can be
HOST-149 WARN No such device Tag type (Cx or Sx). used with this command.
The system does not support selected Either select another
HOST-150 WARN Invalid argument protocol. protocol or install the
No more Ethernet The System has run out of buffers to Reduce the number of
HOST-151 WARN buffers. communicate with the Ethernet simultaneous connections
Consult your network
FTP: no connection An error occurred in the networking administrator. If the error
HOST-158 WARN available software. is not cleared, document
The Comm Tag does not have a valid Enter a valid username
HOST-159 WARN FTP: login failed username and password. and password for the
FTP: tag dismount An error occurred in the networking administrator. If the error
HOST-160 WARN request ignored software. is not cleared, document
FTP: need remote host The Comm Tag does not have a remote Enter a remote host name
HOST-161 WARN name host defined. in SETUP TAGS menu
FTP: Error on Ethernet The Ethernet PCB isn't initialized Ensure both Ethernet PCB
HOST-162 WARN EXMG:
Init. Invalid Buffer properly. firmware and Main PCB
HOST-163 WARN Size Invalid buffer size in call Ensure correct buffer size
Make a read call after
HOST-164 WARN EXMG: Read Pending Attempt to write before read. write before making
Unrecoverable a
- Contact
HOST-165 WARN EXMG: Internal Error Error in Explicit Messsaging Task. Help
A Desk.
write should precede
HOST-166 WARN EXMG: Write Pending Attempt to read before write. read.
EXMG: Connection Check cable & remote
HOST-167 WARN Error Explicit Messaging Connection broken device. Close connection
Invalid Channel specified. Channel may Make sure the channel
HOST-168 WARN EXMG: Invalid Channel not be online. specified is online or
Verify Path format
specified
HOST-169 WARN EXMG: Invalid Path Invalid Path Specified. EM:/DNET/1/10/40 DNET-
Verify Explicit Messaging
HOST-170 WARN EXMG: Message
Invalid Name Invalid Name specified. mappingconnection
Reopen system variables
with
HOST-171 WARN Truncated Connection Buffer size small. correct buffer size.
Make sure your host
name and local domain
HOST-172 WARN DNS: Host Not Found Domain Name Does Not exist name are correct. Your
Verify that you DNS server
is running. Check with
HOST-173 WARN DNS: Server Failure Problem with DNS server. your DNS administrator to
Verify that the host name
and local domain name
DNS: Format or and formated correctly.
HOST-174 WARN Recovery Error DNS Recovery Error . Verify that your server
Your host name is valid
and is recognized by the
DNS: Server Has No DNS server. The server has
HOST-175 WARN Address Server has no IP address listed. no IP address for the host
DNS: Configuration Go to the DNS
HOST-176 WARN Error DNS is not properly configured configuration menu and
Router Name Not No router name has been defined. The If your network has a
HOST-177 WARN Defined router name has been set to the robot router, then define a
Router does not have an address listed If your network has a
Router Address Not in the local host table. The router router, then define an
HOST-178 WARN Defined address will be set to the robot address for it in the local
Reconfigure the Ethernet
IP Address mis- interfaces such that each
HOST-179 WARN configuration The entered IP address is invalid. interface is on a different
NETMEM: buffer is not Internal software problem. Network Network memory should
HOST-180 WARN created memory occured
Timeout service request occurs
at getting before
memory be created
Network maybefore
overload if
HOST-181 WARN NETMEM: time out access right. this error occurs
Internal software problem. Specified Verify that correct buffer
HOST-182 WARN NETMEM: BD error network memory buffer descriptor was descriptor is specified.
Internal software problem. Network
NETMEM: buffer is auto memory update request issued to Verify that correct buffer
HOST-183 WARN ack mode automatic acknowledge transmit descriptor is specified.
NETMEM: transmit BD Internal software problem. Specified Verify that correct buffer
HOST-184 WARN error buffer descriptor is not for transmit descriptor is specified.
NETMEM: receive BD Internal software problem. Specified Verify that correct buffer
HOST-185 WARN error buffer descriptor is not for receive descriptor is specified.
NETMEM: send socket UDP open for datagram sending was Confirm that UDP port
HOST-186 WARN open fail failed. was consumed by another
NETMEM: receive UDP open for datagram receiving was Verify that there is
HOST-187 WARN socket open fail failed. RLSYNC entry
Verify that in
a correct port
HOST-188 WARN PPP init on port %d fails invalid port/insufficient memory number
Verify is specified
that a correct port
HOST-189 WARN Invalid port number invalid port/insufficient memory number
Verify is specified
that a correct port
HOST-190 WARN Invalid baud rate invalid port/insufficient memory number is specified
Verify that a correct port
HOST-191 WARN PPP
Invalid devicealready
channel type invalid port/insufficient memory number
Verify is specified
that a correct port
HOST-192 WARN initialized invalid port/insufficient memory number is specified
HOST-193 WARN TLNT:Login to %s login made to a device using telnet This is not an error
HOST-194 WARN TLNT:Logout of %s logout made out of device using telnet This is not an error
TLNT:rejected conn TELNET connection attempt rejected. Correct the cause of
HOST-195 WARN TLNT:%s
request already Please look at cause code for further failure and
ensure try again
the device is not
HOST-196 WARN connected the device is already connected connected
ensure the and
logintry
id again
is valid
HOST-197 WARN TLNT:invalid login
password invalid login id supplied
id and try again
ensure the password is
HOST-198 WARN %s invalid password supplied valid and try again
the inactivity timer for the device log in again or increase
HOST-199 WARN TLNT:timeout on %s expired the timer value for the
TLNT:FSAC need lvl %d the FSAC security feature is enabled make an entry for the PC
HOST-200 WARN for %s and the client PC doesn't have in the FSAC table
TLNT:bad access lvl for check the access level for
HOST-201 WARN %s Insufficent access level the device from the
configure a valid port for
HOST-202 WARN TLNT:invalid port for %s valid port not configured for device device from Port Init
HOST-203 WARN TLNT:from %s connection from remote host detected not an error
SM: Remote Client The host name in the Client tag is not Change the host name to
HOST-204 WARN Name is invalid set correctly. If DNS is enabled, DNS be a valid name in the
SM: Tag Already A request to mount a tag which was Do not try to remount a
HOST-205 WARN Mounted already mounted was received. tag without dismounting
Set the
The system variable $server_port in the $hosts_cfg[n].$server_por
HOST-206 WARN SM: Bad Port Number Client tag or the host tag was invalid. t sysvarthe
Mount for tag
the before
server tag
HOST-207 WARN SM: Tag is not mounted The requested tag is not mounted using it
The requested tag is not yet connected Use MSG_CONNECT to
HOST-208 WARN SM: Connection
Not Yet Connected The
to the remote host/device
connection was aborted by remote connect
Check thethe tag before
remote host
HOST-209 WARN SM:
Aborted
Connection Timed host and reconnect
Reconnect to it
to remote
HOST-210 WARN Out Connection was timed out by remote. host.
SM: Connection Write Write buffer is full. The remote host Check remote host and
HOST-211 WARN SM:
Buffer is full
Write Direction may not
Write be responding
direction or the network
was shutdown by network
Check connection.
remote and
HOST-212 WARN shut down by Peer remote.
SM: Read Direction shut Read direction was shutdown by reconnect
Check remote and host
to remote
HOST-213 WARN SM:
downConnection
by Peer is remote. reconnect
Wait to remote
for remote to host
HOST-214 WARN Pending Remote host has not yet connected. connect.
Stop using the remote tag.
SM: Connection is in If necessary close any
HOST-215 WARN use The requested tag is in use. open file to the tag and
A request was received for a socket Re-establish the
HOST-216 WARN SM: Invalid Socket which is invalid connection.
Retry the operation. All
sockets may be use. Free
A socket error was returned by the some resources by closing
HOST-217 WARN SM: Socket Error tcpip library. some connections to
A diagnostic TP session was connected
HOST-218 WARN DTP: Connect %s in interactive mode. Input is allowed. not an error
A diagnostic TP session was connected
HOST-219 WARN DTP: Monitor %s in monitor mode.
A diagnostic Input was
TP session is not allowed. not an error
HOST-220 WARN DTP: Disconnect %s disconnected.
connection from remote browser not an error
HOST-221 WARN DTP: ident %s detected not an error
HOST-222 WARN DHCP: server %s response
A response from
fromDHCP serverserver
the DHCP detected
was not an error
HOST-223 WARN DHCP: using IP %s detected. None.
DHCP: No response No response exists from the DHCP Check your cable and
HOST-224 WARN from server server. server configuration, and
Check the DHCP server
configuration. Identify the
The DHCP server returned an IP address device that is using the
HOST-225 WARN DHCP: duplicate IP %s which is already in use. same IP address that the
Check the Ethernet cables
and make sure the robot
The DHCP lease time expired and the controller is still
DHCP: Lease time robot could not renew the DHCP lease connected to the Ethernet
HOST-226 WARN expired on the robot controller's IP address. network. Check that the
The lease might have
DHCP: shutting down expired. Check the
HOST-227 WARN ethernet
DHCP: invalid reply The Ethernet interface was shut down. cabling/server
HOST-228 WARN from server
DHCP: request rejected this mayprotocol
Normal be normal protocolhas
operation operation not an error
HOST-229 WARN by server occurred. None.
DHCP: renewal attempt The robot tried to renew IP address, Check the network cabling
HOST-230 WARN failed but the renew attempt failed. and DHCP server setup.
HOST-231 WARN Initializing The DHCP operation is initialized. None.
HOST-232 WARN In progress The DHCP operation is in progress. No action is required.
Check the network cabling
HOST-233 WARN Failed The DHCP operation failed. for defects,
This or the
is a status DHCP
message.
HOST-234 WARN Success The DHCP operation succeeded. No remedy
This is required.
is a status message.
HOST-235 WARN Disabled The DHCP operation is disabled. No remedy is required.
FTP: servers not auto- After loading the FTP option, the FTP Start the FTP servers from
HOST-236 WARN started servers could not be automatically the Hostcomm Server
FTP: server tags not The system was unable to start the FTP Start FTP servers
HOST-237 WARN available servers because no free server tags manually.
A web page tried to issue a KCL Load the KCL option on
HOST-239 WARN KCL option not loaded command, but KCL is not loaded on the the robot controller at
Check and verify your
SMTP configuration. On
an iPendant, this is done
EMAIL: Email send using the DRC menus.
HOST-240 WARN failed An SMTP server failure has occurred. Otherwise, see the
This warning can be
disabled from the DRC
EMAIL: Email send menus: Data Services
HOST-241 WARN successful An SMTP message was delivered. Setup. The warning can
Check to make sure the
SNTP: NTP server No packets were received from NTP NTP server IP address is
HOST-242 WARN unreachable server. correct. If it is not, correct
The Address Conflict Detection has Change the configured IP
detected a duplicate IP address on the address to an IP address
HOST-243 ACD: duplicate IP %s network. not on the network. If
Important robot operations might be Contact your system
effected by the high level of traffic on administrator to fix the
HOST-244 WARN Ethernet Throttle the Ethernet network. The Ethernet network problem. 3.6.2
Change the robot
Hostname in the Host
Comm TCP/IP screen to a
legal name. A legal
Hostname is a text string
The robot name configured for the of characters drawn from
HOST-245 Illegal Hostname TCP/IP interface is illegal. the alphabet (A-Z, a-z),
Change the robot
Hosttable entry in the
A Hosttable entry is configred with an Host Comm TCP/IP screen
illegal name. If n1 = 1, the illegal name to a legal name. A legal
is in the local host table. If n1 = 2, the Hostname is a text string
illegal name is in the shared host table. of characters drawn from
Illegal Hosttable Entry n2 indicates the entry number of the the alphabet (A-Z, a-z),
HOST-246 %d %d name in the respective table. digits
Be sure (0-9),
the and minus
camera is
HOST-260 GigE: Invalid Handle The camera handle was not found. initialized.
Could not get access rights to camera. Be sure the robot can get
HOST-261 GigE: Access Denied
Cam parms not Some other device might be using it. exclusive rights to the
HOST-262 set The parameter setting failed. See PIPC:GIGE_LOG.DT.
HOST-263 Invalid Argument
GigE: Camera Not Internal GigE Error. See PIPC:GIGE_LOG.DT.
HOST-264 Supported A configuration error has occurred. See PIPC:GIGE_LOG.DT.
This could be caused by a
HOST-265 GigE: Image XFER Error Failed to get image. temporary network issue
The camera IP address is not on same The camera and the robot
HOST-266 GigE: Invalid IP Address subnet as the robot. should be on same
The Mac address does not match
HOST-267 GigE: Camera Mismatch camera. The camera might have been Set up a new camera.
GigE: Fail to add See PIPC:GIGE_LOG.DT.
HOST-268 Camera Could
The notcommand
GigE add camera definition.
to the camera There might be too many
HOST-279 GigE: Command Failed failed. See PIPC:GIGE_LOG.DT.
Verify your PC is running a
supported platform.
Supported operating
The PC responded to a robot PC Share systems include Windows
SMB: Invalid response request in a way the robot couldn't XP, Windows Vista, and
HOST-280 from PC understand. Linux running Samba 3.2.
Verify the PC is properly
connected to the
network, and can be
pinged on the network.
Verify the PC Share client
tag is properly configured,
and the PC has properly
shared the
The robot timed-out while waiting for location/directory being
SMB: Time-out waiting the PC to respond to a PC Share accessed. The default
HOST-281 for PC request. timeout value can be
Configure the client tag
with a shared drive to
perform the requested file
The requested file operation can not be operation. Make sure the
SMB: No share performed unless the client tag is shared drive is porperly
HOST-282 configured configured with a share. configured on the remote
Either configure a valid
WINS server, or enable
broadcast name
resolution. Both settings
SMB: Netbios NetBios name resolution is not properly can be configured in the
HOST-283 configuration error configured. PC Share protocol page in
The PC server has
message signing enabled.
The Secure Signature failed on a This forces the robot
SMB: Secure Signature network message sent from the PC to controller to perform
HOST-284 from PC failed the robot controller. Secure Signatures to
Verify the Remote
Path/Share field is
properly configured in the
client tag setup screen.
Verify the requested file
SMB: DOS error: File The PC server was unable to find the exists on the remote PC
HOST-285 not found requested file. server by performing a
Verify the Remote
Path/Share field is
properly configured in the
client tag setup screen.
Verify the requested path
SMB: DOS error: Path The PC server was unable to find the exists on the remote PC
HOST-286 not found requested path. server by performing a
Close some files that the
The PC server was unable to open the robot controller has
requested file, because the robot opened on the PC Share
SMB: DOS error: Too controller has too many files opened to client tag associated with
HOST-287 many open files the remote PC. the remote PC. If the
Verify your username and
re-enter your password in
the robot controller client
The PC server denied the robot tag setup screens. Verify
SMB: DOS error: Access controller access to a file, share, or permissions have been
HOST-288 denied directory path. properly set on the shared
Verify on the remote PC
that a folder has been
properly shared. Verify
SMB: DOS error: that the share name is
Requested share does The PC server cannot find the Share configured in the robot
HOST-289 not exist requested by the robot controller. controler client tag setup
First, check for an alarm
cause code for more
information on the
specific DOS error. If no
alarm cause code exists,
SMB: DOS Error %d The PC responded to a PC share note the DOS error code.
HOST-299 from PC
Can't connect to request with a DOS File Error. Lookupthe
Check thecommunication
DOS error
HOST-300 CNC(%s) Robot cannot connect to CNC. setup.
Connect the CNC to the
HOST-301 Not Connected(Tag=%s) The CNC is not connected. robot
Connect controller.
the CNC to the
HOST-302 CNC doesn't Connected The CNC is not connected. robot controller.
Change the CNC to a
HOST-303 Not supported CNC The CNC is not suported. supported type.
Cycle power to change Cycle power on the robot
HOST-304 CNC No.
Start Comm. with CNC The CNCthe
Starting No.communication
was changed. with the controller
This to activate the
is for notification
HOST-305 No.%dI/O number for
Input specified
The CNC. entered is not for the only.
I/O number Enter the proper I/O
HOST-306 CNC No. selected CNC. number
Enter a CNCfor the
no. selected
which is
HOST-307 CNC No. is duplicated You entered a duplicate CNC no. not already in use.
Add CNC to be The CNC number is greater than the Control Start and set the
HOST-308 connected maximum number allowed. maximum number of
HOST-309 Please set CNC No.%d The CNC
You pressNo.
theisOPR
not enable
set. button but Enter the CNC No.
HOST-310 TP disable TP is disable. Set TP enable.
Interlock Mode signal is You press the OPR enable button but Set the interlock signal
HOST-311 off interlock signal is off. ON.
Operation isn't You try to jog machine tool but Set the operation
HOST-312 available operation isn't available. available
Do M.Tool Operation You try to jog machine tool but Set the Machine Tool
HOST-313 enable Machine Tool Operation in Setup Operation available.
An error occurred in the Ethernet Consult your network
HRTL-001 WARN Not owner networking software (TCP/IP). administrator or call the
Either retype the file
name or DEFINE the
File/Comm Tag does Either the file or the Comm Tag could Comm Tag. Please refer to
HRTL-002 WARN not exist not be found the section of Defining
HRTL-003 WARN No such process networking software (TCP/IP). administrator or call the
HRTL-004 WARN Interrupted system call networking software (TCP/IP). administrator or call the
HRTL-005 WARN I/O error networking software (TCP/IP). administrator or call the
No protocol or device The Comm Tag either does not have a DEFINE a protocol to the
HRTL-006 WARN dest protocol defined or if required does not Comm Tag or assign a port
HRTL-007 WARN Arg list too long networking software (TCP/IP). administrator or call the
HRTL-008 WARN Exec format error networking software (TCP/IP). administrator or call the
The file number passed does not match Copy the conditions which
HRTL-009 WARN Bad file number with any open files. caused this to occur.
HRTL-010 WARN No children networking software (TCP/IP). administrator or call the
HRTL-011 WARN No more processes networking software (TCP/IP). administrator or call the
HRTL-012 WARN Not enough core networking software (TCP/IP). administrator or call the
Access permission Access Ethernet socket table Consult your network
HRTL-013 WARN denied permission denied. administrator or call the
HRTL-014 WARN Invalid Comm Tag A bad address has been detected administrator or call the
The selected protocol requires a device First ensure the Port has
HRTL-015 WARN Port device required port No Use from Port Init
Either STOP the Comm
Tag or select another Tag.
Comm Tag already Either the Comm Tag is STARTED or it's Please refer to the section
HRTL-016 WARN defined presently in use of Defining and Starting
HRTL-017 WARN File exists networking software (TCP/IP). administrator or call the
HRTL-018 WARN Cross-device link networking software (TCP/IP). administrator or call the
The passed Device Type is not a Comm Only Comm Tags can be
HRTL-019 WARN Invalid device type Tag type (Cx or Sx) used with this command.
HRTL-020 WARN Not a directory networking software (TCP/IP). administrator or call the
HRTL-021 WARN Is a directory networking software (TCP/IP). administrator or call the
System does not support selected Either select another
HRTL-022 WARN Invalid argument protocol. protocol or install the
HRTL-023 WARN File table overflow networking software (TCP/IP). administrator or call the
HRTL-024 WARN Too many open files networking software (TCP/IP). administrator or call the
HRTL-025 WARN Not a typewriter networking software (TCP/IP). administrator or call the
HRTL-026 WARN Text file busy networking software (TCP/IP). administrator or call the
HRTL-027 WARN File too large networking software (TCP/IP). administrator or call the
HRTL-028 WARN No space left on device networking software (TCP/IP). administrator or call the
HRTL-029 WARN Illegal seek networking software (TCP/IP). administrator or call the
HRTL-030 WARN Read-only file system networking software (TCP/IP). administrator or call the
HRTL-031 WARN Too many links networking software (TCP/IP). administrator or call the
HRTL-032 WARN Broken pipe networking software (TCP/IP). administrator or call the
HRTL-035 WARN Operation would block networking software (TCP/IP). administrator or call the
Operation now in An error occurred in the Ethernet Consult your network
HRTL-036 WARN progress networking software (TCP/IP). administrator or call the
Operation now in An error occurred in the Ethernet Consult your network
HRTL-037 WARN progress networking software (TCP/IP). administrator or call the
Socket operation on An error occurred in the Ethernet Consult your network
HRTL-038 WARN non-socket networking software (TCP/IP). administrator or call the
Destination address An error occurred in the Ethernet Consult your network
HRTL-039 WARN required networking software (TCP/IP). administrator or call the
HRTL-040 WARN Message size too long networking software (TCP/IP). administrator or call the
HRTL-041 WARN Protocol wrong type networking software (TCP/IP). administrator or call the
HRTL-042 WARN Protocol not available networking software (TCP/IP). administrator or call the
HRTL-043 WARN Protocol not supported networking software (TCP/IP). administrator or call the
Socket type not An error occurred in the Ethernet Consult your network
HRTL-044 WARN supported networking software (TCP/IP). administrator or call the
Operation not An error occurred in the Ethernet Consult your network
Address family not An error occurred in the Ethernet Consult your network
HRTL-048 WARN Address already in use networking software (TCP/IP). administrator or call the
Can't assign requested An error occurred in the Ethernet Consult your network
HRTL-049 WARN address networking software (TCP/IP). administrator or call the
HRTL-050 WARN Network is down networking software (TCP/IP). administrator or call the
HRTL-051 WARN Network is unreachable networking software (TCP/IP). administrator or call the
Connection dropped on An error occurred in the Ethernet Consult your network
HRTL-052 WARN reset networking software (TCP/IP). administrator or call the
Software caused An error occurred in the Ethernet Consult your network
HRTL-053 WARN connect abort networking software (TCP/IP). administrator or call the
Connection reset by An error occurred in the Ethernet Consult your network
HRTL-054 WARN peer networking software (TCP/IP). administrator or call the
No buffer space An error occurred in the Ethernet Consult your network
HRTL-055 WARN available networking software (TCP/IP). administrator or call the
Socket is already An error occurred in the Ethernet Consult your network
HRTL-056 WARN connected networking software (TCP/IP). administrator or call the
HRTL-057 WARN Socket is not connected networking software (TCP/IP). administrator or call the
Can't send, socket is An error occurred in the Ethernet Consult your network
HRTL-058 WARN shutdown networking software (TCP/IP). administrator or call the
Ethernet Connection An error occurred in the Ethernet Consult your network
HRTL-060 WARN timed out networking software (TCP/IP). administrator or call the
Ethernet Connection An error occurred in the Ethernet Consult your network
HRTL-061 WARN refused networking software (TCP/IP). administrator or call the
Protocol family not An error occurred in the Ethernet Consult your network
HRTL-064 WARN Host is down networking software (TCP/IP). administrator or call the
HRTL-065 WARN Host is unreachable networking software (TCP/IP). administrator or call the
HRTL-066 WARN No urgent data networking software (TCP/IP). administrator or call the
HRTL-067 WARN No out of bound data networking software (TCP/IP). administrator or call the
Device is already
HRTL-068 WARN attached
Device Function Code Device is already in use Free
CheckDevice
useage foragainst
use
HRTL-069 WARN invalid detach with
Cannot Device does not support command devicefor command
Wait
HRTL-070 WARN open
Devicefiles
is already Device in use complete
Wait until then
Device retry
free
HRTL-071 WARN allocated
Device doesn't support Device is already allocated then retry
Check useage against
HRTL-072 WARN attach
End of device list Device does not support attaching device
HRTL-073 WARN reached Device limit reached Check that device is valid
HRTL-074 WARN Device is not File
Compressed supported
too Device
File not available
Header indicates more data than Check device
Delete file andinstallation
try to get
HRTL-075 PAUSE. small found in file. copy from original source
IB-00S G Slave
Pleasesystem
powererror(%d)
OFF/ON System internal error Notify FANUC
IB-S-10 WARN
PAUSE. for Master
Not match System internal error Notify FANUC
IB-S-101 G
PAUSE. Configuration
Too many device list are System internal error Notify FANUC
IB-S-102 G
PAUSE. connected
Configuration change System internal error Notify FANUC
IB-S-103 G
PAUSE. (ID-scan) System internal error Notify FANUC
IB-S-104 G
PAUSE. Multi data
InterBus cycle error
Timeout System internal error Notify FANUC
IB-S-105 G
PAUSE. processmissing
Device cycle in setup System internal error Notify FANUC
IB-S-106 G
PAUSE. config
Configuration change System internal error Notify FANUC
IB-S-107 G
PAUSE. (runtime)
No connection to System internal error Notify FANUC
IB-S-108 G
PAUSE. InterBus-S
Master system System internal error Notify FANUC
IB-S-11 G error(%d)
Master board not System internal error Notify FANUC
IB-S-12 WARN
PAUSE. installed
Master PCB Slave PCB is not installed Slave
PleasePCB is installed
exchange Slave.
IB-S-13 G
PAUSE. abnormal(%d)
Master No Data Slave baoard is defective. board
Plase check Cable and
IB-S-14 G
PAUSE. Exchange Slave data exchange is stopped. Master status.
IB-S-15 G
PAUSE. Module error System internal error Notify FANUC
IB-S-150 G
PAUSE. Sequence error System internal error Notify FANUC
IB-S-16 G
PAUSE. Module reconfiguration System internal error Notify FANUC
IB-S-17 G
PAUSE. Defect
No warmW1-interface
start System internal error Notify FANUC
IB-S-170 G
PAUSE. command
Too many modules System internal error Notify FANUC
IB-S-171 G
PAUSE. configured
More module are System internal error Notify FANUC
IB-S-172 G
PAUSE. connected
Less module are System internal error Notify FANUC
IB-S-173 G
PAUSE. connected
Non supported length System internal error Notify FANUC
IB-S-174 G
PAUSE. code System internal error Notify FANUC
IB-S-175 G
PAUSE. Wrong length code System internal error Notify FANUC
IB-S-176 G
PAUSE. Wrong ident code System internal error Notify FANUC
IB-S-177 G
PAUSE. Wrong segment level System internal error Notifycheck
Plase FANUC other device
IB-S-178 G
PAUSE. Master Watch dog error Slave detects watch dog error. status.
IB-S-18 G Defect W2-interface System internal error Notify FANUC
PAUSE. An error has occurred with the Remedy of the cause code
IB-S-19 G %d: %d.%d
Slave board%snot specified slave device. (displayed immediately
IB-S-2 WARN
PAUSE. installed Slave PCB is not installed Slave PCB is installed .
IB-S-20 G
PAUSE. All clear done System internal error Notify FANUC
IB-S-21 G
PAUSE. External periphery
Defective Datacycleerror
& System internal error Notify FANUC
IB-S-22 G
PAUSE. Rescan
HOST watchdog failed, System internal error Notify FANUC
IB-S-220 G
PAUSE. timeout
HOST not acknowledge System internal error Notify FANUC
IB-S-221 G
PAUSE. process
Error in IBS Controller System internal error Notify FANUC
IB-S-224 G
PAUSE. comm
Transmission Quality System internal error Notify the
Check FANUC
slave device or
IB-S-23 G
PAUSE. DownPCB
Slave Transmission Quality Down the cable.
Please exchange Slave
IB-S-3 G abnormal(%d) Slave baoard is defective. board
PAUSE. Device missing in last
IB-S-30 G
PAUSE. scan System internal error Notify FANUC
IB-S-31 G
PAUSE. Device reports other IDSystem internal error Notify FANUC
IB-S-32 G
PAUSE. length System internal error
Further device Interface Notify FANUC
IB-S-33 G
PAUSE. 1 System internal error
Further device Interface Notify FANUC
IB-S-34 G
PAUSE. 2
Device missing in last System internal error Notify FANUC
IB-S-35 G
PAUSE. scan System internal error Notify FANUC
IB-S-36 G
PAUSE. peripheral error
Device reconfiguration System internal error Notify FANUC
IB-S-37 G
PAUSE. req
Dev detect checksum System internal error Notify FANUC
IB-S-38 G
PAUSE. error System internal error Notify FANUC
Plase check Cable and
IB-S-4 G
PAUSE. Slave No Data Exchange
Defective Slave data exchange is stopped. Master status.
IB-S-40 G
PAUSE. Interface1(local)
DefectiveInterface2(re System internal error Notify FANUC
IB-S-41 G
PAUSE. mote)
No report ID & length System internal error Notify FANUC
IB-S-42 G
PAUSE. code
Interrupt IBS System internal error Notify FANUC
IB-S-43 G
PAUSE. connection
Interrupt IBS local System internal error Notify FANUC
IB-S-44 G
PAUSE. before
Interrupt IBS local System internal error Notify FANUC
IB-S-45 G
PAUSE. behind System internal error Notify FANUC
IB-S-46 G
PAUSE. Connect force stopped System internal error Notify FANUC
Plase check other device
IB-S-5 G
PAUSE. Slave watch
Unknown dog error
process Slave detects watch dog error.
data status.
IB-S-52 G
PAUSE. handshake System internal error Notify FANUC
IB-S-56 G
PAUSE. No
IBS device table
controller is foundSystem internal error Notify FANUC
IB-S-57 G defective System internal error Notify FANUC
PAUSE. Can not find the group which is Please reset the group
IB-S-6 L Can not find IBS Group specified by IBS CAHNGE. name by using the sub-
Please confirm to match
PAUSE. IBS Config change Can not change the INTERBUS-S the INTERBUS-S
IB-S-7 L
PAUSE. Timeoutaddress
Double configuration by IBS CAHNGE. configuration which is
IB-S-70 G
PAUSE. configured System internal error Notify FANUC
IB-S-71 G
PAUSE. Device data
Process dataset
cfglen
lenfault System internal error Notify FANUC
IB-S-72 G
PAUSE. fault
Additional table len System internal error Notify FANUC
IB-S-73 G
PAUSE. fault System internal error Notify FANUC
IB-S-74 G
PAUSE. PCP data length fault System internal error Notify FANUC
IB-S-75 G
PAUSE. Whole size length fault System internal error Notify FANUC
IB-S-76 G
PAUSE. Add table
Max inconsistent
Output offset System internal error Notify FANUC
IB-S-77 G
PAUSE. overstep
Max Input offset System internal error Notify FANUC
IB-S-78 G
PAUSE. overstep
Max Offset overstep > System internal error Notify FANUC
IB-S-79 G
PAUSE. 255 System internal error Notify FANUC
Please modify the slave
IB-S-8 G
PAUSE. Slave Length
Module countcode error
or offset The slave length code setting is invalid. length code setting.
IB-S-80 G
PAUSE. er System internal error Notify FANUC
IB-S-81 G
PAUSE. Out Mod No <> out ofs System internal error Notify FANUC
IB-S-82 G
PAUSE. In Mod No <> in ofs System internal error Notify FANUC
IB-S-83 G
PAUSE. Real out len <> cfg len System internal error Notify FANUC
IB-S-84 G
PAUSE. Real in len <> cfg len System internal error Notify FANUC
IB-S-85 G
PAUSE. Overlapped output data System internal error Notify FANUC
IB-S-86 G
PAUSE. Overlapped
Out input
Dev define In data System internal error Notify FANUC
IB-S-87 G
PAUSE. module
In Dev define Out System internal error Notify FANUC
IB-S-88 G
PAUSE. module
Out Dev define In System internal error Notify FANUC
IB-S-89 G module System internal error Notify FANUC
%s I/O Overmapping The offset or byte number of slave Please modify the offset
IB-S-9 WARN
PAUSE. no.:%d
In Dev define Out configuration is invalid. or byte number of slave
IB-S-90 G
PAUSE. module System internal error Notify FANUC
IB-S-91 G
PAUSE. Installation
Length codedepth
is error
System internal error Notify FANUC
IB-S-92 G
PAUSE. unknown
Remove non exist System internal error Notify FANUC
IB-S-93 G
PAUSE. device System internal error Notify FANUC
IB-S-94 G
PAUSE. Device is
Config is differ
activefrom System internal error Notify FANUC
IB-S-95 G msg
Alarm Code Slave System internal error Notify FANUC
IBSS-001 STOP system error(%d)
Slave board not System internal error Notify FANUC
IBSS-002 WARN installed
Slave PCB Slave PCB is not installed Slave PCB
Please is installed
exchange Slave.
IBSS-003 STOP abnormal(%d) Slave baoard is defective. board
Please check Cable and
IBSS-004 STOP Slave No Data Exchange Slave data exchange is stopped. Master status.other device
Please check
IBSS-005 STOP Slave watch dog error Slave detects watch dog error. status.
Can not find the group which is Please reset the group
IBSS-006 STOPL Can not find IBS Group specified by IBS CAHNGE. name by using the sub-
Please confirm to match
IBS Config change Can not change the INTERBUS-S the INTERBUS-S
IBSS-007 STOPL Timeout configuration by IBS CAHNGE. configuration
Please modifywhich is
the slave
IBSS-008 STOP Slave Length code error The slave length code setting is invalid. length code setting.
%s I/O Overmapping The offset or byte number of slave Please modify the offset
IBSS-009 WARN no.:%d configuration is invalid. or byte number of slave
Please power OFF/ON Document the events that
IBSS-010 WARN for Master System internal error led to the error, and call
Master system Document the events that
IBSS-011 STOP error(%d)
Master board not System internal error led to the error, and call
IBSS-012 WARN Master
installedPCB Slave PCB is not installed Slave PCB
Please is installed
exchange Slave.
IBSS-013 STOP Master
abnormal(%d)
No Data Slave baoard is defective. board
Please check Cable and
IBSS-014 STOP Exchange Slave data exchange is stopped. Master status.
IBSS-015 STOP Module error System internal error led to the error, and call
IBSS-016 STOP Module reconfiguration System internal error led to the error, and call
IBSS-017 STOP Defect W1-interface System internal error led to the error, and call
IBSS-018 STOP Defect W2-interface System internal error led to the error, and call
An error has occurred with the Remedy of the cause code
IBSS-019 WARN %d: %d.%d %s specified slave device. (displayed immediately
IBSS-020 STOP All clear done System internal error led to the error, and call
IBSS-021 STOP External periphery error System internal error led to the error, and call
Defective Datacycle & Document the events that
IBSS-022 STOP Rescan
Transmission Quality System internal error led to the error,
Check and callor
slave device
IBSS-023 STOP Down Transmission Quality Down the cable.
Device missing in last Document the events that
IBSS-030 STOP scan System internal error led to the error, and call
IBSS-031 STOP Device reports other ID System internal error led to the error, and call
Device reports other Document the events that
IBSS-032 STOP length System internal error led to the error, and call
Further device Interface Document the events that
IBSS-033 STOP 1 System internal error led to the error, and call
Further device Interface Document the events that
Device missing in last Document the events that
IBSS-035 STOP scan System internal error led to the error, and call
IBSS-036 STOP Device peripheral error System internal error led to the error, and call
Device reconfiguration Document the events that
IBSS-037 STOP req System internal error led to the error, and call
Dev detect checksum Document the events that
IBSS-038 STOP error System internal error led to the error, and call
Defective Document the events that
IBSS-040 STOP Interface1(local) System internal error led to the error, and call
DefectiveInterface2(re Document the events that
IBSS-041 STOP mote) System internal error led to the error, and call
No report ID & length Document the events that
IBSS-042 STOP code System internal error led to the error, and call
Interrupt IBS Document the events that
IBSS-043 STOP connection System internal error led to the error, and call
Interrupt IBS local Document the events that
IBSS-044 STOP before System internal error led to the error, and call
Interrupt IBS local Document the events that
IBSS-045 STOP behind System internal error led to the error, and call
IBSS-046 WARN Connect force stopped System internal error led to the error, and call
Unknown process data Document the events that
IBSS-052 STOP handshake System internal error led to the error, and call
IBSS-056 STOP No device table found System internal error led to the error, and call
IBS controller is Document the events that
IBSS-057 STOP defective System internal error led to the error, and call
Double address Document the events that
IBSS-070 STOP configured System internal error led to the error, and call
IBSS-071 STOP Device data set len fault System internal error led to the error, and call
Process data cfg len Document the events that
IBSS-072 STOP fault System internal error led to the error, and call
Additional table len Document the events that
IBSS-073 STOP fault System internal error led to the error, and call
IBSS-074 STOP PCP data length fault System internal error led to the error, and call
IBSS-075 STOP Whole size length fault System internal error led to the error, and call
IBSS-076 STOP Add table inconsistent System internal error led to the error, and call
Max Output offset Document the events that
IBSS-077 STOP overstep System internal error led to the error, and call
Max Input offset Document the events that
IBSS-078 STOP overstep System internal error led to the error, and call
Max Offset overstep > Document the events that
Module count or offset Document the events that
IBSS-080 STOP er System internal error led to the error, and call
IBSS-081 STOP Out Mod No <> out ofs System internal error led to the error, and call
IBSS-082 STOP In Mod No <> in ofs System internal error Notify FANUC
IBSS-083 STOP Real out len <> cfg len System internal error led to the error, and call
IBSS-084 STOP Real in len <> cfg len System internal error led to the error, and call
IBSS-085 STOP Overlapped output data System internal error led to the error, and call
IBSS-086 STOP Overlapped input data System internal error led to the error, and call
Out Dev define In Document the events that
IBSS-087 STOP module System internal error led to the error, and call
In Dev define Out Document the events that
Out Dev define In Document the events that
In Dev define Out Document the events that
IBSS-091 STOP Installation depth error System internal error led to the error, and call
Length code is Document the events that
IBSS-092 STOP unknown System internal error led to the error, and call
Remove non exist Document the events that
IBSS-093 STOP device System internal error led to the error, and call
IBSS-094 STOP Device is active System internal error led to the error, and call
Config is differ from Document the events that
IBSS-095 STOP msg System internal error led to the error, and call
Not match Document the events that
IBSS-101 STOP Configuration list System internal error led to the error, and call
Too many device are Document the events that
IBSS-102 STOP connected System internal error led to the error, and call
Configuration change Document the events that
IBSS-103 STOP (ID-scan) System internal error led to the error, and call
IBSS-104 STOP Multi data cycle error System internal error led to the error, and call
InterBus Timeout Document the events that
IBSS-105 STOP process cycle System internal error led to the error, and call
Device missing in setup Document the events that
IBSS-106 STOP config System internal error led to the error, and call
Configuration change Document the events that
IBSS-107 STOP (runtime) System internal error led to the error, and call
No connection to Document the events that
IBSS-108 STOP InterBus-S System internal error led to the error, and call
IBSS-150 STOP Sequence error System internal error led to the error, and call
No warm start Document the events that
IBSS-170 STOP command System internal error led to the error, and call
Too many modules Document the events that
IBSS-171 STOP configured System internal error led to the error, and call
More module are Document the events that
Less module are Document the events that
Non supported length Document the events that
IBSS-174 STOP code System internal error led to the error, and call
IBSS-175 STOP Wrong length code System internal error led to the error, and call
IBSS-176 STOP Wrong ident code System internal error led to the error, and call
IBSS-177 STOP Wrong segment level System internal error led
Plasetocheck
the error,
otherand call
device
IBSS-178 STOP Master Watch dog error Slave detects watch dog error. status. check cable and
Please
IBSS-200 No data
Slave board Exchange Slave data exchange is stopped.
not master status.
IBSS-201 installed Slave board is not installed. Install a slave board.
Too many board Keep only one slave board
IBSS-202 installed More than one slave board is
Consult Phoenix Contact for more installed. and remove
Consult other
Phoenix slave
Contact
IBSS-203 Init Error %d information.
Consult Phoenix Contact for more for morePhoenix
Consult information.
Contact
IBSS-204 Runtime
Please Erroroff
power %dfor information.
Setting is modified and power off is for more
Power information.
off/on the
IBSS-205 Slave required. controller to activate new
Firmware should be
Firmware Updating Controller started in firmware updating updated only in firmware
IBSS-206 Mode
Firmware update mode. updating
Power mode.
off/on theUpdate
IBSS-207 successful Firmware is updated successfully. controller to return
Firmware update failed Write down the number
IBSS-208 %d Error occurs during firmware
in accessing update. Please
the firmware displayed in the
check error
if the
IBSS-209 Firmware file error %d file. firmware file is broken.
The name of the firmware
file is supposed to start by
IBSS-210 No firmware The name of the firmware file is wrong. IBS. Please check if you
Write down the numbers
displayed in the error
IBSS-211 System Error %d %d Internal Error message. Contactslave
Please exchange FANUC
IBSS-212 Slave PCB abnormal Slave board is defective. board.
Write down the number
Additional information of the error displayed in the error
IBSS-213 Error code %x message displayed together. message. Please see the
The number displayed in
the error message is the
IBSS-214 PCP Init Error %d Error is PCP initialization. error code returned by
PCP initialization is stopped by the Please check the PCP
IBSS-215 PCP size
DIO Init Stopped
to UOP not%d wrong parameter. setting. For
Increase DIOexample,
size if youthe
IBSS-216 enough The DIO size is too small to use UOP. want to use UOP.
HOST watchdog failed, Document the events that
IBSS-220 STOP timeout System internal error led to the error, and call
HOST not acknowledge Document the events that
IBSS-221 STOP process System internal error led to the error, and call
Error in IBS Controller Document the events that
IBSS-224 STOP comm System internal error led to the error, and call
Serch slave which has non-
bit len is set with byte zero BIT LENGTH and BYTE
IBSS-260 WARN len BIT LENGTH is set with BYTE LENGTH LENGTH. in config detail
Create InterBus I/O
InterBus has no I/O assignment if it is
IBSS-263 assignment InterBus I/O assignment is cleared. supposed to be created
Set system pointer Contact FANUC America
IBSS-264 failed Internal Error Corporation to report the
Please see manual IBS SYS FW G4 UM E
IBSS-300 STOP %s:Bus error from Phoenix Contact
%s:Max. number was Please see manual IBS SYS FW G4 UM E
IBSS-301 STOP exceeded from Phoenix Contact
%s:Too many faulty Please see manual IBS SYS FW G4 UM E
IBSS-302 STOP data cycle from Phoenix Contact
%s:Configuration not Please see manual IBS SYS FW G4 UM E
IBSS-303 STOP activated from Phoenix Contact
%s:Control_Device_Fun Please see manual IBS SYS FW G4 UM E
IBSS-304 STOP ction from Phoenix Contact
%s:CRC error in Please see manual IBS SYS FW G4 UM E
IBSS-305 STOP segment from Phoenix Contact
%s:Error at interface Please see manual IBS SYS FW G4 UM E
IBSS-306 STOP (In) from Phoenix Contact
IBSS-307 STOP %s:Bus error occured from Phoenix Contact
IBSS-308 STOP %s:Device is missing from Phoenix Contact
%s:Multiple errors in Please see manual IBS SYS FW G4 UM E
%s:Multiple timeouts in Please see manual IBS SYS FW G4 UM E
IBSS-311 STOP %s:CRC error (In) from Phoenix Contact
%s:Defective interface Please see manual IBS SYS FW G4 UM E
%s:Error at interface Please see manual IBS SYS FW G4 UM E
%s:Interrupted Please see manual IBS SYS FW G4 UM E
IBSS-314 STOP interface (In) from Phoenix Contact
IBSS-315 STOP %s:Transmission error from Phoenix Contact
IBSS-316 STOP %s:Error in segment from Phoenix Contact
IBSS-317 STOP %s:Wrong length code from Phoenix Contact
IBSS-318 STOP %s:Wrong ID code from Phoenix Contact
IBSS-319 STOP %s:Data register error from Phoenix Contact
IBSS-320 STOP %s:Invalid ID code from Phoenix Contact
%s:Remote device in Please see manual IBS SYS FW G4 UM E
IBSS-321 STOP local bus from Phoenix Contact
IBSS-322 STOP %s:Device not possible from Phoenix Contact
IBSS-323 STOP (Out1) from Phoenix Contact
%s:Interrupted interf. Please see manual IBS SYS FW G4 UM E
%s:Interrupted interf. Please see manual IBS SYS FW G4 UM E
IBSS-327 STOP %s:I/O timeout from Phoenix Contact
IBSS-328 STOP %s:Reset of device from Phoenix Contact
%s:Device not initialized Please see manual IBS SYS FW G4 UM E
IBSS-329 STOP yet from Phoenix Contact
%s:Invalid mode at Please see manual IBS SYS FW G4 UM E
IBSS-330 STOP device from Phoenix Contact
IBSS-331 STOP %s:Wrong data length from Phoenix Contact
IBSS-332 STOP %s:Wrong ID code (PCP) from Phoenix Contact
%s:Inadmissible width Please see manual IBS SYS FW G4 UM E
IBSS-333 STOP (PCP) from Phoenix Contact
%s:Dynamic PCP cannot Please see manual IBS SYS FW G4 UM E
IBSS-334 STOP be used from Phoenix Contact
IBSS-335 STOP %s:State conflict (On) from Phoenix Contact
IBSS-336 STOP %s:State conflict (Off) from Phoenix Contact
%s:Operation not Please see manual IBS SYS FW G4 UM E
IBSS-337 STOP possible from Phoenix Contact
%s:Multiple errors Please see manual IBS SYS FW G4 UM E
%s:Multiple timeout Please see manual IBS SYS FW G4 UM E
%s:Further device at Please see manual IBS SYS FW G4 UM E
IBSS-340 STOP bus from Phoenix Contact
%s:Data register error Please see manual IBS SYS FW G4 UM E
%s:Further local bus Please see manual IBS SYS FW G4 UM E
IBSS-343 STOP device from Phoenix Contact
%s:Invalid ID code Please see manual IBS SYS FW G4 UM E
%s:Too many devices at Please see manual IBS SYS FW G4 UM E
%s:Multiple errors Please see manual IBS SYS FW G4 UM E
%s:Multiple timeouts Please see manual IBS SYS FW G4 UM E
%s:Further device at Please see manual IBS SYS FW G4 UM E
%s:Data register error Please see manual IBS SYS FW G4 UM E
%s:Too many devices Please see manual IBS SYS FW G4 UM E
IBSS-350 STOP activated from Phoenix Contact
IBSS-351 STOP %s:Error in local bus from Phoenix Contact
%s:Too many devices in Please see manual IBS SYS FW G4 UM E
%s:Invalid ID code Please see manual IBS SYS FW G4 UM E
IBSS-354 STOP %s:Error on channel from Phoenix Contact
%s:Short circuit at Please see manual IBS SYS FW G4 UM E
IBSS-355 STOP output from Phoenix Contact
IBSS-356 STOP %s:Initiator supply error from Phoenix Contact
IBSS-357 STOP %s:Power supply error from Phoenix Contact
led to the error, and call
IBSS-358 %s:Configuration error System internal error your FANUC America
%s:Peripheral electronic led to the error, and call
IBSS-359 error System internal error your FANUC America
IBSS-360 %s:Temperature excess System internal error your FANUC America
IBSS-361 %s:Loop error (Out2) System internal error your FANUC America
%s:Isolated Please see manual IBS SYS FW G4 UM E
IBSS-362 STOP disconnection error from Phoenix Contact
IBSS-380 STOP %s:Look for Failure from Phoenix Contact
IBSS-381 WARN %s:Peripheral warning from Phoenix Contact
IBSS-382 STOP %s:Control Fault from Phoenix Contact
IBSS-383 STOP %s:User Fault from Phoenix Contact
IBSS-384 STOP %s:User Fault (%s) from Phoenix Contact
%s:Controller Board Please see manual IBS SYS FW G4 UM E
IBSS-390 STOP Error from Phoenix Contact
%s:Board has not Please see manual IBS SYS FW G4 UM E
IBSS-391 STOP enough memory from Phoenix Contact
%s:Board checksum Please see manual IBS SYS FW G4 UM E
IBSS-392 STOP error from Phoenix Contact
IBSS-393 STOP %s:Board system error from Phoenix Contact
%s:is reported by Please see manual IBS SYS FW G4 UM E
IBSS-394 STOP firmware from Phoenix Contact
%s: Can't execute Please see manual IBS SYS FW G4 UM E
IBSS-395 STOP service from Phoenix Contact
IBSS-396 WARN Board status is READY from Phoenix Contact
IBSS-397 WARN Board status is ACTIVE from Phoenix Contact
IBSS-398 WARN Board status is RUN from Phoenix Contact
IBSS-399 WARN Board status is Bus Fail from Phoenix Contact
%s:Service called w/o Please see manual IBS SYS FW G4 UM E
IBSS-400 STOP Rights from Phoenix Contact
%s:Firmw.command Please see manual IBS SYS FW G4 UM E
IBSS-401 WARN busy now from Phoenix Contact
SYSTE %s:Board error Please see manual IBS SYS FW G4 UM E
IBSS-402 M reported from Phoenix Contact
SYSTE %s:Firmware error Please see manual IBS SYS FW G4 UM E
IBSS-403 M reported from Phoenix Contact
%s:Bus warning time Please see manual IBS SYS FW G4 UM E
IBSS-404 WARN elapsed from Phoenix Contact
IBSS-405 WARN %s:Wrong Variable ID from Phoenix Contact
%s:1st Seg. Please see manual IBS SYS FW G4 UM E
IBSS-420 WARN Unswitchable from Phoenix Contact
%s:Can't enable Please see manual IBS SYS FW G4 UM E
IBSS-421 STOP multiple Alt.Group from Phoenix Contact
%s:Dev dependency Please see manual IBS SYS FW G4 UM E
IBSS-422 STOP conflict from Phoenix Contact
%s:Can't take Exclusive Please see manual IBS SYS FW G4 UM E
IBSS-423 STOP Rights from Phoenix Contact
Peripheral warning Please see manual IBS SYS FW G4 UM E
IBSS-424 WARN exists from Phoenix Contact
Peripheral warning Please see manual IBS SYS FW G4 UM E
IBSS-425 WARN cleared from Phoenix Contact
Seg.%d at outgoing led to the error, and call
IBSS-447 remote bus System internal error your FANUC America
Seg.%d at outgoing led to the error, and call
IBSS-448 local bus System internal error your FANUC America
IBSS-449 %d.%d device not found System internal error your FANUC America
IBSS-450 %d.%d %s System internal error your FANUC America
IBSS-451 Additional Info %s System internal error your FANUC America
IBSS-452 Slave No data Exchange System internal error your FANUC America
IBSS-453 Bus Fault is indicated System internal error your FANUC America
IBSS-454 CMD mode is selected System internal error your FANUC America
IBSS-455 TP mode is selected System internal error your FANUC America
IBSS-456 Device %d is inserted System internal error your FANUC America
IBSS-457 Device %d is deleted System internal error your FANUC America
Please power OFF/ON led to the error, and call
IBSS-458 for Master System internal error your FANUC America
IBSS-459 Too many device System internal error your FANUC America
Can't swich at READY led to the error, and call
IBSS-461 state System internal error your FANUC America
Parameterization is led to the error, and call
IBSS-462 performed System internal error your FANUC America
IBSS-463 Load SVC successful System internal error your FANUC America
Clear parm mem is led to the error, and call
Load Config is led to the error, and call
IBSS-466 Board not ready System internal error your FANUC America
BackUp %d board files led to the error, and call
IBSS-467 (%s) System internal error your FANUC America
Slave external power led to the error, and call
IBSS-468 off System internal error your FANUC America
IBSS-469 Slave not Init/Ready System internal error your FANUC America
Slave DIP setting led to the error, and call
IBSS-470 mismatch System internal error your FANUC America
Firmware version led to the error, and call
Please power OFF/ON led to the error, and call
IBSS-472 for Slave System internal error your FANUC America
Parameterization not led to the error, and call
IBSS-473 finished System internal error your FANUC America
“Use CMD” setting led to the error, and call
IBSS-475 PCI board not installed System internal error your FANUC America
IBSS-476 newmem %d failed System internal error your FANUC America
IBSS-477 mktsk %d failed %d System internal error your FANUC America
Slave Parameterization led to the error, and call
IBSS-478 invalid System internal error your FANUC America
Firmware Updating led to the error, and call
IBSS-479 Mode System internal error your FANUC America
IBSS-480 Sysfail Reset Failed System internal error your FANUC America
IBSS-481 MPM1 Ready Bit OFF System internal error your FANUC America
Alternative Recovery led to the error, and call
IBSS-482 Disabled System internal error your FANUC America
Execute param. for led to the error, and call
IBSS-483 Baud-Rate System internal error your FANUC America
Slave : Power off, led to the error, and call
IBSS-484 Discon. 24V System internal error your FANUC America
Power off or Execute led to the error, and call
IBSS-485 param. System internal error your FANUC America
Power OFF/ON is led to the error, and call
IBSS-486 necessary System internal error your FANUC America
IBSS-487 Trying to reset Bus Fault System internal error your FANUC America
IBSS-488 Master is not running System internal error your FANUC America
Update Dev. Name by led to the error, and call
IBSS-489 Load Conf. System internal error your FANUC America
Parameterization by led to the error, and call
IBSS-490 SVC failed System internal error your FANUC America
IBSS-491 SVC file is not loaded System internal error your FANUC America
Alternative is not led to the error, and call
IBSS-492 recovered System internal error your FANUC America
Firmware reply %s led to the error, and call
IBSS-493 timeout System internal error your FANUC America
Slave err1shot is led to the error, and call
IBSS-494 disabled System internal error your FANUC America
Failed to enable byte led to the error, and call
IBSS-495 swap System internal error your FANUC America
len/ofs not multiple of led to the error, and call
IBSS-496 16 System internal error your FANUC America
IBSS-497 Failed to change len/ofs System internal error your FANUC America
len/ofs must be led to the error, and call
IBSS-498 multiple of 16 System internal error your FANUC America
Analog I/O setting is led to the error, and call
Welding I/O setting is led to the error, and call
AI/AO needs analog I/O led to the error, and call
IBSS-502 option System internal error your FANUC America
Welding I/O needs Arc led to the error, and call
IBSS-503 Tool System internal error your FANUC America
Restore Alternative led to the error, and call
IBSS-504 manually System internal error your FANUC America
Loading IBPXC.SV (need led to the error, and call
IBSS-505 1 minute) System internal error your FANUC America
Failed to optimize I/O led to the error, and call
IBSS-506 transfer An internal system error has occurred. your FANUC America
Bad PDD Type(%x) at led to the error, and call
IBSS-507 %d.%d An internal system error occurred. your FANUC America
Print: Internal error led to the error, and call
Printing of config. led to the error, and call
IBSS-511 devices System internal error your FANUC America
IBSS-512 Printing finished System internal error your FANUC America
DevName: Internal led to the error, and call
IBSS-520 error (%s) System internal error your FANUC America
IBSS-521 Port already assigned System internal error your FANUC America
IBSS-522 Port is invalid System internal error your FANUC America
IBSS-523 Set assignment failed System internal error your FANUC America
IBSS-530 Save: Internal error (%s) System internal error your FANUC America
Start saving DevName led to the error, and call
IBSS-531 List System internal error your FANUC America
Saving DevName List led to the error, and call
IBSS-534 Save: System error (%s) System internal error your FANUC America
Load: Internal error led to the error, and call
Start loading DevName led to the error, and call
IBSS-536 List System internal error your FANUC America
Loading DevName List led to the error, and call
IBSS-538 No Integer in Line (%s) System internal error your FANUC America
IBSS-539 Load: System error (%s) System internal error your FANUC America
IBSS-550 Internal error (%d) An internal system error has occurred. your FANUC America
Can't open InterBus led to the error, and call
IBSS-551 Archive An internal system error has occurred. your FANUC America
IBSS-552 Get_Directory failed An internal system error occurred. your FANUC America
IBSS-553 File_Open %s failed An internal system error occurred. your FANUC America
IBSS-554 File_Read %s failed An internal system error occurred. your FANUC America
IBSS-555 File_Write %s failed An internal system error occurred. your FANUC America
IBSS-556 File_Close %s failed An internal system error occurred. your FANUC America
Archive version (%x) led to the error, and call
IBSS-557 unsupported An internal system error occurred. your FANUC America
Clear_Param_Mem led to the error, and call
IBSS-558 failed An internal system error occurred. your FANUC America
%d files saved as Please see manual IBS SYS FW G4 UM E
IBSS-559 WARN ibbdfil.iba from Phoenix Contact
%d files loaded by Please see manual IBS SYS FW G4 UM E
No file to Please see manual IBS SYS FW G4 UM E
IBSS-561 WARN backup/restore from Phoenix Contact
File size in archive is Please see manual IBS SYS FW G4 UM E
IBSS-562 WARN wrong from Phoenix Contact
ibbdfil.iba is truncated Please see manual IBS SYS FW G4 UM E
IBSS-563 WARN %d from Phoenix Contact
File name must be MS Please see manual IBS SYS FW G4 UM E
IBSS-564 WARN DOS format from Phoenix Contact
IBSS-565 WARN Can't backup %s from Phoenix Contact
IBSS-566 WARN Can't restore %s from Phoenix Contact
Too many files in Please see manual IBS SYS FW G4 UM E
IBSS-568 WARN File list is too small from Phoenix Contact
Can't get right. Try Please see manual IBS SYS FW G4 UM E
IBSS-569 WARN again. from Phoenix Contact
Too many PCI board Please see manual IBS SYS FW G4 UM E
IBSS-570 STOP found from Phoenix Contact 3.7.2 INTP Alarm Code
Failed to backup Please see manual IBS SYS FW G4 UM E Please see manual IBS SYS
IBSS-571 ibbdfil.iba from Phoenix Contact FW G4 UM E from
Set Master-Only HW. Master-Only board is found but Set $IBPX_HW.$HW_TYPE
IBSS-572 setting hardware type setting is disabled. = 1 and cycle power.
Remove Master-Only System coupler board is found but Set $IBPX_HW.$HW_TYPE
IBSS-573 HW. setting
Use CMD for Master- hardware
Use CMD istype setting
disabled is enabled.
but Master-Only =Enable
0 andUse
cycle power.
CMD setting
IBSS-574 Only HW. board is found. and cycle power.
The SVC file stored in the controller
IBSS-575 SVC type mismatch does not match the type of current Load SVC file again.
ibbdfil.iba type The IBA file being restored to the Check that the IBA file for
IBSS-576 mismatch controller does not match the type of the installed
Wait for rightInterBus
robot to
ICRZ-001 Wait for right robot Too close to right robot. move away.
Wait for left robot to
ICRZ-002 Wait for left robot Too close to left robot. move away.
ICRZ-003 Unhold robot UNHOLD robot. Robot is ready to move.
Right robot zone Right robot moves away from the
ICRZ-004 cleared interferenced
Left robot movesrail away
zone.from the None.
ICRZ-005 Left robot zone cleared interferenced rail zone. None.
Both robots are moving to same rail Unlock the robots and jog
ICRZ-006 Dead disable
Zone lock condition
while zone check is disabled while robot is
Zone robots away from
ICRZ-007 robot held
GOUT is not set for being held
GOUT is not set properly for right Enable
set theDOUT
Group zone check.
for right
ICRZ-008 right robot
GOUT is not set for left robot. robot.
ICRZ-009 robot
GIN is not set for right GOUT is not set properly for left robot. Set GOUT for left robot.
ICRZ-010 robot GIN is not set properly for right robot. Set GIN for right robot.
GIN is not set for left
ICRZ-011 robot GIN is not set properly for left robot. Set GIN
and for left right
enable robot.
ICRZ-012 Right robot is not set Right is not set properly or not enabled. robot.
ICRZ-013 Left robot is not set Left is not set properly or not enabled. Set and enable left robot.
ICRZ-014 Upper Barrier Limit Reach upper rail limit. Change rail motion range.
ICRZ-015 Lower Barrier Limit Reach lower rail limit. Change rail motion range.
Pos %d wrong output Output signal of I/F panel
signal(push push button cannot be
button:page%d,row%d, read. Position number,
IFPN-001 col%d) page number, row and
Output signal of I/F panel
Pos %d wrong output push button lamp cannot
signal(push button be read. Position number,
lamp:page%d,row%d,co page number, row and
IFPN-002 l%d) column of the button
Pos %d wrong status Status signal of I/F panel push button Please check if I/O type
signal(push button lamp cannot be read. Position number, and index is correct or
IFPN-003 lamp:page%d,row%d,co page number, row and column of the not.
Pos %d wrong Signal(Left/Up) of I/F panel 2 contact
signal(left/up)(2 contact point switch cannot be read. Position Please check if I/O type
point number, page number, row and and index is correct or
IFPN-004 switch:page%d,row%d,c column of the button when alarm was not.
Pos %d wrong Signal(Right/Down) of I/F panel 2
signal(right/down)(2 contact point switch cannot be read. Please check if I/O type
contact point Position number, page number, row and index is correct or
IFPN-005 switch:page%d,row%d,c and column of the button when alarm not.
Pos %d wrong Signal of lamp of I/F panel cannot be Please check if I/O type
signal(lamp:page%d,ro read. Position number, page number, and index is correct or
IFPN-006 w%d,col%d) row and column of the button when not.
Pos %d wrong Signal of I/F panel digital switch cannot
signal(%d)(digital be read. If the number in ( ) is N, the Please check if I/O type
switch:page%d,row%d,c Nth signal cannot be read. Position and index is correct or
IFPN-007 ol%d) number, page number, row and not.
Signal of I/F panel digital
Pos %d wrong lamp cannot be read. If
signal(%d)(digital the number in ( ) is N, the
lamp:page%d,row%d,co Nth signal cannot be read.
IFPN-008 l%d) Position number, page
Button of I/F panel was pressed Press the button while
IFPN-009 Press shift key without pressing shift key. holding shift key.
Button of I/F panel was pressed but I/F Turn on enable switch of
IFPN-010 Enable Interface panel panel was disabled. Enable switch of I/F I/F panel before pressing
Confirm input value and
IFPN-011 Out of range(%d - %d) Input value is out of range. valid range. Input valid
Requested operation
cannot be performed
now. I/F panel is displayed
IFPN-012 I/F panel is displayed by another pane. Remedy:
The button is Another pane is displaying
configured in another detail screen of the
IFPN-013 pane button that you tried to
Requested operation
cannot be performed
Button type setup now. Button type setup
IFPN-014 screen is displayed screen is displayed by
Software for I/F panel
could not get enough
IFPN-015 Not enough memory memory to display I/F
The number you input or
increment of number is
Max value decided by not allowed. The value
the number of signals is exceeds maximum value
IFPN-016 %d decided by specified
Another pane is displaying
I/F panel detail setup
Detail setup screen is screen. You cannot
IFPN-017 displayed perform the operation
Button of I/F panel cannot
be pressed. It is because
IFPN-018 TP Estop is pressed check of dead man switch
check of TP enable switch
IFPN-019 TP is disabled is specified and TP is
Deadman switch is not check of dead man switch
IFPN-020 gripped properly is specified and it is not
Pos %d wrong condition be pressed. It is because
IFPN-021 signal check of condition signal
IFPN-022 Condition signal is OFF check of condition signal
IFPN-023 Condition
ABORT. Req signal
has not beenis ON check of condition signal
INTP-000 G processed yet
Cannot lock the motion Motion control for the specified group enable switch and other
INTP-001 WARN grp cannot be locked. running programs to
ABORT. Program manager and hold the SHIFT and
INTP-002 G internal error Internal system error. RESET keys. 3. While still
ABORT. and hold the SHIFT and
INTP-003 G Invalid request Internal system error. RESET keys. 3. While still
PAUSE. Cannot ATTACH with TP The ATTACH statement requires the Disable the teach
INTP-004 G
PAUSE. enabled
Cannot release motion teach pendant to be disabled. pendant.
Abort the running or
INTP-005 G control Motion control cannot be released. paused program.
ABORT. (%s^4, %d^5) Internal and hold the SHIFT and
INTP-100 L error (PXnn) Internal system error. RESET keys. 3. While still
ABORT. (%s^4, %d^5) Internal and hold the SHIFT and
INTP-101 L error (system) Internal system error. RESET keys. 3. While still
For TPE programs, if
possible, reload program
ABORT. (%s^4, %d^5) Code from back-up device. If a
INTP-102 L format is invalid Program data is corrupted. back-up is not available, it
ABORT. (%s^4, %d^5) Program An error occurred while the program Refer to the error cause
INTP-103 L error was running. code. Use MENU to
ABORT. (%s^4, %d^5) Single Refer to the error cause
INTP-104 L step failed Single step cannot be executed code. Use MENU to
ABORT. (%s^4, %d^5) Run Refer to the error cause
INTP-105 L request failed Program cannot be started. code. Use MENU to
PAUSE. (%s^4, %d^5) Continue Refer to the error cause
INTP-106 L request failed Program cannot be resumed. code. Use MENU to
ABORT. (%s^4, %d^5) Pause An error occurred when program Refer to the error cause
INTP-107 L request failed execution was held. code. Use MENU to
ABORT. (%s^4, %d^5) Abort An error occurred when program Refer to the error cause
INTP-108 L request failed execution was aborted. code. Use MENU to
(%s^4, %d^5) BWD Refer to the error cause
INTP-109 WARN motion request failed Backward motion cannot be executed. code. Use MENU to
(%s^4, %d^5) Get task The specified task attribute is not found
INTP-110 WARN status request failed or is not read accessible. Check the attribute.
(%s^4, %d^5) Skip The currently executing line cannot be Refer to the error cause
INTP-111 WARN statement request changed. code. Use MENU to
PAUSE. Cannot call interrupt The interrupt routine cannot be Refer to the error cause
INTP-112 L routine executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Stop An error occurred when motion was Refer to the error cause
INTP-113 L motion request failed stopped. code. Use MENU to
PAUSE. (%s^4, %d^5) Cancel An error occurred when motion was Refer to the error cause
INTP-114 L motion request failed canceled. code. Use MENU to
PAUSE. (%s^4, %d^5) Resume An error occurred when motion was Refer to the error cause
INTP-115 L motion request failed resumed. code. Use MENU to
PAUSE. (%s^4, %d^5) Hold An error occurred when motion was Refer to the error cause
INTP-116 L motion request failed held. code. Use MENU to
PAUSE. (%s^4, %d^5) Unhold An error occurred when motion was Refer to the error cause
INTP-117 L motion request failed unheld. code. Use MENU to
PAUSE. (%s^4, %d^5) Walk back An error occurred trying to obtain the Refer to the error cause
INTP-118 L data request failed execution history. code. Use MENU to
PAUSE. (%s^4, %d^5) Get trace An error occurred trying to obtain the Refer to the error cause
INTP-119 L data request failed trace data. code. Use MENU to
PAUSE. (%s^4, %d^5) Unwait An error occurred trying to continue Refer to the error cause
INTP-120 L action request failed program execution. code. Use MENU to
PAUSE. (%s^4, %d^5) Release An error occurred trying to obtain Refer to the error cause
INTP-121 L inquiry request failed motion information for the RELEASE code. Use MENU to
PAUSE. (%s^4, %d^5) Process An error occurred during process Refer to the error cause
INTP-122 L motion data failed motion. code. Use MENU to
PAUSE. (%s^4, %d^5) Process An error occurred during process Refer to the error cause
INTP-123 L application data failed application. code. Use MENU to
ABORT. (%s^4, %d^5) Invalid ITR The specified interrupt routine is not a Refer to the error cause
INTP-124 L routine valid type. code. Use MENU to
ABORT. Failed to convert The conversion of one position type to Refer to the error cause
INTP-125 L position another failed. code. Use MENU to
ABORT. Vision built-in return Refer to the error cause
INTP-126 L failed The vision built-in failed to return. code. Use
Resume theMENU to after
program
INTP-127 WARN
PAUSE. Power fail detected Power failure was detected. hot start is complete.
INTP-128 L Pos reg is locked Pos register is locked. Wait a moment
ABORT. Cannot use motion Try to lock motion group even though Clear motion group mask
INTP-129 L group this program cannot use motion group in program detail screen
ABORT. (%s^4, %d^5) Exec Refer to the error cause
INTP-130 L
ABORT. status recovery
Number of stop failed Failed
Too to recover
many execution
stop data status.
is created at one code. Usenumber
Decrease MENU toof stop
INTP-131 LPAUSE. exceeds limit
Unlocked groups time.
The specified motion groups are data.
Change the specify of
INTP-132 L specified already unlocked. motion group.
PAUSE. Motion is already Some specified motion groups are Change the specify of
INTP-133 L released already unlocked. motion group. Lock the
The automatic start was done the
defined times but the alarm was not
PAUSE. Over automatic start fixed. And the automatic start count of Please fix the alarm by
INTP-134 L Max counter auto error recovery function is over the manual.
The error recovery DO status is OFF in Please check the
PAUSE. Recovery DO OFF in the automatic start feature So the condition of error
INTP-135 L auto start mode resume program cannot be exeucted recovery DO status
Can not use motion $PAUSE_PROG should specify a Please set another
INTP-136 WARN group for dry run program that has NO motion group. program with no motion
Program specified by The program which is specified by Please check
INTP-137 WARN $PAUSE_PROG doesn't $PAUSE_PROG doesn't exist. $PAUSE_PROG.
Program specified by The program which is specified by Please check
INTP-138 WARN $RESM_DRYPROG $RESUME_PROG doesn't exist. $RESUME_PROG.
PAUSE. (%s^4, %d^5) Local An error occurred trying to access the Refer to the error cause
INTP-139 L variable request failed local variable(s). code. Use MENU to
(%s^4, %d^5) Start pre- Error occured just before sending start This is internal error.
INTP-140 PAUSE planed motion failed motion packed for pre-planned motion. Perform cold start.
INTP-141 Returndelete
Illegal failed(TUI)
of N/A N/A
INTP-142 MMR/AMR
(%s^4, %d^5)Duplicate N/A N/A
INTP-143 use of MIR
(%s,%d) got MIR that N/A N/A
INTP-144 (%s,%d)
Illegal is of
use using N/A N/A
INTP-145 MLB(%s,%d) N/A N/A
The program cannot be started. The
action program of Monitor instructionPerform remedy
INTP-146 Run request failed failed to start. Refer to the error cause
according to the cause.
Internal system error. Refer to the error
Cycle power. If the error is
cause in the alarm detail screen of not cleared, document
INTP-147 Internal error (system) ALARM/HIST. Not enough memory pool the events that led to the
Motion group mismatch Sub program has the motion group thatChange motion group of
INTP-148 between Main and Sub
String for argument is Main program doesn't have. Sub
Passprogram to same
more short string for
INTP-149 too long String for argument is too long. argument.
(%s^4, %d^5) Multiple Multiple calls of USER function are Please make only one call
INTP-150 USER are
PAUSE. (%s^4, %d^5)enabled. enabled
The teachinpendant
a P-SPS. program instruction
of USER
Check fucntion
the be
appropriate
INTP-200 L
PAUSE. Unimplemented
(%s^4, TP
%d^5) Untaught is not available. option is loaded.
INTP-201 L
PAUSE. element%d^5)
(%s^4, encountered
Syntax The instruction is not taught. Teach the instruction.
INTP-202 LPAUSE. error
(%s^4, %d^5) Variable Instruction syntax error. Reteach the instruction.
INTP-203 L
PAUSE. type mismatch
(%s^4, %d^5) Invalid The variable type is not correct. Check the variable type.
INTP-204 L value for index The index value is invalid. Check the index value.
PAUSE. (%s^4, %d^5) Analog Refer to the error cause
INTP-205 L port access error Analog I/O is not functioning properly. code. Use MENU to
PAUSE. (%s^4, %d^5) Digital Refer to the error cause
INTP-206 L port access error Digital I/O is not functioning properly.
code. Use MENU to
PAUSE. (%s^4, %d^5) Group I/O Refer to the error cause
INTP-207 LPAUSE. port access
(%s^4, %d^5) error
Divide by Group I/O is not functioning properly. code. Use MENU to
INTP-208 L 0 Division by 0 was executed. Check the value.
PAUSE. (%s^4, %d^5) SELECT is A CASE instruction was executed before Add a SELECT instruction
INTP-209 L needed a SELECT instruction. before the CASE
PAUSE. (%s^4, %d^5) Start Refer to the error cause
INTP-210 L TIMER failed The program timer cannot be started. code. Use MENU to
PAUSE. (%s^4, %d^5) Delete Refer to the error cause
INTP-211 L TIMER failed The program timer cannot be stopped. code. Use MENU to
PAUSE. (%s^4, %d^5) Invalid The indicated value cannot be used for
INTP-212 L value for OVERRIDE the OVERRIDE instruction. Check the value.
PAUSE. %s^7 (%s^4, %d^5) Refer to the user alarm
INTP-213 L UALM[%d^9] A user alarm occurred. code. Use MENU to
PAUSE. (%s^4, %d^5) Specified The position register or frame setup Set up the motion group
INTP-214 L
PAUSE. group not
(%s^4, locked
%d^5) Group instructions were executed in a in the program DETAIL
INTP-215 L mismatch The position data is invalid. Check the position data.
PAUSE. (%s^4, %d^5) Invalid The indicated value is invalid for the
INTP-216 L value for group number motion group number. Check the value.
PAUSE. (%s^4, %d^5) SKIP The SKIP instruction was executed Add a SKIP CONDITION
INTP-217 L CONDITION needed before a SKIP CONDITION instruction. instruction.
PAUSE. The SKIP instruction or SKIP CONDITION Refer to the error cause
INTP-218 L (%s^4, %d^5) Skip failed instruction cannot be executed. code. Use MENU to
ABORT. (%s^4, %d^5) Pause The PAUSE instruction cannot be Refer to the error cause
INTP-219 L task failed executed. code. Use MENU to
ABORT. (%s^4, %d^5) Abort The ABORT instruction cannot be Refer to the error cause
INTP-220 L task failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) The application instruction cannot be Refer to the error cause
INTP-221 L Application failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Call The program CALL instruction cannot Refer to the error cause
INTP-222 L program failed be executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Delay The WAIT instruction cannot be Refer to the error cause
INTP-223 L time failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Jump The BRANCH instruction cannot be Refer to the error cause
INTP-224 L label failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Motion The MOTION instruction cannot be Refer to the error cause
INTP-225 L statement failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Read Refer to the error cause
INTP-226 L position register failed The position register cannot be read. code. Use MENU to
PAUSE. (%s^4, %d^5) Write Refer to the error cause
INTP-227 L position register failed The position register cannot be written. code. Use MENU to
INTP-228 L register failed The register cannot be read. code. Use MENU to
INTP-229 L register failed The register cannot be written. code. Use MENU to
PAUSE. (%s^4, %d^5) Wait A condition WAIT instruction cannot be Refer to the error cause
INTP-230 L condition failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) Read next Refer to the error cause
INTP-231 L
PAUSE. line failed
(%s^4, %d^5) Invalid The next line cannot be read. code. Use MENU to
INTP-232 L frame number The frame number is invalid. Check the frame number.
INTP-233 L frame value failed The specified frame cannot be read. code. Use MENU to
INTP-234 L frame value failed The specified frame cannot be written. code. Use MENU to
PAUSE. (%s^4, %d^5) Read pos Refer to the error cause
INTP-235 L item failed The position variable cannot be read. code. Use MENU to
PAUSE. (%s^4, %d^5) Write pos The position variable cannot be Refer to the error cause
INTP-236 L item failed written. code. Use MENU to
(%s^4, %d^5) No more Backward execution cannot be Do not use backward
INTP-237 WARN motion%d^5)
(%s^4, for BWD
BWD executed any more because the current Do execution
not useatbackward
this point
INTP-238 WARN execution
(%s^4, completed
%d^5) Cannot Backward
This execution
instruction wasbecompleted.
cannot executed execution
Set fromtothis
the cursor thepoint.
INTP-239 WARN execute backwards backwards. following line.
PAUSE. (%s^4, %d^5) The specified data type in the
INTP-240 L
PAUSE. Incompatible
(%s^4, %d^5) data type PARAMETER instruction is invalid for data type.
Check the parameter
INTP-241 L Unsupported This type of parameter cannot be used. type.
An OFFSET instruction was executed Add an OFFSET
PAUSE. (%s^4, %d^5) Offset before an OFFSET CONDITION CONDITION instruction
INTP-242 L value is needed instruction. A position register was not before the OFFSET
ABORT. (%s^4, %d^5) Def grp is This program has no motion group Remove the MOTION
INTP-243 L
PAUSE. not specified
(%s^4, %d^5) Invalid defined. The MOTION instruction instruction or set up the
INTP-244 L line number The input line number is incorrect. Check the line number.
PAUSE. (%s^4, %d^5) RCV stmt The RECEIVE R[] instruction cannot be Refer to the error cause
INTP-245 L failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) The SEMAPHORE instruction cannot be Refer to the error cause
INTP-246 L SEMAPHORE stmt failed executed. code. Use MENU to
Press RESET to clear the
Pre-execution system of motion or error and continue the
application has some trouble and program. If this error
PAUSE. (%s^4, %d^5) Pre exec system pauses the program execution continues to occur,
INTP-247 L failed for safety. perform a cold start by
PAUSE. (%s^4, %d^5) MACRO The MACRO instruction cannot be Refer to the error cause
INTP-248 L failed executed. code. Use MENU to
Check the MACRO setup.
PAUSE. Macro is not set For more information on
INTP-249 L correctly The MACRO setup was invalid. setting up macros, Refer
PAUSE. (%s^4, %d^5) Invalid Refer to the error cause
INTP-250 L uframe number The user frame number is invalid. code. Use MENU to
PAUSE. (%s^4, %d^5) Invalid Refer to the error cause
INTP-251 L utool number The tool frame number is invalid. code. Use MENU to
PAUSE. User frame number The user frame number in the Check the user frame
INTP-252 L mismatch positional data is not the same as the number.
PAUSE. Tool frame number The tool frame number in the Check the tool frame
INTP-253 L
PAUSE. mismatch
(%s^4, %d^5) positional
The dataparameter
specified is not thename
same cannot
as the Check
number.the parameter
INTP-254 L Parameter not found be found. name.
PAUSE. (%s^4, %d^5) The CAL_MATRIX instruction cannot be Refer to the error cause
INTP-255 L CAL_MATRIX failed executed. code. Use MENU to
PAUSE. (%s^4, %d^5) No data The origin 3 points or destination 3 Teach the origin 3 points
INTP-256 L for CAL_MATRIX points are not taught. or destination 3 points.
PAUSE. (%s^4, %d^5) Invalid The wait time value is negative or
INTP-257 L delay time exceeds the maximum value of Input a correct value.
PAUSE. (%s^4, %d^5) Weld port Refer to the error cause
INTP-258 L access error The weld is not functioning properly. code. Use MENU to
PAUSE. (%s^4, %d^5) Invalid The data type of the position register Change position register
INTP-259 LPAUSE. position type Invalid
(%s^4, %d^5) was taught using joint type. data to cartesian.
INTP-260 L torque limit value Invalid torque value. Input a correct value.
PAUSE. (%s^4, %d^5) Array A subscript is missing from a TPE Correct the PARAMETER
INTP-261 L subscript missing PARAMETER statement that specifies statement to include the
PAUSE. (%s^4, %d^5) Field A field name is required in a Correct the PARAMETER
INTP-262 LPAUSE. name
(%s^4,missing
%d^5) Invalid PARAMETER statement that specifies a statement to include the
INTP-263 L
SERVO register%d^5)
(%s^4, type Soft float The register type is not valid. Check the register type.
INTP-264 2 time out
PAUSE. (%s^4, %d^5) Invalid The indicated value cannot be used for
INTP-265 L value for speed value the AF instruction. Check the value.
One (or both) of the
A MOVE statement was executed in an following should correct
(%s^4, %d^5) interrupt routine while a motion in the this problem: 1. Add
ABORT. Mnemonic in interupt is interrupted program was still in CANCEL or STOP condition
INTP-266 LPAUSE. failed
(%s^4, %d^5) RUN stmt progress. handler action before the
INTP-267 L
PAUSE. failed %d^5) This
(%s^4, Specified
This program
startment can isexist
already running
in one Abort specified
in each Delete the extraprogram
INTP-268 LPAUSE. statement
(%s^4, only
%d^5) one in
Skip line startment can exist in one in each Delete
Skip statementthe extra skip
INTP-269 L statement only one in line statement
During backward execution, a move is
PAUSE. (%s^4, %d^5) Different encountered that has a different group Use FWD execution
INTP-270 L group cannot BWD number from the previous motion carefully
(%s^4, %d^5) Excessive Torque limit value exceeds maximum Set torque limit value less
INTP-271 WARN torque limit value value. Torque limit value was modified than or equal to the
PAUSE. (%s^4, %d^5) Check the operator Refer
INTP-272 L Unsupported operator This operator is not supported. to the KAREL and TPP
PAUSE. (%s^4, %d^5) Too many The number of the condition exceeds Reduce the number of
INTP-273 L conditions the maximum number. condition.
PAUSE. (%s^4, %d^5) CH This monitor statement cannot be Refer to the error cause
INTP-274 L
PAUSE. program
Invalid suberror
type of CH executed.
The sub type of specified ch program code. Use
Check the MENU
sub typeto of this
INTP-275 L program cannot be used. CH program.
(%s^4, %d^5) Invalid The motion option instructions (SKIP,
PAUSE. combination of motion TIME BEFORE/AFTER, and application Delete the motion option
INTP-276 L option instruction) cannot be taught together instruction
(%s^4, %d^5) Internal The EPT index in macro table doesn't Please set the correct EPT
PAUSE. MACRO EPT data point the program name defined in index for the program
INTP-277 L mismatch macro table. That is, the EPT index in name defined in macro
PAUSE. The DI monitor alarm for auto error %s^7 This alarm is defined
INTP-278 L %s^7 recovery function occurs. by the customer.
(%s^4, %d^5) The application instruction was Please change the
PAUSE. Application instruction executed. But this application application process data
INTP-279 L mismatch instruction doesn't match to the of this program to the
PAUSE. (%s^4, %d^5) The application data of called program Please change the
INTP-280 L Application data is different from that of the original structure of program
PAUSE. This program doesn't have the Please define the
INTP-281 L
PAUSE. No application
(%s^4, datafault
%d^5) Fast application data application data in the
INTP-282 L status mismatch
PAUSE. (%s^4, %d^5) Stack over Stack over flow to record the fast fault Reduce the nesting of the
INTP-283 L
PAUSE. flowdetection
No for fast fault
of fast recovery
The pointnesting
for the data
fast fault recover program
INTP-284 L fault recovery cannot detected
Karel program cannot The fast entry cannot be performed in
INTP-285 WARN MAINT
entry inprogram
fast fautlisn't the karel
MAINT program.
program is not defined in fast Use TP program.
INTP-286 WARN defined in fast fautl fault recovery.
PAUSE. Fail to execute MAINT Confirm the MAINT
INTP-287 L program It failed to execute MAINT program program name is correct
PAUSE. (%s^4, %d^5) The parameter designated by AR Please confirm the index
INTP-288 L Parameter does not register does not exist. of AR register and the
When fast fault is enabled, the program Check whether the CONT
PAUSE. Can't save ffast point at was paused at the part of program terminaton exists at end
INTP-289 L program change change of sub-program If exist,
PAUSE. Fast fault recovery During fast fault recovery sequence,
INTP-290 L position is not saved any alarm occurs. So the fast fault
(%s^4, %d^5) Index for The parameter designated by AR Please confirm the index
INTP-291 WARN AR is not correct register does not exist. But this error of AR register and the
PAUSE. more than 6 motion More than 6 motion statements with Please change teaching so
INTP-292 LPAUSE. with DB executed
(%s,%d)DB too Distance Before are mixed was not
condition that less
Please thandistance
make 5 motion
INTP-293 L small(away)(%dmm). established. value larger.
ABORT. The parameter designed in Document the events that
INTP-294 G TPE parameter
(%s,%d)DB too error CALL/MACRO
Distance Before instruction
conditioniswas
notnot
correct. led to the
Please error
make and call
distance
INTP-295 WARN small(away)(%dmm). established. value larger.
(%s,%d) Distance Before doesn't work if Please set $SCR_GRP_[
INTP-296 WARN $SCR_GRP[%d].$M_POS
(%s,%d)DB too $SCR_GRP[ ].$M_POS_ENB
Motion completed is FALSE.
before trigger of DB ].$M_POS_ENB to TRUE.
Please change distance
INTP-297 WARN (%s,%d)DB
small(done)(%dmm)
interrupt condition. value.
INTP-298 error(%d) interrupt
(%s,%d)DB N/A N/A
INTP-299 error(%d) N/A N/A
ABORT. (%s^4, %d^5) KAREL program error. This KAREL Check the KAREL
INTP-300 L Unimplemented P-code statement cannot be executed. translater software
ABORT. (%s^4, %d^5) Stack KAREL program error. Execution A GOTO statement cannot
INTP-301 L underflow entered into a FOR loop by the GOTO be used to enter or exit a
The program stack overflowed. Too For KAREL programs, refer
ABORT. (%s^4, %d^5) Stack many local variables were declared or to the KAREL Reference
INTP-302 L overflow too many routines were called. Manual, Stack Usage and
ABORT. (%s^4, %d^5) Specified KAREL program error. The specified
INTP-303 L value exceeds limit value exceeds the maximum limit. Check the value.
ABORT. (%s^4, %d^5) Array KAREL program error. The dimensions Check the dimensions of
INTP-304 L length mismatch of the arrays are not the same. the arrays.
ABORT. (%s^4, %d^5) Error KAREL program error. A condition Refer to the error cause
INTP-305 L related condition handler error occurred. code. Use MENU to
ABORT. (%s^4, %d^5) Attach KAREL program error. The ATTACH Refer to the error cause
INTP-306 L request failed statement failed. code. Use MENU to
ABORT. (%s^4, %d^5) Detach KAREL program error. The DETACH Refer to the error cause
INTP-307 L request failed statement failed. code. Use MENU to
ABORT. (%s^4, %d^5) No case KAREL program error. The CASE Check the CASE value and
INTP-308 L match is encountered statement does not match any branches.
ABORT. (%s^4, %d^5) KAREL program error. The specified
INTP-309 L
ABORT. Undefined
(%s^4, %d^5)WITHCH
Invalid parameter
KAREL cannot
program be used
error. in theofwith
The index the parameter.
Check the length of the
INTP-310 L subscript for array array is invalid. array and index value.
PAUSE. (%s^4, %d^5) KAREL program error. Untaught or Teach or initialize the data
INTP-311 L
ABORT. Uninitialized
(%s^4, %d^5)data is
Invalid uninitialized
KAREL programdata was used.
error. The wrong axis beforethe
Check using
axisit.number
INTP-312 L joint number number was used. and the data value.
ABORT. (%s^4, %d^5) Motion KAREL program error. The MOTION Refer to the error cause
INTP-313 L statement failed statement cannot be executed. code. Use MENU to
ABORT. (%s^4, %d^5) Return KAREL program error. Execution cannot Refer to the error cause
INTP-314 L program failed be returned from the routine. code. Use MENU to
ABORT. (%s^4, %d^5) Built-in KAREL program error. A built-in routine Refer to the error cause
INTP-315 L execution failed error occurred code. Use MENU to
ABORT. (%s^4, %d^5) Call KAREL program error. The routine Refer to the error cause
INTP-316 L program failed cannot be called. code. Use MENU to
ABORT. (%s^4, %d^5) Invalid KAREL program error. The specified
INTP-317 L
ABORT. condition
(%s^4, specified
%d^5) Invalid condition
KAREL was invalid.
program error. The specified Check the condition.
INTP-318 LABORT. action specified
(%s^4, %d^5) Invalid action was
KAREL invalid.
program error. The data type Check the action.
INTP-319 LABORT. type code
(%s^4, %d^5) was invalid.
KAREL program error. The built-in Check the data type.
appropriate
INTP-320 L Undefined built-in routine is not defined. option is loaded.
ABORT. (%s^4, %d^5) END stmt KAREL program error. The END Add a RETURN statement
INTP-321 L of a func rtn statement was executed in a function to the function routine.
ABORT. (%s^4, %d^5) Invalid KAREL program error. The argument Check the argument
INTP-322 L arg val for builtin value of a built-in routine was wrong. value.
ABORT. (%s^4, %d^5) Value KAREL program error. The data value Check the variable's type
INTP-323 L overflow for the variable was too large. and data value.
ABORT. (%s^4, %d^5) Invalid KAREL program error. The usage string Check the usage string in
INTP-324 L open mode string in the OPEN FILE statement was invalid. the OPEN FILE statement.
ABORT. (%s^4, %d^5) Invalid file KAREL program error. The file string in Check the file string. If no
INTP-325 L string the OPEN FILE statement was invalid. device is specified, the
ABORT. (%s^4, %d^5) File var is KAREL program error. The FILE variable Close the file before
INTP-326 L already used is already being used. reusing the FILE variable
ABORT. (%s^4, %d^5) Open file KAREL program error. The file could not Refer to the error cause
INTP-327 L failed be opened. code. Use MENU to
ABORT. (%s^4, %d^5) File is not KAREL program error. The specified file Open the file before
INTP-328 L opened was not opened before operation. operation.
ABORT. (%s^4, %d^5) Write KAREL program error. The value cannot Refer to the error cause
INTP-329 L variable failed be written to the variable. code. Use MENU to
ABORT. (%s^4, %d^5) Write file KAREL program error. Writing to the Refer to the error cause
INTP-330 L failed file failed. code. Use MENU to
ABORT. (%s^4, %d^5) Read KAREL program error. Reading the Refer to the error cause
INTP-331 L variable failed variable failed. code. Use MENU to
ABORT. (%s^4, %d^5) Read data KAREL program error. Data read from Make sure the data in the
INTP-332 L is too short the file is too short. file is valid.
ABORT. (%s^4, %d^5) Invalid KAREL program error. The string read
INTP-333 L ASCII string for read from the file is wrong. Check the data of the file.
ABORT. (%s^4, %d^5) Read file KAREL program error. Reading from the Refer to the error cause
INTP-334 L failed file failed. code. Use MENU to
ABORT. (%s^4, %d^5) Cannot KAREL program error. A file pre-defined Use the file defined by the
INTP-335 L open pre-defined file by the system cannot be opened. system without opening
ABORT. (%s^4, %d^5) Cannot KAREL program error. A file pre-defined
INTP-336 L
ABORT. close pre-defined
(%s^4, file
%d^5) Invalid by the program
KAREL system cannot
error. be closed.
This routine Do notsure
Make try to
youclose
haveit.the
INTP-337 L routine type cannot be used. correct routine type and
ABORT. (%s^4, %d^5) Close file KAREL program error. Closing the file Refer to the error cause
INTP-338 L
ABORT. failed %d^5) Invalid
(%s^4, failed. program error. The program
KAREL code. Use
Make sureMENU to the
you have
INTP-339 LABORT. program
(%s^4, nameInvalid
%d^5) name isprogram
KAREL invalid. error. The variable correctsure
Make program name.
you have the
INTP-340 LABORT. variable name
(%s^4, %d^5) Variable name is invalid. error. The variable
KAREL program correct variable name.
Verify the program name
INTP-341 L not found cannot be found. and variable name.
ABORT. (%s^4, %d^5) KAREL program error. The data type Make sure you have the
INTP-342 L Incompatible variable defined by the BYNAME function and correct data type and
ABORT. (%s^4, %d^5) Reference KAREL program error. Too many Decrease the number of
INTP-343 L stack overflow variables are passed using the BYNAME BYNAME functions.
ABORT. (%s^4, %d^5) KAREL program error. The buffer to
INTP-344 L Readahead buffer read ahead from the device Increase the buffer size.
ABORT. (%s^4, %d^5) Pause KAREL program error. The PAUSE Refer to the error cause
INTP-345 L task failed statement cannot be executed. code. Use MENU to
ABORT. (%s^4, %d^5) Abort KAREL program error. The ABORT Refer to the error cause
INTP-346 L task failed statement cannot be executed. code. Use MENU to
ABORT. (%s^4, %d^5) Read I/O KAREL program error. The digital input Refer to the error cause
INTP-347 L value failed signal cannot be input. code. Use MENU to
ABORT. (%s^4, %d^5) Write I/O KAREL program error. The digital Refer to the error cause
INTP-348 L value failed output signal cannot be output. code. Use MENU to
ABORT. (%s^4, %d^5) Hold KAREL program error. The HOLD Refer to the error cause
INTP-349 L motion failed statement cannot be executed. code. Use MENU to
ABORT. (%s^4, %d^5) Unhold KAREL program error. The UNHOLD Refer to the error cause
ABORT. (%s^4, %d^5) Stop KAREL program error. The STOP Refer to the error cause
ABORT. (%s^4, %d^5) Cancel KAREL program error. The CANCEL Refer to the error cause
ABORT. (%s^4, %d^5) Resume KAREL program error. The RESUME Refer to the error cause
ABORT. (%s^4, %d^5) Break KAREL program error. The break point Refer to the error cause
INTP-354 L point failed function cannot be executed. code. Use MENU to
ABORT. (%s^4, %d^5) AMR is KAREL program error. The AMR
INTP-355 L not found operated by the RETURN_AMR built-in Check program operation.
ABORT. (%s^4, %d^5) AMR is KAREL program error. The Operate the AMR using
INTP-356 L not processed yet RETURN_AMR built-in routine cannot the WAIT_AMR built-in
ABORT. (%s^4, %d^5) KAREL program error. The execution of The program executing
INTP-357 LABORT. WAIT_AMR
(%s^4, %d^5) is Timeout
cancelled the WAIT_AMR
KAREL program built-in routine
error. The READwas the WAIT_AMR
Check the devicemust be
being
INTP-358 L at read request statement timed out. read.
ABORT. (%s^4, %d^5) Read KAREL program error. Another READ
INTP-359 LABORT. request is nested
(%s^4, %d^5) Vector is statement was executed
KAREL program error. Thewhile
vectora READ
value Remove nested reads.
INTP-360 L 0 was invalid. Check the vector value.
KAREL program error. The X-axis
PAUSE. (%s^4, %d^5) direction cannot be calculated in the Teach P1 and P2 as
INTP-361 L FRAME:P2 is same as P1 FRAME built-in routine because P1 and different points.
KAREL program error. The X-Y plane
PAUSE. (%s^4, %d^5) cannot be calculated in the FRAME Teach P1 and P3 as
INTP-362 L FRAME:P3 is same as P1 built-in routine because P1 and P3 are different points.
(%s^4, %d^5) KAREL program error. The X-Y plane
PAUSE. FRAME:P3 exists on line cannot be calculated in the FRAME Teach P3 out of the X-axis
INTP-363 L
ABORT. P2-P1 %d^5) String too
(%s^4, built-inprogram
KAREL routine because P3target
error. The is located in
string direction.the target string
Increase
INTP-364 L short for data was too short. size.
ABORT. (%s^4, %d^5) KAREL program error. A FILE pre-
INTP-365 L
ABORT. Predefined
(%s^4, %d^5)window not
I/O status definedprogram
KAREL by the system is not
error. The opened.
last file Check the
Reset the error
use ofusing
this file.
the
INTP-366 L is not cleared operation failed. CLR_IO_STAT built-in
ABORT. (%s^4, %d^5) Bad base KAREL program error. I/O mode
INTP-367 L in format operates only from binary to Check the specified mode.
PAUSE. (%s^4, %d^5) Cannot KAREL program error. The specified Refer to the error cause
INTP-368 L use specified program program cannot be used. code. Use MENU to
ABORT. (%s^4, %d^5) Timeout KAREL program error. The WAIT_AMR If an AMR was expected
INTP-369 L at WAIT_AMR built-in routine timed out. within the time-out value
ABORT. (%s^4, %d^5) Vision KAREL program error. The vision CPU Plug in the vision CPU
INTP-370 L CPU not plugged in board is not plugged in. board.
ABORT. (%s^4, %d^5) Vision KAREL program error. The operation Modify program so fewer
INTP-371 L built-in overflow overflowed in the vision built-in vision builtins are
ABORT. (%s^4, %d^5) KAREL program error. The vision built- Check the appropriate
INTP-372 L Undefined vision built- in routine is not defined. option is loaded.
ABORT. (%s^4, %d^5) KAREL program error. The parameter to Check the parameter of
INTP-373 L Undefined vision the vision built-in routine is invalid. the vision built-in routine.
ABORT. (%s^4, %d^5) KAREL program error. The return value Check the return value
INTP-374 L Undefined vision return from the vision built-in routine is from the vision built-in
ABORT. (%s^4, %d^5) System KAREL program error. System variables Pass without using
INTP-375 L var passed using cannot be passed using the BYNAME BYNAME or use GET_VAR
One (or both) of the
A MOVE statement was executed in an following should correct
interrupt routine while a motion in the this problem: 1. Add
ABORT. (%s^4, %d^5) Motion in interrupted program was still in CANCEL or STOP condition
INTP-376 L ISR failed progress. handler action before the
(%s^4, %d^5) Local Refer to the error cause
INTP-377 WARN COND
(%s^4, recovery failed This
%d^5) Local Locallocal condition
variable can't be is
or parameter recovered.
used for code. Use MENU
Use global toto
variable
INTP-378 WARN variable is used the condition. recover local condition.
An invalid condition handler number Correct the condition
ABORT. Bad condition handler was used in a condition handler handler number.
INTP-379 L number definition, or an ENABLE, DISABLE, or Condition handler
A invalid program number has been Use a valid program
ABORT. specified in an ABORT PROGRAM, number. Prorgam
INTP-380 L Bad program number PAUSE PROGRAM, or CONTINUE numbers must be in the
ABORT. (%s^4, %d^5) Invalid An invalid delay time has been Use a valid delay time.
INTP-381 L
ABORT. Delay Time
(%s^4, specified
%d^5) Invalid bit An invalidinvalue
DELAYhasstatement.
been specified in Delay
Use time must
a valid value be
forinthe
the
INTP-382 LPAUSE. field value
(%s^4, %d^5) Path node bit field bit field.
INTP-383 L out of range The specified path node is out of range. Check the path node.
(%s^4, %d^5) Invalid The indicated value cannot be used for
INTP-384 PAUSE value for CNT the CNT instruction. Check the value.
Decrease the number of
ABORT. (%s^4, %d^5) Number Too many motions are executed at the motions executed at the
INTP-400 L
ABORT. of motions
(%s^4, %d^5)exceeded
Not On same time.
Paused same time.
motion exists after the motion Resume theExecute
motion thethat
INTP-401 L Top Of Stack was resumed. was previously paused.
Motion Optim. not Loading/Running optimized program Refer to the error cause
INTP-410 PAUSE
PAUSE. loaded %d^5) OFIX is
(%s^4, without OPTM loaded. code. Check
Please checkprogram
motion typeand
INTP-420 L not available
(%s^4, %d^5) Stitch OFIX is not available. and options
INTP-421 WARN disable(S/S)
(%s^4, %d^5) Stitch Single step mode is enable. Please disable
turn on single
stitch step
INTP-422 WARN
PAUSE. enable %d^5)
(%s^4, signal off Stitch enable signal is off. enable check
Please signal Equipment
INTP-423 LPAUSE. Eq.condition signal
(%s^4, %d^5) Stitch Equipment conditon signal is abnormal conditon signal
INTP-424 L speed error Setting of Stitch speed is illegal. Please check stitch speed
PAUSE. (%s^4, %d^5) Illegal Please check motion type The motion Change the motion
INTP-425 L motion type(J) statement is JOINT motion. statement to LINEAR
PAUSE. (%s^4, %d^5) Another Please force abort
INTP-426 L prog is %d^5)
(%s^4, in stitching
Stitch Another program is in stitch mode. anotherselect
Please program if it is
the other
INTP-427 WARN disable(T1 mode) System is in T1 mode. mode
Enable all motion groups
for the program. If some
The program does not have all motion groups should not be
(%s^4, %d^5) Dry Run groups. All motion groups are required affected by Dry Run, set
INTP-430 PAUSE needs other groups for Dry Run. $DRYRUN.$GRP_MASK to
(%s^4, %d^5) Dry Run Dry Run cannot start in an incremental Exit the incremental
INTP-431 PAUSE on Incremental motion motion statement. motion statement by
(%s^4, %d^5) Dry Run Dry Run cannot start in a circular Exit the circular motion by
INTP-432 PAUSE on Circular
(%s^4, %d^5)motion motion
Dry Run Dry Runstatement.
cannot start in an interrupt moving the cursor to
INTP-433 PAUSE in P-SPS routine. Exit the interrupt routine.
Please do BWD to exit P- This is used as a cause code for INTP-
INTP-434 PAUSE SPS 433, to recommend backward None.to additional errors
Refer
INTP-435 PAUSE Dry Run execution error An error occurred in Dry Run execution. for more information.
(%s^4, %d^5) Invalid The item specified in left side of Do not use the item for
INTP-436 PAUSE item for%d^5)
(%s^4, output
Marker assignment
Depth statement
of Marker is not
nesting available
is greater than output. the nesting level
Reduce
INTP-437 PAUSE (%s^4,
nesting%d^5)
too deep 10.
The Marker being read is not defined of Marker.
Define the Marker
INTP-438 PAUSE Undefined Marker by any expression. expression.
(%s^4, %d^5) Marker Multiple tasks are attempting to Check recursive
INTP-439 PAUSE conflict execute the same Marker at the same references to Markers.
(%s^4) Stopped by Program is paused by TC_ONLINE, Check TC_ONLINE
INTP-440 PAUSE TC_ONLINE because the result of the defined expression.
Please stop Background The setting of Background Logic cannot Stop the Background
INTP-441 WARN Logic be changed when the Background Logic Logic.
(%s^4, %d^5) The Background Logic that was running
Background program is at power down was changed before Execute the Background
INTP-442 PAUSE changed this COLD start. This Background Logic Logic manually.
There is an operator or data that Use the operator or data
(%s^4, %d^5) Invalid cannot be used in Mixed Logic. Mixed in a normal Logic
INTP-443 PAUSE item for Mixed Logic Logic statements are those that have instruction.
There is an operator or data that Remove the operator or
(%s^4, %d^5) Invalid cannot be used in Fast mode data, or execute this
INTP-444 PAUSE item for Fast mode Background Logic. Fast Mode program in Normal mode
(%s^4, %d^5) There is an indirection of index, (ex. Remove the indirection,
Indirection in Fast DI[R[1]]), in Fast mode Background or execute this program in
INTP-445 WARN mode Logic. Fast mode Background Logic Normal mode Background
(%s^4, %d^5) Too many The parentheses nesting is too deep. Divide the expression into
INTP-446 PAUSE parentheses
(%s^4, %d^5) The maximum
combination number of nestingisis 11.
of parentheses two
Checklines.
the parentheses
INTP-447 PAUSE Parentheses mismatch wrong. pairs.
Fast mode programs Total size of Fast mode programs is Set execution mode of
INTP-448 WARN too big
(%s^4, %d^5) Marker greater
There isthan 4000 steps.
a recursive 4000of
reference steps
a is some
CheckBackground
recursive reference
INTP-449 PAUSE recursion Marker. of Marker.
PAUSE. (%s^4, %d^5) Cannot Master/Slave/SlaveAlone program Master/Slave/SlaveAlone
INTP-450 L call KAREL program cannot call KAREL program program cannot call
Master/Slave/SlaveAlone
program cannot call
PAUSE. (%s^4, %d^5) Cannot Normal program which
INTP-451 L call Motion program has motion group.
Master/Slave/SlaveAlone
PAUSE. (%s^4, %d^5) Robot link program can call different
INTP-452 L type mismatch type of program.
PAUSE. (%s^4, %d^5) Not in Slave program cannot be
INTP-453 L remote execute without remote
ABORT. (%s^4, %d^5) Illegal Program type is different between
INTP-454 L return occurred caller program and called program.
PAUSE. (%s^4, %d^5) Group Master program does not have the Master program must
INTP-455 L mismatch(Link pattern) same motion group which is specified have the same motion
PAUSE. (%s^4, %d^5) Group Slave program does not have the same Slave program must have
INTP-456 L mismatch(Slave group) motion group which is specified by the the same motion group
Current tool frame number of master Current tool frame
PAUSE. (%s^4, %d^5) Master robot is different from the master tool number of master robot
INTP-457 L tool number mismatch No of robot link data of the slave and the master tool No of
PAUSE. (%s^4, %d^5) Robot is Since robot is still moving, it is After robot stops
INTP-458 L still moving impossible to synchronize. completely, countinue the
PAUSE. (%s^4, %d^5) Slave The motion statement of slave program Change the motion
INTP-459 L cannot JOINT motion is JOINT motion. statement of slave
PAUSE. (%s^4, %d^5) Cannot The position data of slave program is Change the position data
INTP-460 L use JOINT pos for Slave JOINT type. of slave program to
PAUSE. (%s^4, %d^5) Master TP Slave program is paused,
INTP-461 L
ABORT. is enabled
(%s^4, %d^5) Cannot Master program is executed by TP. when master program is
INTP-462 L start Robot Link
PAUSE. (%s^4, %d^5) Motion The motion group of specified program Change the robot to
INTP-463 L group is Master becomes to be master. normal from master.
PAUSE. (%s^4, %d^5) Motion The motion group of specified program Change the robot to
INTP-464 LABORT. group
(%s^4,is%d^5)
Slave Tracking becomes to be slave. normal from slave. Then,
INTP-465 L
PAUSE. error %d^5) Robot link
(%s^4, Tracking
Robot linkofcalibration
slave program is failed.
has not been
INTP-466 LPAUSE. not calibrated
(%s^4, %d^5) Cannot done yet.
The slave program cannot use Calibrate
Remove the theIncremental
robot link.
INTP-467 LPAUSE. use INC%d^5)
(%s^4, for Slave
Cannot Incremental
The instruction.
slave program cannot use Offset instraction.
Remove the Offset
INTP-468 LPAUSE. use OFFSET
(%s^4, %d^5) forBWD
Slaveis instruction. instraction.
Change the Slave robot to
INTP-469 LPAUSE. failed for Master
(%s^4, %d^5) Not Synchronize
BWD of Slaveofprogram
Master is falid
not for BWD. be
BWD synchronize
of Slave programwaiting is
INTP-470 L support BWD for Slave supported. not supported.
When robot is
Master(Manual), you
PAUSE. (%s^4, %d^5) Robot is Current status of the robot is cannot use external
INTP-471 L Master(Manual) Master(Manual). program execution. To
When robot is
Slave(Manual), you
PAUSE.(%s^4, %d^5) Robot is Current status of the robot is cannot execute other
INTP-472 G Slave(Manual) Slave(Manual). Slave program. To execute
PAUSE.(%s^4, %d^5) Synchro The synchro ID of the specified Synchro ID 0 is not
INTP-473 L ID is ZERO program is zero. available number. Please
PAUSE.(%s^4, %d^5) Synchro The program whose synchro ID is Please change the synchro
INTP-474 L
PAUSE.ID mismatch
(%s^4, %d^5) Cannot different
Slave from current
program synchro
cannot use singleIDstep
is ID to fitrelease
Please the current
single step
INTP-475 LABORT.
single step
(%s^4, %d^5) BWD is execution. key.
INTP-476 LABORT.
failed %d^5) Cannot
(%s^4, BWD is
Slave failed. cannot be executed
program BWD is
Slave failed. must be
program
INTP-477 L run Slave
This groupdirectly
can not be directly.
This motion group is not specified as called
Use by normal
another group program.
as
INTP-478 WARNMASTER master in SETUP. master or change SETUP.
PAUSE.
Bad Hostname or HOSTNAME, IP Address or group Confirm RobotLink and
INTP-479 G Address(MASTER) number about MASTER is not correct. HOST Comm TCP/IP
PAUSE.
Bad Hostname or HOSTNAME, IP Address or group Confirm RobotLink and
INTP-480 G Address(SLAVE)
PAUSE. number about SLAVE
Synchronization ID in is not correct.
program is HOST Comm
Modify TCP/IP
Synchronization ID
INTP-481 G
PAUSE. Synchronization
Bad Link Pattern ID invalid.
Link Pattern Number in program is at Program
Modify LinkList Screen.
Pattern
INTP-482 G Number
PAUSE. invalid. NumberMaster
Modify at Program
NumberList at
INTP-483 G
PAUSE. Masternumber
Bad Group Number Master Number
Specified in program
group number is invalid.
about MASTER Programgroup
Confirm List Screen.
number
INTP-484 G (MASTER)
PAUSE.
Bad Group number is invalid.
Specified group number about SLAVE is setup about MASTER.
Confirm group number
INTP-485 G (SLAVE)
PAUSE. invalid. setup about SLAVE.
INTP-486 G SLAVE
PAUSE.
No is not
Valid calibrated
SLAVE in Link Specified
No SLAVEisisspecified
valid SLAVE not calibrated.
in Link CalibrateLink
Confirm SLAVE robot.
Pattern at
INTP-487 G Pattern
PAUSE.
RLINK communication Pattern data.
At comm-buffer init, comm-processor is RobotLink
Increase SETUP screen.
INTP-488 G timeout
PAUSE.
Bad Hostname or too busy. or IP Address, Group
Hostname $RK_SYSCFG.$RMGR_PHT
Check HOST Comm TCP/IP
INTP-489 G Address, Group
PAUSE. number setup is invalid. and RobotLink
Check another SETUP.
robot and
INTP-490 G Timeout for link start Timeout for Robot Link start robot link program
PAUSE.
Linked robot or comm Check another robot is
INTP-491 G stoppedprogram
PAUSE.
Master Robot link communication stopped paused or communication
INTP-492 G stopped
PAUSE. Detect Master HELD input signal Check master robot status
INTP-493 G Slave program stopped Detect slave HELD input signal Check slave robot status
Proc_sync Sched Schedule number for PROC_SYNC is not Use SYNC_SCHED
INTP-494 PAUSE number not set initialized instruction prior to using
NO Proc_END after PROC_END statement is not found after Use PROC_END
INTP-495 PAUSE PROC_STRT PROC_START instruction after a
User AMR is being
INTP-500 WARN processed
User AMR is not
INTP-501 WARN processed
INTP-502 WARN Unknown primary tag
INTP-503 WARN Onlymore
No flag,data
not error
in the
INTP-504 WARN line
INTP-505 WARN Invalid currentPSpointer
(%s^4, %d^5) is not PS statement is not available for this
INTP-530 available
(%s^4, %d^5) PS motion system. of PS motions has reached the
Number Please check robot type.
INTP-531 limit limit. Please modify program.
(%s^4, %d^5) PS item Number of PS items per one motion
INTP-532 limit
PS(%s^4,%d^5- has reached the limit. modify program.
Please confirm PS logic
INTP-533 %d^9)Invalid PS
PS(%s^4,%d^5- logic is
PS time statement is notfor
not available valid.
this motion statement.
Set time value to 0 or
INTP-534 %d^9)time is not
PS(%s,%d-%d)Undone type. change motion PS
Please confirm type or
trigger
INTP-535 PS exists Untriggered PS logic exists. condition.
Please record the detail of
INTP-536 PS error
Failed(0x%X)
to get cur PS system error. the lastconfirm
Please operation which
calibration
INTP-537 pos(G:%d) Failed to get the current TCP. and mastering.
PS(%s,%d-%d)Error PS PS item which caused the error still Do BWD motion to clear
INTP-538 exists
PS(%s,%d- exists
PS itemattriggered
paused status.
immediately after the remaining
Please check andPS items.
modify
INTP-539 %d,%dmm)Already in
PS(%s,%d- motion
PS item start.
triggered immediately after PS trigger
Please condition.
check and modify
INTP-540 %d,%dmm)Already
PS(%s,%d- in motion start. PS trigger
Please condition.
check and modify
INTP-541 %d,%dmm)Forced
PS(%s,%d- PS item was not triggred. PS trigger
Please condition.
check and modify
INTP-542 %d,%dmm)No trigger PS item was not triggred. PS trigger condition.
PS(%s,%d-%d)Cancel Paused PS item was canceled at resume If you want to continue
INTP-543 pending PS
PS(%s,%d-%d)Time by time
PS BWD,value
singleisstep or cursor
too large change.
against program
Please execution,
reduce time valueplease
INTP-544 value limit distance value. or enlarge distance value.
Cannot use motion Program that has motion group is used Clear motion group mask
INTP-559 group in action as action
The program
Distance Before for this line was of action
Do program
not change lineinfor
INTP-560 DB was deleted deleted. restart or do not enable
The Distance Before for this line was Do not change the line for
INTP-561 DB was deleted deleted. restart, or do not enable
No kinematics in DB Attempt to perform distance before Please use time before
INTP-562 group with non-kinematics robot instruction instead of
INTP-570 ABORT IBGN internal error Internal error. Please do COLD start.
IBGN file format After check and modify
INTP-571 PAUSE error(%d^9) File format for IBGN is not correct. the
Checkcontents
file andofthen
the file,
try
INTP-572 PAUSE IBGN file cannot open IBGN file cannot open. again.
IBGN rtcp and usual During IBGN recording, remote tcp Modify programand try
INTP-573 WARN tool mixed motion and usual motion cannot used again.
No motion statement No motion statement executed before Execute at least one
INTP-574 PAUSE exected
IBGN ITPbefore RECORD
time does not RECORD
ITP start[
time in ] instruction
ASCII file is not same as this motionwhether
Check statement before
ASCII file is
INTP-575 PAUSE match
IBGN TCP data does not system.
ITP time in ASCII file is not same as this correct.
Check whether ASCII file is
INTP-576 PAUSE match system. correct.
IBGN Program can not Program can not be restarted because Enable Constant Joint
INTP-577 PAUSE be restarted Constant Joint Path is disabled. Path function.
IBGN RECORD Program is paused. Recording is To start recording, start
INTP-578 WARN interrupted stopped. your program again from
IBGN RECORD doesn't RECORD start instruction doesn't work Disable single step. There
INTP-579 WARN work in single step in single step mode is no poin data in buffer.
INTP-580 IBGN Buffer
Cannotisexecute
empty There is no point
The program can data
not be in executed
buffer. using Check IBGN**.IBG file.
INTP-581 ABORT backwards
IBGN RECORD buffer is BWD.
Buffer for recording is full. Record Please shorten time to
INTP-582 WARN full stopped here. record
IBGN program Program call or return from program Teach RECORD start and
INTP-583 WARN call/return during occurred during recording. end in a program and
IBGN tool changed Don't change tool
INTP-584 WARN during RECORD Tool changed during recording. between IBGN RECORD
IBGN user frame Don't change user frame
INTP-585 WARN changed during User frame changed during recording. between IBGN RECORD
IBGN jmp label during Don't change user frame
INTP-586 WARN RECORD Jmp label occured during recording. between IBGN RECORD
If Joint, use %. If
linear/circle, use mm/sec,
cm/min or inch/min.
IBGN illegal speed Buffer for executing is full.
INTP-587 WARN unit(%s,%d) Illegal speed unit for IBGN record. Check the number of
INTP-588 IBGN Buffer is full Buffer for executing is full. point in IBGN file.
Check whether IBGN END
Teaching of IBGN instruction is not instruction is exist. Check
INTP-589 IBGN teach error correct. whether
Check IBGNfor
setting END
INTP-590 IBGN File transfer failed File transfer by FTP protocol failed. communication.
IBGN FWD execution When BWD execution is paused, FWD Afetr BWD execution is
INTP-591 PAUSE cannot be done execution cannot be done until BWD finished, perform FWD
Index of IBGN REC END[ ] is different
IBGN RECORD index from IBGN REC START[ ]. Record of the
INTP-592 PAUSE mismatch(%d, %d) 1st index was in progress when end Use proper index.
IBGN file cannot read because previous
INTP-593 PAUSE IBGN file
record file is being IBGN command does not finish.
cannot read Please
Wait fordoa COLD
while start.
and
INTP-594 PAUSE copied IBGN record file is being copied. resume program.
Someone is updating IBGN file. Now Wait for a while and try
INTP-595 WARN Updating IBGN exe file IBGN file cannot be saved. again.
Someone is saving IBGN file. Now IBGN Wait for a while and try
INTP-596 WARN Saving IBGN exe file file cannot be updated. again.
IBGN START[ ] instruction is using one Wait for a while and try
INTP-597 WARN IBGN exe file is in use of IBGN file. Now IBGN file cannot be again.
Please make sure record is
There is no successful record data of successful. Access record
INTP-598 WARN IBGN no record data specified index. file before another record
Another IBGN RECORD instruction is Execute an IBGN RECORD
INTP-599 PAUSE IBGN Now recording recording. END instruction, then
IBGN RECORD file index Record file of Specified index isn't Access record file before
INTP-600 WARN error available now. Robot doesn't have another recording starts.
IBGN more than 256 SENSPS file or IBGN file contains a line
INTP-601 PAUSE characters in a line that has more
A motion than
cannot be255
usedcharacters.
if Accupath is Check ascii file and fix it.
ARC:Accupath enabled
%d^5)ARC:path enabled
The path of A motion without cursor is Disablesingle
Enable Accupath
step to
INTP-603 change changed. resume.
(%s^4, This instruction is not allowed between
%d^5)ARC:Cannot use
%d^5)ARC:Offset A motion
Offset statements
is used with $SCR.$ofstincval in A Delete set
Please this instruction
increment in A motion
%d^5)ARC:No motion. $SCR.$ofstincval = 0
INTP-606 PAUSE motion
(%s^4, statement Motion statement
Syntax error is not
is found by Afound
motion Internal error
%d^5)ARC:Syntax
%d^5)ARC:Iterror
is processing Internal error
INTP-608 PAUSE not A
ARC:A needs 3 points The specified line is not A motion Internal error
INTP-609 (%d)
ARC:Motion type N/A N/A
INTP-610 changed
(%s^4, N/A N/A
INTP-611 PAUSE %d^5)ARC:Group
(%s^4, %d^5)ARC:PR[R[ The specified
position group
register of Aismotion
not processed
must not Internal error
INTP-612 PAUSE ]] in A motion be indirect. Delete indirection.
(%s^4, Destination position data conflict Internal error. It may be
INTP-613 PAUSE %d^5)ARC:Position
(%s^4, internally. caused by motion option.
INTP-614 PAUSE %d^5)ARC:Palletizing in Palletizing is not allowed for A motion Please delete palletizing
(%s^4, %d^5)ARC:Call The call nesting between A motion Please check recursive
INTP-615 PAUSE nesting is too deep statements is too deep. call.
(%s^4, %d^5)ARC:Sub Sub program called between A motion Don't call the program
program has motion
%d^5)ARC:JMP statement
There is JMPhasstatement
motion statement.
between A that hasdelete
Please motionJMP
INTP-617 PAUSE between A motion
(%s^4, %d^5)ARC:END motion statements.
There is END statement between A statement.
Please delete END
INTP-618 PAUSE between A motions motion statements. statement.
(%s^4, %d^5)ARC:PR is There is assignment statement to PR Please delete assignment
set between A motion
%d^5)ARC:LBL between
There is aALBL
motion statements.
statement between A statement to PR.
between A motion in
%d^5)ARC:INC motionisstatements.
There an INC instruction in A motion Delete the LBL statement.
INTP-621 PAUSE A motion
(%s^4, %d^5)ARC:SKIP statement.
There is SKIP instruction in A motion Delete the INC
SKIPinstruction.
INTP-622 PAUSE in A motion statement. instruction.
(%s^4, UFRAME data, UFRAME numer, UTOOL
%d^5)ARC:UFRAME/UT data, UTOOL number must not be Don't change UFRAME
INTP-623 PAUSE OOL between A motion changed between A motion and UTOOL.
(%s^4, There is an ABORT statement between Please delete ABORT
INTP-624 %d^5)ARC:ABORT A motion statements. statement.
(%s^4, There is OFFSET / TOOL OFFSET Please delete OFFSET /
%d^5)ARC:OFFSET cond condition
KAREL statement
program between
is called A motion
between A TOOL OFFSET condition
INTP-626 PAUSE %d^5)ARC:KAREL call motion statements. Please delete KAREL call.
(%s^4, Position data is changed in a sequence Please find the reason
INTP-627 PAUSE %d^5)ARC:Inconsistent of A motion statements. why the position data is
(%s^4, Line order of execution is changed in a Please find the reason
INTP-628 PAUSE %d^5)ARC:Inconsistent sequence of A motion statements. why the line order is
(%s^4, UFRAME/UTOOL is changed in a Please find the reason
INTP-629 PAUSE %d^5)ARC:UFRAME/UT sequence of A motion statements. why FRAME/UTOOL is
(%s^4, %d^5)ARC:Logic Specified line violate restriction of logic Please refer to cause
INTP-630 PAUSE error between A motion code.
(%s^4, %d^5)ARC:RTCP If A motion uses RTCP, related motion Cause code shows which
INTP-631 PAUSE mismatch
(%s^4, %d^5)Illegal lines must use RTCP,too. Vice versa line is inconsistent. Teach
time %d^5)Illegal time of TB.
Illegal value is specified as distance of time
Set proper distance 3.7.3
INTP-633 PAUSE distance DB. ISD Alarm Code
(%s^4, If a motion uses COORD, related The cause code shows
INTP-634 %d^5)ARC:COORD motion lines must use COORD,too, and which line is inconsistent.
Use another
Instruction number is
The specified RESUME/MAINT RESUME/MAINT
INTP-635 wrong instruction number cannot be used. instruction number. If the
There're multiple There are two RESUME/MAINT Only one RESUME/MAINT
INTP-636 RESUME/MAINT instructions in one teach pendant instruction can be used in
The Multi Robot Control (J605) option Multi Robot Control (J605)
(required for all Multi-Arm systems) is is necessary to use the
INTP-637 Please install J605 not installed. instruction. Make sure
This program can't The program where the Remove the
INTP-638 execute by RUN RESUME/MAINT instruction exists can RESUME/MAINT
Other program are Another program is using the Remove the
INTP-639 using RESUME/MAINT RESUME/MAINT instruction. RESUME/MAINT
(%s^4, MONITOR/MON. END cannot be used Delete
INTP-640 %d^5)MONITOR/MON. when J893 is installed. MONITOR/MON.END
(%s^4, DB can only be used if $DISTBF_VER is 2
INTP-641 %d^5)$DISTBF_VER when J893 is installed Set $DISTBF_VER to 2
(%s^4, TB/TA can only be used if $TIMEBF_VER
INTP-642 %d^5)$TIMEBF_VER is 2 when J893 is installed. Set $TIMEBF_VER to 2
(%s,%d)DB was The RESUME/MAINT instruction cannot Remove the
INTP-643 triggered by go-away. be used in RESUME/MAINT program. RESUME/MAINT
The specified RESUME/MAINT Use another
RESUME/MAINT cannot instruction number cannot be used. RESUME/MAINT
INTP-644 be used here The relation between RESUME/MAINT instruction number.
Instruction number is Because the PNSTROBE pulse signal is Do not input the
INTP-645 wrong input, resume program or fast fault PNSTROBE pulse signal
PNSTROBE signal is Because the maintenance DO is OFF, Confirm the setup of fast
INTP-646 input the fast fault recovery sequence cannot fault recovery.
The Error Recovery option (J664) is not The Error Recovery Option
INTP-647 Maintenance DO is OFF installed. (J664) is necessary to use
Reset the alarm. If the
The fast fault recovery sequence error still occurs,
INTP-648 Please
FFR install J664
sequence can't be cannot
The fastbe executed.
fault recovery sequence document
Reset the events
the alarm that
and try
INTP-649 executed cannot be executed. the operation again.
A power failure was detected before
Distance Before was triggered. The
DB was lost by power power failure occurred after the Run the program from
INTP-650 failure recovery. motion ended successfully. DB is not appropriate line again.
High level mode Total size of high level mode programs Please set execution
INTP-651 programs too big is greater than 370 step. 370 steps is mode of some
(%s^4, %d^5) Dry Run To do Dry Run, some programs that Please run programs
INTP-652 can't execute
J983: multi task
System variables have motion groups can not be alternately by single task.
INTP-653 not found
J983: DO for program System variables not found. None.
assign and specify DO
INTP-654 run is DO
J983: invalid
for program Specified DO is invalid appropriately
INTP-655 end is invalid
J983: DO for program Specified DO is invalid appropriately
INTP-656 abort issoftware
Option invalid not Specified DO is invalid appropriately
INTP-657 installed Option software not installed. Install J611 and J969.
INTP-658 Invalid
Axis notgroupexist value
or is robot Invalid group value. Input a correct value.
INTP-659 axis
Invalid torque limit Axis not exist or is robot axis. Input a correct value.
INTP-660 value
Intarnal error occurred Invalid torque limit value. Input a correct value.
INTP-661 (%s) Internal error occurred. Restart system.
Excessive torque limit Torque limit value exceeds maximum Set torque limit value less
INTP-662 value (%s) value. Torque limit value was modified than or equal to the
Org path resume not To do Dry Run of this type, Original Please set Original Path
INTP-664 available Path Resume must be enable. Resume enable.
(%s^4, %d^5) RUN stmt RUN statement in background progarm Please set motion group
failed in background is failed. Program with motion group 0. Please don't execute
INTP-665 program
(%s^4) TC_ONLINE cannot run by backgroud logic. Or, the same
Checkprogram
TC_ONLINEin the
INTP-666 result is FALSE Result of TC_ONLINE is FALSE. expression.
TC_ONLINE result is Program is cannot started by Check TC_ONLINE
INTP-667 FALSE TC_ONLINE, because the result of the expression.
Please read the error
INTP-668 %s
Need FOR for ENDFOR Please read the error message. message.
Teach FOR before the line
INTP-669 in lineENDFOR
Need %d for FOR ENDFOR is more than FOR. number
Teach displayed.
ENDFOR after the
INTP-670 in line %d FOR is more than ENDFOR. line number displayed.
FOR statements are continuously Delete FOR statements till
INTP-671 Too many FOR instructed more than 10. their continuous number
Only integer type can be
(%s^4, %d^5) Value Not integer type is used in used in FOR/ENDFOR
INTP-672 type isFOR/ENDFOR
IBGN not integer statement.occurred
FOR/ENDFOR statement statement.
During Especially
recording don't
INTP-673 during RECORD
(%s^4, %d^5) Invalid duringof
Value recording.
math function instruction is use FOR/ENDFOR
Please input a correct
INTP-674 Argument invalid value.
Jog override has been Try to jog robot under Prog override Jog override mode has
INTP-675 enabled mode that $mcr.$actoverride = 1. been already enabled.
Prog override has been Try to run a program under Jog Program override mode
INTP-676 enabled override mode that $mcr.$actoverride has been already enabled.
(%s^4, %d^5)IBGN Value of argument is invalid This value
INTP-677 invalidThere
IBGN indexis no isn't supported in IBGN REC instruction Fix value
Try again of argument
after you save
INTP-678 RECORD data You tried to trans without record data record data
(%s^4, %d^5) Program that started by background
Background program is logic is aborted. This program is started
INTP-679 aborted%d^5) LVC:
(%s^4, from statement
Wait first line byisnext execution.
executed in LVC None.use WAIT statement
Don't
INTP-681 WAIT
(%s^4,in%d^5)
block LVC: motion block.
JMPLBL is executed in LVC motion in LVCuse
Don't motion block.
JMPLBL
INTP-682 JMPLBL in block block. statement in LVC motion
(%s^4, %d^5) LVC: An LVC_START instruction is started Delete one of the
INTP-683 LVC_START in block while another LVC START instruction is LVC_START instructions.
LVC cannot be used LVC cannot be executed while the Use LVC after the iRvision
INTP-684 while Vision is running
(%s^4, iRvision application is running. application is done.
INTP-685 %d^5)TIMER[%d^9]
(%s^4, %d^5)This taskhas This timer already been started. Use
Stopother timerby
this timer index.
task
INTP-686 cannot stop This timer can not stopped by this task. that it was startted.
LVC: The NORMAL_MOTION_END is missing Add a
INTP-687 NORMAL_MOTION_EN
LVC: duplicated between the NORMAL_MOTION_START
A NORMAL_MOTION_START NORMAL_MOTION_END
Delete one of the
INTP-688 NORMAL_MOTION_STA instruction is duplicated. NORMAL_MOTION_START
Same robot already in The robot is already selected on The robot selected on
IRPK-001 conveyor. another conveyor station. another conveyor station
Interface is not Contact your FANUC
IRPK-002 supported. Internal Error. America Corporation
Contact your FANUC
IRPK-003 Empty object. Internal Error. America Corporation
Logout from the page of
Can't find selected iRPickTool and login again.
IRPK-005 object. Internal Error. If the problem persists,
IRPK-006 Empty
This name.
sensor task is not Name is empty. Inputthe
Start a valid name.
sensor task
IRPK-011 running.
Number of running This sensor task is not running. correctly.
Wait for completion of
IRPK-012 action isconveyor
Indexer over. The number of running action is over.
is not the action.
IRPK-013 set up. is already
Sensor Indexer conveyor is not set up. Set up indexer conveyor.
IRPK-014 running. Sensor is already running. Stop the sensor task.
An invalid or uninitialized scale factor Make sure that this value
IRPK-015 Invalid
The scale factor.
custodian was valuecustodian
The by conveyor
was station.
moved to another is properly set. NOTE: This
IRPK-016 moved to another
Conveyor station is not controller. None.
Please set up conveyor
IRPK-017 set up controller is off- Conveyor station is not set up.
Target station.
Please set up RIPE or turn
IRPK-018 line Target controller is off-line. on power.
Please increase max.
IRPK-019 There is no free sensor There is no free sensor. number of sensor or
IRPK-020 Sensor is not set up Sensor is not set up. Please set up sensor.
There is no conveyor There is no conveyor station next to Please change order of
IRPK-021 stationconveyor
Servo next to sensor
is not in sensor in tree. sensor set
Please so that sensor
up servo
IRPK-022 set internal
An up error has Servo conveyor is not set up. conveyor.
IRPK-023 occurred in iRPickTool. Internal error. Please contact FANUC.
There are already Please increase the
IRPK-024 maximum objects. There are already maximum objects. maximum number of
Logout from the page of
IRPK-025 Invalid object type. Internal error. iRPickTool and login again.
Can't delete the robot The robot object has children of Select another robot on
IRPK-026 which is selected on a operation objects. the conveyor station or
Failed to read the Contact your FANUC
IRPK-028 grandchild object.
The controller selected Internal error. selected on the robot
The controller America Corporation
Please select the correct
IRPK-029 on the robot object is object is invalid. controller on the robot
IRPK-030 Conveyor is not set up Conveyor is not set up. Please set up conveyor.
This controller doesn't Please set up sensor on
IRPK-031 have sensor This controller doesn't have sensor. this controller. This is only
Double SetTrigger from SetTrigger is executed twice in the Modify your teach
IRPK-032 the robot. programs. pendant programs not to
IRPK-033 SetTrigger
Invalid is station
fixed timeout. SetTrigger has timed out. Adjust specify
Please the waittime.
a valid fixed
IRPK-034 specified.
Invalid conveyor station Invalid fixed station is specified. station.
Please specify a valid
IRPK-035 specified. Invalid conveyor station is specified. conveyor
Please station.
specify a valid
IRPK-036 sensor specified.
Invalid conveyor Invalid sensor is specified. sensor.
IRPK-037 specified Invalid conveyor is specified. conveyor.
IRPK-038 Invalid tray specified Invalid tray is specified. Please specify a valid tray.
IRPK-039 Invalid robot specified Invalid robot is specified. robot.
IRPK-040 Invalid gripper specified Invalid gripper is specified. gripper.
IRPK-041 Invalid zone specified Invalid zone is specified. zone.
IRPK-042 Invalid recipe specified
track schedule Invalid recipe is specified. recipe.
IRPK-043 specified Invalid tracking schedule is specified. trackingspecify
Please schedule.
a valid
IRPK-044 Invalid indexer specified Invalid indexer is specified. indexer.
IRPK-045 Invalid group specified Invalid group is specified. group.
IRPK-046 Invalid
Part part
with specified
invalid model Invalid
Part part
with is specified.
invalid model ID is pushed Please
Add thespecify
modelaIDvalid
in the part.
IRPK-047 ID is pushed into queue into the queue. line configuration.
Part queue manager received unknown Contact your FANUC
IRPK-048 Unknown function code request. America Corporation
Invalid ACK status in Modify call to AckQueue
IRPK-049 AckQueue Invalid ACK status. in your program to pass a
AckQueue before AckQueue is called before a part is Modify your TP program
IRPK-050 GetQueue allocated in GetQueue to call AckQueue after a
No AckQueue after the AckQueue is not called after the last Modify your TP program
IRPK-051 last GetQueue GetQueue. to call AckQueue before
Conveyor station is GetQueue request is canceled because Don't call GetQueue until
IRPK-052 disabled
There is no part the conveyor
There is no partstation is disabled.
meeting the specified the conveyor
Please confirmstation
the is re-
IRPK-053 meeting the specified condition. specified condition.
Invalid model ID is Specify the model ID for
IRPK-054 specified.
Specified load balance Invalid model ID is specified. that youload
Specify want to change
balance in a
IRPK-055 is over range.
Conveyor load balance
station is too Specified conveyor is over
station range.
is too range.
Set up proper boundaries
IRPK-056 narrow parameter is narrow.
Specified of conveyor
Specify station.
supported
IRPK-057 not supported. Specified parameter is not supported. parameter.
Only the last zone of There is only one zone or the selected Please delete the last
IRPK-058 plural zones can be zone is not the last one. zone when there are
IRPK-059 HDI is not set up. HDI is not set up. Set up HDI.
No conveyor station in No conveyor station is added in the Add one or more
IRPK-060 the conveyor.
No more cell can be conveyor, so required operation cannot conveyor stations
Delete unused cellsininthe
the
IRPK-061 added
The to the
points aretray. No more
too close The pointscells
arecan
toobe added
close to thetotray.
together tray. points that are
Touch
IRPK-062 together to calculate calculate. further apart.
Encoder count of this The encoder count of this robot is Turn all robots off and
IRPK-063 robot is different from different from one of other robots. then on again.
GetQueue request is canceled because Don't call ClearQueue
IRPK-064 Queue ismy
Missing cleared.
conveyor ClearQueue is called. until AckQueue
Please train the is called.
conveyor
IRPK-065 station data is not
Conveyor Missing my conveyor station data train the conveyor
Please
IRPK-066 trained Conveyor data is not trained data
IRPK-067 No conveyor is selected No conveyor has been selected. Select a line.
SetTrigger before SetTrigger is called before a part is Modify your TP program
IRPK-068 GetQueue
The object name '%s^1' allocated in GetQueue to call SetTrigger after a
IRPK-069 is already in use. The specified name is already in use. Specify another name.
The name has been The specified object name is too long If truncating the object
IRPK-070 truncated to '%s^1'. and therefore truncated to a valid name poses a problem,
Conveyor speed cannot Speed of the specified conveyor cannot Please select the
IRPK-071 be
Theobtained.
action of sensor is be obtained. appropriate
Please selectencoder
the action
IRPK-072 for virtual robot. The action of sensor is for virtual robot. for real robot.
Don't power off
controllers during the
IRPK-073 Login timed out. Login of iRPickTool timed out. login. Please retry login
Failed to synchronize Failed to synchronize the data of Please do [F6: SYNC DATA]
IRPK-074 data.operation is not
This iRPickTool.
There is a controller that is running a TP again.the
Stop If the problem and
TP program
IRPK-075 allowed during program. retry the operation.
There are already all There are already all controllers which You need not to add any
IRPK-076 controllers which can can be added to treeview. more robots.
There is already the There is already the robot of the Please select the unique
IRPK-077 robot of the selected selected controller and group number. controller and group
Confirm that the all
There might be a controller that is contollers have finished
IRPK-078 Login Failed. powered on or off during logging in. the boot and retry login. If
There is a controller which has different Login to the controller
Need to synchronize setup data of iRPickTool from this that has the correct setup
IRPK-079 data. controller. data and click [F6: SYNC
Can't use Action of Sensor action cannot be used with load Please specify the load
IRPK-080 '%s^1' with load balance for each model ID. balance for all model IDs
UPDATE TREE is Please perform UPDATE
IRPK-081 necessary because data Data has been changed in runtime. TREE in workcell setup
Can't update Can't update configuration because Please synchronize the
IRPK-082 configuration because there is a data difference among data for all robots by
Another recipe process Another recipe process is already Please try again after the
IRPK-083 is running. running. running recipe process
Recipe operation time Recipe operation of iRPickTool timed Please retry after a while
IRPK-084 out. out. was an error running the named
There and the
See if the problem cause
associated
IRPK-202 Error running task %s task. code posted with this
An error was encountered while getting Check the associated
IRPK-203 Error getting %s the value of a KAREL or system variable. cause code. Make sure
An error was encountered while setting Check the associated
IRPK-204 Error setting %s the value of a KAREL or system variable. cause code. Make sure
An error occured while trying to Make sure that all the I/O
IRPK-205 Error simulating DI %s simulate
An optionanwhich
I/O Input port
was required was not inputs are specified
Install the cofigured
IRPK-206 Option required: %s installed. option.
A notification that data recording for
collecting profiler data with PickPRO -
IRPK-207 Profiler recording On duty, cycle time, power consumption or N/A
A notification that data recording for
collecting profiler data with PickPRO -
IRPK-208 Profiler recording Off duty, cycle time, power consumption or None.
Invalid data was received for Profiler Specify a valid value for
IRPK-209 Profiler Invalid data recording. duration, parts or cycles
Sending or receiving data between one Check the Ethernet cables
or more controllers failed because the and connections and
IRPK-210 A controller is off-line those controllers
An invalid Recipe were offlinewas
id or name ensure
Specify the controllers
a valid recipe idare
(1-
IRPK-211 Invalid Recipe encountered.
An invalid conveyor id or name was 99) or aavalid
Specify validname.
conveyor id
IRPK-212 Invalid Conveyor encountered.
An invalid tray id or name was (1-32) ora avalid
Specify validtray
name.
id (1-
IRPK-213 Invalid Tray encountered. 16) or a valid name.
Invalid Conveyor An invalid Conveyor station id or name Specify a valid conveyor
IRPK-214 Station wasinvalid
An encountered.
sensor id or name was station id
Specify (1-84)sensor
a valid or a valid
id (1-
IRPK-215 Invalid Sensor encountered.
An invalid Fixed station id or name was 32) or a valid name.
Specify a valid fixed
IRPK-216 Invalid Fixed Station encountered.
An invalid robot id or name was station id
Specify (1-84)robot
a valid or a id
valid
(1-
IRPK-217 Invalid Robot encountered.
An invalid gripper id or name was 32) or a valid name.
Specify a valid gripper id
IRPK-218 Invalid Gripper encountered.
An invalid Gripper zone id was (1-32) ora avalid
Specify validgripper
name.
IRPK-219 Invalid Gripper Zone encountered. zone id (1-20)
Invalid Gripper Zn An invalid Activation I/O for a gripper Specify a valid and
IRPK-220 Activation I/O zone was encountered. configured I/O port for
Invalid Gripper Zn An invalid Part presence I/O for a Specify a valid and
IRPK-221 PartPresence I/O gripper zone
An invalid was encountered.
motion group number was configured I/O motion
Specify a valid port for
IRPK-222 Invalid Motion Group encountered. group (1-8)
Gripper zone utool is This is only a warning. It is
IRPK-223 NILPOS The UTOOL for a gripper zone is NILPOS not typical that the
Specify a valid tracking
IRPK-224 Invalid Track Schedule The tracking schedule is invalid. schedule (1-8) for the
Specify a valid RIPE id
IRPK-225 Invalid RIPE Id The RIPE index for a robot is invalid. based on RIPE setup for
A valid operation is Pick=1
or Drop=2. Make sure that
the operation argument in
IRPK-226 Invalid Operation An invalid operation was encountered. your TP program calls is
A valid pick or drop
Invalid pick or drop An invalid pick or drop quantiy was quantity should match
IRPK-227 quantity encountered. with the number of zones
Specify a valid I/O type
IRPK-228 Invalid I/O type An invalid I/O type was encountered . such as DO or RDO based
Specify a valid I/O value
IRPK-229 Invalid value for I/O valuenumber
An invalid I/O port was encountered
was . such as aON=1,
Specify OFF=2
valid I/O portor
IRPK-230 Invalid I/O port
pulse number
time for encountered.
An invalid pulse time was specified for number
Specify a valid integer I/O
IRPK-231 I/O I/O pulse time (ms).
An invalid position register number was Specify a position register
IRPK-232 Invalid Positon Register encountered. value that is available in
Invalid Numeric An invalid numeric register number was Specify a numeric register
IRPK-233 Register encountered. value that is available in
An invalid vision register number was Specify a vision register
IRPK-234 Invalid Vision Register encountered. value that is available in
An invalid string register number was Specify a string register
IRPK-235 Invalid String Register encountered. value that is available in
Invalid Name for An invalid name was encountered for Specify a valid name in
IRPK-236 iRPickTool Object an iRPick object such as conveyor, the User interface for the
This check is performed
Remote I/O check A validation of I/O port that exists in over RIPE. Check if all
IRPK-237 timeout out another controller failed (timed out) controllers are on-line or
Argument data type not The parameter passed to TP program Specify a valid integer
IRPK-238 INTEGER was expected to be an integer but is value for the appropriate
Argument data type not The parameter passed to TP program Specify a valid REAL value
IRPK-239 REAL
Invalid Gripper zone was expected to be a REAL but is not. for the appropriate
Ensure the zone utool is
IRPK-240 utool The UTOOL for a gripper zone is invalid initialized and is correct.
Ensure a Valid Uframe
The Uframe number for a Fixed Station number is specified in the
IRPK-241 Invalid Uframe number is invalid. Fixed Station menu and
You should not generally
An uninit value was encountered while see this error. Try to trace
IRPK-242 Value is uninitialized executing a routine or a program. the execution history of
You should not generally
see this error. iRPick
A reallocation or resizing of a KAREL or attempts to keep memory
IRPK-243 Error resizing var: %s system variable failed. size optimal using only as
Specify a valid I/O
IRPK-244 Invalid
Enc encoder
Sync number
Fail.Stop Cnv An invalid encoder id was encountered. encoder number in the
IRPK-245 Repower There is problem to sync this encoder Manual sync this encoder
CV %d encoder sync This is just a message to
IRPK-246 master
CV %d encoder sync This conveyor
There encoder
is problem is this
to sync synced
enthernet indictate encoder has
IRPK-247 failed Encoder Manual
System wassyncnot
thissetup
Encoder
IRPK-248 No iRPickTool variables QMGR global variable does not exist correctly.
Reload system and re-
IRPK-249 No iRPickTool sysvars Can not find reference system variable perform setup
Check the data type in the
position and make sure it
Error getting Pos Reg An error occurred while getting data is cartesian type. Check if
IRPK-250 %s from the indicated position register. all controllers are on-line
From related error
messages, check the
An error occurred while setting data to source of the position
IRPK-251 Error setting Pos Reg %s the indicated position register. data. Check if all
From related error
messages, check the
Error getting CONFIG An error occurred while getting source of the position
IRPK-252 data CONFIG. data. Check if all
A routine was called with an invalid Check that all setup was
Invalid iRPickTool iRPickTool object type such as CStn, done correctly. Each robot
IRPK-253 Object type FStn, conveyor, etc. must have a pick and drop
Specify a valid part id for
An invalid part id or name was the Conveyor or Fixed
IRPK-254 Invalid Part encountered. Station where the part is
Part presence check failed for gripper Check why the part is not
zone. The part was either not detected getting picked or placed
PP Check failed for zone during pick or was detected after a during pick and place
IRPK-255 %s place operation. operations. Also check
Insufficient gripper There are not enough gripper zones to Add zones to the gripper
IRPK-256 zones to pick or drop pick or place the specified quantity of in the Gripper menu or
IRPK-257 Creating recipe %s A new recipe is being created None.
IRPK-258 Created %s A new recipe was successfully created None.
IRPK-259 Saving recipe %s is being
The active recipe was saved
successfully N/A
IRPK-260 Recipe %s saved saved None.
IRPK-261 Recipe %s loaded A recipe was successfully loaded None.
IRPK-262 Recipe %s renamed A recipe was successfully renamed None.
IRPK-263 Deleting recipe %s A recipe is being deleted None.
IRPK-264 Recipe %s deleted A recipeare
Recipes wasbeing
successfully
exporteddeleted
to the None.
IRPK-265 Exporting recipes to %s default file device. None.
Recipe export to the default file device
IRPK-266 Recipes exported
Importing recipes to %s Recipes
from completedaresuccessfully.
being imported from the None.
IRPK-267 %s default file device. None.
Recipes imported from Recipe import from the default file
IRPK-268 %s device
An completed
attempt successfully.
to switch recipes is being None.
IRPK-269 Switching to recipe %s made
An attempt to restore the active recipe None.
IRPK-270 Restoring recipe %s is being made None.
No recipes exist to A recipe Export was attempted but First create at least one
IRPK-271 Export there are no saved or created recipes recipe.
No recipes exist to A recipe Import was attempted but Check that the
IRPK-272 Import there are no recipes on the default file IRPICKTOOL directory with
Recipe operation failed This was an unusual error.
IRPK-273 %s A recipe operation failed. Contact FANUC for this
Active recipe cannot be An attempt was made to delete the You are not allowed to
IRPK-274 deleted active recipe. delete the active recipe.
Invalid device for An attempt was made to import recipes The valid devices for
IRPK-275 Recipe Import or Export from or export recipes to an invalid file import and export are
PLC Recipe Change A notification that the controller
IRPK-276 started. received a DI signal to initiate a recipe None.
An attempt to switch recipes was made You must either Save the
Unsaved data changes when there were recent changes to recent changes to the
IRPK-277 exist. setup data that have not yet been current recipe or Restore
This error is posted with
The existing object sizes are inadequate other error messages that
Object expansion to initialize the recipe that you are indicate which objects
IRPK-278 required trying to load. require expansion. Check
The size of the robot object is Use the Object Config
IRPK-279 Expand robot size to %s inadequate to initialize the recipe that menu in the Workcell to
The size of the tray object is inadequate Use the Object Config
IRPK-280 Expand tray size to %s to initialize the recipe that you are menu in the Workcell to
Expand gripper size to The size of the gripper object is Use the Object Config
IRPK-281 %s inadequate to initialize the recipe that menu in the Workcell to
The size of the zone object is Use the Object Config
IRPK-282 Expand zone size to %s inadequate to initialize the recipe that menu in the Workcell to
Expand sensor size to The size of the sensor object is Use the Object Config
IRPK-283 %s inadequate to initialize the recipe that menu in the Workcell to
The size of the Conveyor Station object Use the Object Config
IRPK-284 Expand CStn size to %s is inadequate to initialize the recipe menu in the Workcell to
The size of the Fixed Station object is Use the Object Config
IRPK-285 Expand FStn size to %s inadequate to initialize the recipe that menu in the Workcell to
Expand Conveyor size The size of the conveyor object is Use the Object Config
IRPK-286 to %s inadequate to initialize the recipe that menu in the Workcell to
Cycle power to take You changed setup data that requires Cycle the power on the
IRPK-287 effect cycle power of the controller to take controller.
Check that the
A recipe Move was attempted but iRPICKTOOL directory with
No recipes exist to there are no recipes in the recipe the individual RECIPEx
IRPK-288 Move controller directories exist in the
Write down the exact
error number and
This error is displayed when the ISD message displayed. Write
system encounters a problem that it is down exactly what your
ISD-000 WARN %s unable to solve internally. robot was doing at the
This error is posted when the system Perform the following
detects excessive pressure in the operations: 1. Make sure
dispensing material. This condition is no clogs exist in the
High pressure (disp-%s) usually caused by one or more of the dispensing tubing. 2.
ISD-001 WARN (ISD%d) following: * The dispenser line (gun Make sure the dispensing
This error is posted when the system Check the following items:
detects low pressure in the dispensing * Make sure that the
material. This condition is usually dispensing line is ok. *
Low pressure (disp-%s) caused by one or more of the Make sure that the
ISD-002 WARN (ISD%d) following: * The dispenser line (gun dispensing flow rate is not
detects excessive pressure in the * Make sure that the
material supply line. This condition is pressure is appropriate at
High pressure (sup-%s) usually caused by one or more of the the supply pump. * Make
ISD-003 WARN (ISD%d) following: * The supply pressure was sure that the high
detects low pressure in the material * Make sure that the
supply. This condition is usually caused supply line is ok. * Make
Low pressure (sup-%s) by one or more of the following: * The sure that the low pressure
ISD-004 WARN (ISD%d) supply line (hose, and so forth) was limit value is appropriate.
This warning is posted when the meter Perform the following
has reached its stroke limit during operations: 1. Modify
dispensing. After this occurs, the your program and use the
system automatically reverses the provided macros to
ISD-005 WARN Meter empty (ISD%d) meter direction, and resumes reposition the meter
Motor velocity limit The motor velocity has reached its Lower the flow rate to
ISD-006 WARN (ISD%d) maximum limit. within the acceptable
Continuously press and
hold the SHIFT and RESET
keys on the teach pendant
Meter OverTravel A This error is posted when the meter has at the same time while
ISD-007 WARN (ISD%d) tripped the overtravel limit switch. you jog the meter away
Press and hold the SHIFT
key and then press the
RESET button on the
Meter OverTravel B The meter has tripped the overtravel teach pendant. While you
ISD-008 WARN (ISD%d) limit switch. are still pressing the SHIFT
The meter has reached its stroke limit 1. Make sure supply
Meter stroke limit during prepressuring. This typically pressure is not too high.
ISD-009 WARN (ISD%d) occurs when the meter has traveled in 2. Slightly increase the
Meter axis error The digital servo system for the proces
ISD-010 WARN (ISD%d) axis has detected an error.
If you want to use this I/O
port, set the port index
Incorrect I/O The index value or I/O port type is and I/O type to the
ISD-011 WARN assignment (ISD%d) incorrectly assigned. correct values. Verify that
Usually, this error occurs
when the servo power is
ISD servo not ready This error is posted when the ISD servo turned off because of a
ISD-012 WARN (ISD%d) is not ready. strapped OT sensor, the
This error is posted when the SS[] Insert the check repos
SS[] used while instruction is executed while the metermacro in the program so
ISD-013 WARN reposition (ISD%d) is doing the reposition operation. that the program waits for
Stroke limit while The meter has reached its stroke limit 1. Make sure supply
ISD-014 WARN depressure (ISD%d) while trying to decrease the pressure pressure is not too high.
1. Increase the
Max prepressure The meter has travelled its maximum $isd_config[eq].$maxprp_
ISD-015 WARN distance (ISD%d) distance allowed for prepressurization. strk value to allow for a
The analog input tick of pressure
Transducer analog transducer has exceeded the max value Check the wiring of the
ISD-016 WARN input error (ISD%d) of the specific I/O module. This error pressure transducers.
The material pressure did not build up 1. Check for material
Reload Tmout/Low within the specified time (in SETUP/ISD supply system to the
ISD-017 WARN Supp Prs (ISD%d) menu) after the meter has moved to meter. 2. Set a larger
This error is posted when the system Check the following: *
detects excessive pressure in the Make sure that there is no
second dispensing material. This clog in the dispensing
High pressure (disp-%s) condition is usually caused by one or tubing. * Make sure
ISD-018 WARN (ISD%d) more of the following: A dispenser line dispensing flow rate is not
This error is posted when the system * Make sure dispensing
detects inadequate pressure in the line is ok. * Make sure the
second dispensing material. This dispensing flow rate is not
Low pressure (disp-%s) condition is usually caused by one or too low. * Make sure the
ISD-019 WARN (ISD%d) more of the following: * The dispenser low pressure limit value is
This error is posted when the system * Make sure the pressure
detects excessive pressure in the is appropriate at the
second material supply. This condition supply pump. * Make sure
High pressure (sup-%s) is usually caused by one or more of the the high pressure limit
ISD-020 WARN (ISD%d) following: * The supply pressure was value is appropriate. *
This error is posted when the system * Make sure the supply
detects inadequate pressure in the line is ok. * Make sure the
second material supply. This condition low pressure limit value is
Low pressure (sup-%s) is usually caused by one or more of the appropriate. * Make sure
ISD-021 WARN (ISD%d) following: * The supply line (hose, etc.) the low pressure time out
This warning is posted when the * Make sure the material
inactive meter could not finish supply pressure is high
reloading before the active meter enough. * Make sure Pre-
Premature switching reaches the Pre-Near-Empty position. Near-Empty location is set
ISD-022 WARN req (ISD%d) This is where the sub-meter should properly. * Make sure PLC
This warning is posted when the * Make sure material
inactive meter could not finish supply pressure is high
reloading before the active meter enough. * Make sure the
Meter switching fault reaches the Near-Empty position. This Near-Empty location is set
ISD-023 WARN (ISD%d) is where the sub- meter should start properly. * Nake sure the
This warning is posted when both * Make sure the material
meters are within the Near-Empty area supply pressure is high
when the meters are switched. This enough. * Make sure the
Both meter empty condition is usually caused by one or Near-Empty location is set
ISD-024 WARN (ISD%d) more of the following: * The supply properly. * Make sure the
This warning is posted when the * Make sure the material
previous reload did not finish when the supply pressure is high
meter was switched. This condition is enough. * Make sure Near-
Reload sequence fault usually caused by one or more of the Empty location is set
ISD-025 WARN (ISD%d) following: * The supply pressure was properly. * Make sure PLC
Dual ISD number The number of Dual ISD dispenser does Display NumCFG menu
ISD-026 WARN mismatch NOT match the number specified under SEAL Config menu,
Use The number of the Dual ISD dispenser Display the NumCFG
ISD-027 WARN SealConfig/NumCFG to does NOT match the number specified menu under SEAL Config
This error is displayed when the system Check the following: 1.
detects an excessive pressure Make sure that no clogs
difference between the two dispensing exist in the dispensing
Disp pressure diff too materials. This condition is usually tubing. 2. Make sure that
ISD-028 WARN high (ISD%d) caused by one or more of the the dispensing flow rate is
This error is posted when the system Check the following: 1.
detects too low of a pressure difference Make sure dispensing line
between the two dispensing materials. is ok 2. Make sure that the
Disp pressure diff too This condition is usually caused by one dispensing flow rate is not
ISD-029 WARN low (ISD%d) or more of the following: 1. The set too low. 3. Make sure
This error is posted when the system Make sure there is no clog
detects an excessive pressure in the dispensing tubing.
difference between the two dispensing Make sure that the
materials. This condition is usually dispensing flow rate is not
caused by one or more of the too high. Make sure high
following: - The dispenser line (gun pressure limit value is
Disp pressure diff too nozzle, hose, etc.) is clogged. - The appropriate. Make sure
ISD-030 high warn(ISD%d) dispensing rate is too high. - The high the high pressure time out
This error is posted when the system Please make sure there is
detects excessive pressure in the no clog in the dispensing
dispensing material. This condition is tubing. Make sure
usually caused by one or more of the dispensing flow rate is not
following: - The dispenser line (gun too high. Make sure high
High pressure nozzle, hose, etc.) is clogged. - The pressure limit value is
ISD-031 warn(disp-%s) (ISD%d) dispensing rate is too high. - The high appropriate. Make sure
This error is posted when the system Make sure the dispensing
detects too low pressure in the line is ok. Make sure the
dispensing material. This condition is dispensing flow rate is not
usually caused by one or more of the too low. Make sure the
following: - The dispenser line (gun low pressure limit value is
Low pressure warn(disp- nozzle, hose, etc.) is removed. - The appropriate. Make sure
ISD-032 %s) (ISD%d) dispensing rate is too low - The low the low pressure time out
This error is posted when the system Check the following: -
detects excessive pressure in the Make sure there is no clog
second dispensing material. This in the dispensing tubing. -
condition is usually caused by one or Make sure dispensing flow
more of the following: - The dispenser rate is not too high. -
High pressure line (gun nozzle, hose, etc.) is clogged. - Make sure high pressure
ISD-033 warn(disp-%s) (ISD%d) The dispensing rate is too high. - The limit value is appropriate. -
detects too low pressure in the second Make sure the dispensing
dispensing material. This condition is line is ok. - Make sure
following: - The dispenser line (gun too low. - Make sure low
Low pressure warn(disp- nozzle, hose, etc.) is removed - The pressure limit value is
ISD-034 %s) (ISD%d) dispensing rate is too low. - The low appropriate. - Make sure
detects too low pressure in the second Make sure the dispensing
dispensing material. This condition is line is ok. - Make sure the
following: - The dispenser line (gun too low. - Make sure the
Can not goto dispense nozzle, hose, etc.) is removed. - The low pressure limit value is
ISD-035 mode (ISD%d) dispensing rate is too low. - The low appropriate. - Make sure
If the gap between the
The minimum recovery pressure was rods is not closed increase
Meter recovery time not reached within the specified time in the recovery time, or
ISD-040 WARN out (ISD%d) the ISD SETUP menu. increase the recovery
Enter gap recovery Dispense pressure is below the
ISD-041 (ISD%d) minimum recovery pressure. None.
Dispense pressure increased above the
Exit gap recovery minimum recovery pressure after
ISD-042 (ISD%d) dropping below the minimum value. None.
This fault is usually fixed
This error is caused when the Integral when you perform a COLD
Pneumatic System (IPS) encounters a start. If the error is not
problem that it is unable to solve cleared, contact your
ISD-050 WARN %s internally. supervisor or call the
The commanded velocity
is limited to
$IPS_CONFIG[n].$CMDSP
The commanded velocity for the D_MIN or
Velocity command indicated pneumatic servo axis is too $IPS_CONFIG[n].$CMDSP
ISD-051 WARN excessive (IPS%d) high. D_MAX, where n is the
A sudden change in load, inadequate Verify that adequate air
air supply, malfunctioning servo- valve supply is available. See if
or poor servo tuning caused an air pressure dips
Excessive positional excessive error in the pneumatic servo considerably during meter
ISD-052 WARN error (IPS%d) position. This warning is posted when operation: this indicates
A sudden change in load, inadequate Press RESET to continue
air supply, malfunctioning servo- valve the operation. Verify that
or poor servo tuning caused excessive adequate air supply is
Excessive error during error in the pneumatic servo position. available. See if the air
ISD-053 WARN stop (IPS%d) This alarm is posted when the pressure dips considerably
A sudden change in load or poor servo Press RESET to continue
tuning caused an excessive error in the the operation. Verify that
pneumatic servo position. This alarm is adequate air supply is
Excessive error during posted when the positional error (in available. See if the air
ISD-054 WARN move (IPS%d) mm.) of that axis exceeds pressure dips considerably
A digital output that is used to provide 1. Perform a Controlled
Servo Enab o/p not power to the servo valve for the start and display the IPS
ISD-055 STOP assigned (IPS%d) specified axis number has not been Config screen. 2. Set up
The analog output required to control 1. Perform a Controlled
Analog output not the servo valve for the specified axis start and display the IPS
ISD-056 STOP assigned (IPS%d) number has not been assigned. Config screen. 2. Assign
The digital input required to detect air 1. Perform a Controlled
Press. sw. inp not pressure loss to pneumatic servo start and display the IPS
ISD-057 WARN assigned (IPS%d) valve(s) has not been assigned. Config screen. 2. Assign
The pressure switch monitoring the air If the gauge indicates
supply to pneumatic servo valves is adequate pressure, verify
Low air supply pressure switched off because the air supply is that the Air Supply
ISD-058 WARN (IPS%d) too low. Pressure digital input is
The specified pneumatic servo is unable Verify that when RESET is
to reset because of an external pressed, the digital output
condition such as an Emergency Stop. configured as servo
Servo not ready: ext. e- This external condition is forcing the enable comes on briefly.
ISD-059 STOP stop(IPS%d) digital servo ready input to stay off. Determine and rectify the
Meter hyd. inp not Meter hydraulic running input signal is Assign Meter hydraulic
ISD-060 assigned (IPS%d) not assigned. running input signal to a
Meter hydraulic not Meter hydraulic running input signal is Make sure meter
ISD-061 running (IPS%d) OFF. hydraulics are turned ON
Input pwr. inp not Input power input signal is not Assign the Input power
ISD-062 assigned (IPS%d) assigned. Checked only on Power up. input signal to a valid
Input power is off Input power signal is OFF. Checked only Make sure that the input
ISD-063 (IPS%d) on power up. power to the hydraulics is
Ctrl. pwr. inp not Control power output signal is not Assign the control power
ISD-064 assigned
Gun hyd. (IPS%d)
input not assigned.
Gun Checked
hydraulics only on
running Power
input signalup.is
outputgun
Assign signal to a valid
hydraulics
ISD-065 assigned (IPS%d) not assigned. running signal to a valid
Mtr. can't run w/o gun Meter hydraulics can not run if gun Start the gun hydraulics
ISD-066 hyd. hydraulic
Gun (IPS%d) low hydraulics
Gun are not
hydraulics notrunning.
low input signal isfirst and
Make surethen
gunstart meter
hydraulics
ISD-067 pressure (IPS%d)
Gun hydraulic high OFF. pressure is normal.
Make sure gun hydraulics
ISD-068 pressure
Gun (IPS%d)
hydraulic over not high signal
Gun hydraulics overload input is OFF.is
pressure is normal.
signal
ISD-069 heatedhydraulic
Meter (IPS%d) over ON.
Meter hydraulics overload input signal gun hydraulics
Check meter hydraulicsunit.
ISD-070 heated (IPS%d)
Local dispenser stop is ON. unit.
Check dispenser stop
ISD-071 (IPS%d) dispenser stop System
System Local dispense
dispensestop input
stop inputsignal is ON.
signal buttonsystem
is
Check on the dispense
dispenser's
ISD-072 (IPS%d)
Fire dispenser stop OFF. stop buttons
Check / logic. stop
fire dispenser
ISD-073 (IPS%d)
Spare dispenser stop Fire
Sparedispenser
dispenserstop input
stop inputsignal is is
signal OFF.
logic.
Check spare dispenser
ISD-074 (IPS%d) OFF. stop logic.
The ISO/POLY flow rate
has exceeded the
“ISO/POLY Max Warn
Flow” level for a period of
%s high flow warn The software has detected a high flow time greater than the
ISD-080 (ISD%d) level for the ISO/POLY material. “Flow Lo/Hi Time Out”
The software has detected an has exceeded the
excessively high flow level for the “ISO/POLY Max Fault
ISO/POLY material. This case is more Flow” level for a period of
severe than ISD-080, and may result in time greater than the
ISD-081 %s high flow (ISD%d) serious material application defects. “Flow Lo/Hi Time Out”
The ISO/POLY flow rate is
less than the “ISO/POLY
Min Warn Flow” level for
a period of time greater
%s low flow warn The software has detected a low flow than the “Flow Lo/Hi Time
ISD-082 (ISD%d) level for the ISO/POLY material. Out” duration. Verify that
The software has detected an was less than the
excessively low flow level for the “ISO/POLY Min Fault
ISO/POLY material. This case is more Flow” level for a period of
severe than ISD-082, and may result in time greater than the
ISD-083 %s low flow (ISD%d) serious material application defects. “Flow Lo/Hi Time Out”
The deviation of the
ISO/POLY ratio is greater
than the “ISO/POLY Max
Warn Ratio” level for a
period of time greater
%s ratio high warn The software has detected a high ratio than the “ISO/POLY Hi
ISD-084 (ISD%d) for the ISO/POLY mixture. Ratio Wrn T/O” duration.
The software has detected an than the “ISO/POLY Max
excessively high ratio for the ISO/POLY Fault Ratio” level for a
mixture. This is more severe than ISD- period of time greater
084, and may result in serious material than the “ISO/POLY Hi
ISD-085 %s ratio high (ISD%d) application defects. Ratio Flt T/O” duration.
than the “ISO/POLY Min
Warn Ratio” level for a
period of time greater
%s ratio low warn The software has detected a low ratio than the “ISO/POLY Lo
ISD-086 (ISD%d) for the ISO/POLY mixture. Ratio Wrn T/O” duration.
The software has detected an than the “ISO/POLY Min
excessively low ratio for the ISO/POLY Fault Ratio” level for a
mixture. This is more severe than ISD- period of time greater
086, and may result in serious material than the “ISO/POLY Lo
ISD-087 %s ratio low (ISD%d) application defects. Ratio Flt T/O” duration.
The instantaneous material flow ratio Verify that the limit and
%s ratio inst high exceeded the amount set in the timeout in the setup
ISD-088 (ISD%d) dispenser setup menu. menu are reasonable or
The instantaneous material flow ratio Verify that the limit and
%s ratio inst low was less than the amount set in the timeout in the setup
ISD-089 (ISD%d) dispenser setup menu. menu are reasonable or
The material pressure differential (ISO Verify that the limit and
Pressure diff too high minus POLY) exceeded the Max. timeout in the setup
ISD-090 (ISD%d) differential fault limit set in the menu are reasonable or
Pressure diff too high minus POLY) exceeded the Max. timeout in the setup
ISD-091 warn (ISD%d) differential warn limit set in the menu are reasonable or
Pressure diff too low minus POLY) was less than the Min. timeout in the setup
ISD-092 warn (ISD%d) differential warn limit set in the menu are reasonable or
Pressure diff too low minus POLY) was less than the Min. timeout in the setup
ISD-093 (ISD%d) differential fault limit set in the menu are reasonable or
The iso pressure variation detected Verify that the related
when transitioning from RECIRC to limit and capture delay
Iso prs. R->D var high DISPENSE mode exceeded the Iso max. time in in the setup menu
ISD-094 (ISD%d) variation flt limit set in the dispenser are reasonable or check
Iso prs. R->D var high DISPENSE mode exceeded the Iso max. time in in the setup menu
ISD-095 warn (ISD%d) variation warn limit set in the dispenser are reasonable or check
Iso prs. R->D var low DISPENSE mode was less than the Iso time in in the setup menu
ISD-096 warn (ISD%d) min. variation warn limit set in the are reasonable or check
Iso prs. R->D var low DISPENSE mode was less than the Iso time in in the setup menu
ISD-097 (ISD%d) min. variation flt limit set in the are reasonable or check
The poly pressure variation detected Verify that the related
Poly prs. R->D var high DISPENSE mode exceeded the Poly time in in the setup menu
ISD-098 (ISD%d) max. variation flt limit set in the are reasonable or check
Poly prs. R->D var high DISPENSE mode exceeded the Poly time in in the setup menu
ISD-099 warn (ISD%d) max. variation warn limit set in the are reasonable or check
Poly prs. R->D var low DISPENSE mode was less than the Poly time in in the setup menu
ISD-100 warn (ISD%d) min. variation warn limit set in the are reasonable or check
Poly prs. R->D var low DISPENSE mode was less than the Poly time in in the setup menu
ISD-101 (ISD%d) min. variation flt limit set in the are reasonable or check
The iso pressure difference between SS Verify that the related
Iso prs. unstable high and SE has exceeded the Iso max. limit and capture delay
ISD-102 (ISD%d) stability flt: limit set in the dispenser time in in the setup menu
Iso prs. unstable high and SE has exceeded the Iso max. limit and capture delay
ISD-103 warn (ISD%d) stability warn: limit set in the dispenser time in in the setup menu
Iso prs. unstable low and SE is less than the Iso min. stability limit and capture delay
ISD-104 warn (ISD%d) warn: limit set in the dispenser setup time in in the setup menu
Iso prs. unstable low and SE is less than the Iso min. stability limit and capture delay
ISD-105 (ISD%d) flt: limit set in the dispenser setup time in in the setup menu
The poly pressure difference between Verify that the related
Poly prs. unstable high SS and SE has exceeded the Poly max. limit and capture delay
Poly prs. unstable high SS and SE has exceeded the Poly max. limit and capture delay
Poly prs. unstable low SS and SE is less than the Poly min. limit and capture delay
Poly prs. unstable low SS and SE is less than the Poly min. limit and capture delay
F-P stability mon and Use F-P control
F-P ctrl and mon not are mutually exclusive in the sealing
ISD-110 allowed (ISD%d) schedule data menu. They cannot both Disable one or both items.
Ensure that the system is
otherwise operating
normally. Also check the
material characteristics
for undesired changes in
F-P shift factor has been adjusted to temperature and
F-P shift factor at max the maximum value as set in the ISD viscosity. ISD setup menu
ISD-111 (ISD%d) setup menu. Shift factor max may be
otherwise operating
F-P shift factor at min the minimum value as set in the ISD viscosity. ISD setup menu
ISD-112 (ISD%d) setup menu. Shift
Ensurefactor
that min may be is
the system
otherwise operating
temperature and
viscosity. This error may
also be part of normal
operation if the system
has been idle for a while.
F-P shift factor has been adjusted by If so then this error will
F-P shift factor max the maximum amount as set in the ISD most likely not continue
ISD-113 change (ISD%d) setup menu for this check. to be posted on every
otherwise operating
F-P shift factor at max the maximum value as set in the ISD viscosity. ISD setup menu
ISD-114 (ISD%s) setup menu. Shift factor max may be
otherwise operating
F-P shift factor at min the minimum value as set in the ISD viscosity. ISD setup menu
ISD-115 (ISD%s) setup menu. Shift factor min may be
otherwise operating
temperature and
viscosity. This error may
also be part of normal
operation if the system
has been idle for a while.
F-P shift factor has been adjusted by If so then this error will
F-P shift factor max the maximum amount as set in the ISD most likely not continue
ISD-116 change (ISD%s) setup menu for this check. to be posted on every
Data point #1 for the F-P calibration has Enter a flow rate for data
F-P cal pt1 flow <= 0.0 a flow rate selected that is <= 0.0 point #1 that is greater
ISD-117 (ISD%d) percent. than 0.0 percent and re-
F-P cal pt1 cc/sec <= 0.0 a flow rate selected that when point #1 that is slightly
ISD-118 (ISD%d) converted to cc/sec is <= 0.0 percent. larger and greater than
F-P cal pt2 flow <= 0.0 a flow rate selected that is <= 0.0 point #2 that is greater
ISD-119 (ISD%d) percent. than 0.0 percent and re-
F-P cal pt2 cc/sec <= 0.0 a flow rate selected that when point #2 that is slightly
ISD-120 (ISD%d) converted to cc/sec is <= 0.0 percent. larger and greater than
Enter flow rates for data
F-P cal flow not Data points for the F-P calibration have points that are all
ISD-121 increasing (ISD%d) flow values that are not all increasing. increasing and re-record
Data points for the F-P calibration have Enter flow rates for data
F-P cal cc/sec not flow values (after being converted to points that are all
ISD-122 increasing (ISD%d) cc/sec) that are not all increasing. increasing and re-record
Enter flow rates for data
Data points for the F-P calibration have points that are all
F-P cal pressr not pressure values that are not all increasing and re-record
ISD-123 increasing (ISD%d) increasing. the pressure values for
Data points in the F-P curve that are Enter pressure values of (-
F-P cal press ele not = - not used should have pressure values )1.0 for data points that
ISD-124 1.0 (ISD%d) set to (-)1.0 One or more data points are not being used. Note
Data points in the F-P curve that are Enter flow rate values of (-
not used should have flow rate values )1.0% for data points that
F-P cal cc/sec ele not = - set to (-)1.0% One or more data points are not being used. Note
ISD-125 1.0 (ISD%d) were found not to be set this way that good calibration data
Write down the exact
error number and
message shown. Write
down exactly what your
robot was doing at the
time of the failure. Make
sure you include: Program
This error is caused when ISD system name, line number,
encounters a problem that is unable to robot's location in the
ISD-126 %s solve internally. work cell, any cell I/O or
Joint speed limit (G:%d Joint can not rotate as fast as the input Even though this is just a
ISDT-001 WARN A:%d) speed required. warning, reference
Motor speed limit Motor can not rotate as fast as the Even though this is just a
ISDT-002 WARN
PAUSE. (G:%d A:%d) input speed required. warning, reference
ISDT-003 G
PAUSE. No global
Unable to variables
Allocate ISDT global
Failed variables
to allocate are not
memory forloaded.
ISDT Re-install
Check ISDT softparts.
amount of memory
ISDT-004 G
PAUSE. Memory system variables. being used by system.
Check if isaxcold() is called
ISDT-005 G
PAUSE. No AMR pointer ISDT recieves
Servo NULL ISDT
error occurs, AMR failed
from AX.
to create duringifcold
Check start. is called
isaxcold()
ISDT-006 G Failed to create AMR AMR. during cold start.
PAUSE. Servo not READY (G:%d Attempted to start process axes when
ISDT-007 G
PAUSE. A:%d) speed cmnd
Uninit servo is not
Process axesready.
speed command is not Reset process
Check process axes
axes speed
ISDT-008 G (G:%d A:%d) initialized. commands
PAUSE. Mastering Lost (G:%d Severe servo errors. It requires Set
ISDT-009 G A:%d) remastering. ISDT ignores all speed $IS_DMR.$ignore_motn =
Invalid Grp In for Ax%d Group Input specified for this axis is Specify a proper group
ISDT-010 Speed invalid input number in
Invalid Grp Out for Group Output specified for this axis is Specify a proper group
ISDT-011 Ax%d Speed invalid output number in
Invalid Axis %d in L:%d Axis number specified in TP Instruction Change the indicated axis
ISDT-012 Instr SET ISDT SPEED is not a valid ISDT axis number in the instruction
Duplicate Ax:%d in L:%d Axis number specified in TP instruction Change one of the
ISDT-013 Instr SET ISDT SPEED was used more than instances of this axis to be
Torque Limit feature is enabled on 1. Check mechanical
indicated axis and the motor current loading of axis 2. Increase
ISDT-014 Torque Limit on Ax:%d has exceeded this level for the specified current
Refer tolimit in setup
co-occurring
ISDT-015 %s fault (A:%d) Something is wrong with process axis. servo alarm's remedy.
Invalid Start Motor DI Digital Input specified for this axis is Specify a proper digital
ISDT-016 Ax%d invalid input number in
Invalid Start Usage DI Digital Input specified for this axis is Specify a proper digital
Digital Input specified for this axis is Specify a proper digital
ISDT-018 Invalid Usage GO Ax%d invalid input number in
Invalid Servo Ready DO Digital Input specified for this axis is Specify a proper digital
Invalid Motor Active DO Digital Input specified for this axis is Specify a proper digital
Invalid Speed Control Digital Input specified for this axis is Specify a proper digital
ISDT-021 DO Ax%d invalid input number in
Invalid Trq Grp Out for Digital Input specified for this axis is Specify a proper digital
Invalid Trq Ctrl DO for Digital Input specified for this axis is Specify a proper digital
Invalid Inc Move DI Digital Input specified for this axis is Specify a proper digital
Invalid Pos Grp In for Digital Input specified for this axis is Specify a proper digital
Invalid Pos Grp Out for Digital Input specified for this axis is Specify a proper digital
Invalid Move Complete Digital Input specified for this axis is Specify a proper digital
ISDT-027 DO Ax%d invalid input number in
Invalid Pos Req DO Digital Input specified for this axis is Specify a proper digital
Invalid Jog Permissive Digital Input specified for this axis is Specify a proper digital
ISDT-029 DI Ax%d invalid input number in
Digital Input specified for this axis is Specify a proper digital
ISDT-030 Invalid Master DI Ax%d invalid input number in
Invalid Not Master DO Digital Input specified for this axis is Specify a proper digital
Invalid At Master DO Digital Input specified for this axis is Specify a proper digital
ISDT-032 Ax%d invalid
Digital Input specified for this axis is input number
Specify in digital
a proper
ISDT-033 Invalid Pos Req DI Ax%d invalid input number
JOG-000 WARN Unknown error (MJ00)
Use the MANUAL FCTNS
OT release menu in to find
out which axis is in an
overtravel condition.
JOG-001 WARN Overtravel Violation A robot overtravel has occurred Release overtravel by
Set the system variable
$MASTER_ENB to 1.
Select SYSTEM then
Master/Cal, to display the
JOG-002 WARN Robot not Calibrated Robot has not been calirated Master/Cal menu. Select a
Abort the program that
JOG-003 WARN No Motion Control Other
You program
cannot has motion
do more control
than one has motion
Only control
press one by
rotational
JOG-004 WARN Illegal linear jogging rotational
The systemjog
callattoa time
clear hold flag failed. jog key at a time.
JOG-005 WARN Can not clear hold flag error Perform a cycle start.
No extended axis exist in this group This is a notification. You
JOG-006 WARN Subgroup does not exist with which to jog. do not have to do
You must press the SHIFT
key when jogging the
JOG-007 WARN Press shift key to jog The SHIFT key is not pressed robot. Release the jog key
Hold the DEADMAN and
JOG-008 WARN Turn on TP to jog Teach pendant is not enable turn on the teach pendant
Press the DEADMAN
JOG-009 WARN Hold deadman to jog The DEADMAN switch is not pressed switch, then press the
The jog key was pressed before the Release the jog key.
JOG-010 WARN Jog pressed before shift shift key was pressed Then,hold the SHIFT key
Release the SHIFT key and
Utool changed while The selected tool frame changed while the JOG key. The new
JOG-011 WARN jogging jogging TOOL frame will take
Engage all the brakes by
pressing EMERGENCY
JOG-012 WARN manual brake enabled The manual brake enabled STOP button, then press
The robot already reach
the stroke limit and
Stroke limit (G:%d A:%x Robot axis reaches its specified stroke cannot jog in the current
JOG-013 WARN Hex) limit direction any more.
Robot reaches its vertical fixture To continue jogging,
JOG-014 WARN Vertical fixture position position release the JOG key then
Horizontal fixture Robot reaches its horizontal fixture To continue jogging,
JOG-015 WARN Softfloat
position time position time is over when softfloat is Make
Follow-up releasethe
thesystem
JOG key then
variable
JOG-016 SERVO out(G:%d) ON $SFLT_FUPTIM larger.
At R-Theta robot Robot reaches its R-Theta posture To continue jogging,
JOG-017 WARN posture position release the JOG key then
JOG-018 WARN
JOG-019 WARN
PATH JOG has selected, but robot is not Use shift-FWD to execute
currently on a taught path, or tool Z program path, or specify
JOG-020 WARN Can not PATH JOG now Use
direction is samejog
of multiple teaching path, so Y
keys is not another
Use onlyjog
oneframe.
jog key at a
JOG-021 WARN Multi key is pressed supported in PATH JOG time.
PATH jog is available in
JOG-022 WARN Disabled in JOINT path PATH jog is disabled
availablein JOINT
only path
in PAUSE LINEAR
PATH jogand CERCULAR
is available only
JOG-023 WARN Available only
Currently in PAUSE
this key is status in PAUSE status
JOG-024 WARN invalid This key is invalid at current jog mode Change jog mode
JOG-025 WARN J4 is not zero J4 angle is not zero. Move J4 to zero position.
JOG-026 WARN J4 is zerodirection from
Reverse J4 angle
This is zero.
direction J4 joint jog
is reverse is disabled.
direction from Now OFIX jog is available.
JOG-027 WARN J4=0 J4 = 0. Press opposite
Confirm jog key.
TCP's XYZ
JOG-028 WARN OFIX TCP config limit Stroke limit with this TCP configuration. location.
JOG-029 WARN OFIX jog error OFIX jog internal error. Contact FANUC Robotics.
JOG-030 WARN Can't jog as OFIX OFIX jog is not available. Check cause code.
A locked multi-robot system requires Use coordinated jogging,
you to use coordinated jogging. Refer or unlock the multi-robot
Multi-robot needs to the Coordinated Motion Setup and system. Refer to the
JOG-031 WARN coord jog Operations Manual for information on Coordinated Motion
Coord not supported in The selected coordinate system Select a supported
JOG-032 WARN TJOG WRIST JOINT JOG Wrist
Can't (COORD)jointis mode
not supported in DualinArm
is not available Tracking Jog COORD:
JOG-033 WARN now coordinated jog. Disable coordinated jog.
JOG Disable by JOG has been disabled by Please set
JOG-034 Application $SCR.$TPMOTNENABL setting. $SCR.$TPMOTNENABL to
Jog Retract request Jog Retract request was received, but it The cause of the error is
JOG-051 ignored
No program is running could not be processed displayed in the next
Do the operation line
while a
JOG-052 or paused User program is not running program is running
Robot Return request Robot Return request was received, but The cause of the error is
JOG-053 ignored it could not be processed displayed in the next line
Jog Retract NOT in Request the Jog Retract
JOG-054 progress Jog Retract operation is not in progress. operation prior to this
Abort Jog Retract Abort Jog Retract request was received, The cause of the error is
JOG-055 request ignored but it could not be processed displayed in the next line
Jog Retract has recorded maximum You may request Robot
Jog Retract recorded number of jogged positions, and Return at this point. The
JOG-056 Max Num positions therefore, cannot record any more. robot can still be returned
The system could not use the recorded
Returning to recorded jogged position in Cartesian space. The None. It is just an
JOG-057 Joint Position
Undefined parse syntax system is using the recorded position in informational
KCLI-002 WARN error.
Internal error. Parser
KCLI-003 WARN stack underflow.
Internal error. cannot
KCLI-004 WARN be extracted.
Internal error. Handle =
KCLI-005 WARN %d, offset = %d
Internal error.
KCLI-006 WARN Production
Not enoughnot
memory to
KCLI-007 WARN perform command.
KCLI-008 WARN Integerdata
PATH expected.
type is not
KCLI-009 WARN allowed in
Number ofarrays.
array
KCLI-010 WARN dimensions exceeded
Number of values
KCLI-011 WARN entered exceeds
A maximum of 3 values
KCLI-012 WARN can
Entrybenot
entered
allowedforwhen
KCLI-013 WARN multiple values
Multiple entries not
KCLI-014 WARN allowed.
Id must be defined
KCLI-015 WARN before this use. Id: %s
Id is undefined, it must
KCLI-016 WARN be defined before use
Group number is not in
KCLI-017 WARN valid range.
KCLI-018 WARN Number expected.
KCLI-019 WARN Integer
Programorname "*" expected.
KCLI-020 WARN expected.
KCLI-021 WARN "=" expected.
KCLI-022 WARN "[" expected.
KCLI-023 WARN "]" expected.
KCLI-024 WARN "OF" expected.
KCLI-025 WARN "GROUP" expected.
KCLI-026 WARN "," or "]" expected.
KCLI-027 WARN ":" expected. hh:mm'
'dd-mmm-yy
KCLI-029 WARN Type name expected.
KCLI-030 WARN Field name
Variable nameexpected.
or value
Variable not defined.
KCLI-032 WARN Var: %s invalid. Index:
Indexing
KCLI-033 WARN %s
Id type is not an ARRAY
KCLI-034 WARN or type
Id indexing
is notexceeded
a
KCLI-035 WARN STRUCTURE. Id:
Id type is not a field%s in a
KCLI-036 WARN STRUCTURE. Id: %s
KCLI-037 WARN Data type mismatch.
Wildcard characters are
KCLI-038 WARN permitted
Not only in the
valid element
KCLI-039 WARN name.
Error detected by
KCLI-040 WARN VaraiabletoManager.
Variable be set is
KCLI-041 WARN specified
Array incorrectly.
of user type is not
KCLI-042 WARN implemented
User type not yet.
KCLI-043 WARN implemented yet.
KCLI-044 WARN Cannot
A maximumopenoffile %s.
6 entries
KCLI-045 WARN is permitted.
ALL, BREAK, DICT,
KCLI-046 WARN PROG, or VARS
KCLI-047 WARN VAR expected.
NODE, FILE or VAR
KCLI-049 WARN NODE expected.
ALL, DICT, FORM,
KCLI-050 WARN MASTER, PROG, SERVO,
KCLI-051 WARN PROGVAR,
FILE, or VAR expected.
or VARS
MASTER, SERVO,
KCLI-053 WARN SYSTEM,
TASK, TP, orVAR,
TRACE, VARSor
KCLI-054 WARN VERIFY TRACE,
TASKS, expected. TYPES,
KCLI-055 WARN VAR, VARS or data_type
KCLI-056 WARN FILE or NODE expected.
KCLI-057 WARN FILE expected.
Variables of this type
KCLI-058 WARN cannot
CONDITIONrecorded.
be or
KCLI-059 WARN PROGRAM
Too expected.
many arguments
KCLI-060 WARN specified.
Structure type
KCLI-062 WARN ON
BREAKor OFF expected.
or CONDITION
KCLI-064 WARN PROGRAM
Variable name expected.
File specification
DEFAULT, ENGLISH,
KCLI-067 WARN JAPANESE, FRENCH,
Language has not been
KCLI-068 WARN created yet. Use SHOW
DPADD returned a
KCLI-069 WARN status ofprogram
Default %d. name
KCLI-070 WARN not set.specification
Device
KCLI-072 WARN "TO"name
File expected.
exceeds %d
KCLI-073 WARN characters.
KCLI-074 WARN "NODEDATA"
"PATHHEADER" expected.
Dictionary name
KCLI-077 WARN File name
Integer or expected.
real
Unrecognized
KCLI-079 WARN command.
Must specify DRAM
KCLI-080 WARN when
ALL orloading
port_name from port
KCLI-082 WARN Device
DONE or not supported.
PAUSE
KCLI-084 WARN Port namename
Attribute expected.
Cannot record on
KCLI-086 WARN extended or
PRIORITY axes robot.
TRACELEN
String size must be
KCLI-088 WARN greater than
"CMOS" 0 and less
or "DRAM"
DICT or FORM
KCLI-091 WARN Keeping existing RD:
KCLI-092 WARN Files exist inof
DISMOUNT RD: existing
KCLI-093 WARN RD: failed
FORMAT of new RD:
KCLI-094 WARN failed
MOUNT of new RD:
KCLI-095 WARN failed
No user currently
KCLI-096 WARN logged in.
KCLI-097 WARN Could not open file %s
Input file_spec must
KCLI-098 WARN have an extension of
KCLI-099 WARN KCONVARS
Routine name file_spec
KCLI-101 WARN Quoted string expected.
KCLI-102 WARN VAR or VARS
Routine expected.
not found in
KCLI-103 WARN program.
No local data defined
KCLI-104 WARN for routine.
Local variable data size
KCLI-105 WARN mismatch.
Not allowed in AUTO
KCLI-106 WARN mode
Routine stack file (.RS)
KCLI-107 WARN does not
PATH datamatch
typesloaded
are
KCLI-108 WARN not supported.
LANG-000 WARN Success return
LANG-001 WARN System error
(1) The wrong port is set to the port (1) Set the currect port.
LANG-004 WARN File is nottype
Program openis you
Onlywant
able to use. (2) The
process teachdevice may be
pendant (2) Check the device if it
LANG-005 WARN different programs. Select a TPE program.
A when loading .TP file, invalid data Generate (using SAVE,
was found. This may occur if a .TP file with $ASCII_SAVE =
has become corrupted or if some other FALSE) and load a valid .TP
Invalid or corrupted TP type of file e.g., a .PE file, has been file. Note: An existing TP
LANG-006 WARN file copied or renamed to a .TP file. program in the controller
The program that is being loaded Before you load the
LANG-014 WARN Program already exists already exists in the system. program,
Check thedelete the of
connection
LANG-015 WARN Can not write file writing data
Failure when reading datato thethe
from floppy. the device.
Check the connection of
LANG-016 WARN Can not read file floppy. the device.
The data you are trying to save to a file The file cannot be loaded
is either abnormal or broken, therefore with the data as it is. The
LANG-017 WARN File format is incorrect the file cannot be loaded. data must be normal to
When printing the program, there was Reteach the position data
Group mask value is an illegal position that did not match so that the group number
LANG-018 WARN incorrect the group mask of the program. matches the group mask
%s contains %s, The file name and the program name Rename the file to be
LANG-050 WARN program/file names are not the same. Their names must same as the program
Wrong daughter The daughter program name is not Please verify the daughter
LANG-051 program name matched with the parent program program name.
Cannot load daughter The loading of the daughter program Please check the contents
LANG-052 program(%d) failed. of the specified file.
Cannot process The save/load/print operation cannnot Specify the parent
LANG-053 daughter program be processed to a daughter program program.
The program that cannot be loaded Please confirm if you are
Can't load(Reversed needs J858 option. You might load not loading wrong
LANG-054 WARN repr.
Can't disabled)
print(Reversed wrong
The program
program tocannot
that the robot where
be printed program.
Please PleaseJ858
confirm confirm
is
LANG-055 WARN repr. disabled) needs J858 option. ordered in the robot.
The positions of program whose
handle_part is ON are printed by
Print Reversed repr. reversed representation when J858 is Please correct position
LANG-056 WARN failed(P:%d,G:%d) ordered, but the print is failed because data and try again
This program was created on a robot You must upgrade to a
LANG-057 WARN Group number too big which supports groups that are not later software version
Requires extended This program was created on a robot You must load the
LANG-058 frame option which had the extended frame option. extended frame option
LANG-075 WARN Invalid attribute syntax
application
LANG-076 WARN syntax
LANG-077 WARN Invalid mnenonic syntax
LANG-078 WARN Invalid position syntax
LANG-079 WARN Invalid section
LANG-080 WARN Invalid application
filename
LANG-081 WARN header
The Ascii Input encountered a program Shorten the line in the
LANG-090 Buffer is too small line with too many characters. /MN section of the .LS file.
Can't print optimize Optimize data exists in the program Special handling may
LANG-091 data and this cannot be printed. occur for programs which
The specified file already exists in the Before you write the new
LANG-094 WARN File already exists floppy.
The specified file does not exist in the file
Checkto the floppy,
file namedelete
or
LANG-095 WARN File does not exist floppy. content of the floppy.
The floppy disk has reached its limit Either use a new floppy
LANG-096 WARN Disk is full
Only one file may be and is full. was made to open more
An attempt disk
Do notor delete
attempt anto open
LANG-097 WARN opened than one file. more than
Check if theone file atdevice
correct a
LANG-098 WARN Disk timeout
Write protection It could not access the disk. is set to port
Remove the write and it turns
LANG-099 WARN violation The disk has write protection. protection.
Connect the correct
LANG-100 WARN Device error Could not access the device. device to the correct port.
A message was sent to another part of Verify all devices in the
the system through the digital system are properly
Action db failed communications link (ArcLink) but no powered. Notify FANUC or
LECO-017 (%d^1,%d^2,%d^3) response was received. This often FANUC America
Machine settings that are saved during Notify FANUC or FANUC
power down could not be restored America Corporation for
because the data is corrupt. The two flashing system with latest
backup copies of the machine settings Firmware. Notify FANUC
Failure to restore non- are not complete or do not contain or FANUC America
LECO-019 volatile attributes valid data. Default values have been Corporation if problem
Machine settings that are saved during Cycle power on system.
power down could not be restored Notify FANUC or FANUC
Primary non-volatile because the data is corrupt. The first of America Corporation for
LECO-020 section failure two copies did not verify correctly. flashing system with latest
power down could not be restored Notify FANUC or FANUC
Secondary non-volatile because the data is corrupt. The second America Corporation for
LECO-021 section failure of two copies did not verify correctly. flashing system with latest
Non-volatile attributes power down could not be restored Notify FANUC or FANUC
restore fault because the data does not match the America Corporation for
LECO-022 (%d^1,%d^2,%d^3) current configuration. This can be flashing system with latest
An attempt to establish Verify that the weld
ArcLink mapping failed communications between the robot power supply is turned
LECO-024 WARN (%d^1) and a Lincoln PowerWave welding on. Verify the ArcLink
The input current to the machine Check the input power
exceeded the safe limit. This is normally
(voltage and frequency).
caused by low input voltage or a Verify the primary
Primary over current missing phase (with 3 phase input reconnect is properly
LECO-049 (%s^1,%s^2) power) but it could be caused by a configured for the input
The voltage on one of the two input Check the input power
capacitor banks (bank A) has fallen (voltage and frequency).
below the normal operating limit. This Verify the primary
Cap A under voltage is normally caused by low input voltage reconnect is properly
(Cap A volts, Cap B or a missing phase (with 3 phase input configured for the input
LECO-050 volts) power) but it could be caused by a voltage.
capacitor banks (bank B) has fallen (voltage and frequency).
below the normal operating limit. This Verify the primary
Cap B under voltage is normally caused by low input voltage reconnect is properly
(Cap A volts, Cap B or a missing phase (with 3 phase input configured for the input
LECO-051 volts) power) but it could be caused by a voltage.
capacitor banks (bank A) has exceeded (voltage and frequency).
the high voltage limit. This is normallyVerify the primary
Cap A over voltage (Cap caused by high input voltage but it reconnect is properly
LECO-052 A volts, Cap B volts) could be caused by a faulty switch configured for the input
capacitor banks (bank B) has exceeded (voltage and frequency).
the high voltage limit. This is normallyVerify the primary
Cap B over voltage (Cap caused by high input voltage but it reconnect is properly
LECO-053 A volts, Cap B volts) could be caused by a faulty switch configured for the input
Verify the welding
The machine has shutdown because it procedure does not
has overheated. This will normally exceed the duty cycle
occur because the output duty cycle limits of the machine.
has been exceeded but it could be Check the setup for
caused by insufficient air flow through proper air flow around
Thermostat tripped the machine, a faulty fan, or a faulty and through the system.
LECO-054 (%s^1,%s^2) thermostat. Check that the system has
During the start up sequence, the Check the input power
capacitor banks failed to reach an (voltage and frequency).
expected minimum voltage. This can be Verify the primary
Soft start failed caused by a faulty contactor or low reconnect is properly
LECO-055 (%s^1,%s^2) input voltage; this error is typically configured for the input
For process related issues,
verify the welding
procedure does not
exceed the output limits
of the machine. Verify the
A high level of output current (long stick out, wire size, and
average) has caused an overload. This is gas are correct for the
commonly seen if the wrong output process that is selected.
stud is used on an STT machine or if Check the weld circuit for
there is a missing phase (with 3 phase short circuits and other
input power). When this fault occurs, leakage paths. Verify all
the output current will be reduced to three legs of the input
Secondary over current 100A and a welding condition referred power are present at the
LECO-065 (%s^1,%s^2) to as "noodle welding" may occur. input contactor. When
The voltage difference between the Check input line voltage.
two input capacitor banks has Check reconnect links and
exceeded the safe limit. This will cables. AC/DC Systems:
normally occur when the power is Check for shorts in the
turned ON (if the machine has not been welding circuit. Make sure
Cap balance error used for a long period) or if there is a feedhead is properly
LECO-067 (%s^1,%s^2) missing phase (with 3 phase input isolated.
The machine detected that the welding
Output voltage high voltage was to high. Verify the correct
LECO-069 (%d^1,%d^2,%d^3) input voltage selection has be made on Verify input line voltage.
A high level of output current (short Verify that the welding
average) has caused an overload. This is circuit does not have a
commonly seen when there is a short short in it. Verify stick out,
in the welding circuit outside of the wire size, and gas are
machine. It can also be caused if the correct for the process
Secondary over current wrong output stud is used on an STT that is selected. Notify
LECO-070 (%s^1,%s^2) machine or if there is a missing phase FANUC or FANUC America
Verify all fuses are good.
Verify all three legs of the
input power are present
Single phase input power has been at the input contactor.
detected so the machine may operate When the contactor
at a reduced output level. Refer to the closes, be sure all three
instruction manual of the machine for legs are present on the
Single phase more information on single phase output side as well
LECO-073 (%s^1,%s^2) operation. (toward the related
For process rectifier). If
issues,
verify the welding
procedure does not
exceed the output limits
of the machine. Verify the
stick out, wire size, and
gas are correct for the
A high level of output current (long process that is selected.
average) has caused an overload. This is Check the weld circuit for
commonly seen if the wrong output short circuits and other
stud is used on an STT machine or if leakage paths. Verify all
there is a missing phase (with 3 phase three legs of the input
Secondary overcurrent input power). When this fault occurs, power are present at the
LECO-084 fault the machine output will be turned OFF. input contactor. When
Weld settings could not be updated Notify FANUC or FANUC
properly while the system was welding. America Corporation for
Seq. weld cycle data This normally occurs when a device is flashing system with latest
LECO-098 retry (%d^1,%d^2) not operating properly or it is busy Firmware. Notify FANUC
Check Drive tension.
Check drive rolls
alignment and gears.
Check Wire feed ability
The wire feeder drive motor has been and control cables are not
overloaded. This can be caused by a run along current currying
Wire drive motor wire tangle or a high resistance from conduit. If the system is in
LECO-129 overload (%d^1,%d^2) pulling wire off of the spool or drum. a constant current
The wire feeder drive motor has been
Wire drive motor overloaded by exceeding the current
overcurrent limit. This can be caused by a wire
LECO-130 (%d^1,%d^2) tangle or a high resistance from pulling
Check Wire feed ability.
Shutdown circuit #1 on the wire drive Verify the circuit
Shutdown 1 external I/O connector is open. This "Shutdown1 Input" is
LECO-131 (%d^1,%d^2) open circuit generates an error in order
closed. Notify FANUC or
Shutdown circuit #2 (typically a waterVerify the circuit
Shutdown 2, water fault cooler fault) on the wire drive external
"Shutdown2 Input (Water
LECO-132 (%d^1,%d^2) I/O connector is open. This open circuit
Fault)" is closed. Notify
The machine could not properly send Use Production
Error sending email an email. Verify the correct settings are
Monitoring software to
LECO-356 (%d^1) entered into the email system and thatverify E-mail
Email settings could not be properly Use Production
Error access email mem restored. All email settings need to be
Monitoring software to
LECO-357 (dir %d^1, image %d^2) verified. verify E-mail
Production Monitoring weld totals Notify FANUC or FANUC
could not be saved when the machine America Corporation for
was turned OFF. The values for the flashing system with latest
weld totals displayed in the Weld Totals
Firmware. Notify FANUC
LECO-769 PM save counters failed tab of the application and the or FANUC America
Verify the configuration of
Production Monitoring
Production Monitoring weld profiles weld profiles. Notify
configuration could not be saved when FANUC or FANUC America
LECO-770 PM save weld cfg failed the machine was turned OFF. Corporation for flashing
Production Monitoring.
Production Monitoring system Notify FANUC or FANUC
configuration could not be saved when America Corporation for
LECO-771 PM save sys cfg failed the machine was turned OFF. flashing system with latest
Production Monitoring weld totals Notify FANUC or FANUC
could not be restored when the America Corporation for
machine was turned ON. The values for flashing system with latest
the weld totals displayed in the Weld Firmware. Notify FANUC
LECO-772 PM read counters failed Totals tab of the application and the or FANUC America
Production Monitoring
Production Monitoring weld profiles weld profiles. Notify
configuration could not be restored FANUC or FANUC America
LECO-773 PM read weld cfg failed when the machine was turned ON. Corporation for flashing
Production Monitoring.
Production Monitoring system Notify FANUC or FANUC
configuration could not be restored America Corporation for
LECO-774 PM read sys cfg failed when the machine was turned ON. flashing system with latest
Verify welding set points,
The output current is outside the changes in setup, and
Production Monitoring weld profile work piece position. Setup
PM I fault limits. The output current was less than includes but is not limited
(hi:%d^1,lo:%d^2,wp:% the Current Low Limit or was greater to: gas flow, wire type and
LECO-849 d^3) than the Current High Limit. size, stick out, welding
changes in setup, and
work piece position. Setup
includes but is not limited
The output voltage is outside the to: gas flow, wire type and
Production Monitoring weld profile size, stick out, welding
PM V fault limits. The output voltage was less than cable length, spatter
(hi:%d^1,lo:%d^2,wp:% the Voltage Low Limit or was greater buildup, and tip wear.
LECO-850 d^3) than the Voltage High Limit. Verify the voltage limits
Verify the welding setting
for wire feed speed is
The wire feed speed (WFS) is outside correct. Verify the wire
the Production Monitoring weld profile feed limits for the weld
PM W fault limits. The wire feed speed was less profile are a reasonable
(hi:%d^1,lo:%d^2,wp:% than the WFS Low Limit or was greater range for the application.
LECO-851 d^3) than the WFS High Limit. This would also include
The welding time (arc time) is outside Verify the weld was made
PM T fault the Production Monitoring weld profile at the proper travel speed
(hi:%d^1,lo:%d^2,wp:% limits. The welding time was less than and for the correct
LECO-853 d^3) the Time Low Limit or was greater than amount of time. Verify the
The output current is outside the to: gas flow, wire type and
PM I alarm limits. The output current was less than cable length, spatter
(hi:%d^1,lo:%d^2,wp:% the Current Low Limit or was greater buildup, and tip wear.
LECO-865 d^3) than the Current High Limit. Verify the current limits
PM V alarm limits. The output voltage was less than cable length, spatter
PM W alarm limits. The wire feed speed was less profile are a reasonable
PM T alarm the Production Monitoring weld profile at the proper travel speed
LECO-869 d^3) the Time Low Limit or was greater than amount of time. Verify the
Production Monitoring could not Verify the duration of the
Weld profile runt perform limit checking on a weld weld is greater then the
occurred because the welding time (arc time) combination of the start
LECO-881 (t:%d^1,wp:%d^2) was too short. The welding time was delay and end delay.
The wire package weight has dropped Replenish the wire
below the Production Monitoring package and reset the
"Warning Package Weight" limit. The current wire weight.
Consumable low supply of wire should be checked and Verify the following setup
LECO-882 (weight:%s^1) replaced if necessary. The welding time items have been correctly
The output current is outside the to: gas flow, wire type and
PM I latched alarm limits. The output current was less than cable length, spatter
(hi:%d^1,lo:%d^2,wp:% the Current Low Limit or was greater buildup, and tip wear.
LECO-897 d^3) than the Current High Limit. Verify the current limits
PM V latched alarm limits. The output voltage was less than cable length, spatter
PM W latched alarm limits. The wire feed speed was less profile are a reasonable
PM T latched alarm the Production Monitoring weld profile at the proper travel speed
LECO-901 PAUSE. d^3) the Time Low Limit or was greater than amount of time. Verify the
LNTK-000 G Unknown error (LN00)
PAUSE. The Line Track global variables have Check the application
LNTK-001 G
PAUSE. No global variables NOT been properly loaded. installation manual for the
LNTK-002 G
PAUSE. Motion
Error data missing
allocating data
LNTK-003 G memory
PAUSE. The Line Track system variables (eg. Check the application
LNTK-004 G No system variables $LNSCH[], $LNSNRSCH[]) were not installation manual for the
An invalid Line Track schedule (track or Check all schedule
frame) number was used within a numbers (TRK[] or FRAME
PAUSE. program instruction (eg. TRK[59]) or usages) used within the
LNTK-005 G Illegal schedule number program header data (eg. FRAME = 59). specified program to
Check the value of
An invalid tracking type was specified $LNSCH[i].$TRK_TYPE
within the tracking schedule (i.e. (where 'i' is the FRAME
PAUSE. $LNSCH[]) associated with the specified number specified within
LNTK-006 G Illegal tracking type program. the DETAIL screen for the
An invalid sensor(encoder) number was Check the value of the
used within the specified tracking specified program
program instruction or within the instruction's LINE[]
program's associated schedule parameter and the
PAUSE. $LNSCH[i].$TRK_ENC_NUM value program's associated
LNTK-007 G Illegal encoder number (where 'i' is the FRAME number used schedule
An invalid or uninitialized nominal Check the value of
tracking frame position was used within $LNSCH[i].$TRK_FRAME
PAUSE. the tracking schedule (i.e. $LNSCH[]) (where 'i' is the FRAME
LNTK-008 G Invalid nominal position associated with the specified program. number specified within
The position type or representation Check the KAREL or TPE
used within the specified program is user manual for valid
PAUSE. not valid. (LINE and CIRC tracking position types. Check the
LNTK-009 G Illegal position type programs MUST store all positions in position representation
An invalid sensor(encoder) schedule Check the $LNSNRSCH[]
PAUSE. Illegal encoder schedule number was used within the specified system variable
LNTK-010 G num tracking program instruction's SCH[] description for the range
An illegal value was used within the Check the value of the
specified tracking program instruction specified program
or within the program's associated instruction's BOUND[]
PAUSE. Illegal boundary set schedule $LNSCH[i].$SEL_BOUND value parameter and the
LNTK-011 G number (where 'i' is the FRAME number used program's associated
An invalid or uninitialized position was Check the position (or
PAUSE. used within the specified tracking position register) value for
LNTK-012 G Invalid input position program instruction. the specified tracking
PAUSE. Invalid trigger input An invalid or uninitialized value was Check the value of the
LNTK-013 G value used for the specified tracking program program register used by
The tracking sensor(encoder)
associated with the specified program
(specified by Use the LINE enable
$LNSCH[i].$TRK_ENC_NUM, where 'i' is instruction to enable the
PAUSE. Encoder/sensor not the FRAME number used within the proper tracking
LNTK-014 G enabled DETAIL screen for the specified sensor(encoder).
An invalid or uninitialized Make sure that this value
sensor(encoder) trigger value (specified is properly set prior to
PAUSE. Invalid encoder trigger by $LNSCH[i].$TRIG_VALUE, where 'i' is either teaching path
LNTK-015 G value the FRAME number used within the positions, or issuing
PAUSE. An invalid or uninitialized prediction Check the prediction time
LNTK-016 G
PAUSE. Invalid input time time was used within the specified being used for proper
LNTK-017 G Invalid input pointer
An invalid or uninitialized teach Make sure that this value
distance value (specified by is properly set prior to
PAUSE. $LNSCH[i].$TEACH_DIST, where 'i' is the either teaching path
LNTK-018 G Invalid teach distance FRAME number used within the DETAIL positions, or issuing
An invalid or uninitialized scale factor Make sure that this value
value (specified by $LNSCH[i].$SCALE, is properly set prior to
PAUSE. where 'i' is the FRAME number used either teaching path
LNTK-019 G Invalid scale factor within the DETAIL screen for the positions, or issuing
An invalid or uninitialized extreme Make sure that this value
position value (specified by is properly set prior to
PAUSE. $LNSCH[i].$TCP_EXTRM, where 'i' is the either teaching path
LNTK-020 G Invalid extreme position FRAME number used within the DETAIL positions, or issuing
An invalid or uninitialized track axis Make sure that this value
number (specified by is properly set to one of
PAUSE. Invalid track axis $LNSCH[i].$TRK_AXIS_NUM, where 'i' is the valid values listed
LNTK-021 G number the FRAME number used within the under the description for
PAUSE. No tracking sensor hardware interface Check tracking hardware
LNTK-022 G
PAUSE. No tracking hardware or improperly initialized system setup and
Check the values of
all sensor
LNTK-023 G
PAUSE. Bad tracking hardware Bad tracking sensor hardware interface hardware,
Use a valid cables,
encoderand
LNTK-024 G
PAUSE. Illegal encoder average Illegal encoder average number average number
Use a valid encoder
LNTK-025 G multiplier Illegal encoder multiplier number multiplier number
PAUSE. Enable the tracking
LNTK-026 G Encoder not enabled Tracking encoder is not enabled encoder before reading its
PAUSE. Invalid data on LNTK Invalid data was found on the tracking Perform a COLD start of
LNTK-027 G stack stack. the system. (Cycle power.)
PAUSE. The tracking stack attempted to read Perform a COLD start of
LNTK-028 G LNTK stack underflow more data than was present. the system. (Cycle power.)
Too many tracking subprocesses are Check to ensure sub-
PAUSE. present. There is a limit to the number processes are not being
LNTK-029 G LNTK stack overflow of tracking processes that can be called called erroneously.
PAUSE. Stack / header The schedule number on the tracking Perform a COLD start of
LNTK-030 G
PAUSE. mismatch stackframes
User did notcannot
match betheused
schedule
whenof the the $MNUFRAMENUM[]
Set system. (Cycle power.)
LNTK-031 G UFRAME must be zero tracking. to zero.
Make sure the Tracking
PAUSE. The conveyor was not resynchronized Schedule is properly
LNTK-032 G Conveyor resync failed properly. initialized, the encoder is
PAUSE. Failed to send a packet including trigger Perform a COLD start of
LNTK-033 G Failed to send a packet value. the system. (Cycle power.)
PAUSE. Failed to make a packet including Perform a COLD start of
LNTK-034 G Failed to make a packet trigger value. the system. (Cycle power.)
PAUSE. Invalid INTR function An invalid internal function pointer was Perform a COLD start of
LNTK-035 G pointer encountered. the system. (Cycle power.)
Modify
PAUSE. $LNCFG.$GROUP_MSK to
LNTK-036 G
PAUSE. Invalid tracking
Rotation group This group does not support tracking
diff exceeds enable this group for
LNTK-037 G
PAUSE. limit tracking not
CIRCLE
LNTK-038 G
PAUSE. supported
Use track uframe is not
LNTK-039 G YESline tracking task
No
LNTK-040 WARN found
If the encoder motion is detected in T1
PAUSE. Encoder is moved in T1 mode, the robot stops with this alarm Do not move the encoder
LNTK-041 G mode. to prevent the robot violating the safty in T1 mode.
The robot can not reach the destination Program at a faster speed
Skip outbound move before it gets out of the specified or extend the boundary.
LNTK-042 WARN LN:%d boundary. Skip this motion to prevent 3.9.4 LSTP Alarm Code
Multiple group not Tracking programs do not support Change the program to a
LNTK-043 supported multiple group motion. single group program.
Invalid DOUT %d^3 in The Digital output specified in the Change the variable for
LNTK-044 Sched %d^2 indicated schedule is not a valid DOUT. Outbound DOUT to
This is a warning to
The robot is approaching the indicate that a Track
Gp %d^2 near downstream boundary that is currently Destination Gone error
LNTK-045 downstrm bound %d^3 in use. could be imminent. It can
Cont_Turn permit key Continuous turn option is loaded Continuous turn greoup
LNTK-046 Not on without turn on permition key can not be line tracking
Change Fee is needed to avoid limit
error. However new fee verification fail.
Limit Checking Typically it is because boundary setting Re-teach the position or
LNTK-047 verification fail cause new fee delay tracking move that adjust tracking boundary
Try to run a tracking move in a none-
Tracking environment tracking environment or try to run a Abort the program. Then
LNTK-048 mismatch none-tracking move in a tracking make the move
System change robot last axis moving This is a warning to
FEE Change to avoid direction for this motion line to avoid indicate that System
LNTK-049 limit LN:%d
Notify FANUC Robotics limit error change robot last axis
LNTK-050 WARN if problem persists.
$LNCFG.$SLC_PT_TRIG Use accutrig without setting Set $lncfg.$slc_pt_trig to
LNTK-051 not setFANUC Robotics $lncfg.$slc_pt_trig
Notify true then cycle power
LNTK-052 WARN if problem
Check persists.
Memory usage
LNTK-053 WARN and Line Track
Not a line tracking Line Tracking does not support Encoder Change Tracking schedule
LNTK-054 encoder Master DAL
Ethernet number above
Ethernet Master 8 Encoder has DAL to use encoder 1-8
LNTK-055 (Enc:%d) Alarm Fix Master's DAL alram
Ethernet Enc Timeout Ethernet Master Encoder did not Ethernet Master Encoder
LNTK-056 (Enc:%d) update slave for a timeout period controller maybe offline.
If the encoder motion is detected with
Encoder is moved use Joint space JBF, the robot stops with Do not move the encoder
LNTK-057 100% ovrd this alarm to prevent path shift along or use 100% ovrd.
If lnsch scale done with
lnsch Indexer scale Indexer setup and tracking schedule actual teaching, the
LNTK-058 mismatch
Notify FANUC Robotics scale setup mismatch. Indexer setup for index
LNTK-067 WARN
ABORT. if problem persists.
LODC-000 LPAUSE. Internal Error (system)
LODC-010 LPAUSE. Grind start failed
LODC-011 LPAUSE. Grind end failed
LODC-012 L Over Load is detetcted
LODC-013 WARN
PAUSE. Missingposition
Illegal processregister
IO boad
LODC-014 LPAUSE. number
Uninit position register
LODC-015 LPAUSE. used
This group can't use
LODC-016 LPAUSE. LOAD CLUTCH can't
Grind command
LODC-017 LPAUSE. use in position
Illegal this case
LODC-018 LPAUSE. representation
Cannot execute RETRY
LODC-019 LPAUSE. motion
LODC-020 LPAUSE. Offset is too large
LODC-021 LPAUSE. Illegal schedule
Cannot execute data
REPEAT
LODC-022 LABORT. motion
LODC-023 LPAUSE. Buffer data
Analog error
output setting
LODC-024 LPAUSE. error
Detect signal did not
LODC-025 LPAUSE. turn off
LODC-026 L Invalid singlestep
UNUSED ERROR type
LSR-000 WARN CODE(LW00)
Other program is Laser processing is executing by the
LSR-001 WARN locking laser other program task. Change this program.
PAUSE. This program doesn't
LSR-002 L have LE This program doesn't have LE. Please add LE instruction.
PAUSE. System does't have Please execute this
LSR-003 L
PAUSE. laser-appl This R-J system doesn't have laser tool. program in R-J system
LSR-004 L Illegal
Can not VEIN
stoprevolution
hour The revolution of the vein is lower. Please check the vein.
LSR-005 WARN meter
Can not start hour
LSR-006 WARN meter
Can not create hour
LSR-007 WARN
PAUSE. meter Mapping of assist gas signals is not Please check I/O mapping
LSR-008 L AGS
LE signals are
execution not set
without correct. of assistcheck
Please gas signal.
this
LSR-009 WARN
PAUSE. LP, LS
Laser internal error LE is executed without LP or LS. program.
LSR-010 LPAUSE. occured
Other motion is locking The other motion group is executing Please check this
LSR-011 LPAUSE. laser
Undefined EQ number laserR-J
This processing
system doesn't have this EQ program.
Please change EQ number
LSR-012 L in program number. in the program attribute.
PAUSE. Program can't start in It is not possible to execute the Please execute it after
LSR-013 L
PAUSE. RFHV uneffective
Receive program in RFHV. laser oscillator become to
LSR-014 LPAUSE. packet
Fail to receive
LSR-015 LPAUSE. packet(rcvpkt)
LSR-016 LPAUSE. Unknown timer
LSR-017 L Unknown case
It is not possible to turn on High Please wait for the end of
LSR-018 WARN
PAUSE. Program is executing
Fail to delete voltage switch while a program is the program execution.
LSR-019 LPAUSE. monitor(delmon)
LSR-020 LPAUSE. Fail to number
Illegal get DATA(getvar)
of
LSR-021 LPAUSE. equipment
Board condition has The number of EQ was changed. Please do control start.
LSR-022 LPAUSE. changed
Can't create DATA The kind of laser board was changed. Please do control start.
LSR-023 LPAUSE. area(cremem)
Can't set DATA
LSR-024 LPAUSE. area(setmem)
Fail to get SP-
LSR-025 LPAUSE. index(getidx)
Fail to get
LSR-026 LPAUSE. memory(getmem)
LSR-027 LPAUSE. to Output
Fail of read Input signal
LSR-028 LPAUSE. signal(valset)
Fail to send
LSR-029 LPAUSE. packet(sndpkt)
Illegal register
LSR-030 LPAUSE. value(getreg)
Can't create AMR
LSR-031 LPAUSE. stopped
Can't pkt one more
create
LSR-032 LPAUSE. AMR pkt
Fail to send one more
LSR-033 LPAUSE. AMRofpkt
Fail AMR
LSR-034 LPAUSE. done(apdone)
Receiv STOP AMR
Receiv ERROR AMR
LSR-037 LPAUSE. Receiv unkown AMR
LSR-038 LPAUSE. error(38) The signal from assist gas equipment is Please check assist gas
LSR-039 L Not ready of assist gas OFF. equipment.
PAUSE. Not set assist gas Please check assist gas
LSR-040 L output data The assist gas select value is 0. select value in the
PAUSE. Illegal assist gas output The assist gas select value is not Please check assist gas
LSR-041 LPAUSE. data correct. select value in the
LSR-042 L
PAUSE. error(42)
LSR-043 LPAUSE. error(43)
Fail creating
LSR-045 L packet(syinipkt)
PAUSE.
Can't action
LSR-047 L
PAUSE. block(chaunwt)
Can't when
LSR-048 LPAUSE. block(chwhen)
Can't mon
LSR-049 LPAUSE. block(chmon)
Fail to add
LSR-050 LPAUSE. monitor(chaddmon)
Can't be enable
LSR-051 LPAUSE. monitor
Can't condition
LSR-052 LPAUSE. block(cportb)
Can't condition
LSR-053 LPAUSE. block(ctime)
Can't condition
LSR-054 L block(ctp)
PAUSE. Please check the shutter
LSR-055 L Shutter still not open The shutter was not opend. and shutter alarm mask
PAUSE. Please check the shutter
LSR-056 L
PAUSE. Shutter still not close The shutter was not closed. and shutter alarm mask
Can't create
LSR-058 LPAUSE. AMR(apcreamr)
Fail of table
LSR-060 LPAUSE. data(spdatptr)
Unkown softpart( No
LSR-061 LPAUSE. spindex
Illegal )
schedule data The index number of laser instruction is Please check the index
LSR-062 L number
Can't increase not correct. number of the laser
LSR-063 WARN
PAUSE. data(vmralvar)
Fail to get DATA at
LSR-064 LPAUSE. initial
LSR-065 LPAUSE. Fail tocondition
Can't detauch packet
LSR-066 LPAUSE. block(csp)
Can't condition
LSR-067 LPAUSE. block(cdedge)
Unkown condition
LSR-068 LPAUSE. block
LSR-069 LPAUSE. Fail to start COND-CNTL
LSR-070 LPAUSE. Fail tocondition
Can't stop COND-CNTL
LSR-071 LPAUSE. block(cop)
Can't create DATA
LSR-072 LPAUSE. area(newmem)
Illegal MMR number at
LSR-073 L resume
PAUSE. Joint motion in LASER It is impossible to execute a joint Please change the motion
LSR-074 L
PAUSE. exec motion while laser is processing. type of this motion
LSR-075 LPAUSE. Z axis
Fail tolimited
disposeover
PLAN
LSR-076 LPAUSE. DATA
No preplanned data at
LSR-077 LPAUSE. start
Fail to get
LSR-078 L memory(getmem)
PAUSE. Jogged while laser is In the case that while laser processing Please try again from the
LSR-079 L
PAUSE. paused cabinet
Abnormal is paused the robot is jogged, it is first. cool down the
Please
LSR-080 L temparature The cabinet temparature is over heat. cabinet.
PAUSE. Not ready of laser Please check the laser
LSR-081 L
PAUSE. oscillator The laser oscillator is not ready. oscillator is turned on.
LSR-082 LPAUSE. Not ready
Chiller of chiller
water volume The chiller is not ready. Please check the chiller.
water
LSR-083 LPAUSE. drop
Lower laser gas The water volume of chiller is lower. volumecheck
Please of chiller.
the laser gas
LSR-084 LPAUSE. pressure
Abnormal blower laser blower
The root gas pressure is lower.is over
temparature process.
Please cool down the root
LSR-085 L temparature heat. blower.
PAUSE. Lower chiller water Please stop chiller
LSR-086 L
PAUSE. temp.
Abnormal absober The chiller water temparature is lower. Please
equipment
cool and
downwait
theuntil
LSR-087 LPAUSE. temparature The absober temparature is over heat. absober.
Please check the laser gas
LSR-088 L Leak of tubes The laser gas leaks. process.
PAUSE. Not arrive setting The arrival to the destination pressure Please check the laser gas
LSR-089 L
PAUSE. pressure is too late. process or change gas
LSR-090 LPAUSE. Tube voltage
Abnormal drop
vacuum The voltage of the tube is lower. tube.
Please check the rotaly
LSR-091 LPAUSE.pump The rotaly pump is abnormal. pump.
Please take away safety
LSR-092 L Safety interlock The safety interlock is enable. interlock.
PAUSE.Can't turn of in this When the oscillator is not in PURGE, it Please turn off R-J after
LSR-093 L status is impossible to turn off R-J. the oscillator is in PURGE.
PAUSE.Servo off alarm Because servo off alarm of ROBOT Please reset the alarm and
LSR-094 LPAUSE.
happened
Undischarging tube happens, the oscillator becomes to turn on HVON switch.
LSR-095 L exist
PAUSE.
Uncorrect tube There are some undischarging tubes. Please check the tubes.
LSR-096 LPAUSE.
selection Shutter
Abnormal The selection of tube is not correct. checkdown
Please cool that.the
LSR-097 LPAUSE.
temparature
Abnormal external The shutter temparature is over heat. shutter.
Please check the external
LSR-098 LPAUSE.
mirror The external mirror is abnormal. mirror.
LSR-099 LPAUSE.
RDI7 broken
Hight sensor alarm RDI7 is broken. Please check RDI7.
LSR-100 LPAUSE.
happened
Abnormal queuing Hight sensor is ubnormal. Please check hight sensor.
LSR-101 LPAUSE.
packet Please reset emregency
LSR-102 LPAUSE.
Emergency stop Emergency stop is pressed. stop.
LSR-103 LPAUSE.
Request monitor failure
LSR-104 LPAUSE.
Abnormal RF01 power The discharging tube 1 is abnormal. Please check this tube.
LSR-105 LPAUSE.
LSR-106 LPAUSE.
LSR-107 LPAUSE.
LSR-108 LPAUSE.
LSR-109 LPAUSE.
LSR-110 LPAUSE.
LSR-111 LPAUSE.
LSR-112 LPAUSE.
LSR-113 LPAUSE.
LSR-114 LPAUSE.
LSR-115 LPAUSE.
LSR-116 LPAUSE.
LSR-117 LPAUSE.
LSR-118 LPAUSE.
LSR-119 LPAUSE.
LSR-120 Chenbmon failure LPAUSE.
LSR-121 Power fail recovery L The recovery of power faile is executed.
Shutter is mechanical The shutter is mecanically locked on If you want to be output
LSR-122 WARN locked operator pannel. beam, please change the
Alignment beam is If you want to be output
LSR-123 WARN active The adjustment beam is active. beam, please change the
PAUSE. The status of laser oscillator changes Please reset the alarm and
LSR-124 L Laser oscillator down from LSTR to RFHV due to some alarm. turn on HVON switch.
External shtr signal is The shutter is locked by the external If you want to be output
LSR-125 WARN locked signal. beam, please change the
External beam signal is The beam is locked by the external If you want to be output
LSR-126 WARN locked signal. beam, please change the
LSR-127 WARN Be clean mirror
PAUSE. The mirror is dirty. clean the
Please check the mirror.
inverter
LSR-128 LPAUSE. Abnormal inverter 1 The inverter 1 is abnormal. 1.
Please check the inverter
LSR-129 L Abnormal inverter 2 The inverter 2 is abnormal. 2.
LSR-130 WARN Blower Gress 1 The gress of turbo 1 is lack. Please fill up the vacancy.
LSR-131 WARN
PAUSE. Blower
Abnormal Gress 2 current
turbo The gress of turbo 2 is lack. Please fill up the vacancy.
LSR-132 LPAUSE. 1
Abnormal turbo current The current of turbo 1 is abnormal. Please check the turbo 1.
LSR-133 LPAUSE. 2
Abnormal turbo The current of turbo
temparature 2 is abnormal.
of turbo 1 is over Please check the turbo 2.
LSR-134 LPAUSE. temparature
Abnormal 1
turbo heat.
The temparature of turbo 2 is over Please cool down turbo 1.
LSR-135 LPAUSE. temparature 2 heat. Please cool down turbo 2.
LSR-136 LPAUSE. Abnormal revolution 1 The revolution of turbo 1 is abnormal. Please check the turbo 1.
LSR-137 LPAUSE. Abnormal revolution 2 revolution
The arrival of of
signal turbo
turbo2 is1 abnormal.
is not Please check the turbo 2.
LSR-138 LPAUSE. Not arrival AR 1 signal arrived.
The arrival signal of turbo 2 is not Please check the turbo 1.
LSR-139 LPAUSE. Not arrival AR 2 signal arrived. Please check the turbo 2.
AD converter
LSR-140 LPAUSE. AD1 illegal conversion The AD1 convesion is failed. 1 or check
Please check noise
AD in I/O link
converter
LSR-141 LPAUSE. AD2 illegal
Laser conversion
output power The AD2 convesion is failed. 2 or check
Please check noise
powerin I/O link
LSR-142 LPAUSE. drop
Abnormal laser gas The laser outout powerisisnot
gas pressure lower. process of oscillator.
Please check gas pressure
LSR-143 L pressure appropriate. process of oscillator.
PAUSE. Pressure sensor is Please check gas pressure
LSR-144 L
PAUSE. negative The laser gas pressure is negative. process of oscillator and
LSR-145 LPAUSE. Tube voltage drop The voltage of the tube is lower. the tube.
Please check power table
LSR-146 LPAUSE. Power
Abnormaltable error
beam The set power is over table's power. value in setup data.
Please check power
LSR-147 LPAUSE. reflection The beam reflection is abnormal. process and power
LSR-148 LPAUSE. Laser calculate
Can't beam notTCPP
ready The laser process is not ready.
LSR-149 L speed
Over driven packet
LSR-150 WARN
PAUSE. table
Not supported this SLC2
LSR-151 LPAUSE. cycle
Fail to change the
LSR-152 L priority
PAUSE. Gas pressure isn't
Laser gas pressure in gas control 2 is Please check gas pressure
LSR-153 L
PAUSE. reached
not reached to LSTR pressure process of oscillator.
LSR-154 LPAUSE. Blower oil shortage
Turbo blower oil is shortage Please check blower oil
LSR-155 LPAUSE. Mirror not installed
Mirror is not$LGP_LSTR2
$LGP_LSTR,LSTR2
$LGP_LSTR, installed or LSTR_BIAS
or Please check mirror
LSR-156 L $LSTR_BIAS is changed
was changed Please do HV-ON again
You have requested that a motion Press RESET and ensure
group enter local stop mode while that the requested group
LSTP-001 STOP Motion grp %d is active motion is still active for the requested does not have motion
Brake on error in grp The brake is not engaged after the This is an internal system
LSTP-002 ABORT %d brake on timer has expired. error. Contact FANUC
This is a warning message.
Brake off error in grp The brake is not released after the Contact FANUC Robotics
LSTP-003 WARN %d brake off timer has expired. technical support if the
Error setting DO An error has occurred when the SDO Verify that the SDO signal
LSTP-004 ABORT ON(G:%d) singal was set to ON. port type and port
Error setting DO An error has occurred when the SDO This is an internal system
LSTP-005 ABORT OFF(G:%d) signal was set to OFF. error. Contact FANUC
DI1 ON timer This is an internal system
LSTP-006 ABORT expired(G:%d) The SDI1 ON signal timer has expired. error. Contact FANUC
DI1 OFF timer This is an internal system
LSTP-007 ABORT expired(G:%d)
The SDI1 OFF signal timer has expired. error. Contact FANUC
DI1 OFF in
The SDI1 signal is OFF while local stop is This is an internal system
LSTP-008 ABORT HDWR_ENBL(G:%d)
enabled for the specified motion group. error. Contact FANUC
DI1 ON in
The SDI1 signal is ON while local stop is This is an internal system
LSTP-009 ABORT HDWR_DSBL(G:%d)
disabled for the specified motion error. Contact FANUC
Motion command is received while the Press RESET then set the
Motion grp %d entering specified group is entering the local SDI2 signal to ON to
LSTP-010 STOP LSTOP stop mode. disable the local stop
Motion grp %d is in The motion command was received Press RESET then disable
LSTP-011 STOP LSTOP while the specified group is in the local the local stop if you want
LSU %d is in HDWR FAIL The Local Stop Unit is in hardware This is an internal system
LSTP-012 ABORT mode failure mode. error. Contact FANUC
Trying to request a motion group to Please reset the error and
Motion grp %d Torque enter local stop mode while torque is ensure the requested
LSTP-013 active still active for the requested group. group does not have
Trying to request a motion group to This is a warning message.
Motion grp %d Torque enter local stop mode while torque is A real alarm will be
LSTP-014 warning still active for the requested group. posted after the timer has
1: Servo off(brake control) of the local 1: Enable servo off(brake
stop group is disabled. 2: The brake control) for the local stop
Brake setting error %d number of the local stop group is zero. group. 2: Set correct
LSTP-015 (G:%d) ERROR
UNUSED 3: The brake number of the local stop brake number for the
MACR-000 WARN CODE(MCR00)
Can't assign to MACRO The conditions for assigning macros are Check if there is a double
MACR-001 WARN command
Already assigned to not correct. definition or if the index is
MACR-002 WARN MACRO
Can't assign motn_prog It is not possible to assign a program Remove the motion lock
MACR-003 WARN to UK with MOTION lock group to the User group from the program.
Can't execute It is not possible to execute a program Remove the motion lock
MACR-004 WARN motn_prog by UK with MOTION lock group with the User group from the program.
Please enable teach It is not possible to execute a program
MACR-005 WARN pendant when the teach pendant is disabled. Enable the teach pendant.
Please disable teach It is not possible to execute a program Disable the teach
MACR-006 WARN pendant
The same macro type when the teach pendant is enabled. pendant.the assign type to
Change
MACR-007 WARN exists
Remote-cond isn't The
This macro
assign assign
type istype
only already
enabledexists.
at another.
MACR-008 WARN satisfied
The index is out of REMOTE condition. Create REMOTE condition.
MACR-009 WARN range This assign index is out of range. Change the assign index.
Change the value of the
$MACRSOPENBL system
variable. Refer to the
This SOP button is This SOP buttom is not enabled for SYSTEM R<#0106>J
MACR-010 WARN disabled macro execution. Software Reference
Change the value of the
$MACRSOPENBL system
variable. Refer to the
This UOP button is This UOP signal is not enabled for SYSTEM R<#0106>J
MACR-011 WARN disabled macro execution. Software Reference
The number of RI+DI is over the
maximum number. You can assign RI First deassign the other RI
and DI to macro assign type, but the or DI assignments. Then
total number of assignments possible is assign the new macro as
MACR-012 WARN Number of DI+RI is over restricted by the system variable RI or DI.
MACRO execution Refer to the error cause
MACR-013 WARN failed Cannot execute this MACRO. code. Use to display the
MACR-014 WARN Internal ERROR occured
MACR-015 WARN Unknown assign type
The macro is not The macro will begin
MACR-016 WARN completed The macro aborted while executing. executing from the first
Data modification User tried to change data that was in This is a warning message.
MARL-000 WARN disallowed use by robot In order to change data, in
User tried to change data that was in This is a warning message.
MARL-001 WARN Data in use by Robot use by robot In order to change data, in
Check if the variable exists
or is initialized If the
KAREL GET_VAR built-in did not return variable does not exist or
MARL-002 PAUSE GET_VAR failed %s a successful status is uninitialized, try to
Check if the variable exists
or is initialized If the
KAREL SET_VAR built-in did not return a variable does not exist or
MARL-003 PAUSE SET_VAR failed %s successful status is uninitialized, try to
Check if the disk drive is
connected or if there is a
Could not save .VR file problem with the cable.
MARL-004 WARN %s Error occurred while saving a .VR file Check if the floppy disk is
Check if the disk drive is
connected or if there is a
problem with the cable.
MARL-005 WARN Could not load file %s Error occurred while loading a .VR file Check if the floppy disk is
Check RAM memory from
the STATUS Memory
Error occurred while creating the file menu. Perhaps there isn't
MARL-006 PAUSE Could not create file %s MRDTxxx.vr enough memory to create
Error creating new This message is an
MARL-007 WARN variables Error occurred while creating a variable informational message
Error occurred while reading the data Try again. If you keep
MARL-008 WARN Error reading data %s which the user entered. getting this message
User is trying to modify a file which This is a warning message.
MARL-009 WARN Cannot use MODIFY
File not loaded or does not exist
File does in the
not exist in controller RAM.
the controller Either create a new file or
MARL-010 WARN created: %s RAM. This is a warning message.
Either operator panel E-STOP, teach This is a warning message
Cannot resume pendant E-STOP is ON or teach pendant and is posted with
MARL-011 WARN program is enabled. another message which
Operator Panel E-stop Program cannot run with operator Release Operator panel E-
MARL-012 PAUSE ON panel E-STOP stop, press reset and push
Teach pendant E-stop Program cannot run with teach Release teach pendant E-
MARL-013 PAUSE ON pendant E-STOP stop, press reset and push
Teach pendant is Program cannot run with teach Disable teach pendant,
MARL-014 PAUSE enabled pendant enabled press reset, and push
No program was selected from the Select a program and then
MARL-015 WARN Program not selected SELECT menu prior to pressing CYCLE press CYCLE START.
An attempt was made to run a program No action necssary. This is
MARL-016 WARN %s already running that was already running. only a if
Check warning message.
the register is
MARL-017 PAUSE Register not defined %s Register not defined or out of range. defined, if it is between 1-
MARL-018 PAUSE Reg %s could not be set Register operation failed defined, if it is between 1-
User switched to another screen This is a warning message.
MARL-019 WARN MRTool aborted without pressing DONE in the cycle Do not switch screens
Product number not User pressed DONE key without This is a warning message.
MARL-020 WARN entered entering the product number in the Enter the product number
An attempt was made to copy a file
MARL-021 WARN %s exists. Not loaded which is already loaded on the This is a warning message.
The file did not get
An error occurred while loading a file to loaded. Check if the
MARL-022 WARN Loading error - %s the controller memory. communications cable is
PosReg %s could not be Check if the position value
MARL-023 PAUSE set Position Register operation failed is defined and if it is valid.
You must clear the serial
This alarm indicates that there is a line by changing it in the
problem with the serial line used for PORT I/O menu from No
MARL-031 WARN %s Semaphore timeout the active gripper device. Use to Host Comm and
You must clear the serial
This indicates that there is a problem line by changing it in the
with the serial line used for the active PORT I/O menu from No
MARL-038 WARN %s Invalid field value gripper device. Use to Host Comm and
Refer to Pushcorp's
FCU1000 Controller
Manual for detailed info
An error has occurred. THIS NEEDS TO on the error. If you are
MARL-046 WARN %s Unknown AFD Error BE MORE SPECIFIC. unable to resolve the
The system may have
Internal error. This class of error should or additional software not
not be encountered during normal on the original software
MASI-001 Internal Error (G: %d^2) operation distribution media is the
The system may have
Internal error that cause assert. This or additional software not
Internal Assert Error (G: class of error should not be on the original software
MASI-002 %d^2) encountered during normal operation distribution media is the
Feature Not Supported This function does NOT support this Disable the feature and
MASI-003 (G: %d^2) feature. try again
The system ran out of memory during Check $MASYCFG for too
MASI-004 Out of Memory initialization. large values Use a larger
Warning message. The cause is
MASI-005 %s displayed in the message. Check system setup
STOP error message. The cause is
MASI-006 %s displayed in the message. Check system setup
The system may have
MASI-010 MEMORY ALLOC ERROR operation distribution media is the
1. Set up RIPE via HOST
COMM in setup menu 2.
MASI-011 Pls Setup MASH MASH has not been setup yet Set up MASH
Please set up in setup
a master
MASI-012 Pls Set Master in MASH Users have not set a master device yet. device via MASH in setup
The program that has Please set group mask in
Pls Set Group Mask in WaitZone/SyncZone/EnterZone/ExitZo the TP program header or
MASI-013 Prog ne instructions does not have group don't use the instructions
The specified device ID in Please re-specify the
MASI-014 Invalid Device ID WaitZone/SyncZone is not valid device ID in the
Pls Use Different Device The specified device ID has been used Please re-specify valid
MASI-015 ID in the same WaitZone/SyncZone device ID in the
The specified space ID is invald in the Please re-specify valid
MASI-016 Invalid Space ID Enter/ExitZone statement space ID
Please in the
check theinstruction
device
MASI-017 Check Device:%d^2 The Device may stop running status
There is an error when sending pkt Please check MASH and
MASI-018 Err in OSXSND from one controller to different RIPE setup
There is an error when sending pkt to Please check MASH and
MASI-019 Err in OSSND the same controller RIPE setup
The system may have
System variables are not available. This or additional software not
No System Variables (G: class of error should not be on the original software
The system may have
Internal Data structure is not available. or additional software not
No Data Structure (G: This class of error should not be on the original software
The system may have
Stack Underflow (G: not be encountered during normal on the original software
MASI-022 %d^2) operation distribution media is the
The system may have
MASI-023 No Stack (G: %d^2) operation distribution media is the
The system may have
Stack Overflow (G: not be encountered during normal on the original software
The system may have
MASI-025 Stack Not Full (G: %d^2) operation distribution media is the
The system may have
MASI-026 Corrupt Data (G: %d^2) operation distribution media is the
The system may have
Cycle Power: WS stk (G: not be encountered during normal on the original software
The system may have
Cycle Power: Z stk (G: not be encountered during normal on the original software
Teach pendant is enabled, therefore Disable the teach
MCTL-001 WARN TP is enabled motion control was not granted. pendant, and try the
The teach pendant is disabled, Enable the teach pendant,
MCTL-002 WARN TP is disabled therefore motion control was not and try the operation
The system is in error status, therefore Clear the error by pressing
MCTL-003 WARN system is in error status motion control was not granted. RESET, and try the
Motion control was not granted Wait until the robot
MCTL-004 WARN motion is in progress because otion is still in progress. comes to a complete stop.
Motion control was not granted Make sure all brakes are
MCTL-005 WARN not in control of motion because brakes were engaged. released and try the
The teach pendant currently has the Disable the teach
MCTL-006 WARN TP has motion control motion control, therefore motion pendant, and try the same
PROG has motion The program has the motion control, Pause or abort the
MCTL-007 WARN control therefore motion control was not program, and try the
Operator panel has Becasue the operator panel has the Set the $rmt_master
MCTL-008 WARN motion control motion control, the motion control was system variable correctly,
Other has motion Other device has the motion control, Set the $rmt_master
MCTL-009 WARN control and the motion control was not system variable correctly,
Other than msrc is and hold the SHIFT and
MCTL-010 WARN rel'ing System internal error. RESET keys. 3. While still
MCTL-011 WARN Due to error processing System internal error. RESET keys. 3. While still
subsystem code and hold the SHIFT and
MCTL-012 WARN unknown System internal error. RESET keys. 3. While still
MCTL-013 WARN ENBL input is off ENBL input on the UOP is off. Set ENBL input ON.
The motion control was not granted Wait for a few seconds
MCTL-014 WARN Waiting for Servo ready because servo was not up. until servo is up and
The motion control was not granted Disable the manual brake
MCTL-015 WARN Manual brake enabled because manual brake control is control.
MEMO-000 WARN Success return
MEMO-001 WARN System error
Specified program is in The specified program is being edited Abort the specified
MEMO-002 WARN use or executing. program. Or select it again
Specified program is in The specified program is being edit or Abort the specified
MEMO-003 WARN use executing. program. Or select it once
MEMO-004 WARN use or executing. program. Or select it once
Protection error The specified program is protected by Cancel the protection of
MEMO-006 WARN occurred user.
The specified break number does not the specified
Specify program.
the correct break
MEMO-007 WARN Invalid break number exist. number.
Specified line no. not The specified line number does not Specify a correct line
MEMO-008 WARN exist exist in the specified or default number.
The specified program name is Specify the same program
MEMO-010 WARN Program name error different form that of the P-code file. name.
Program type is The specified program type is different Specify the same program
MEMO-013 WARN different
Specified label already from that of the
The specified object
label being exists in
id already type.
Specify another label
MEMO-014 WARN exists the program. number.
The specified program already exists in Specify another program
MEMO-015 WARN Program already exists the system. name. Or delete the
The number of the programs and Delete unnecessary
MEMO-019 WARN Too many programs routines exceeded the maximum programs or routines.
MEMO-024 WARN System error Set the index to an
MEMO-025 WARN Label does not exist Specified label does not exist. existing label.
The number of line data exceeded the Delete unnecessary line
MEMO-026 WARN Specified
Line data line
is fulldoes not maximum possible line number ( 65535 data. another line
Specify
MEMO-027 WARN exist The specified line data does not exist. number.
The specified line data can't be Specify another line
The line data can't be changed. The size of modified data is number or the data of
MEMO-029 WARN changed different from that of original data same size.
MEMO-032 WARN use or executing. program. Or select it once
The item can't be The specified item is locked to change
MEMO-034 WARN changed by system. Specify another item.
The number of the programs exceeded Delete unnecessary
MEMO-038 WARN Too many programs the maximum number. programs.
MEMO-047 WARN Systempoint
Break errordata The specified break point data does not Specify another break
MEMO-048 WARN doesn't exist exist. point.
The specified program does not exist in Specify another program
MEMO-050 WARN Program does not exist the system. or create the same
MEMO-056 WARN Program does not exist the system. or create the same
The program must be opened with Open the program with
MEMO-061 WARN No write access write access before attempting write write access before
Too many CALL instructions is used. The Abort the unnecessary
Too many opened number of opened programs exceeded programs. Or, remove
MEMO-065 WARN programs the maximum possible number( 100 ). unnecessary CALL
1. The specified program is editing or 1. Abort the specified
Specified program is in executing. 2. The specified program is program. Or select it once
MEMO-068 WARN use entried to MACRO more after select another
MEMO-070 WARN System error The specified position data does not
MEMO-071 WARN Position does not exist exist. Specify another position.
Position data already Position data already exists in the Specify another position.
MEMO-072 WARN exists specified position you want to move. Or, delete the data in the
MEMO-073 WARN Program does not exist The
the system.
operation can be apply only to TPE or create the same
MEMO-074 WARN Program type is not TPE programs. Select a TPE program.
The program must be opened before Open the program before
MEMO-075 WARN Program can't be used attempting read or write operations. reading or writing.
The specified operation is not Specify a program whose
MEMO-078 WARN Program can't be used supported for this program type. program type matches the
Protection error The specified program is protected by Cancel the protection of
MEMO-080 WARN occurred user. the specified program.
Specified program is in The specified program is editing or Abort the specified
MEMO-087 WARN System error The specified position data does not
MEMO-088 WARN Program does not exist exist. Specify another position.
Specified program is in The specified program is editing or Abort the specified
EOF occurs in file access. When P-code The P-code data may be
MEMO-098 WARN EOF occurs in file access file was scaned, EOF occurs. broken. Translate the
The program name length is different Check the program name
MEMO-099 WARN Program name is wrong from that of the P-code data. of the specified program.
Check sum error The specified data was broken. This is and hold the SHIFT and
MEMO-103 WARN occurred the internal error. RESET keys. 3. While still
The specified program already exists in Specify another program
MEMO-104 WARN Program already exists the system. name. Or delete the
Break data already The specified break point data already Specify another break
MEMO-112 WARN exists exists in the program. point.
The port that has the program you Check the port setting and
MEMO-113 WARN File access error want to load is not connected. the connected device.
Break point can't be The break point data can not be Cancel the protection of
MEMO-114 WARN removed overwriten. The program is protected the program. Or, abort
Break point can't be The break point data can not be Cancel the protection of
MEMO-115 WARN removed removed. The program is protected by the program. Or, abort
The specified application data does not Specify another
Application data exist because the program does not application data. Then
MEMO-119 WARN doesn't exist correspond to the specified application. create the program in the
Application data exist because the program does not application data. Create
MEMO-120 WARN doesn't exist correspond to the specified application. the program in the
Application data exist because the program does not application data. Create
MEMO-123 WARN doesn't exist correspond to the specified application. the program in the
Program version is too KAREL program version number is Translate the program
MEMO-124 WARN new newer than that of the system. with an older version of
Program version is too KAREL program version number is older Translate the program
MEMO-125 WARN old more available
No than that of the system. with a newer
Delete version of
unnecessary
MEMO-126 WARN memory Lack of the memory which can be used. programs.
Pos reference over 255 Reference of the same position Set new position ID for
MEMO-127 WARN times exceeded the maximum count (256). the referenced position.
A routine exists in memory with a Update the calling
%s parameters are different parameter definition than the convention in the KAREL
MEMO-128 WARN different routine in the PC file being loaded. program being loaded or
MEMO-129 WARN
SYSTE System error
MEMO-130 M
SYSTE Please power up again The data of the system been broken. Please poweroffupand
Turn power again.
then
MEMO-131 M Please power up again System data in CMOS has been broken.. back on.
Delete the program and
create it again. Press the
Program data has been broken at the RESET key to clear the
MEMO-132 WARN
SYSTE %s has been broken power fail recover. error. If the error
Turn power is not
off and then
MEMO-133 M Please power up again System data in CMOS has been broken.. back on.
TPE program %s already The TPE program which has the same Delete the teach pendant
MEMO-134 WARN exists
Cannot create TPE name
The TPEalready exists.
program cannot be created in (TP) program.
Select Then menu
the function load
MEMO-135 WARN Cannot
programload
hereP-code this start
The KARELmode. to change
program cannot be loaded Select the the start menu
function mode.
MEMO-136 WARN here in this start mode. to change the start mode.
Specified KAREL program cannot be
Load at Control Start loaded in this mode. Because the same Load the program at
MEMO-137 WARN Only name program has already been loaded controlled start.
Specified program has already been
Delete at Control Start loaded at controlled start. Because of Delete the program at
MEMO-138 WARN Only this, you can only delete the program controlled start.
The TPE header size specified is too big. Change size to range of 1-
MEMO-144 WARN Header size too big Must be less than 256. 256. If necessary, use
The routine of the specified program Change the program
has been already referred by the KAREL name, or delete the
program. Because of this, the specified KAREL program which
TPE cannot have KAREL program must be the KAREL program. refers the routine of the
MEMO-145 WARN routine The user
Invalid cannotisuse
variable theinspecified
used the specified specified
Check theprogram.
varialbe used in
MEMO-146 WARN Invalid variable is used KAREL program. the specified KAREL
Flash File access The write access to the Flash File(F- The Flash File(F-ROM)
MEMO-147 WARN error(write) ROM) failed. Some program may be may be broken. Create or
Flash File access The read access to the Flash File(F- The Flash File(F-ROM)
MEMO-148 WARN error(read) ROM) failed. Some program may be may be broken. Create or
Specified program is Please power off and on.
MEMO-149 WARN broken Program data has been broken. Then check the program
No more available Lack of the temporary memory which Delete unnecessary
MEMO-151 WARN memory(TEMP) can be used for the program. programs. Or, change the
Perform one of the
The specified program is being edited following: * Abort the
MEMO-152 WARN Program %s is in use or
Theisunused
executing.
program can not be specified
Cycle powerprogram orthe
and try
MEMO-153 WARN %s is not deleted deleted. operation again.
Parent program still When the parent program exists, the Delete the parent
MEMO-154 WARN exists daughter program cannot be deleted. program before deleting
The total number of positions exceeds Delete the unused
MEMO-155 WARN Too many positions
Renumber program the maximum number(32766). positions.
Cycle power and try the
MEMO-156 WARN failed The renumber operation failed. operation again.
Delete the program and
create it again. Press
Cannot execute this RESET to clear the error. If
MEMO-157 WARN program The specified program is broken. the error is not cleared,
If conversion was
When loading the specified KAREL expected, then no action
program the variable type definition is required. If conversion
required conversion. The program was was not expected, then
MEMO-158 WARN Type converted in %s loaded and converted as needed. maybe the loaded
When loading the specified KAREL See the diagnostic data
program the variable type definition file, FR:KRLCONV.LS, for
required conversion. The variable more information about
reference could not be converted. the specific variable and
MEMO-159 WARN Convert failed in %s Therefore, the program was not loaded program involved.
When loading a KAREL program or Check that there is space
dictionary, a backup copy could not be available on the specified
made to the specified file. The program device. If not, remove
MEMO-160 WARN Save failed for %s or dictionary was loaded into memory. some unneeded files.
If conversion was
When loading the specified KAREL expected then no action is
Converting KAREL program the variable type definition required. If conversion
program %s to version required conversion to the specified was not expected, then
MEMO-161 WARN %s version. maybe the loaded
The type definition for a local variable Translate this program
Line: %d Local variable in a KAREL routine already exists but is using a version of the
MEMO-162 WARN mismatch not handled of a different type than what you are translator that matches
The type definition for a field in a Translate this program
Line: %d Field mismatch structure already exists but is of a using a version of the
MEMO-163 WARN not handled different type than what you are translator that matches
The type definition for a structure in a Translate this program
Line: %d Structure KAREL program already exists but is of using a version of the
MEMO-164 WARN mismatch not handled a different type than what you are translator that matches
The type definition for a structure in a Translate this program
Line: %d First field is KAREL program already exists but the using a version of the
MEMO-165 WARN different first field is different than what you are translator that matches
The type definition for a PATH in a Translate this program
KAREL program already exists but is of using a version of the
MEMO-166 WARN Path conversion failed a different type than what you are translator that matches
Restore of a program failed. See error Consult cause code for
MEMO-167 WARN Restore failed for %s cause code for details. more information.
A file backup was attempted uses the
PROG_BACKUP() builtin. This specific Refer to the remedy on
MEMO-168 WARN Backup failed for %s program failed to backup because of the cause code.
Refer to the remedy on
the cause code. Typically
The program that you attempted to the cause of the error is
clear with the PROG_CLEAR builtin that the program is
MEMO-169 WARN Clear failed for %s failed. selected. In this case,
The program name must be shorter Load the longname option
than eight characters when long by setting
MEMO-170 Program name too long program names are not enabled or $LONGNAM_ENB=TRUE.
FILE programs are write protected Move the program to
FILE program cannot be unless they are in the editor. So you another storage type
MEMO-171 modified cannot modify attributes and other temporarily or
Extended storage The operation requires extended Load extended storage
MEMO-172 feature not loaded storage option to be loaded. option or choose another
Remove unnecessary
programs. If you have less
No more program name than 7500 programs
MEMO-173 space No more program space is available document the events that
The FROM path is not configured or Fix the File path
MEMO-174 FILE path does not exist points to a directory which does nto specification from the
Your TPP program may be
An error has occurred converting a invalid. If the problem
Cannot convert program from DRAM or FILE to persists please document
MEMO-175 program data executable TPP code the events that led to the
FILE program file A TP file in the file directory has been Check the TP FILE
MEMO-176 missing deleted or the resource containing TP programs directory to
If the problem persists
Cannot load ON The ON DEMAND program could not be please document the
MEMO-177 DEMAND
No program
more available loaded events unnecessary
Delete that led to the
MEMO-178 SYSTE DRAM (SHADOW/FILE) Lack of the memory which can be used. programs.
MENT-000 M ME-NET system
PCB noterror System internal error Notify
ME-NET FANUC
board is installed
MENT-001 WARN installed
SYSTE ME-NET board is not installed .
MENT-002 M
SYSTE ME-NET PCB abnormal
Communication CPU ME-NET baoard is abnormal. Check ME-NET board
MENT-003 M
SYSTE ROM abnormal CPU
Communication Communication CPU ROM is abnormal. Check ME-NET board
MENT-004 M
SYSTE RAM abnormal CPU LSI
Communication Communication CPU RAM is abnormal. Check ME-NET board
MENT-005 M
SYSTE abnormal
More than one taken Communication CPU RAM is abnormal. Check ME-NET board
MENT-006 M
SYSTE occured
Duplicate address was More than one taken occured. Check ME-NET board
MENT-007 M detected duplicate address was detected. Check ME-NET board
SYSTE My station Transmitter
MENT-008 M
SYSTE broke down My station Transmitter broke down. Check ME-NET board
MENT-009 M
PAUSE. Taken not come around Taken not come around. Check ME-NET board
MENT-010 G
PAUSE. Type 3 buffer
Data-link overflow
TX length Type 3 buffer overflow. Check ME-NET
ME-NET'sboard
system
MENT-011 G
PAUSE. abnormal
Relay-link TX length Data-link TX length is abnormal. variable.
Check ME-NET's system
MENT-012 G
PAUSE. abnormal
Register-link TX length Relay-link TX length is abnormal. variable.
MENT-013 G
PAUSE. abnormal
Relay-link RX offset register-link TX length is abnormal. variable.
MENT-014 G
PAUSE. abnormal
Register-link RX offset Relay-link RX offset is abnormal. variable.
MENT-015 G
PAUSE. abnormal register-link RX offset is abnormal. variable.
MENT-016 G RX frame ID abnormal RX frame ID is abnormal. variable.
PAUSE. Communication CPU no Even if 60 seconds pass, a logical link
MENT-017 G
PAUSE. response was construction
The not able to beofjoined
the media is Check ME-NET
Improve board
the construction
MENT-018 G
PAUSE. Frame length error defective
The construction of the media is of the media
Improve the construction
MENT-019 G Media defective defective of the media
Program cannot run because an error
Cannot resume condition will not clear. When on the Fix the error condition,
MHND-001 WARN program ALARM page, select this error and press press reset,
Operator Panel E-stop Program cannot run with operator Release Operator panel E-
MHND-002 PAUSE ON panel E-STOP stop, press reset and push
Teach pendant E-stop Program cannot run with teach Release teach pendant E-
MHND-003 PAUSE ON pendant E-STOP stop, press reset and push
Teach pendant is Program cannot run with teach Disable teach pendant,
MHND-004 PAUSE enabled pendant enabled press reset, and push
System still in fault An error condition exists such that the Fix the error condition,
MHND-005 PAUSE state robot cannot be reset. press reset.
To run a .tp program in local you must Press SELECT key and
MHND-006 WARN Program not selected first select the program. choose a program to run.
UOP Ignored. Wrong A UOP signal was detected, but the UOP must be set as the
MHND-007 WARN Start Mode controller is not set up to start using start device or the UOP
SOP Ignored. Wrong A SOP signal was detected, but the SOP must be set as the
MHND-008 WARN Start Mode controller is not set up to start using start device or the SOP
While M.H. Shell was internally trying
MHND-009 WARN Could not run task %s to run another program in multi- ABORT ALL and retry.
An old smaller POSREG.VR file was M.H. Shell logic has
loaded onto the controller. The number automatically set the
Cycle power to change of position registers was changed to number of position
MHND-010 WARN registers fewer than what the current version of registers to the necessary
An old smaller SYSMACRO.SV file was M.H. Shell logic has
Cycle power to change of macros was changed to fewer than number of macros to the
MHND-011 WARN macros what the current version of M.H. Shell necessary size again. But
TEMP DRAM memory is Temporary memory is getting too low Warning only. Delete any
MHND-012 WARN low to
Thedownload more
robot must files.
be calibrated unneeded data before
to run tp
MHND-013 PAUSE Robot is not calibrated programs. Calibrate the robot.
Robot must be at home The At home check function is enabled Move the robot to the
MHND-014 PAUSE position but the robot is not at the home home position. Once the
Select SETUP, [TYPE], Ref
Position. Make sure the
The At home check function is enabled selected Refpos is taught
HOME refpos not but the Home refpos has not been fully and enabled. Select
MHND-015 PAUSE taught setup. SETUP, [TYPE], Shell
REMOTE switch must The REMOTE keyswitch is on LOCAL, Turn the REMOTE
MHND-016 WARN be REMOTE and needs to be set to REMOTE. keyswitch to REMOTE.
UOP is not the master The UOP is not the master device, Go the the Variables
MHND-017 WARN device which prevents the run request from menu under SYSTEM, and
Load or create the
program. If the program
The program that you tried to run is name shown in the error
MHND-018 WARN Program %s not loaded not loaded on the controller. code is wrong, then check
Robot mode must be The robot mode is not MANUAL, so the The manual mode din
MHND-019 WARN MANUAL operation requested cannot be from the PLC is set OFF. It
Robot must be in AUTO The robot must be in full automatic The manual mode din
MHND-020 WARN mode mode with the PLC before production from the PLC is set ON. It
On manual mode entry - Manual mode
Robot is in MANUAL input from the PLC just turned ON. All
MHND-021 WARN mode PLC manual mode input functions are Status message only.
On manual mode exit - Manual mode
input from the PLC just turned OFF. All
MHND-022 WARN Robot is in AUTO mode PLC manual mode input functions are Status message only.
When the robot is idle,
Robot is busy. Mode Robot mode is being changed while the change the manual mode
MHND-023 WARN change pending. robot is busy bit again to the desired
Step mode must be Step mode is enabled, which prevents Press the STEP hardkey to
MHND-024 WARN disabled the run request from executing. disable step mode.
None available. This error
is only generated if your
Cell interface has been
UOP CYCLE START can A UOP CYCLE START input was detected specified using
MHND-025 WARN only resume but no paused program exists. $shell_cfg.$cont_only=TR
A DIN program select was detected but Check the keyswitch
Illegal DIN program either the keyswitch is not in remote or settings. Check the
MHND-026 WARN %s
select received
program select the selected program does not exist. program selected.
MHND-027 WARN signal received A program select was detected. Status message only.
A PNS program select was detected but Check the keyswitch
Illegal PNS program either the keyswitch is not in remote or settings. Check the
MHND-028 WARN select received the selected program does not exist. program selected.
A GIN program select was detected but Check the keyswitch
Illegal GIN program either the keyswitch is not in remote or settings. Check the
MHND-029 WARN select received the selected program does not exist. program selected.
A RSR program select was detected but Check the keyswitch
Illegal RSR program either the keyswitch is not in remote or settings. Check the
MHND-030 WARN select received the selected
The program
cycle interrupt doeshas
option notbeen
exist. program
This selected.
is a status message
MHND-031 WARN Cycle interrupt disabled disabled.
The cycle interrupt option has been only.
This is a status message
MHND-032 WARN Cycle interrupt enabled enabled. only.
DIN Ignored. Wrong A DIN signal was detected, but the DIN must be set as the
MHND-033 WARN Start Mode controller is not set up to start using start device or the DIN
The job selection setup was not Go to the MENU, SETUP,
%s Job select setup completed properly. Selected I/O does Shell Config menu and
MHND-034 WARN error not exist. make sure the TP program
A start signal was received but a TP
Start Ignored. Already program is already running. A second
MHND-035 WARN running TP program will not be started at this Informative message only.
The menu test screen is displayed on Display a different menu
START Ignored. Menu the TP. A TP program cannot be started on the TP and give
MHND-037 WARN Testing. until a different screen is displayed. another start signal.
MULTIIO.TP is not running. It will be If MULTIIO.TP does not
MHND-038 WARN %s is not running. restarted. automatically restart,
Cycle power to change The new number of user alarms will not
MHND-039 WARN user alarms take effect until after a cold start. Informative message only.
Cycle power to change The new number of tasks will not take
MHND-040 WARN no of tasks effect until after a cold start. Informative message only.
CMOS memory is getting too low to Warning only. Delete any
MHND-041 WARN Perm memory is low create
A more variable
customized files. was
pause error unneeded data.
MHND-100 PAUSE %s detected. Follow instructions given.
MHND-101 PAUSE Reg %s could not be set Register operation failed defined, if it is between 1-
MHND-102 WARN %s General status messages. N/A
MHND-103 PAUSE Register not defined %s This is just a debug message N/A
MHND-104 WARN %s General status messages. N/A
MHND-105 ABORT %s General status messages. N/A
Controller has no UOPs The controller has no UOPs installed. So Check Hardware
MHND-106 WARN assigned. you cannot select UOPs for job installation.
Macro Table is too The MACRO table must have at least Increase the MACRO table
MHND-107 WARN small for menu option 100 elements for the MENU UTILITY size.
MHND-108 ABORT Aborting TP program An error occurred in the TP program. Check the TP program.
There was a problem loading the Check the communication
MHND-120 WARN Loading error - %s specified
The file. file already exists on the
specified line andthe
Delete make
file sure
fromthat
the
MHND-121 WARN %s exists. Not loaded controller.
Data in a setup menu could not be controller before
Cold start the controller
MHND-122 PAUSE CREATE_VAR
File failed
not loaded or %s created
File does not exist in the controller and retry.
MHND-123 WARN created: %s RAM. This isstart
Cold a warning message.
the controller
MHND-124 PAUSE GET_VAR failed %s Data in a setup menu could not be set and retry.
MHND-125 PAUSE SET_VAR failed
IO_STATUS error%s Data
An I/Oinerror
a setup menu could
occurred duringnot be set
data and retry.
MHND-127 WARN occurred
Could not save .VR file transfer and retry.
MHND-128 WARN %s Error occurred while saving a .VR file and retry.
MHND-129 WARN Could not load file %s Error occurred while loading a .VR
accessing the file and
Make retry
sureifthe
you know you
MHND-130 WARN Error
Couldusing
not access
CLEARfiles
built- floppy
An disk
error occurred while clearing a communication
Reset controller isandcorrect
try
MHND-133 WARN in variable file. again.
The file you requested to transfer is First stop the robot. Then
File is in use by robot. being used by the robot. It is being ABORT ALL. Then attempt
MHND-134 WARN Cannot transfer used in production or is being edited to transfer
Check the communication
MHND-135 WARN Could not read %s Could not read the .dt file - Data error. status.
If the file is being used in production it Wait until production is
MHND-136 WARN Could not clear file cannot be cleared. aborted and clear the file.
.VR file has not been During the transfer of data from the PC, Check the available
MHND-137 WARN created the .VR data
An error file could
occurred not
while be created.
creating the memory.
Cold startIftheRAM is full,
controller
MHND-138 PAUSE Could not create .vr file file and retry.
Check the available
Error creating new An error occurred while creating a new memory. If RAM is full,
MHND-139 WARN variables file. clear unneeded data and
Robot in use-Cannot You cannot TEST a menu when the All menu changes should
MHND-160 WARN Error:
TEST menu.
tp program not robot
The is menu
List executing
test aattempted
TP program.
to run a be made
Reset thewhen the robot
controller and
MHND-161 WARN running
doing unpause in tp program. try again.
MHND-162 WARN doing
prompt box
continue in Status debug message only. N/A
MHND-163 WARN prompt box Status debug message only. N/A
MHND-164 WARN %s Illegal type that is illegal. The parameter has the the TP program.
MHND-165 WARN %s missing parameter that must be entered. the TP program.
Status Menu does not A Status Macro used a string name for Check the MACRO call in
MHND-166 WARN exist a menu that does not exist. the TP program.
PLC not reading alarm The PLC is not handshaking with the Check PLC status. Clear
MHND-200 WARN outputs robot to send alarms to the PLC. the PLC alarms.
Error:too many entries At most 100 alarms can be entered into
MHND-201 WARN in alarm table the PLC alarm table. Other alarms will Extra alarms are ignored.
A fault has ocurred, so the operation Clear the source of the
MHND-230 WARN FAULT must be reset requested cannot be performed. fault, and press FAULT
Program already A program is already running, so the Re-issue the request when
MHND-231 WARN running or paused operation requested cannot be the current program is
Teach pendant must be The teach pendant must be enabled
MHND-232 WARN enabled when accessing this teach pendant Enable the teach pendant.
TP hardkey macros are One of the MH gripper macros is Wait until the current
MHND-233 WARN Valve
in use %s: Manual grip already in use. Only one macro can be macro is finished.
MHND-234 WARN Valve
part %s: Manual Information message only N/A
MHND-235 WARN release Information message only N/A
Error: Valve is not The valve signal number (S#) can not be Select MENU, I/O, MH
MHND-236 WARN setup. zero. Valves to setup the
Error: Clamp is not The clamp signal number (S#) can not Select MENU, I/O, MH
MHND-237 WARN setup. be zero. Valves to setup the
Error: PartPres is not The part present signal number (S#) can Select MENU, I/O, MH
MHND-238 WARN setup. not be zero. Valves to setup the
Error: Vacuum Made is The vacuum made signal number (S#) Select MENU, I/O, MH
MHND-239 WARN not setup. can not be zero. Valves to setup the
MHND-240 ABORT %s missing parameter that must be entered. the TP program.
MHND-241 WARN %s Illegal type that is illegal. The parameter has the the TP other
Check program.
alarm log
MHND-242 WARN Parameter %s error Send PC Macro data error. errors other
Check for more details.
alarm log
MHND-243 PAUSE %s I/O error I/O data error.
A MACRO was called with too many errors for more details.
Check the MACRO call in
MHND-244 WARN Parameter
Valve %s is %s
notignored
a parameters. the TP the
Check program.
MACRO call in
MHND-245 ABORT vacuum
Valve %sgripper
is not a clamp This MACRO requires a vacuum gripper. the TP the
Check program.
MACRO call in
MHND-246 ABORT gripper This MACRO required a clamp gripper. the TP program.
Parm %s is not between Parameter passed to MH macro is not Change parameter to an
MHND-247 ABORT 1-2 between 1 and 2. The valve referenced integer between 1 and 2
TRYOUT MODE: %s In TRYOUT mode: The part present There must be no part
MHND-248 PAUSE reading part input does detect the signal present in tryout mode.
Must press SHIFT key The shift key must be pressed when
MHND-249 WARN too
Parm %s is not an accessing
Parameterthis teachtopendant
passed hardkey.
MH macro Press
is not
Change theparameter
shift key. to an
MHND-250 ABORT integer
Parm %s is not between an integer passed to MH macro is not
Parameter integer parameter to an
Change
MHND-251 ABORT 1-9 between
Valve 1 andby
selected 9 paramter has not integerappropriate
Enter between 1 and 9
MHND-252 ABORT Valve %s is not setup
No parameters passed been setup
No parameters have been passed to information
Place parameter through user
in the list
MHND-253 ABORT to routine the routine
The part present input does not detect following
Check theismacro
if part callof
in range
MHND-254 PAUSE %s not sensing part the signal
The part present input sees the signal the switch
Ensure robot has dropped
MHND-255 PAUSE %s still reading part after dropoff off the part
Check if all the clamp has
MHND-256 PAUSE Clamp %s state error The specified clamp open signal failed. is obstructed or the
Check if all the clamp has
MHND-257 PAUSE Clamp
%s did %s
notstate
makeerror specifiedswitch
The vacuum clampisclosed signal failed. Check
not detecting is obstructed or vacuum
all of the the
MHND-258 PAUSE vacuum vacuum.
The vacuum switch is still detecting cups for a complete
Check if all the clamps seal.
MHND-259 PAUSE %s vacuum
Parm is not
%s is not off
between vacuum. passed to MH macro is not Change
Parameter have completely
parameter closed.
to an
MHND-260 ABORT 1-10 between 1 and 10 integer between 1 and 10
ERRORS: Check Fix data and try again to
MHND-261 WARN FR:GRERRORS.LS File FR:HTVALVE contains errors. gripper CONFIG.
The Macro Table was The MACRO table was reloaded and is Must coldstart to
MHND-262 WARN updated. now too small. The table size has been physically increase the
Check Clamp Opened or Check Clamp Either disable the Clamp
Check Clamp Enabled Closed is enabled. An Operation Delay Checks or set a reasonable
MHND-264 WARN but delay=0.
This is English element of 0 ms is not enough time to allow the Clamp Operation Delay.
MIGE-000 WARN
ABORT. 0
MIGE-001 LABORT. Internal Error (system)
MIGE-002 L Internal Error
Unknown (avst)
packet was
MIGE-003 WARN received
Fail to comm to vision
MIGE-004 WARN
ABORT. CPU
MIG-EYE Internal Error
MIGE-005 LABORT. (PMPT)
MIGE-006 LABORT. (INTR)
MIGE-007 LABORT. (PMPT2)
MIGE-008 LPAUSE. Internal Error (SRIF)
MIGE-010 LABORT. Sensor does not exsist
MIGE-011 LABORT. Can't solve LSM
MIGE-012 LABORT.
MIGE-013 LPAUSE. Invalid LSM Parameter
MIGE-014 L Sensor is turned off
MIGE-015 WARN
ABORT. Over Offset Data Range
MIGE-016 LPAUSE.
MIGE-017 LPAUSE. Sensor on/off failed
MIGE-018 LABORT. Search jointdebug
Fail to start failed
MIGE-019 LPAUSE. utility
MIGE-020 LPAUSE. Track start failed
MIGE-021 L Track End failed
MIGE-022 WARN
ABORT. Sensor is working
MIGE-023 LABORT. Bad task status
MIGE-024 L Receive bad sensor data
MIGE-025 WARN
PAUSE. Can't detect joint
MIGE-026 LPAUSE. Buffer lengthjoint
Can't detect error
MIGE-027 LABORT. continuously
MF buffer index
MIGE-028 LPAUSE. overflow
Can't track this motion
MIGE-029 LPAUSE. type
Schedule number is
MIGE-030 LABORT. wrong
Invalid sensor data
MIGE-031 LPAUSE. (internal)
Rotator axis data
MIGE-032 LABORT. incorrect
MIGE-033 LPAUSE. Invalid calculation
MIGE-034 LABORT. Path
Can'tpoints too close
track with this
MIGE-035 LPAUSE. command
MIGE-036 LPAUSE. Track
No MIG calculation
EYE data fault
in
MIGE-037 LPAUSE. buffer
Can't calculate track
MIGE-038 LPAUSE. offset
MIGE-039 LPAUSE. Offset
Gap is too large
exceeds max in
MIGE-040 LPAUSE. Adapt Sch
MIGE-041 L Invalid
Arc adapt is
software schedule
not
MIGE-042 WARN installed
ABORT. Invalid command
MIGE-043 LPAUSE. executed
Invalid Search Type
MIGE-044 L
PAUSE. specified
MIGE-045 LPAUSE. Search points
Fail to turn ontoo close
Digital
MIGE-046 LPAUSE. Output
Illegal search schedule
MIGE-047 LPAUSE. number
Cannot use OFFSET in
MIGE-048 LPAUSE. this case
Illegal position
MIGE-049 LPAUSE. representation
MIGE-050 L Cannot preplan
OFFSET START isOFFSET
not
MIGE-051 WARN executed
Duplicate OFFSET
MIGE-052 WARN
PAUSE. START position
Illegal executedregister
MIGE-053 LPAUSE. number
Uninit position register
MIGE-054 LPAUSE. used
MIGE-055 LABORT. Track ready for resume
MIGE-056 LABORT. Can't
Invalidturn on/off
offset datasensor
MIGE-057 LABORT. (internal)
Segment buffer index
MIGE-058 LPAUSE. overflow
MIGE-059 LPAUSE. Invalid
No offsetcircler
datanumber
is
MIGE-060 LPAUSE. available
MIGE-061 LPAUSE. Mpass start failed
MIGE-062 LPAUSE. Mpass end failed
Buffer number is not
MIGE-063 LPAUSE. correct
Can't use MIG EYE in
MIGE-064 LPAUSE. this group
MIGE-065 LPAUSE. Lack ofweld
Adapt received data
calculation
MIGE-066 LPAUSE. fault
MIGE-067 L Invalid adaptive type
MIGE-068 WARN
PAUSE. Lack of received data
MIGE-069 LABORT. Invalid datacan
Parameter is received
not be
MIGE-070 LPAUSE. changed
Vision system error
MIGE-100 LPAUSE. (Ext.)
Vision system error
MIGE-101 LPAUSE. (Camera)
Vision system error
MIGE-102 LPAUSE. (Temp.)
Comm. error (V:Bad
MIGE-103 LPAUSE. checksum)
Comm. error (V:Time
MIGE-104 LPAUSE. out)
Comm. error (V:Bad
MIGE-105 LPAUSE. end)
Comm. error
MIGE-106 LPAUSE. (V:Unknown
Vision: Unknown command)
MIGE-107 LPAUSE. parameter
Vision: Value out of
MIGE-108 LPAUSE. range
Joint number out of
MIGE-109 LPAUSE. range
Comm. error
MIGE-110 LPAUSE. (H:Hardware)
Comm. error (H:DSR
MIGE-111 LPAUSE. off)
Comm. error
MIGE-112 LPAUSE. (H:Unknown
Comm. error command)
(H:Bad
MIGE-113 LPAUSE. checksum)
Comm. error (H:Data
MIGE-114 LPAUSE. format)
Comm. error (H:Time
MIGE-115 LPAUSE. out)
MIGE-116 LPAUSE. Laser is Port
Comm. not ONis not
MIGE-117 LPAUSE. initialize
MIGE-118 LPAUSE. Message type mismatch
MIGE-119 L Joint ID mismatch
PAUSE. Detection Algorithm
MIGE-120 L mismatch
The system may have
Internal system error. This class of error have been caused by any
should not be encountered by the user of a number of reasons
MOTN-000 WARN Unknown error (MO00) during normal operation including: Incorrect
Internal error in Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-001 WARN osmkpkt should not be encountered by the user 000
PAUSE. Internal error in Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-002 G ossndpkt should not be encountered by the user 000
MOTN-003 G oswrtmbx should not be encountered by the user 000
PAUSE. Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-004 G Internal error in ossigflg should not be encountered by the user 000
MOTN-005 G Internal error in osclrflg should not be encountered by the user 000
MOTN-006 G osrcvpkt should not be encountered by the user 000
MOTN-007 G osredmbx should not be encountered by the user 000
MOTN-008 G oswaiflg should not be encountered by the user 000
PAUSE. Normal Single Step / System executes normal Single Step or This is a normal condition.
MOTN-009 G BWD stop Backward motion stop No action is required
MOTN-010 G osathpkt should not be encountered by the user 000
MOTN-011 G
PAUSE. osdltpkt should not be encountered by the user 000
Make sure the correct
MOTN-012 G
PAUSE. Invalid softpart MIR Invalid softpart MIR basic motion
Make sure thesoftpart
correctis
MOTN-013 G Invalid softpart SEG Invalid softpart SEG basic motion softpart is
Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-014 WARN unknown error (MO14) should not be encountered by the user 000
MOTN-016 WARN
PAUSE. unknown
Limit errorerror (MO16)
(G:%d^2, should not be encountered by the user 000
Reteach the position out
MOTN-017 G
PAUSE. A:%x^3 Hex) Limit error
Position not reachable Or near by of limits
Reteach the position that
MOTN-018 G Position not reachable singularity is not reachable
Reteach the position that
MOTN-019 WARN In singularity Position near by singularity is near a singularity point.
MOTN-020 WARN
PAUSE. Wristjoint warning Wrist joint warning Wrist joint warning
MOTN-021 G
PAUSE. No kinematics error No kinematics Use joint motion
MOTN-022 G
PAUSE. Invalid limit number Invalid limit number Set limit the
Reteach number correctly
position that
MOTN-023 G
PAUSE. In singularity The position is near a singularity point. is near a singularity point.
MOTN-024 G Kinematics not defined Kinematics is not defined Define Kinematics
MOTN-029 G unknown error (MO29) should not be encountered by the user 000
MOTN-030 G MMGR:PEND should not be encountered by the user 000
MOTN-031 G MMGR:ESEG should not be encountered by the user 000
MOTN-032 G MMGR:PRSD should not be encountered by the user 000
MOTN-033 G MMGR:GNL should not be encountered by the user 000
MOTN-034 G MMGR_MMR should not be encountered by the user 000
MOTN-035 G MMGR_MIR should not be encountered by the user 000
MOTN-036 G MMGR:MSTR should not be encountered by the user 000
MOTN-037 G MMGR:MDON should not be encountered by the user 000
MOTN-038 G MMGR:CAN should not be encountered by the user 000
MOTN-039 G MMGR:FCAN should not be encountered by the user 000
MOTN-040 G MMGR:CAND should not be encountered by the user 000
MOTN-041 G MMGR:PSTR should not be encountered by the user 000
MOTN-042 G Internal in MSSR should not be encountered by the user 000
MOTN-043 G MMGR:EPKT should not be encountered by the user 000
MOTN-044 G MMGR:ERR should not be encountered by the user 000
Internal error in pro. Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-045 WARN start should not be encountered by the user 000
MOTN-046 G MMGR:LSTP should not be encountered by the user 000
MOTN-047 G MMGR:PRST should not be encountered by the user 000
MOTN-048 G
PAUSE. Attempt to move w/o should not be encountered by the user
unknown error (MO48) 000
MOTN-049 G
PAUSE. calibrated
Invlaid spdlim (G:%d^2 Robot not calibrated Calibrate
Set the robot.
$SPEEDLIMJNT
MOTN-050 G A:%x^3
PAUSE. Speed outH) of range Invalid joint speed limit correctly
MOTN-051 G (G:%d^2) out of range Speed out of range
PAUSE. Jntvellim Set speed correctly
MOTN-052 G (G:%d^2) Joint vel limit out of range Set $JNTVELLIM correctly
PAUSE. Internal planner error Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-053 G
PAUSE. (G:%d^2)
Uninitialized dest pos should not be encountered by the user 000
MOTN-054 G
PAUSE. (G:%d^2)
Uninitialized via pos Uninitialized destination position Teach destination position
MOTN-055 G (G:%d^2) Uninitialized via position Teach via position
Speed limits used This is just a notification.
MOTN-056 WARN (G:%d^2) Speed limits used You do not have to do
PAUSE. and hold the SHIFT and
MOTN-057 G Invalid mir (G:%d^2) Invalid packet received by planner RESET keys. 3. While still
PAUSE. Invalid cancel request Invalid cancel request received by and hold the SHIFT and
MOTN-058 G (G:%d^2) planner RESET keys. 3. While still
PAUSE. Null segment received Planner received null seg when not and hold the SHIFT and
MOTN-059 G
PAUSE. (G:%d^2)
Uninitialized base vec expecting one
Uninitialized base vector in relative RESET keys. 3. While still
MOTN-060 G
PAUSE. (G:%d^2)
Uninitialized distance moves Initialize base vector
MOTN-061 G (G:%d^2) Uninitialized distance in relative moves Initialize distance
PAUSE. Invalid position type Invalid position type received by and hold the SHIFT and
MOTN-062 G (G:%d^2) planner RESET keys. 3. While still
Reteach the destination
PAUSE. Position config change position so that its
MOTN-063 G (G:%d^2) Configuration mismatch configuration string
PAUSE. Rs orientation error and hold the SHIFT and
MOTN-064 G (G:%d^2) RS orientation planning error RESET keys. 3. While still
PAUSE. AES orientation error and hold the SHIFT and
MOTN-065 G
PAUSE. (G:%d^2) circle
Degenerate AES orientation planning error RESET keys.
Reteach 3. While still
via and/or
MOTN-066 G (G:%d^2) Degenerate circle destination positions
PAUSE. Ata2 error in circle Internal system error during circular and hold the SHIFT and
MOTN-067 G
PAUSE. (G:%d^2)
Invalid Prgoverride planning RESET
Set keys. 3. While
$prgoverride still0
within
MOTN-068 G (G:%d^2) Prgoverride is not within 0 to 100 to 100
PAUSE. Error in mocmnd Internal error: planner received invalid and hold the SHIFT and
MOTN-069 G (G:%d^2) mocmnd RESET keys. 3. While still
PAUSE. Error in motype Internal error: planner received invalid and hold the SHIFT and
MOTN-070 G (G:%d^2) motype RESET keys. 3. While still
PAUSE. Error in termtype Internal error: planner received invalid and hold the SHIFT and
MOTN-071 G (G:%d^2) termtype RESET keys. 3. While still
PAUSE. Error in segtermtype Internal error: planner received invalid and hold the SHIFT and
MOTN-072 G (G:%d^2) segtermtype RESET keys. 3. While still
PAUSE. Error in orientype Internal error: planner received invalid and hold the SHIFT and
MOTN-073 G
PAUSE. (G:%d^2) orientype RESET keys.
Set speed 3. While
within 0 tostill
MOTN-074 G
PAUSE. speed (G:%d^2)
Error in rotspeed Speed is not
Rotspeed within
is not 0 to0$speedlim
within to $speedlim
Set Rotspeed within 0 to
MOTN-075 G
PAUSE. (G:%d^2)
Error in contaxisvel $rotspeedlim $rotspeedlim
Set contaxisvel to within 0
MOTN-076 G
PAUSE. (G:%d^2)
Error in seg_time Contaxisvel is not within 0 to 100 to 100
MOTN-077 G
PAUSE. (G:%d^2)
Error in accel_ovrd Seg_time is negative seg_time positive
Set accel_ovrd within 0 to
MOTN-078 G (G:%d^2) Accel_ovrd greater than 500 500
PAUSE. Error in accu_num Internal error: planner received invalid and hold the SHIFT and
MOTN-079 G
PAUSE. (G:%d^2)
Via position required accu_num RESET keys. 3. While still
MOTN-080 G (G:%d^2) Missing via position for circular motion Teach via position
PAUSE. Extended position error Internal error: planner received invalid and hold the SHIFT and
MOTN-081 G (G:%d^2) extended position representation RESET keys. 3. While still
PAUSE. Null mir pointer and hold the SHIFT and
MOTN-082 G (G:%d^2) NULL MIR pointer RESET keys. 3. While still
PAUSE. Illegal SEG recvd Internal error: planner received and hold the SHIFT and
MOTN-083 G (G:%d^2) segment belonging to another group RESET keys. 3. While still
PAUSE. Illegal CONSEG recvd and hold the SHIFT and
MOTN-084 G (G:%d^2) Not used RESET keys. 3. While still
PAUSE. Error in Internal error: planner received invalid and hold the SHIFT and
MOTN-085 G gp_concurrent(G:%d^2) mmr.gp_concurrent RESET keys. 3. While still
PAUSE. Not all CON_SEGs Group motion: not all segments are and hold the SHIFT and
MOTN-086 G
PAUSE. recvd(G:%d^2)
Utool change not received RESET
Do notkeys.
change3. While
$utoolstill
for
MOTN-087 G
PAUSE. allowed(G:%d^2)
Not cartesian move $utool is changed before move this move
Must set motype to
MOTN-088 G (G:%d^2) Motype is not cartesian cartesian
PAUSE. Segment not planned Internal plan error:seg in list not all and hold the SHIFT and
MOTN-089 G (G:%d^2) planned RESET keys. 3. While still
PAUSE. and hold the SHIFT and
MOTN-090 G MIR mismatch (G:%d^2) Internal plan error:mir mismatch RESET keys. 3. While still
PAUSE. Va orientation error and hold the SHIFT and
MOTN-091 G (G:%d^2) Internal plan error:atan2 error RESET keys. 3. While still
PAUSE. Extended not and hold the SHIFT and
MOTN-092 G supported (G:%d^2) Extended axes not supported RESET keys. 3. While still
PAUSE. Internal PLAN blend Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-093 G err(G:%d^2) should not be encountered by the user 000
PAUSE. Blend corner too big and hold the SHIFT and
MOTN-094 G (G:%d^2) Not used RESET keys. 3. While still
Can't blend corner Warning, there is not enough distance If corner blending is still
MOTN-095 WARN line:%d^5 to perform corner blending required for the line
PAUSE. Cart rate not Intellitrak On: $linear_rate and Set $linear_rate equal to
MOTN-096 G equal(G:%d^2) $circ_rate must be equal $circ_rate. cycle power
INTR overrun %d^3 and hold the SHIFT and
MOTN-097 WARN (G:%d^2) Interpolator overrun RESET keys. 3. While still
If arc bigger than half
circle is intended use two
or more Circular
PAUSE. Taught points define an arc larger than instructions to teach the
MOTN-098 G Circle angle too large half circle circle. If the intended arc
PAUSE. INTR Fail to get MIRPKT Internal interpolator error:failed to and hold the SHIFT and
MOTN-099 G (G:%d^2) receive mir when expecting one RESET keys. 3. While still
PAUSE. INTR Fail to get FDO Internal interpolator error:failed to and hold the SHIFT and
MOTN-100 G (G:%d^2) receive fdo when expecting one RESET keys. 3. While still
PAUSE. MIR list is empty Internal interpolator error: mir list is and hold the SHIFT and
MOTN-101 G (G:%d^2) empty when it shouldn't be RESET keys. 3. While still
PAUSE. SEG list is empty Internal interpolator error: seg list is and hold the SHIFT and
MOTN-102 G (G:%d^2) empty when it shouldn't be RESET keys. 3. While still
PAUSE. Send ENB pkt fail Internal interpolator error: error in and hold the SHIFT and
MOTN-103 G (G:%d^2) sending ENB packet RESET keys. 3. While still
PAUSE. Send DSB pkt fail Internal interpolator error: error in and hold the SHIFT and
MOTN-104 G (G:%d^2) sending DSB packet RESET keys. 3. While still
PAUSE. Send TRG pkt fail Internal interpolator error: error in and hold the SHIFT and
MOTN-105 G (G:%d^2) sending TRG packet RESET keys. 3. While still
Internal interpolator error: process the teach pendant, press
PAUSE. Process motion done motion had completed without being and hold the SHIFT and
MOTN-106 G (G:%d^2) restarted RESET keys. 3. While still
PAUSE. Internal interpolator error: invalid filter and hold the SHIFT and
MOTN-107 G Bad filter type (G:%d^2) type received RESET keys. 3. While still
PAUSE. INTR seglist error Internal interpolator error: error in seg and hold the SHIFT and
MOTN-108 G (G:%d^2) list management RESET keys. 3. While still
PAUSE. Internal INTR error Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-109 G (G:%d^2) should not be encountered by the user 000
PAUSE. Use FINE in last L Cannot replan joint motion in Use FINE in last L
MOTN-110 G (G:%d^2) interpolator for this move statement
Can't switch Warning message to indicate that This is just a notification.
MOTN-111 WARN
ABORT. filter(G:%d^2)
Increment move turn switch filter cannot
Incremental motiontake place
causes turn You do not
Change have to do
position
MOTN-112 G Mismatch number mismatch absolute position
MOTN-113 WARN Robot not calibrated Robot not calibrated Calibrate the robot
MOTN-114 WARN Servo isbrake
Invalid on (G:%d^2)
mask Servo in still on Turn off servo
MOTN-115 WARN (G:%d^2) Invalid brake mask Check brake mask
Invalid solution
MOTN-116 WARN (G:%d^2) Invalid kinematics solution reteach position
Robot not mastered Master the robot. Refer to
MOTN-117 WARN (G:%d^2) Robot not mastered the Setup and Operations
Robot in over travel Reset over travel jog the
MOTN-118 WARN (G:%d^2) Robot in overtravel robot outside over travel
MOTN-119 WARN Invalid
Servo isreference
off (G:%d^2) Robot servo is on Turn off servo
MOTN-120 WARN position (G:%d^2)
Invalid config. string Invalid reference position Check reference position
MOTN-121 WARN (G:%d^2) Invalid config string Reteach your config string
PAUSE. Dfilter not empty and hold the SHIFT and
MOTN-122 G (G:%d^2) System internal error RESET keys. 3. While still
Not enough node and hold the SHIFT and
MOTN-123 WARN (G:%d^2) System internal error RESET keys. 3. While still
PAUSE. INTR:Bad Mirpkt and hold the SHIFT and
MOTN-124 G req_code(G:%d^2) System internal error RESET keys. 3. While still
PAUSE. INTR got illegal pkt and hold the SHIFT and
PAUSE. Can't init CH KPT and hold the SHIFT and
PAUSE. Can't detatch CH PKT and hold the SHIFT and
PAUSE. Group mtn not and hold the SHIFT and
MOTN-128 G supported(G:%d^2) Group motion not supported RESET keys. 3. While still
PAUSE. Local cond ptr and hold the SHIFT and
MOTN-129 G conflict(G:%d^2) Conflict in local condition list pointers RESET keys. 3. While still
PAUSE. Non-empty local cond Local condition list attached to SEG is and hold the SHIFT and
MOTN-130 G
PAUSE. list(G:%d^2) not NULL RESET
Reteachkeys. 3. While
position thatstill
is
MOTN-131 G In singularity Position near by singularity near a singularity point.
PAUSE. Group circ not Group motion: circular motype for all
MOTN-132 G supported(G:%d^2) groups not supported Reteach motype
Time after limit Local condition time after value is too No corrective action
MOTN-133 WARN
PAUSE. used(G:%d^2)
Can not move path big. Systempath/subpath
Backward will use timemotion
after limit This
is not required
Remove backward
MOTN-134 G
PAUSE. backward
Last motype(G:%d^2)
can't be supportedlast node motype can not be
Backward command
MOTN-135 G circular (G:%d^2) circular Change last node motype
Re-teach the points.
PAUSE. Circular Points too Two of the circular taught points are Ideally circular points
MOTN-136 G close(L:%d^5) too close to each other. should be evenly spaced.
PAUSE. No circular softpart The circular motion softpart is not
MOTN-137 G
PAUSE. (G:%d^2)
No joint short motion loaded in the
Joint short system.
motion softpart is notLoad the
jointcircular softpart
short motion
MOTN-138 G SP (G:%d^2) loaded in the system. softpart
PAUSE. No cart short motion SP Cartesian short motion softpart is not
Load cartesian short
MOTN-139 G
PAUSE. (G:%d^2)
No KAREL motion loaded in the
The KAREL system.
motion softpart is notmotion
Load thesoftpart
KAREL motion
MOTN-140 G softpart (G:%d^2) loaded in the system. softpart.
PAUSE. No KAREL motion func. The KAREL motion function pointer isCheck that the KAREL
MOTN-141 G ptr (G:%d^2) not initialized or does not exist. Motion softpart has been
PAUSE. No Group Motion SP The Group Motion softpart is loaded Check that the Group
MOTN-142 G (G:%d^2) and multi-group motion is specified Motion softpart has been
PAUSE. No Motion Resume SP The Motion Resume softpart is loadedCheck that the Motion
MOTN-143 G
PAUSE. (G:%d^2)
No joint Turbo Move SP and path
Joint Turboresume
Movemotion
softpartisisspecified
Resume
not loaded
Load softpart
joint has been
Turbo Move
MOTN-144 G (G:%d^2) in the system. softpart
PAUSE. No cart Turbo Move SP Cartesian Turbo Move softpart is notLoad cartesian Turbo
MOTN-145 G
PAUSE. (G:%d^2)
INTR can't replan major loaded in the system. Move softpart
MOTN-146 G axis(G:%d^2) Mismatch in major axis turn number Reteach position
motion follows several linear motions,
Change the current
L->J replan joint the turn number might be mismatched,motion's motype to linear
MOTN-147 WARN slowdown (G:%d^2) causing the robot to slow down or change the previous
Two motion groups cannot synchronizeIf slow down is not
Can't move with each other due to replanning ofacceptable, re-teach the
MOTN-148 WARN concurrently (G:%d^2) one group. This will cause slow downpath.
PAUSE. CF:rotspeedlim Set
MOTN-149 G exceeded
PM: line:%d^5
XYZ data error CF:rotspeedlim
The distance moveexceeded
exceeded the $cf_paramgp[].$cf_frame
Check the position
MOTN-150 (L:%d)
PM: WPR data error tolerance. data(XYZ)
Please check in the IBGN file.
position
MOTN-151 SVSTOP PM:
(L:%d)
Can't current PM: Rotation move exceed tolerance. data(WPR) in IBGN file.
MOTN-152 SVSTOP record data PM: Can't current record data. Please call FANUC service.
Joint might be move too
PM: Joint move fast Joint angle move exceeded the fast because of moving
MOTN-153 SVSTOP (L:%d) tolerance. around a singular point.
PM: I/O data error I/O data in ibgn.txt might
MOTN-154 SVSTOP (L:%d) Cannot output data. be different from that in
PM: No interpolation Interpolated data does
MOTN-155 SVSTOP data No interpolation data. not exist. Check
PM: Config The configuration has
MOTN-156 SVSTOP changed(L:%d) Configuration changed. been changed. Check the
MOTN-157 STOP PM: Internal error(%d)
Original path An internal error has occurred. led
Set to
thethe error path
original and call
MOTN-158 STOP invalid The original path is invalid. resume function to TRUE.
PM: Joint data error Joint data is invalid. The recorded data Retry recording the data
MOTN-159 SVSTOP (L:%d) might be near a singular point again without the
Could not get the next motion Use LOCK PREG
instruction. This can happen due to: - instruction to lock
Using unlocked position registers - position registers. Remove
(%s^4 L:%d^5) Can't Using IF/SELECT statements - Control conditional branching
MOTN-161 WARN look ahead transfer to another program - Changing (IF/SELECT)
Remove conflict if possible.
optoins
MOTN-165 L%d %s Not support %s There is a conflict with optoin used from motion line
Change the tool or hand
MOTN-170 WARN Load is close to capacity The robot payload is close to capacity. to satisfytool/hand
Change the payload to
MOTN-171 WARN Another
PAUSE. Overloadrobot is re- Overload.
Detect satisfy and
another link robot is paused and Pause loadrestart
condition
all the
MOTN-172 G
PAUSE. linked
Robot link configuration restarted.
Detect wrong configuration for robot link robot.
Confirm setup data and
MOTN-173 G
PAUSE. error link.
Attempted operation needs motion programmotion
Confirm detail data.
control
MOTN-174 G No motion control control. status.
PAUSE. Setup or group mask in program may Confirm setup data and
MOTN-175 G Failed to be MASTER be incorrect or robot is still moving. group mask in program.
PAUSE. Setup or group mask in program may Confirm setup data and
MOTN-176 G Failed to be SLAVE be incorrect or robot is still moving. group mask in program.
PAUSE. Failed to end sync Setup or group mask in program may Confirm setup data and
MOTN-177 G
PAUSE. motion be incorrect or robot is still moving. group mask
Confirm eachinlink
program.
robot's
MOTN-178 G
PAUSE. Link robot is HELD Robot link program is held. position and restart.
MOTN-179 G
PAUSE. internal error Robot
Robot link Calib-data Cart filter
linkiscalibration
used for robot link.
data is not Please call
Confirm theFANUC service.
calibration
MOTN-180 G
ABORT. not found
Robot link Version correct.link version is not compatible
Robot setup.
Confirm software version
MOTN-181 G
PAUSE. Failed to get data from Slave robot failed to get position data is
mismatch with peer robot. consistent
Confirm between
communication
MOTN-182 G
PAUSE. master MNUTOOLNUM of master robot.
Invalid status and setup data.
MOTN-183 G data array
PAUSE. Invalid MNUTOOL data Current UTOOL number is not correct. Confirm UTOOL number.
MOTN-184 G array of ACK BF to be Current UTOOL data is not correct.
Protect UTOOL data.
Confirm communication
MOTN-185 WARN Protect
sent of BCST BF to Failed to send ACK from slave. status.
MOTN-186 WARN be sent
Protect of ACK BF to be Failed to send broadcast from master. status.
MOTN-187 WARN Protect
read of BCST BF to Failed to read ACK from slave. status.
MOTN-188 WARN be read Failed to read broadcast from master. status.
Confirm program that
MOTN-189 WARN Slave cannot
PAUSE. motion use
remained Slave position
JOINT Joint robot is still
datamoving.
is used for slave slaveXYZWPR
Use is already stopped
data for at
MOTN-190 G
PAUSE. pos cannot JOINT
Slave program.
Joint motion is not available for slave slave program.
MOTN-191 G motion
PAUSE. UT of MASTER was program.
Utool of master robot is changed Use cartesian
Confirm master motion.
program
MOTN-192 G
PAUSE. changed
UT of SLAVE was duringoflink
Utool motion.
slave as not toslave
robot is changed during Confirm change utool. as
program
MOTN-193 G changed
PAUSE. Machine Lock is link motion.
Robot link is not available when not to change utool.
Confirm robot position
MOTN-194 G
ABORT. ENABLED
RLINK internal error machine lock status. and disable machine lock.
MOTN-195 G %d^5 Internal error Please call FANUC service.
Circular Start, Via and points are on the Re-teach the points.
MOTN-197 CRC Collinear (L:%d^5) same straight line. Ideally circular points
CRC Start-Via too Circular Start and Via points are too Ideally circular points
MOTN-198 WARN close(L:%d^5) close to each other. should be evenly spaced.
CRC Via-Dest too Circular Via and Dest. points are too Ideally circular points
MOTN-199 WARN close(L:%d^5) close to each other. should be evenly spaced.
(%s^4, %d^5) Too long Specified TimeBefore (anticipation) 1. Reteach the previous
MOTN-200 WARN anticipate time value was too large point to make motion
Not support RA does not support TRACKING Please disable Auto
MOTN-201 AutoSA+TRCK motions Singularity Avoidance
Not support Please disable Auto
MOTN-202 AutoSA+COORD RA does not support COORD motions Singularity Avoidance
Not support RA checks consistency in data and Log debug data and
MOTN-203 AutoSA+RTCP detects error
RA checks consistency in data and report the problem
Log debug data and
MOTN-204 RA INTR%d^5)
(%s^4, error (G:%d^2) detects error report the problem
MOTN-205 WARN Singularity
(%s^4, %d^5) Singular
MOTN-206 WARN Node
WARN: An Axis Changes
MOTN-207 180 An axis will rotate more than 180 deg. It's a warning message.
The Auto Singularity Avoidance Make the taught
function ignores the taught wrist configuration reachable
configuration (flip/non-flip) to avoid a by touching up the point
Config Not Reached detected singularity. As a result, the at the stop position when
MOTN-208 WARN (L:%d) taught configuration might not be the warning message is
This warning message indicates that If you do not want the
the taught position at the specific line is system to modify the
inside a singularity zone. By default, the singularity point, set
Modify Singular system modifies it in order to control $ra_paramgrp[].$use_strt
MOTN-209 WARN Dest(L:%d) the rotation of axis 4. If _j4 = FALSE.
PAUSE. Failed to resume Original Path Resume was used for Abort and re-run the
MOTN-210 G
PAUSE. Dual ARC not allowed at Robot
program Link.
Dual ARC But Resume
motion condition
is not allowed at was
T1 program.
Please change to T2 or
MOTN-211 G T1 mode. AUTO mode
PAUSE. Link is in held status Jog motion of the robot in the status of Change status to MASTER
MOTN-212 G (G:%d^2) Held or Link Incomplete is not allowed. or ALONE at MANUAL
PAUSE. Org path resume not Original path resume feature is not Disable original path
MOTN-213 G available available under this configuration. resume feature.
PAUSE. Resume condition Resume condition does not match Check if original path
MOTN-214 G mismatch
Single Step Complete amongstep
Single master and stops
motion slavesat the taught resume is in
Continue enabled, and
single step
MOTN-215 WARN (Rob#%d^2) position.
Single step motion is held due to other mode.
Continue in single step
MOTN-216 WARN SSTEP HELD robot stops. mode.
The Master or Slave is set to single step Set step statement type to
MOTN-217 STOP SSTEP motion line only on the statement. MOTION in TEST CYCLE
SSTEP motion line Master and Slave must have same Match motion line
MOTN-218 mismatch motion lines when $sstep$simul is numbers or disable
RLINK Can't SSTEP with Single Step engaged during a Robot Engage Single Step only
MOTN-219 SVSTOP GTime Link Global time move. before or after a Robot
Group motion resume This group motion does not have continue from the same
MOTN-220 STOP mismatch consistent resume flag. instruction line. Or
RLINK Broadcast data An internal robot link error has and hold the SHIFT and
MOTN-221 SABRT expected occurred. RESET keys. 3. While still
RLINK Broadcast queue An internal robot link error has and hold the SHIFT and
MOTN-222 SABRT full occurred. RESET keys. 3. While still
RLINK Broadcast queue An internal robot link error has and hold the SHIFT and
MOTN-223 SABRT empty occurred. RESET keys. 3. While still
An internal robot link error has and hold the SHIFT and
MOTN-224 SABRT RLINK No output data occurred. RESET keys. 3. While still
RLINK Turn number The wrist turn number does not match Reteach the program to
MOTN-225 STOP mismatch the destination during robot link. avoid a wrist turn number
A motor speedlimit was encountered Reduce the speed or
MOTN-226 STOP RLINK Motor Speedlim during robot link. reteach program to avoid
RLINK start sync An internal robot link error has and hold the SHIFT and
MOTN-227 STOP mismatch occurred. RESET keys. 3. While still
RLINK Position number Position numbers do not match during Reteach programs so that
MOTN-228 STOP mismatch simultaneous robot link motion. the position numbers in
An internal robot link error has and hold the SHIFT and
MOTN-229 STOP RLINK Internal
T1 rotspeed Error
limit occurred. RESET
Reducekeys. 3. or
speed While
Usestill
MOTN-230 WARN (G:%d^2) T1 mode rotation speed limit is used (deg/sec) or sec as speed
The speed has been reduced at T1 This is just a notification
mode even though the command that the robot may move
MOTN-231 WARN T1 speed limit (G:%d^2) speed is not greater than with lower speed than
An internal Robot Link error has and hold the SHIFT and
MOTN-232 SABRT RLINK FDO queue full occurred. RESET keys. 3. While still
RLINK FDO queue An internal Robot Link error has and hold the SHIFT and
MOTN-233 SABRT empty occurred. RESET keys. 3. While still
Match the Robot Link
RLINK Pri Grp Config A Robot Link primary group primary group
MOTN-234 mismatch configuration error has occurred. configuration between
Match the Robot Link
RLINK Simul Config A Robot Link simultaneous motion simultaneous motion
MOTN-235 mismatch configuration error has occurred. configuration between
RLINK Can't reach The Robot Link primary group can not
MOTN-236 relative spd reach the program relative speed. None.
RLINK option not Robot Link option is not loaded or You may not use robot
MOTN-237 SABRT
PAUSE. loaded enabled. link features without the
MOTN-240 G
PAUSE. J4 is not zero Given position's J4 angle is not zero. Confirm position data
MOTN-241 G
PAUSE. OFIX stroke limit Given position is out of stroke
Specified motion group is OFIX limit Confirm position data
motion group
MOTN-242 G
PAUSE. OFIX is disabled disabled. and robot type
MOTN-243 G
PAUSE. OFIX error By error, OFIX motion is not available. Check cause code.
MOTN-244 G
PAUSE. OFIX Detect J4 is not 0
Wrist config J4 angle is not mismatch
Configuration 0 at start or destination.
between start Confirm position data
MOTN-245 G
PAUSE. mismatch and dest pos. Confirm position data
MOTN-246 G
PAUSE. OFIX Invalid
E-Effector is rail
not vector
vertical This robot angle
E-Effector is not issetuped for OFIX
not vertical to rail Confirm robot type
MOTN-247 G
PAUSE. to rail
OFIX Too large tool axis.
Tool rotation angle is too large for 1 Confirm
Reduce toolposition data
rotation
MOTN-248 G rotation motion. angle
PAUSE. Tool spin angle is too large for 1
MOTN-249 G OFIX Too large tool spin motion. Reduce tool spin angle
PAUSE. Use CNT0/FINE for L/C Linear or Circular motion just before Change term type of
MOTN-250 G
PAUSE. beforeuse
Can't OFIX
OFIX with this OFIX must terminate motion with CNT0 previsou motion.
MOTN-251 G motion
PAUSE. Accupath or CJP may be used. OFIX
MOTN-252 G
PAUSE. No plan type
OFIX: Motion data does not work with these option. Confirm software option.
MOTN-253 G
PAUSE. mismatch OFIX can work with linear motion. Confirm motion
tool spintype.
angle
MOTN-254 G OFIX: Detect large spin Tool spin angle is too large. between start and
PAUSE. Detect J4 is not zero angle during Confirm start and
MOTN-255 G
PAUSE. OFIX: Detect J4 is not 0 Reached
interpolation.
to stroke limit within this TCP destination position are
MOTN-256 G OFIX: TCP config limit configuration. Change position data.
PAUSE. Wrist start angle Wrist axis turn number is differ from Confirm position data turn
MOTN-257 G
PAUSE. mismatch
Not reached to dest position
OFIX datadoes not reached to
motion number and
Confirm actual turn
destination's
MOTN-258 G
PAUSE. rotation
Not reached to dest correct
OFIX rotation
motion doesangle
not reached to wrist axisdestination's
Confirm position data
MOTN-259 G spin correct spin angle wrist axis position data
MPDT not There is an axis which needs to have Execute the Magnetic
finished(G:%d^2 Magnetic Phase Detection (MPDT) Phase Detection process
MOTN-265 STOP
PAUSE. A:%d^3)
TB parameter error performed in
Calculation ofthat group,
Turbo moveand
on the
JointMPDT for that axis.
MOTN-270 G 1(G:%d^2) motion has an error Please call FANUC service.
PAUSE. TB parameter error Torque calculation of Turbo move due
MOTN-271 G 2(G:%d^2) to TB parameter has an error Please call FANUC service.
PAUSE. TB parameter error Calculation of Turbo move on Joint
MOTN-272 G
PAUSE. 3(G:%d^2)
TB parameter error motion has of
Calculation anTurbo
error that
moveiteration
on Joint Please call FANUC service.
MOTN-273 G 4(G:%d^2) motion has an error Please call FANUC service.
LD: exceed resume The resume motion will exceed the Backward execute the
MOTN-280 STOP tolerance Linear Distance tolerance. resume motion to the
LD: Line tracking not The linear distance function does not Remove the Linear
MOTN-281 STOP allow support the line tracking function. distance instruction.
LD: COORD motion not The linear distance function does not Remove the Linear
MOTN-282 STOP allow support Coordinated motion. distance instruction.
LD: Continue motion The linear distance function does not Remove the Linear
MOTN-283 STOP not allow
UTOOL not supported The support
UTOOLa Continuous
specified ismotion type.
not supported distance
Set UTOOLinstruction.
properly for
MOTN-290 STOP G:%d^2 for this robot. this robot.
Can't convert to joint In this point, the Cartesian position can
MOTN-291 STOP pos not be converted to a joint position. Reteach the position.
Encoder Limit (G:%d^2, The maximum encoder rotation limit of Reduce the gear ratio or
MOTN-292 STOP A:%x^3 Hex) 4085 was exceeded. reduce stroke of the axis
Increase the ITP time by at
MOTN-293 STOP
PAUSE. Increase
CD ITP time
not support:Use The ITP time is too short for this robot. least 2ms
Change and recycle
termtype FINE or
MOTN-300 G
PAUSE. CNT L:%d^5
Path to resume is Term type CD is not supported. CNT.
MOTN-301 G changed(G:%d^2) Can't resume motion. Abort and run program.
Corner speed slowdown Corner speed slows down automatically If slow down is not
MOTN-302 WARN L:%d^5 because of robot constraint. acceptable, re-teach the
Can't maintain CDist Can't maintain corner distance because Lengthen path or reduce
MOTN-303 WARN L:%d^5 path is short or speed is high. speed.
CS:Prog speed achieved SPD value does not affect corner speed This is just a notification.
MOTN-304 WARN L:%d^5 anymore. You do not have to do
Can't maintain speed Can't maintain program speed on the This is just a notification.
MOTN-305 WARN L:%d^5 path because of robot constraint. You do not have to do
PAUSE. Can't replan (G:%d^2, Resume motion cannot reach stop
MOTN-306 G
PAUSE. A:%x^3 Hex)
Mismatch MMR position system
Internal Can't resume orginal
error. Can't path.
resume Abort program and rerun
MOTN-307 G (G:%d^2) orginal path. Abort program and rerun
Can't generate corner
between two motion
FINE termtype used because of motion
MOTN-308 WARN L:%d^5
Circular speed reduced Circular speed is reduced because of instruction.
Reduce And CNT
program or
speed
MOTN-309 WARN L:%d^5 robot contraint not to display.
Reteach the destination
PAUSE. Pos. Cfg. change 2 position so that its
MOTN-310 G (G:%d^2) Configuration mismatch configuration string
PAUSE. Path to resume is Can't resume motion on the original Abort and run program.
MOTN-311 G
PAUSE. changed(G:%d^2)
Can't resume in single path.
Can't resume motion in single step Then, the resumed
MOTN-312 G step CJ mode. Abort program and rerun.
PAUSE. Can't resume motion Can't resume motion on the original Abort and run program.
MOTN-313 G CJ(2) path. Then, the resumed
ABORT. Can't resume motion Can't resume motion on the original Abort and run program.
MOTN-314 G CJ(3) path due to motion condition. Then, the resumed
PAUSE. Command speed is Can't resume motion on the original Modify back the
MOTN-315 G changed CJ path due to command speed change. command speed, or abort
Change in teach pendant override Set Teach Pendant's
PAUSE. Override change not setting while the program is resuming override to the desired
MOTN-316 G allowed with disabling CJP. value and resume the
PAUSE. unknown error Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-317 G (MO317) should not be encountered by the user 000
PAUSE. unknown error Internal system error. This class of error Refer to Remedy of MOTN-
MOTN-318 G
PAUSE. (MO318)
CRC large orient change should not be
Small circle butencountered by the user
large orientation 000
MOTN-319 G (G:%d^2) change Reteach circular points
Adj out of limit at line motion error will occur,
MOTN-320 WARN %s adjustment precheck use CLR_Adj to clear the
Posn unreachable at motion error will occur,
MOTN-321 WARN line %s Genoverride
Invalid adjustment precheck use CLR_Adjoverride
Set general to clear the
MOTN-322 (G:%d^2)
Invalid Prgoverride General override is not within 0 to 100 within
Set 0 to 100 within 0
$prgoverride
MOTN-323 (G:%d^2) Prgoverride is not within 0 to 100 to 100
MROT Limit Warn Axis limit is detected during the Check the alarm log to
MOTN-330 (G:%d^2,
CR A:%s^7) CNT minimal rotation
not support:Use find out termtype
Change which axisFINE
has or
MOTN-331 STOP L:%d^5 Term type CR is not supported. CNT.
This is notification for application
PAUSE. process enabled in the fast fault
MOTN-340 G Fast fault recovery recovery when the alarm position is This is just notification.
Z offset is specified for INCREMENTAL
motion. Z offset can not be applied for Please don't use
NO Z offset for INC INCRE motion. This is notification that Z incremental motion if you
MOTN-341 WARN motion offset was not applied for the motion. need Z offset
PAUSE. Override change not Change in teach pendant override Set Teach Pendant's
MOTN-342 G allowed setting while the program is running. override to the desired
Constant Path Low The teach pendant override setting was Increase override setting
MOTN-343 STOP Override too low to ensure
PS statement is nota available
constant path.
with this and resume the program.
MOTN-345 PS is not available motion type
AccuPath does not support Circular Please check
Disable program.
Accupath or do
MOTN-350 STOP Please disable Accupath ARC motions. not teach circular ARC
The Coordinated Motion softpart does Disable COORD or do not
MOTN-351 STOP Please disable COORD not support Circular ARC motions. teach circular ARC
The Line Tracking softpart does not Disable Line Tracking or
MOTN-352 STOP Please disable LineTrack support Circular ARC motions. do not teach circular ARC
The CJ/CJLP softpart does not support Disable CJLP or do not
MOTN-353 STOP Please disable CJLP Circular ARC motions. teach circular ARC
ARC Internal Error Internal system error. This class of error Refer to the Remedy of
MOTN-354 STOP (G:%d^2) should not be encountered during MOTN-000.
ARC: No 3 Poses There is no third position data to plan Make sure there are
MOTN-355 STOP (G:%d^2) an ARC motion. always three points
ARC:180 deg SPIN The change in the SPIN angle from start Re-teach points such that
MOTN-356 STOP change(G:%d^2) to destination is 180 deg. the change in the SPIN
ARC: can't resume The resumed planned data is not the Press RESET or Abort the
MOTN-357 STOP (G:%d^2) same as the original data. program.
Re-touch up the taught
Strt-Prev too close Prev and start positions of this A point(s) of the immediate
MOTN-358 STOP (L:%d^5) motion are too close to each other. previous A motion line(s)
Strt-Next too close Start and Next positions of this A Re-touch up either the
MOTN-359 STOP (L:%d^5) motion are too close to each other. taught point of the
Destination and Previous positions of Re-touch up either the
Dest-Prev too close this A motion are too close to each taught point of the
MOTN-360 STOP (L:%d^5) other. current A motion line or
Dest-Next too close Destination and Next positions of this A Re-touch up either the
MOTN-361 STOP (L:%d^5)
Please disable arc motion
Blendingare
of too
twoclose to each other.
arc segments is not taught point of the
Set $CRCFG.$BLEND_ENB
MOTN-362 blending supported. to FALSE.
MOTN-363 STOP MT_ARC:
Please disable ToTrk
not support Motype A does not support tracking. Do not use motion type A.
MOTN-364 STOP the option
Don't use motion type Motype A does
The softpart notnot
does support themotion
support option. Do not use motion type A.
MOTN-365 STOP A
MT_ARC: not support type A. Do not use motion type A.
MOTN-366 STOP RPM RPM does not support motion type A. Do not use motion type A.
MT_ARC: colinear This is just a notification
MOTN-367 WARN (L:%d^5) Degenerate case for MT_ARC message only. Re-taught
NotSupport KarelPath The system does NOT support KAREL Do not run KAREL Path
MOTN-375 (G:%d^2) path motions. motions and use teach
The main body's arm and runner are Expand the distance of
MOTN-380 STOP Arm-Runner too close too close to each other. main body's arm and
The main body's hand and runner are Expand the distance of
MOTN-381 STOP Hand-Runner too close too close to each other. main body's hand and
The required motion option is not Verify motion options
MOTN-390 FATAL %s is required for %s loaded. loaded in the controller
Motion option cfg file Motion option configuration file is not Re-load correct motion
MOTN-391 WARN missing loaded
The or cannot
number be read.exceeds the
of softparts option config
Reload file. with
the system
MOTN-392 Too many softparts limit of 32. less than 32 softparts.
Can't set w/ When Small Circle Accuracy is ordered, Don't order Small Circle
MOTN-393 Sm.Circ.Accuracy
Can't set with Servo you can't
When useTorch
Servo this setting.
is ordered, you can't Accuracy
Don't when
order ServoyouTorch
use
MOTN-394 Torch use this setting. when you use this setting.
PAUSE. No Coll. Guard Reg. No register has been defined for use Use the Collision Guard
MOTN-400 G Defined with the Collision Guard Update macro. SETUP screen to define a
The data contained in the Collision Enter the correct data
PAUSE. Coll. Guard Reg. Data Guard macro register is not an integer into the Collision Guard
MOTN-401 G Error or is not in the range of 1 to 200. macro register.
HSCD: Update Servo Servo system failed to acknowledge Check that
MOTN-402 Timeout servo parameter update. communication between
Servo system is updating servo No action needed. This
MOTN-403 Updating Servo (%s) parameters to match user-defined warning is only a
The COL ADJUST instruction was used Do not attempt to change
in a teach pendant program, but the the sensitivity for a group
Group %d^1 does not group mask contained a group that did that does not support
MOTN-404 WARN support HSCD not support High Sensitivity Collision HSCD. 3.10.8 MUPS Alarm
Jog frame No%d^2 is The selected UFRAME is disabled for Enable the affected
MOTN-410 disable[P] jogging. UFRAME for jogging, or
This is notification of PX1 for This is an internal
application process enabled in the fast notification. Document
MOTN-411 Fast fault recovery 1 fault recovery when the alarm position the events that led to the
This is notification of PX2 for Document the events that
application process enabled in the fast led to the error and
MOTN-412 Fast fault recovery 2 fault recovery when the alarm position contact your FANUC
This is notification of instruction This is just notification.
number 1 for application process Document the events that
MOTN-431 Fast fault recovery 1 enabled in the fast fault recovery when led to the error and
This is a notification of instruction
number 5 for application process
MOTN-435 Fast fault recovery 5 enabled in the fast fault recovery whenNone.
Resume Motion On Resume motion, the robot moves to Abort and re-run the
MOTN-441 Error(G:%d A:%d) the position that is different from theprogram.
Motion cmd Error The robot moves to the position that isAbort and re-run the
MOTN-442 excess(G:%d
Zero A:%d)
accel time used different
Accel timefrom theshort
is too destination
relative point.
program.accel time or
to ITP
Increase
MOTN-443 (G:%d)
No J2/J3 interaction time.
This group does not have J2/J3 reduce ITP time.
MOTN-444 (G:%d) interaction. No display required.
An internal error occurred in the ClockWrite down the steps that
MOTN-451 CS: Internal error No1 Simultaneous function. led to this error, and
CS: Both of EXT. & VR. Both of external clock and virtual clock The either of external
MOTN-461 clock
CS: Novalid
data signal for are
Datavalid. clock
signal for external clock(GI index) and
Set the virtual
data clock set
signal(GI
MOTN-462 EXT.clock
CS: is not set.
No strobe signal for Strobe signal for external clock(DI index)
Set thefor external
strobe clock.
signal(DI
MOTN-463 EXT.clock
CS: No max time for index) is not set. index)
Set thefor
maxexternal
time forclock.
MOTN-464 EXT.clock
CS: No current time for Max time for external clock is not set. external clock.
Set the current time for
MOTN-465 VR.clock
CS: No max time for Current time for virtual clock is not set.
virtual
Set theclock.
max time for
MOTN-466 VR.clock Max time for virtual clock is not set. virtual clock.
CS: Faster current than Current time is faster than max time forMake the current time
MOTN-467 max time for VR.clock virtual clock. enlarge than max time for
The following items are
considered to this
warning. Please check
MOTN-468 CS: Reverse EXT.clock
Constant Path External clock proceed reversively. them
Pleaseand
set fix the cause. 1:
MOTN-471 Invalid.
CS: Restart motion Constant path function is invalid $CPCFG.$CP_ENABLE
Please set to
MOTN-472 feature Invalid. Restart motion feature is invalid $SCR.$ORG_PTH_RSM to
CS: Both of EXT. & VR. Both of external clock and virtual clock The either of external
MOTN-473 clock
CS: validCLSM with the The
Can't are valid.
option can not use with CLSM clock and
Please virtualeither
remove clock set
MOTN-474 option motion CLSM or the option.
considered to this alarm.
Please check them and fix
the cause. 1: It is possible
for clock speed to be
faster than the robot
motoion. Please make the
clock speed do more
slowly than current one.
CS: Can't execute simul- The robot could not synchronize with 2: It is possible for motion
MOTN-481 motion external/virtual clock sentence in TP program to
considered to this alarm.
Please check them and fix
the cause. 1: The position
between current actual
CS: Can't start simul- robot and simultaneous
MOTN-482 motion Could not start simultaneous motion. start motion sentence is
Starting simultaneous
CS: Can't do simul- Tried to start simultaneous motion on motion on the way to it
MOTN-483 motion on the way the way to it. can not be permitted.
The operation of
OVERRIDE change can not
CS: Changed OVERRIDE Executed operation of OVERRIDE be permitted on
MOTN-484 on simul-motion change on simultaneous motion. simultaneous motion
On simultaneous motion, HOLD or E- Restart after HOLD or E-
CS: Can't restart on STOP signal is inputted into controller STOP on simultaneous
MOTN-485 simul-motion After it, users tried to restart motion can not be
The operation of
singlestep can not be
CS: Set SingleStep on Executed operation of singlestep on permitted on
MOTN-486 simul-motion simultaneous motion. simultaneous motion
This is notification of PX17 for
application process enabled in the fast This is an internal
MOTN-501 Fast fault recovery 17 fault recovery when the alarm position notification.
Reducer torque overs the threshold. 1. Verify payload setting is
Reducer Torque Payload setting is wrong. or the value correct. 2. Lessen
MOTN-520 Over(G:%d A:%d) of acceleration override acceleration(ACC) of
Load that is given to J2 axis exceeds 1. Verify payload setting is
J2TqOver(G:%d ID:%d threshold. Payload setting is wrong or correct. 2. Lessen
MOTN-521 L:%d) the value of ACC is too large. acceleration(ACC) of
Load that is given to the joint between 1: Verify payload setting is
Joint load LinkA and LinkB exceeds threshold. correct. 2: Lessen
MOTN-522 excess(G%dJ%dL%d %s) Payload setting is wrong or the value of acceleration(ACC) of
1. Confirm that the size of
DRAM is as much as
64MB. If not, change
DRAM. 2. If MOTN-525 is
LVC: Out of DRAM LVC has failed of getting memory from posted after you operate
MOTN-525 memory(M%d,Id%d) DRAM the above, the system
Gun touch speed is over designated
speed. The 1st parameter shows line
number at which MOTN-526 is posted.
The 2nd parameter shows how is over Add the new taught point
designated GunTouchSpeed. The cause near the motion
LVC: GunTchSpd might be considered. -The inner statement at which MOTN-
MOTN-526 over(L%d,V%d) override is too high -The filter length of 526 is posted.
First, confirm that the size
of DRAM is at least 64MB.
If not, change DRAM. If
LVC: Failure of getting LVC has failed to get memory for MOTN-527 is posted after
MOTN-527 memory1 before-learning on DRAM. you operate the above,
First, confirm that the size
of DRAM is at least 64MB.
If not, change DRAM.
Next, decrease the
LVC: Failure of getting LVC has failed to get memory for after- number of
MOTN-528 memory2 learning on DRAM. $LVCFG.$MAX_MDL_NU
The motion instruction which can not
be executed with LVC is taught. MOTN-
529 has two parameters. The first
parameter shows line number at which
MOTN-529 is posted. The 2nd Delete motion instruction
parameter shows motion instruction which can not be
LVC: This isn't which can not be executed with LVC as executed with LVC or LVC
MOTN-529 allowed(L%d,Id%d) follows: -external path optimization - instruction.
LVC: axis besides object The axis besides an object of LVC Teach the position not to
MOTN-530 moved(L%d,G%d,A%d)
LVC: Learning %d%% moved. move
There axis
is nobesides
action an
MOTN-531 (M%d)
LVC: Internal error Learning has succeeded. required
Please callforFANUC
this alarm.
service
MOTN-532 2(M%d,Id%d) Internal error in LVC function. center.
Override change has been done in LVC Don't change override
LVC: Change override execution. LVC always works at 100% during LVC execution. If
MOTN-533 on LVC override. override instruction is less
LVC: Input SingleStep Single Step occurred during LVC Don't use single step
MOTN-534 on LVC
LVC: (M%d) Confirm execution. LVC does not work with during LVC execution.
MOTN-535 mode Not a problem. None.
LVC has been disabled on part of the
LVC: (M%d) Partially path because the path has changed. Delete LVC schedule and
MOTN-536 disabled Cycle time may be slower because the re-learn.
The motion which will be executed is
different from the motion saved in LVC.
The cause might be that the re-
teaching occurred after learning
finished. MOTN-537 has three
parameters. The first parameter shows
modal number which is executed when
MOTN-537 is posted. The second
parameter shows line number which is
executed when MOTN-537 is posted.
The third parameter shows the
changed element: - 1: motion type - 2:
start position - 4: destination position -
8: via position - 16: taught speed - 32:
termination type - 64: the value of CNT
termination - 128: user tool
coordination - 256: user frame
coordination - 512: override - 1024:
payload - 2048: the value of ACC
instruction - 4096: PTH instruction -
8192: WJNT instruction - 16384: INC Recover data before re-
LVC: Changed instruction - 32768: the value of PSPD teaching or do learning
MOTN-537 motion(M%d,L%d,P%d) instruction - 65536: MAXSPEED again.
In learning or replaying, the interval
between start of motion might be
changed. For example, WAIT
instruction is inserted between motion Recover data before re-
LVC: Changed motion 2 sentences or the value of it is changed. teaching or do learning
MOTN-538 (M%d,L%d) First paramter means modal number of again.
In learning or replaying, the interval
from start of motion to end might be
changed. For example, DVC or DAC
occurred, or the motion is changed by Recover data before re-
LVC: Changed motion 3 logic instruction. First parameter means teaching or do learning
MOTN-539 (M%d,L%d) modal number of LVC instruction. again. call FANUC service
Please
MOTN-540 LVC: Internal Error
Fatal error of 1 Internal error in LVC function. center.
Please call FANUC service
MOTN-541 memory(M%d,S%x) Internal error in LVC function. center.
Please follow this
procedure. -If you can
reduce the number
LVC: Full memory motion statements
MOTN-542 (M%d,S%x) The memory for LVC is full. between LVC_START and
LVC: No learned There is no learned data to set in This is normally not
MOTN-543 data(M%d,S%x) memory for LVC. posted. Please call FANUC
LVC: Leanred data There is no learned data to get from This is normally not
MOTN-544 empty(M%d,S%x) memory for LVC. posted. Please call FANUC
LVC motion was switched to normal
motion because the motion changed.
LVC: Switched to 1st parameter means the modal
normal number of learning data. 2nd No need to remedy
MOTN-545 motion(M%d,%s,L%d) parameter means the name of TP because of warning.
LVC motion restarted from normal
motion. 1st parameter means the
modal number of learning data. 2nd
LVC: Restart LVC parameter means the name of TP No need to remedy
MOTN-546 motion(M%d,%s,L%d) program. 3rd parameter means line because of warning.
LVC: Sync motion not LVC doesnot support synchronous Please use RUN
MOTN-547 supported(M%d,L%d) motion in case that two or more group instruction in TP program
LVC: Group number Group number of the robot which is in Please set the correct
MOTN-548 mismatch(M%d,G%d,L learning is not match the setup in LVC group number in LVC
Please comment out all of
LVC: Multi data in Multi learn data cannot be in learning LVC_START and LVC_END
MOTN-549 learning(M%d,L%d) at the same time. so that only one learn
The teaching speed with high-speed
Hspd.skip speed skip instruction reached to the speed
MOTN-560 limit(G:%d^2) limit and automatically clamped with This is just a warning.
Col.skip NOT The collision skip is used with normal
MOTN-561 available(G:%d^2) skip instruction or the robot that high- Don't use collision skip.
GLC Payload changed The payload has changed since GLC
MOTN-570 (G:%d^2)
GLC invalid LEARN learning.
The LEARN GLC learned data
instruction does
is not not
valid in Relearn
Remove with
LEARN GLC.
motion
MOTN-571 option iRpick system. instruction.
GLC 2 consecutive 2 Consecutive LEARN instruction is not Remove LEARN motion
MOTN-572 LEARN
use of M-PASS SP's bef. allow. instruction from none
Controlled start, init
MUPS-001 WARN
PAUSE. init
Isolated offset Mult-Pass variables not initialized multipass
Must have at least two
MUPS-002 G destination Isolated offset destination points
PAUSE. Invalid motype with Internal error: motion
MUPS-003 G
PAUSE. offset too short
Segment Invalid motype with offset type is not
Increase Joint, Linear, or
distance
MUPS-004 G
PAUSE. using OFFSET
Invalid OFFSET_MODE Segment too short using OFFSET between
Set points
OFFSET_MODE to a
MUPS-005 G value Invalid OFFSET_MODE value valid value.
PAUSE. BWD not allowed in M- Multi-Pass does not
MUPS-006 G
PAUSE. PASS
Illegal BWD motion
Illegal not(nonCD->CD
transition supported or CD- support
Add backward
or remove motion.
motion
MUPS-007 G
ABORT. transition:nonCD<->CD >nonCD) happens. option COORD.
MUPS-008 G Invalid pass number Pass number is not acceptable Use correct pass number
PAUSE. Pass direction can only be
MUPS-009 G
PAUSE. Invalid Direction directionand
Pass number is not acceptable
direction are not 0: Normal
Check or 1: number
the pass Reverse.
MUPS-010 G Invalid
Pass parameters
number acceptable
is out of and direction
MUPS-011 WARN sequence
Last pass was Pass number is not in sequence Use correct pass number
MUPS-012 WARN incomplete Last pass was not welded to completion
Invalid Leader OFFSET
MUPS-013 MODE Leader Offset requires CD Move Add CD Move.
WARNING - ProcessA 'Force Process Complete' was This is just a warning to let
of %s Complete manuallyperformed from the Soft Panel the operator know that
OPTN-000 WARN Unknown error (OPTN) System internal error. RESET keys. 3. While still
Too many options The maximum number of software None required.
OPTN-001 WARN installed options/updates (50) is installed. Options/updates will load
Installation of software option/update This is just a notification.
OPTN-002 WARN Installed: `%s' has finished successfully. You do not have to do
Some options cannot be
OPTN-003 WARN Skipped: `%s' S/W option was skipped by installer. overlayed, you may need
The specified software option was not
OPTN-006 WARN Not Installed: `%s' installed properly. Reinstall the option.
Software option has not been Call your FANUC Robotics
OPTN-007 WARN Unauthorized: `%s' authorized for this configuration. technicalthe
Reinstall representative.
option using
OPTN-008 WARN Requires: `%s' The required floppy disk was not used. the required floppy disk.
Software option is now authorized for This is a notification. No
OPTN-009 WARN Authorized: `%s' this configuration. action Application
Setup is needed. prior to
OPTN-010 WARN Force Power,
Cycle COLD start
and force Setup Application has not been done STARTthe
Turn (COLD)
controller off,
OPTN-011 WARN CTRL start
ID file is Power down file,
The LICENSE and license.dat,
then up is needed
is missing and then backfrom
Do a full load on the
OPTN-012 WARN missing/corrupt or corrupted
The supplied PAC is not valid for this originaladistribution
Obtain valid PAC for this
OPTN-013 WARN Invalid PAC nesting
Dependency option. option.
OPTN-014 WARN too deep The option nesting tree is too deep. Install sub-options first.
This option is not compatible with an You cannot have both
OPTN-015 WARN Excludes:
Key file is `%s' option
The KEYthat
file,iskeyfile.dat,
already installed.
is missing or options.
Do a full load from the
OPTN-016 WARN missing/corrupt corrupted original distribution
No UPDATES on this The distribution media does not
OPTN-017 WARN media contain, update.tx, so there are no None required.
No CUSTOMIZATIONS The distribution media does not
OPTN-018 WARN on this media contain, custom.tx, so there are no None required.
The distribution media contains
updates or customizations, but has a
OPTN-019 WARN Versions mistmatched different release version than this core. None required.
The maximum number of feature If the alarm includes:
Too many %s references in the .fd files is exceeded. Increase KAREL constant:
OPTN-020 WARN references These include: REQUIRE, INCLUDE, CONFIG CLIMIT REQUIRE
Check orderfil.dat fails: One or more lines in orderfil.dat have Remove or correct the
OPTN-021 WARN %s Order Numbers for options that can line that contains the
The Demonstration version of the None is required. If use
option provides 60 days of free beyond the 60 days is
operation. This message indicates that required, then the option
there are “%d” days that are left for can be purchased and
Demo option %s expires this option to operate. Option authorized for permanent
OPTN-022 in %d days operation will be restricted or operation.
Max number of arms is The maximum number of robot arms Load TQAP:Triple Quad
OPTN-023 exceeded. allowed has been exceeded. The Arm Package to increase
Too many motion The maximum number of motion None required. All of the
OPTN-024 groups installed groups is installed. setup for the Motion
Choose Controlled Start
for the controller and
then choose MENUS, S/W
INSTALL, Option, then
The 60-day use period of this DEMO DEMOS. Please authorize
OPTN-025 %s DEMO has expired option has expired. this option. Refer to the
Software option is now demo This is a notification. No
OPTN-026 Demo Authorized:
ID Mismatch `%s'
: lic(%s) authorized for this configuration. action
Correctisfrom
needed.
Reserialize
OPTN-027 and act(%s) Controller
The ID LAC
supplied doesisnot
notmatch license
valid for this ID. Correct
Page at CTRL Start.
from Reserialize
OPTN-028 Invalid LAC controller.
The supplied LAC is valid for this Page at CTRL Start. No
This is a notification.
OPTN-029 LAC Updated controller. action is needed.
Max number of retries A small number of retries is allowed to Obtain a valid PAC or LAC,
OPTN-030 exceeded. authorize an option or re-authorize a and enter the numbers
The KAREL option is The KAREL option, R632, must be
OPTN-031 required installed in order to load this file. Install the KAREL option.
Extending the number of days to use a Only Demonstration
EXTEND not Demonstration options is not valid in options can be extended.
OPTN-032 appropriate. this context. Permanent options can
Controller Image should be backed up Backup your controller
prior to installing options. This allows image prior to installing.
OPTN-033 Image not backed up. you to restore an image without the additional options.
The controller image cannot be backed Press AUTOUPDT to
BACKUP not up at this time. An AutoUpdate is complete this option
OPTN-034 appropriate.
Image already backed needed to complete
The controller imagethis optionbacked
is already installation.
This is a notification. No
OPTN-035 up. up.
Software option is now enabled for this action
This is aisnotification.
needed. No
OPTN-036 Enabled: `%s' configuration.
Software option is now disabled for this action
This is aisnotification.
needed. No
OPTN-037 Disabled: `%s' configuration.
Software option is NOT enabled for this action is needed.
This is a notification. No
OPTN-038 NOT Enabled: `%s' configuration. action is needed.
The supplied PEC is not valid for this Obtain a valid PEC for this
OPTN-039 Invalid PEC demonstration option. demonstration option.
DISABLE not Disabling a Demonstration Options is A Demonstration Option
OPTN-040 appropriate. not valid in this context. must be enabled before it
OS-000 WARN R E S E T
OS-001 WARN System error
Consult the appropriate
manual and verify the
useage of the attempted
System error - invalid The function performed by the user is operation. Try it again, if
OS-002 WARN function performed not supported or is invalid. possible. If you try again
Contact the FRNA hotline
and provide the following
information for further
SYSTESystem error %x, %x at investigation. o Record
OS-144 M %x An unknown register dump occurred. the entire error
Power off controller to Usually a result of previous Cycle power on the
OS-145 WARN reset unrecoverable system error. controller. If error
Record and report the
An assert occurred on the MAIN parameters following the
OS-147 Assert MAIN %d %d %s processor. 'Assert MAIN' text to the
Assert COMM %d %d An assert occurred on the MAIN parameters following the
OS-148 %s processor. 'Assert MAIN' text to the
Assert VMAIN %d %d An assert occurred on the VMAIN parameters following the
Assert VCOMM %d %d An assert occurred on the VCOMM parameters following the
If the specified length was
less than the width, then
Alarm Code Length the length is forced to the
must be longer than The length dimension must always be width dimension. If the
PALL-001 WARN width greater than the width. specified width was
A layer number greater than the Specify a layer number
PALL-002 WARN Maximum layers = 40 maximum allowed layers was specified. less than the allowed
Cannot Flip Lt or Wd for The length or width flip was specified Specify No flip or diagonal
PALL-003 WARN Unique for a unique
Point matrix
P1 on the whichaid
teaching is not
was not (length
Teach P1 and
onwidth) flip for
the teaching
PALL-004 WARN P1 has not been taught taught. aid.
Layer Barrier on last cyc The layer barrier cannot be selected for Select the layer barrier for
PALL-005 WARN only. anything but the last cycle of a layer. the last cycle only.
Layer Barrier not The user selected * or Layer barrier Set Configure All Layers to
PALL-006 WARN enabled.
Layer Barrier invalid on without enabling Configure all layers
The layer barrier cannot be specified TRUE in the Optimal Path
PALL-007 WARN Unit
top lyr
cycle %s not for the
The top layer.
specified sequence number was This sequence
The is only a notification.
should
PALL-008 WARN defined. not found. include all the items in the
You cannot break the layer barrier if If you want a layer barrier,
Lyr bar invalid w/ you have a slip sheet between two remove the slip sheet
PALL-009 WARN slipsheet enb layers. between the layers by
The position the robot is trying to go to Verify that the value of
is not reachable. If the preceeding error $UTOOL and/or
is: 'Error: Pallet=x Unit=y', it means that
$MNUTOOL are correct. If
the robot was working with pallet x and the robot stopped while
PALL-010 PAUSE Position
%s is nothas
reachable
not been box y when the error occured. heading towards the
PALL-011 WARN taught The position has not been taught. Teach the position.
MOVE-TO could not Motion control was not obtained for Check if another task is
PALL-012 PAUSE execute %s robot motion. running,
Cold startorthe
if the teach
controller,
PALL-013 PAUSE GET_VAR failed %s Data in a SETUP menu could not be set. and retry the operation.
Cold start the controller,
PALL-014 PAUSE SET_VAR failed %s Data in a SETUP menu could not be set. and retry the operation.
Could not create station An error occurred while creating an Cold start the controller,
PALL-015 WARN file infeed
The data or in
pallet station file.
the sequence screen is and retry the operation.
PALL-016 WARN Sequence valid. valid. None.
PalletTool allows initialization of Make sure to pass a valid
palletizing data by allowing users to cycle number to the call
pass a cycle number to the CALL to PMPROCDT in the
Cycle number %s PMPROCDT(cycle_number) in some teach pendant program
PALL-017 ABORT invalid. teach pendant programs. If the user used.
The .VR file does not exist, or an error Check the communication
PALL-018 PAUSE Could not create
load .VR file An
unit occurred in communication.
error occurred line, and
while creating unit
Cold startmake sure that
the controller,
PALL-019 PAUSE load file load file.
Could not open .DT file An error occurred while opening a .DT and retry the operation.
Cold start the controller,
PALL-020 ABORT IO_STATUS
for read error file.I/O error occurred during the data
An and retry
Cold start the
the operation.
controller,
PALL-021 WARN Could
occurred
not save .VR file transfer. and retry
Cold start the
the operation.
controller,
PALL-022 WARN %s Error occurred while saving a .VR file. and retry the operation.
1. An error occurred while loading a .VR Cold start the controller
file. 2. The gripper setup file from and retry the operation if
previous versions of PalletTool cannot you know you should be
be read. The number of grippers was able to read the .vr file
PALL-024 WARN Could not load file %s increased and the structure of the data into PalletTool.
An error occurred while accessing the Make sure the
PALL-028 WARN Could not access files floppy disk. communication is correct,
The file transfer was not successful. Cold start the controller,
PALL-029 WARN File transfer not done Some data might not have been and retry the operation.
.DT files must exist on the
PALL-030 WARN .DT file list is empty No .DT
The files exist
specified on the
station floppy.
number is not floppythe
Load in station
order tofile,
perform
or
PALL-031 PAUSE Pallet Stn %s not found loaded. create one.
The pallet station specified in Teach the pallet station
PALL-032 PAUSE Pallet stn %s not taught PalletSystem setup has not been specified in PalletSystem
Perform one of the
following: * Load the Unit
PALL-033 PAUSE Load file %s not found The unit load file is not loaded. load file. * Transfer the
An invalid layer number was entered at Make sure to enter a valid
cycle start or passed from the PLC. Or, layer for each cycle at
PALL-035 PAUSE Invalid layer number %s PalletTool encountered an invalid layer cycle start or in passing
Multi-case option not The user is trying to select the multi- Install the Multi-case
PALL-036 WARN loaded. case gripper but the multi-case option gripper option.
Fork/Bag option not The user is trying to select fork gripper Install the fork gripper
PALL-037 WARN loaded. but the fork gripper option is not option.
Infeed stn %s not The infeed station specified in Teach the infeed station
PALL-038 PAUSE taught PalletSystem setup has not been specified in the
The specified flip type is unknown to Check the value of flip
PALL-040 PAUSE Unknown flip type %s PalletTool.
The specified infeed station is not type inorUnit
Teach loadload
theSETUP.
infeed It
PALL-041 PAUSE Infeed stn %s not found taught or loaded. station.
An orientation besides LT_ON_LT or Make sure to visit the
WD_ON_LT for a box in a layer was screen in PalletTool PC or
encountered by PalletTool while either PalletPRO where unit
Unknown unit PalletTool PC or PalletPRO data was orientation for each unit
PALL-044 WARN orientation downloaded to the controller. in a layer is defined and
Data created using
Cannot change PC file The unit load data file was created PalletMate PC cannot be
PALL-045 WARN data using PalletMate PC. changed in PalletTool. You
An error occurred while PalletTool was Perform an ABORT ALL,
PALL-046 WARN Could not run task %s internally trying to run another and retry the operation.
An error occurred while PalletTool was Make sure that the .TP
PALL-048 PAUSE Error opening %s trying to open a .TP program. program is loaded, and
An error occurred while PalletTool was Cold start the controller,
PALL-049 PAUSE Set_pos_tpe %s trying to set a position in a .TP and retry the operation.
An error occurred while PalletTool was Cold start the controller,
PALL-050 PAUSE Errorsheet
Slip closing
not%s trying to open a .TP program. and retry
Disable the
slip operation.
sheet in the
PALL-051 PAUSE supported Slip sheet support is not provided. PalletSystem menu.
Some patterns from older versions of Create a new unitload,
PALL-052 WARN Pattern not supported PalltetTool are no longer supported. and select a different
Gripper is not DOUBLE Depalletizing was chosen with a gripper Choose single gripper for
PALL-053 WARN type
Invalid parts requested other thanfor
A request single.
picking up 0 part was depalletizing, and retry
Abort all and retry the
PALL-054 PAUSE %s received. operation.
Perform an ABORT ALL,
PALL-055 PAUSE Error in CNV_STR_CONF Internal error occurred. and retry the operation.
Check the value of the
gripper-id in Optimal path
Gripper type not The specified gripper is unknown to setup. The valid range is 1-
PALL-057 PAUSE supported: %s PalletTool. 9. A value of 10 is also
Cannot select PC A PalletMate PC pattern cannot be Single, Doubleside,
PALL-058 WARN pattern selected while creating or modifying a DoubleTop, or Unique
1. Wait until production is
An error occurred while clearing a aborted and clear the unit
variable file. If a .vr file was loaded into load. 2. If the unitload was
Error using CLEAR built- memory at Controlled start, it can only loaded at Controlled start,
PALL-059 WARN in be cleared at Controlled start. youthe
Set willproduct_id
have to go into the
PALL-063 WARN Id is uninit in UL %s Product-id is not set in the UL file. UL file from Unit load
The motion to P1, P2 or P3 on the
PALL-064 WARN MOVE TO done teaching aid was successful. None.
An invalid register value was From the DATA menu,
PALL-065 PAUSE Invalid reg value %s encountered. verify that the register
defined, if it is between 1-
PALL-066 PAUSE Reg %s could not be set The register operation failed. 64, and if it has the right
From the DATA menu,
An internally calculated value V could verify that the register is
PALL-067 PAUSE Reg value not set %s not be set to the register R. defined, is in the range 1-
The infeed on which the unit load Make the infeed-unit load
Infeed/Pallet for UL %s enters the workcell was not assigned in assignment in the
PALL-068 PAUSE unknown the PalletSystem menu. PalletSystem SETUP
A valid unit load number was not found From the Mixed UnitLd
at the layer indicated for the mixed unit menu, indicate valid unit
PALL-069 PAUSE Invalid UL %s found load. load numbers for each
Not all pallets assigned Not all the pallets have been assigned a Make sure that in the
PALL-071 WARN UL unit load in the PalletSystem menu. PalletSystem menu, all of
Not all infeeds assigned Not all of the infeeds have been Make sure that in the
PALL-072 WARN UL assigned a unit load in the PalletSystem PalletSystem menu, all of
Station teaching All the teaching aid points have been
PALL-073 WARN completed taught, and the teaching of the station None.
1. Select PM_MAIN from
the SELECT screen. 2.
Perch position not The perch position is uninitialized (has Press DATA. 3. Jog the
PALL-074 PAUSE taught not been taught). robot to the perch
Moving to perch This is a notification that the robot will
PALL-081 WARN position.. move
This isto the perch position.
a notification that the pallet is None.
PALL-082 WARN Indexing pallet %s beingisindexed.
This a notification that the slip sheet None.
PALL-083 WARN Placing slip sheet %s is being placed. None.
Operator Panel E-stop The program cannot run with the 1. Release the operator
PALL-085 PAUSE ON operator panel EMERGENCY STOP panel EMERGENCY STOP
Teach pendant E-stop The program cannot run with the teach 1. Release the teach
PALL-086 PAUSE ON pendant EMERGENCY STOP button pendant EMERGENCY
Teach pendant is The program cannot run with teach 1. Disable the teach
PALL-087 PAUSE enabled pendant enabled. pendant. 2. Press RESET.
Pal Stop must be PALLET STOP is already on. You can Disable PALLET STOP, then
PALL-088 WARN disabled only have either CYCLE STOP or PALLET enable CYCLE STOP.
Cycle Stop must be CYCLE STOP is already on. You can only Disable CYCLE STOP, then
PALL-089 WARN disabled have either CYCLE STOP or PALLET enable PALLET STOP.
Slip sheet stack door One of the slip sheet stack doors is Find out which slip sheet
PALL-091 PAUSE open open. stack door is open, and
The robot is attempting to transfer a
unit load file that is being used by the 1. Stop the robot. 2.
File is in use by robot. robot. It is being used in production, or Peform an ABORT ALL. 3.
PALL-101 WARN Cannot transfer is being edited using the SETUP Try the file transfer again.
Either (P1,P2), (P1, P3), (P2, P3), or Use MODIFY under the
PALL-105 WARN Station not taught (P1,P2,P3) were all taught at the same Infeed Stn SETUP menu to
Cannot switch in 1 This is only a message.
PALL-106 WARN Pallet Cell There is only one pallet in the workcell. NOSWITCH is the only
Check if the gripper is in
Part not present in tool The robot did not get part presence or contact with the part and
PALL-108 WARN %s faulty part presence sensor. determine why the part
Part still present in tool The part presence sensor is still Check if the part presence
PALL-109 WARN %s detecting a part or faulty sensor. is OFF and if it is not,
The number of pallets is greater than 1 This is only a message. By
NOSWITCH illegal when (one) and the pallet switch was default, PalletTool forces
PALL-112 WARN pallets > 1 NOSWITCH. This is not allowed in PER_PICK. You can change
Please enable teach The program cannot run if teach This if for safety reasons.
PALL-113 WARN pendant pendant is not enabled. Enable the teach pendant,
A partial or completed pallet is present
Must index pallet at the station where you want to Choose the Index pallet
before changing change the product. If the existing from the menu and index
PALL-114 WARN product pallet is not indexed, then the new the existing pallet first.
Part of the application setup of an R-J2
robot is done at the first Cold start. This
can take up to 20 seconds. The teach
Coldstart setup pendant Hints menu will be displayed
PALL-115 WARN complete. before PalletTool has loaded all of its None.
Check the available
memory. If RAM is full,
Error creating new An error occurred while creating a new clear unneeded data and
PALL-117 WARN variables file. robot could not find the requested
The try theor
Teach operation
load the again. If
PALL-118 WARN Cannot
Stn use loaded
file not MODIFYor data.
The specified station is not taught or required data.
PALL-119 WARN created loaded.
Could not read the unitload .dt file. A Teach
Check or
theload the station.
MOTET
PALL-121 WARN Could not read %s Data error exists. communication and PTPC
Cannot go to DETAIL Not all the gripper information has Display the Gripper
PALL-122 WARN page been specified in the PalletSystem MENU, and fill in the
Data modification The robot is in production. SETUP data Wait until production is
PALL-123 WARN disallowed cannot be changed during production. aborted and then make
The data was not set up properly but Make sure the value is set
PALL-124 WARN Setting length = width was corrected automatically. as needed.
The data was not set up properly, but Make sure the value is set
PALL-125 WARN Setting width = length was corrected automatically. as needed.
PALL-126 WARN Setting layer = 1 was corrected automatically. as needed.
PALL-127 WARN Flip not allowed was corrected automatically. as needed.
Pallet Switch type The data was not set up properly, but Make sure the value is set
PALL-128 WARN changed
Layer num outside was
Layercorrected automatically.
count cannot be more than 40 or as needed.
Pick a legal layer, and
PALL-131 WARN range (1-40) less than 1. retry the operation.
The program cannot run because an
Cannot resume error condition will not clear. When on Fix the error condition,
PALL-132 WARN program the ALARM page, select this error and and press RESET.
If the unitload is being used in 1. Wait until production is
production it cannot be cleared. If a aborted and clear the unit
unitload was loaded into memory at load. 2. If the unitload was
Controlled start, it can only be cleared loaded at Controlled start,
PALL-133 WARN Couldload
Unit notnum
clearout
fileof at Controlled
Specified Unitstart.
load number was out of you willahave
Specify Unitto go to
load
PALL-137 WARN range range. number in the range 1-
Only Pal OR Cycle stop PALLET STOP or CYCLE STOP is already Disable one before trying
PALL-138 WARN allowed on. You can only have either cycle stop, to enable the other.
The routine that calculates the final
destination position while moving from
the current source position has failed.
%s :wrist angle The preceeding error should be : 'Error:Check that all positions
PALL-139 WARN correction failed Infeed=x Pallet=y Unit=x'. This means are in range.
An old smaller NUMREG.VR or PalletTool logic has
POSREG.VR file was loaded onto the automatically set the
Cycle power to increase controller. The number of registers or number of registers to the
PALL-140 WARN registers position registers was changed to fewer necessary size again. But a
An old smaller SYSMACRO.SV file was PalletTool logic has
Cycle power to increase of macros was changed to fewer than number of macros to the
PALL-141 WARN macros what the current version of PalletTool necessary size again. But
Press the SELECT key and
choose a program to run.
To run a teach pendant program .tp in If you are trying to run
local mode, you must first select the PalletTool, the keyswitch
PALL-142 WARN Program not selected program. must be set to REMOTE. If
The robot is in production. Set up data Wait until production is
PALL-143 WARN Data in use by Robot cannot be changed during production. aborted and then make
This is only a warning
Visit layer spacing/flip Number of layers in the unit load was message to remind you to
PALL-144 WARN menus changed. visit the layer flips and
This error is a general purpose text
message posted by PalletTool during
PALL-145 WARN %s production runs for displaying status of None
The operator selects which device can The UOP/PLC must be set
UOP Ignored. Wrong be used to start palletizing on the as the start device or the
PALL-146 WARN Start Mode SETUP Pallet System menu. The start UOP signal will be
The operator must select which device The SOP must be set as
SOP Ignored. Wrong can be used to start palletizing on the the start device on the
PALL-147 WARN Start Mode SETUP Pallet System menu. The start SETUP Pallet System
The approach position the robot is Verify that the value of
trying to go to is not reachable. The $UTOOL and/or
preceeding error should be : 'Error: $MNUTOOL are correct. If
Approach Posn out of Pallet=x Unit=y'. This means that the the robot stopped while
PALL-148 PAUSE range robot was working with pallet x and heading towards the
Verify that the value of
$UTOOL and/or
The placement position the robot is the robot stopped while
PALL-149 PAUSE Unit Posn out of range trying to go to is not reachable. heading towards the
There was a problem loading the Check the communication
PALL-150 WARN Loading error - %s specified file. line, and make sure that
The specified file already exists on the Delete the file from the
PALL-151 WARN %s exists. Not loaded controller. controller before trying to
Warning-ignoring entry The gripper's setup information has an Edit the gripper data and
PALL-152 WARN where CASE# was 0. illegal (zero) case number. specify a valid case
PALL-153 WARN Initializing Data Initializing data for production. None.
Error setting gripper The robot could not read or write the Check the available
PALL-154 WARN data %s gripper data. memory. Remove
PALL-155 PAUSE Register not defined %s This is just a debug message None
R[80] is not set up properly when SET Make sure R[80] contains
PALL-156 PAUSE Current pallet unknown UTOOL macros are used. the number of the desired
UTOOL unknown for The UTOOL of the pallet requested in Make sure all the stations
PALL-157 PAUSE tool %s R[80] is not set up properly. are completely set up.
This is a warning message posted by
PALL-158 PAUSE Last Utool not known PalletTool to help debug problems with None
During product changeovers through
the Cycle Stop menu, you are first
prompted to enter the pallet number Change the unitload
Can change UnitLd on where you want to bring the new number of the selected
PALL-159 WARN palt %s only unitload. This
PalletTool is followed
production by another
is aborted pallet.to other errors in
Refer
PALL-160 WARN PalletTool aborted because of an error. the ALARM log for details.
'Not all cases have I/O Each of the gripper's cases must have Complete the gripper
PALL-161 WARN defined inputs and outputs defined for control. information tables.
Recvd PLC signal for This is a message to notify the user that
PALL-162 WARN indexing pallet %s PLC data for initiating product None.
Infeed I/O undefined- Make sure the infeed I/O
PALL-163 WARN OKTOPICK.TP The infeed I/O must be set up. is set up properly: 1. Press
Gripper number not set R[15] is not set up properly when Make sure R[15] contains
PALL-164 WARN in register gripper macros are used. the number of the desired
R[15] is not set up properly when
gripper macros are used. The Gripper
numbers supported in PalletTool are: * Make sure R[15] contains
Invalid Gripper number Single = 1 * Double icc = 3 * Triple case the number of the desired
PALL-165 WARN set in register = 5 * Custom 1 = 6 * Custom 2 = 7 * gripper.
Certain variable files can change with
Upgrading %s variable each release of PalletTool. Files saved
PALL-166 WARN file with an older release are automatically None.
Certain variable files can change with
Variable file is older each release of PalletTool. Files saved
PALL-167 WARN version with an older release are automatically None.
One of the following has occurred: 1.
The number of units in the unitload is
Units/layer %s exceeds less than the start unit entered. 2. The Enter a valid number of
PALL-168 WARN allowed maximum number of units is greater than the layers.
One of the following has occurred: *
Number of layers %s The number of units in the unitload is
exceeds allowed less than the start unit entered. * The Enter a valid number of
PALL-169 WARN Invalid
maximumpattern type in number
An illegalofmatrix
units is greater
type than the
was received layers.the MOTET
Check
PALL-170 WARN data file from PalletTool PC. communication and PTPC
System still in fault An error condition exists such that the Fix the error condition,
PALL-171 PAUSE state robot cannot be reset. and press RESET.
The PLC sent an invalid infeed number. Make sure a valid infeed
Invalid infeed number The number must be greater than 0, number was sent by PLC.
PALL-172 ABORT from PLC %s and less than or equal to the 'number Check the PLC
PLC sent an invalid pallet number. The Make sure a valid pallet
Invalid Pallet number number must be greater than 0 and number was sent by the
PALL-173 ABORT from PLC %s less than or equal to the 'number of PLC. Check the PLC
Setup Application This indicates that PalletTool Controlled
PALL-174 WARN Completed start setup is complete. None.
Can't use labels-out for Labels out is supported only for the
PALL-175 ABORT triple gripper single and double case gripper. None.
An error occurred while attempting to
PALL-176 ABORT Cannot upgrade vr file upgrade an older variable file to the Create a new variable file.
The selected unitload has the wrong
Single or Double matrix type (it is less than type 4). This
PALL-177 ABORT pattern not supported very old data is no longer supported by Create a new unitload.
Data not calculated for To run in production, you must Display the SETUP
PALL-178 WARN UL %s calculate each unitload's optimal path OPTIMAL PATH screen for
Check GETINF.TP for
GETINF.TP returned an infeed number infeed/unitload data.
which is assigned ul = 0. In other words, Check production setup
GETINF.TP not setup PalletTool received an invalid infeed data. GETINF.TP is used to
PALL-179 WARN correctly
Label data may need number, most likely 0
The optimal path data wasfrom GETINF.TP. return an infeed
Check the number
labels out data
PALL-180 WARN updating automatically updated. for completeness.
Labels out was selected for a gripper
PALL-181 WARN Labels-out disabled that is not supported. None.
Labels out is supported only for the
Not allowed for this single and double case gripper. -- OR--
PALL-182 WARN gripper type 'Place
The remaining
CYCLE boxes' has
STOP option is not allowed None.
been
PALL-183 WARN Cycle stop disabled disabled.
The CYCLE STOP option has been None.
PALL-184 WARN Cycle stop enabled enabled.
The PALLET STOP option has been None.
PALL-185 WARN Pallet stop disabled disabled.
The PALLET STOP option has been None.
PALL-186 WARN Pallet stop enabled enabled. None.
Active only during CYCLE STOP and PALLET STOP functions
PALL-187 WARN palletizing are only available when the robot is None.
Palletizing:STEP mode The STEP key was pressed before None. The STEP mode is
PALL-188 WARN not allowed entering or while in palletizing mode. automatically cleared by
Check the variable
pick_ar_tc_n and
pick_ar_tc_f in the unit
Unit load gripper data has not been load file. Also check the
PALL-189 ABORT Unit load data error. completely set up. variables new_order_n
.VR file has not been During the transfer of data from the PC, Check the available
PALL-190 WARN created the .VR data file could not be created. memory. If RAM is full,
TEMP DRAM memory is Temporary memory is getting too low Delete any unneeded data
PALL-191 WARN low to download more unitload files. before downloading more
Cannot CALC; TEMP Temporary memory is too low to Delete any unneeded data
PALL-192 WARN memory low calculate a unitload. and perform a Cold start
The file was not copied. The file is Cold start the controller,
PALL-193 WARN File copy not done either in use, or there's not enough and retry the operation.
Units missing in All units must be picked up. Not all the Check that no units have
PALL-194 WARN sequence. units have been listed in the NEW been listed twice, change
The total number of PLACEs must add Make sure the sum of the
PALL-195 WARN All units not picked up. up to the number of PICKs for each row PLACEs adds up to the
Pick too big error: row The PICK size cannot be bigger than the Check the selected
PALL-196 WARN %s gripper's number of grips. gripper's grip size, change
The PLACE values must be placed into Make sure the sum of the
the PL1 column first, then PL2, then PLACEs adds up to the
Illegal place sequence: PL3. The total of the PLACEs must add number of PICKs, and are
PALL-197 WARN row %s up to the number of PICKs for each row in the proper columns.
In the Sequence menu,
This is a general configuration table you need to make sure
PALL-198 WARN Other error: row %s error. that for the total number
All units not listed in Check that no units have
PALL-199 WARN FlipConfig All units must be picked up. been listed twice, change
All units not listed in Check that no units have
PALL-200 WARN NoFlip All units must be picked up. been listed twice, change
The total of the PLACEs must add up to Make sure the sum of the
Too many units picked the number of PICKs for each row of PLACEs adds up to the
PALL-201 WARN up. the config table. And, the total number number of PICKs.
Part drop recovery: the selected option
Illegal. At perch or cannot be used when the robot is at
PALL-202 WARN maintenance. perch or at the gripper maintenance Choose another option.
NO boxes are Part drop recovery: the selected option Choose another option, or
PALL-203 WARN remaining. must have boxes remaining in the check the gripper sensors.
Illegal:boxes are Part drop recovery: the selected option Choose another option, or
PALL-204 WARN remaining! cannot have boxes remaining in the check the gripper sensors.
Error - Processing UL There are errors in the unitload data Correct the unit load
PALL-205 WARN data NOT done that caused the CALC calculations errors, and try the CALC
The requested unitload gripper type
cannot be run on this controller. That
Invalid Unit load req: ul is, a multi-case gripper unitload can
PALL-206 WARN %s only be run if the multi- case option is Choose another unitload.
Item %s : illegal data There is something wrong with the data Retype the data, and try
PALL-207 WARN ignored that was entered. the operation again.
Item %s : duplicate data The item in error is a duplicate of Check the entered data.
PALL-208 WARN ignored another entry on the menu. The duplicate will be
Cannot CALC; PTPC This unitload cannot be calculated Try this operation again
PALL-209 WARN production running. during production when PalletTool PC when you are not running
Xfer in process, cannot The same unitload as being transferred Try the operation again
PALL-210 WARN edit file from PalletTool PC cannot be edited. when not transferring or
The controller could not read the .dt Check the MOTET
file. This is a data error. However, a communication and PTPC
PALL-211 WARN Unitload not replaced. unitload with the same name still exists status.
The unitload data file transferred from Delete any unneeded
PalletTool PC was not read because data, and perform a Cold
PALL-212 WARN DT file not read: %s there is not enough memory to save start.
Dropped part during A part was dropped during part drop Check why parts are being
PALL-213 ABORT recovery-abort recovery. PalletTool does not support dropped. Continue normal
You have changed the length of the Make sure all station
The tool pointer length station teaching tool. All station positions are taught with
PALL-214 WARN is changed. positions must be taught using the the same tool length.
Moving to maintenance The robot is moving to the gripper
PALL-215 WARN position.. maintenance position. None.
The slip sheet position registers have Change the position
SlipSheet pos. must be positions that are taught in JOINT representation to
cartesian representation. For the slip sheet logic CARTESIAN: 1. Press
PALL-216 ABORT representation to work properly, the positions must be DATA. 2. Press F1, [TYPE].
Verify that the value of
$UTOOL and/or
Position is not The position the robot is trying to go to the robot stopped while
PALL-217 PAUSE reachable is not reachable. heading towards the
Message buffer to PC is More than 20 messages have not been Check the MOTET
PALL-220 WARN full read by PTPC. The communication is communication and PTPC
Message received from PalletTool-
PC/MOTET was not in the proper
format. The PT-PTPC message types Check the MOTET
PTPC message type %s - are: * 1-start * 2-cycle stop * 3-pallet communication and PTPC
PALL-221 WARN illegal data received stop * 4-status * 5-go * 6-abort * 7-unit status.
PTPC command PalletTool is not in the correct mode to
PALL-222 WARN PTPC
ignored,
%s -inignored,
wrong mode act on this ismessage.
PalletTool busy and cannot act on Try the operation again.
PALL-223 WARN robot busy this message. Try the operation again.
PTPC sent an invalid infeed number. Make sure a valid infeed
The number must be greater than 0 number was sent by PTPC.
Invalid infeed number and less than or equal to the 'number Make sure that the robot
PALL-224 WARN from PTPC: %s of infeeds' set up. has current setup data
PTPC sent an invalid pallet number. The Make sure a valid pallet
number must be greater than 0 and number was sent by PTPC.
Invalid Pallet number less than or equal to the 'number of Make sure that the robot
PALL-225 WARN from PTPC: %s pallets' set up. has current setup data
PTPC sent an invalid gripper number.
The Gripper numbers supported in
PalletTool are: * Single = 1 * Double icc Check the MOTET
Invalid Gripper number = 3 * Triple case = 5 * Custom 1 = 6 * communication and PTPC
PALL-226 WARN from PTPC: %s Custom 2 = 7 * Custom 3 = 8 * Custom status.
Wrong unitload recvd PTPC sent the wrong unit load. The Check the MOTET
PALL-227 WARN from PTPC:
Unitload not%srecvd from unitload that was expected is
PTPC did not send the requested given in communication
Check the MOTET and PTPC
PALL-228 WARN Setup
PTPC %sdata not recvd unitload
PTPC did data. communication
not sent the requested setup Check the MOTET and PTPC
PALL-229 WARN from PTPC data. communication and PTPC
PalletTool requested a unitload from Make sure the right
using unitload NOT PTPC that PTPC did not have. But unitload is being used.
PALL-230 WARN from PTPC PalletTool has a copy of the unitload Consider changing the
PTPC: must be PAUSED PalletTool is not in the correct mode to Pause or abort the robot,
PALL-231 WARN or ABORTED act on this message. and try the operation
Fork infeed positions The conveyor infeed positions must be Teach the conveyor infeed
PALL-235 ABORT not taught. taught in order to use the fork or bag positions.
Errors in infeed The conveyor infeed positions must be Teach the conveyor infeed
PALL-236 ABORT positions. taught correctly in order to use the fork positions.
Fork not big enough to The boxes are too big for this fork Check the conveyor infeed
PALL-237 ABORT pick box gripper. positions and gripper
Infeed %s end-of-batch MULTI_IO.TP logic received a signal to
PALL-240 WARN signal received perform end of batch processing. None.
Previous end of batch signal processing
Infeed %s IGNORE end- is still in progress, or a CYCLE STOP or
PALL-241 WARN of-batch signal PALLET STOP is still in progress. None.
End-of-batch PLC - The robot is requesting pallet, unitload
PALL-242 WARN request infeed number and infeed information from PLC. None.
Set the Part ID method to
End-of-batch PLC - Part ID select method must be set to PLC: 1. Press MENUS. 2.
PALL-243 WARN wrong part ID method PLC. Select SETUP. 3. Select
Wait for PLC index The end of batch is complete. The
PALL-244 WARN pallet %s
End-of-batch processing robot is waiting for the PLC to index the None.
PALL-245 WARN End-of-batch
error none at The end of batch request was ignored. None.
PALL-246 WARN infeed Nothing exists at the infeed to pick up. None.
During a product changeover with the The end of batch feature
End-of-Batch feature enabled, works only when there
End-of-batch enough at PalletTool expected fewer than needed are fewer boxes than
PALL-247 WARN End-of-batch
infeed boxes
part drop - The at infeed
robot for that
dropped a boxcycle.
duringHowever,
the needed for
Replace thethat cycle.box,
dropped
PALL-248 ABORT abort end of batch logic. and continue the
Set up the bag gripper
UTOOL in the gripper
Bag Gripper UTOOL not The bag gripper UTOOL is not set up in SETUP menu. Without this
PALL-252 WARN set
UNUSED ERROR the Gripper SETUP menu. data, you cannot teach
PALT-000 WARN
ABORT. CODE(PLER00)
Inadequate register Please confirm palletizing
PALT-001 G
ABORT. value Column/row/layer number is illegal. register.
PALT-002 G
ABORT. shift vector
Computing rotation
PALT-003 G
ABORT. matrix Increment value of parettaizing config Please correct increment
PALT-004 G
ABORT. Increment value
Application item is ill screen is illegal. value
PALT-005 G
ABORT. unfound
PALT-006 G
ABORT. Amr number isnot
Configulation differnet
PALT-007 G
ABORT. decided
Route pattern
PALT-008 G
ABORT. duplicated
PALT-009 G
ABORT. Bottom point unfound Check route pattren in
PALT-010 G
ABORT. Route pattern unfound Route pattern unfound. palletizing route pattern
PALT-011 G
ABORT. point unfound
Route Bottom point
PALT-012 G
ABORT. unfound
PALT-013 G
ABORT. Memory id error
PALT-014 G
ABORT. Illegal bottom number
PALT-015 G
ABORT. Illegal pattern number
PALT-016 G
ABORT. Illegal rout number
PALT-017 G Illegal current number
ABORT.
PALT-018 G
ABORT. Illegal key input
PALT-019 G
ABORT. Illegal point data
PALT-020 G
ABORT. Function code unfound
PALT-021 G
ABORT. Register
Item codeindex ill value
cannot be
PALT-022 G
ABORT. found
PALT-023 G
ABORT. Illegal element
Calculation value
error Teach bottom point all?
PALT-024 G
ABORT. occured Palletizing data is imcomplete. Teach rout point all?
PALT-025 G
ABORT. OS errorread/write
Cannot occured to Cannot read/write to palletizing Check palletizing register
PALT-026 G
ABORT. PL[] register. index
PALT-027 G
ABORT. Failed program close
PALT-028 G
ABORT. Failed
Not program
exist open
application
PALT-029 G data
Pallet number is over Don't teach palletizing instruction over palletizing instruction
PALT-030 WARN max 16 don't teach more than 16
Can not be set FREE or In FREE configuation, can not be set In FREE configuation, can
PALT-031 WARN INTER ERROR
UNUSED INTER over two directions be set INTER only one
PALT-032 WARN CODE(PL32)
This speed type isn't Palletizing option doesn't support this Please select the other
PALT-033 WARN supported speed type motion statement.
Layer pattern num was The layer pattern number was 0. Delete the pallet
PALT-034 WARN 0.Changed to 1 Because this is an illegal value, change instruction and teach it
If Motion group 1 is not set up, The Set up Motion group 1.
PALT-035 ABORT Palletizing
Group 1 is not set up. A
Internal Palletizing option
palletizing is not
internal avaiable.
error has 3.12.3 PMON Alarm Code
PALT-036 Error
Invalid command is occurred.
This command can not be executed in This is the
Remove internal
the invaliderror.
PALT-037 executed
PROFIBUS-FMS System palletizing. command.
PFMS-000 WARN error(%d)
PROFIBUS-FMS PCB not System internal error Notify FANUC
Please install PROFIBUS
PFMS-001 WARN installed PROFIBUS is not installed PCB.
Connection is The connection with host is Please check the host
PFMS-002 WARN disconnected disconnected. status or cable between
The robot received the negative Please check the host
PFMS-003 WARN Receive negative reply confirmation or response. status.
The specified program is being edited Abort the specified
PFMS-004 WARN
PAUSE. %s program is in use or executing. PCB firmware is
PROFIBUS-FMS program. Or select it once
PFMS-005 G CMI error(code = %d) Data
abnormal.
could not be obtained from the Notify FANUC
PICK-002 GET_VAR failed %s data source. Check the data source.
PICK-003 SET_VAR failed %s Data could not be set in data source. Check the data source.
Data modification The robot is in production. Setup data Wait until production is
PICK-004 disallowed cannot be changed during production. aborted, and then make
No more groups The user is attempting to change
PICK-005 installed groups but there is only one installed None.
Robot Grp %s is already The user is attempting to set the The user should first set
PICK-006 master master for more than one robot or Master = FALSE for the
The Host Comm setup is not done for From the Host Comm
this robot. The robot hostname and IP setup menu, assign a
Robot not assigned to address are important for the part name and a valid IP
PICK-007 network Queue manager to communicate with address for this robot.
Check if all robots have a
valid IP address and
An error occurred while this robot tried PickTool software. If ok,
Error communicating to get data from another robot over then document the events
PICK-008 with Robs the robot ring or Ethernet. that led to the error and
Set one of the robots as
PICK-009 No robot is a master No robot has been set as a master. master in the Setup menu.
More than 1 robot is a More than one robot has been set as Check the setup menus of
PICK-010 master master. all the robots and set only
Check the line track setup
menu and ensure that for
the schedule you intend
Error reading LT An error occurred reading Line track to use, and the boundary
PICK-011 boundary boundary data. set you intend to use,
Check the line track setup
menu and ensure that for
the schedule you intend
Error reading LT enc An error occurred reading the Line to use, a proper value for
PICK-012 scale tracking encoder scale. encoder scale exists. If
Max num of robots The maximum number of robots that PickTool can handle a
PICK-013 exceeded Picktool can handle has been exceeded. maximum of 10 robot
Look at the cause code
with the error. Make sure
that Ethernet is set up
An error occurred while reading data correctly with all the
Error getting rob data from robot ROBOT_NAME in the robot robots. Check the Host
PICK-014 %s ring. Comm menu on each
An error was encountered while trying Make sure to record the
Move-TO could not to move to a taught position. It could position correctly. Check
PICK-015 execute be due to a motion limit error or an the associated cause code
Without completing frame teaching of Teach the frame positions
PICK-016 Frame was not taught. The all 3 robot
positions, you cannot
completed proceed to
a move-to correctly.
PICK-017 MOVE TOhas
Position done
not been operation. None.
The position must be
PICK-018 taught The position has not been taught yet. taught.
Position is not The position the robot is trying to move Verify that the value of
PICK-019 reachable to is not reachable. $UTOOL and/or
The DOUT port number specified for Check if the I/O point is
PICK-020 Invalid Conveyor DO[] the conveyor is invalid. configured correctly.
The ID # of the robot The ID# of the robot could not be Check the PK Robot setup
PICK-021 unknown. determined. menu and make sure the
The utilization percent for each robot In the PK Robot menu of
Total util of all robots < does not add up to 100 percent. This each robot, specify
PICK-022 100 prevents load balancing from working percent utilization so that
No PickTool QMGR The Picktool QMGR task global variable Document the events that
PICK-023 variable does not exist. No dynmaic load led to the error, and
Not all Reference sysv The Picktool QMGR task can not get all Document the events that
PICK-024 exist the relevant system variables. led
Set to
upthe
theerror, and
encoder
PICK-025 Encoder not setup yet The Encoder has not been set up yet. correctly.
An invalid Encoder setting of Correct the system
PICK-035 Invalid encoder number $TRK_ENC_NUM is set in the $LNSCH[] variable
PickTool setting.
only supports up
PICK-036 Invalid motion group An invalid motion group was specified. to 2 motion groups.
Follow the process of
PICK-037 Robot is not calibrated The robot is not calibrated. setting
Move the thetarget
master count
upstream
PICK-038 DIN port is ON The digital input port is already ON. ahead of the DIN location.
An invalid $LNSCH number was Change the line tracking
PICK-039 Invalid
Not $LNSCH number
all positions are specified. schedule
Record allnumber to a
three required
PICK-040 recorded Not enough recorded positions. positions.
Recorded points are too Positions are recorded too closed to Make sure the recorded
PICK-041 close each other. positions are at least 50
$LNSCH has not been The Line Tracking Schedule has not Set up the line tracking
PICK-042 setup been properly set up. schedule before setting
The track frame has been updated
PICK-043 No duplicated update before.
Some required steps have been None.
Follow the setup wizard's
PICK-044 Please follow the steps skipped. steps.
Go to controller of the
Invalide reference reference robot, select
PICK-045 position The reference position is uninitialized. PickTool track frame
The track frame should
have been set up before it
can be used for reference.
PICK-046 Set Track Frame first. Set Reference requires track frame. Select another robot that
The specified file could not be opened Make sure that the file
to read or write data. The file might be exists on the file device
PICK-100 Error opening %s. missing or the file device might be full. and/or that there is room
PickTool was asked to perform a Make sure that a valid
function with an invalid object Id. For object id in the range of
Invalid PickTool object example, read data for a LBG that does the array size of the
PICK-103 id. not exist. Or, an uninitialized id was system variable is used.
Refer to the associated
error code. OS -012
System error This error
Failed to notify PC The PC Monitor task could not be may be seen when
PMON-001 WARN Monitor
Memory allocation notified.
Not enough memory to create client attempting
Perform COLD to monitor
start of a
PMON-002 WARN failure connection controller.
Connect to PMON Check physical
PMON-003 WARN server failed
PMON initialization Failure to connect to PMON
The PC Monitor task had an Server connections and check to
PMON-004 WARN failure initialization
The PC Monitorfailure..
task had an internal error code.
PMON-005 WARN PMON timer failure timer failure. error code.
The PC Monitor task had an internal
PMON task status read task status read failure. The
PMON-006 WARN failed accompanying cause code identifies the Refer to cause code.
The PC Monitor Server lost a This is a warning and may
PMON-007 WARN Lost connection to %s connection with the named client. be normal.
PMON curpos read The PC Monitor task had an internal Refer to the associated
PMON-008 WARN failed CURPOS read failure. error code.
The PC Monitor task had an internal Somehow, PMON is out of
PMON monitor not monitoring failure. The requested sync with the PC. In some
PMON-009 WARN found monitor number was not found in the cases, this may be normal
Unknown PAINTtool PaintTool has detected an unknown Refer to the teach
PNT1-001 WARN error error. pendant
Press RESETerror
to log forthe
clear the
PNT1-002 WARN Press master reset The system is in an error condition. error.
Correct the error, if any,
PNT1-003 WARN Reset failure The reset procedure has failed. and
Turntry
offthe
thereset
robot servo
PNT1-004 WARN Robot Servos
Production Disabled
mode is The robot servo disconnect is on. disconnect.
PNT1-005 PAUS disabled switch must
REMOTE production
The remote mode
switch is ininput is off.
the LOCAL None.the remote switch in
Place
PNT1-006 WARN be REMOTE position. the REMOTE position.
The machine lock is on going into Disable the machine lock
PNT1-007 WARN Machine
Robot lock isisON
motion not production. on the
The UOPteach pendant
enable input
PNT1-008 WARN enabled The UOP enable input is OFF. must be ON.
An invalid job number was received The PLC must initialize the
PNT1-009 ABRT Invalid job %s received from the PLC. robot with a valid job
Invalid tutone %s An invalid tutone option was received The PLC must initialize the
PNT1-010 ABRT received from the PLC. robot with a valid tutone
Invalid repair %s An invalid repair option was received The PLC must initialize the
PNT1-011 ABRT received from the PLC. robot with a valid repair
Invalid color %s An invalid color number was received The PLC must initialize the
PNT1-012 ABRT received from the PLC. robot with a valid color
The teach pendant JOB program is not A teach pendant JOB
loaded, or was not created on the program must be created
PNT1-013 ABRT Job (%s) is not found controller. or loaded in the controller
An invalid job number was received At the PLC, initialize the
from the PLC. Therefore, the robot robot with a valid job
PNT1-014 WARN Invalid job %s in queue cannot put the job into the job queue. number in order to
An invalid color number was received The PLC must initialize the
Invalid color %s in from the PLC. The robot cannot put the robot with a valid job
PNT1-015 WARN queue color into the color queue. number in order to
Remove unneeded job(s)
PNT1-016 WARN Job queue is full The job queue is full. from the job queue before
Remove color(s) from the
PNT1-017 WARN Color queue is full The color queue is full. color queue before
Another task has detected that the Turn off the controller,
PNT1-018 WARN Shell aborted or paused main task has aborted or paused. then turn it on again.
Wait for autoprocessing Autoprocessing of the last editted Wait for autoprocessing
PNT1-019 WARN Invalid
to finishjob type (%s) program
An invalidisjob
stilltype
in process. to complete
was received from The PLC mustbefore
initialize the
PNT1-020 ABRT received the PLC. robot with a valid job
There is an alarm that must be cleared Press RESET to clear all
PNT1-021 WARN System is in error status before Test Cycle can be run. system alarms.
The job is not run and the encoder
counts indicate that the part is past the
Sync Que-Job passed Start switch (plus tolerance). The robot
PNT1-022 WARN window deletes the job from the queue, posts None.
The job is not run and the encoder
counts indicate that the part has not
made it to the Start switch (minus
Sync Que-Job before tolerance). The robot will hold onto
PNT1-023 WARN window that job for the next start signal, post None.
If your system requires
these UOP signals, you
must enable these inputs
UOP's assigned but The User Operator Panel (UOP) inputs on the Teach Pendant as
PNT1-024 PAUS disabled! are assigned, but have been disabled! follows: 1. Press MENUS.
Bad Ghost Job Override Indicates the ghost job override being Please change the Ghost
PNT1-025 %s used on the current ghost job being Job override to a value
Parm %s Value beyond An attempt was made to set an Verify the specified
PNT1-034 WARN limits applicator parameter output beyond its parameter's min/max
SETUP Applicators: The I/O information
PNT1-039 WARN I/O setup verified OK is correct and complete. None.
SETUP Applicators: The I/O information Check that the output
Error attempting to for an applicator was changed and is in type, output number, rack
PNT1-040 WARN setup I/O error. and slot number, first bit
The application is attempting to adjust
Adj. colors table sizes to the size of the color tables based on
PNT1-045 WARN %s the configuration variable setting. None.
The application is attempting to adjust
Adj. color valves table the size of the color valve table based
PNT1-046 WARN size to %s on the configuration variable setting. None.
There is not enough memory available Use a smaller setting that
Failed to adj. color table for the application to adjust the size of is within the memory
PNT1-047 WARN size the color tables to the match requested constraints of the
There is not enough memory available Use a smaller setting that
Failed to adj. color for the application to adjust the size of is within the memory
PNT1-048 WARN valve table size the color valves table to match the constraints of the
Verfiy that the number of
Invalid parameter An invalid parameter indicator value applicator control
PNT1-053 WARN indicator
No channel/parameter was sent from the PLC.
The PLC sent a parameter indicator parameters set up in the
Correct the parameter
PNT1-054 WARN indicated value of 0. indicator value at the PLC.
Manual inputs are On manual mode entry, all PLC manual
PNT1-055 WARN enabled mode input functions are enabled. None.
Manual inputs are On manual mode exit, all PLC manual
PNT1-056 WARN disabled mode input functions are disabled. None.
Manual enabled during Manual mode is being initiated during Robot motion must
PNT1-057 WARN motion robot motion. complete before it enters
Manual enabled in Manual mode is being initiated during a The color change cyle
PNT1-058 WARN color cycle color change cycle. must complete before the
The teach pendant cannot be enabled
PNT1-059 ABRT TP Enabled in cycle when running a remote color change None.
For continuous line systems, indicates Expand the robot
that too many parts have passed the boundaries, or lower the
PNT1-064 ABRT Tracking que exceeded part detect switch within the current conveyor speed.
Linetracking parameter For continuous line systems, a line Ensure that all tracking
PNT1-065 WARN undefined tracking parameter is undefined and is parameters have been set
Railtrack parameter For continuous line systems, a rail Ensure that all tracking
PNT1-066 WARN undefined tracking parameter is undefined and is parameters have been set
The current software
An attempt was made to use an invalid supports tracking frames
PNT1-067 WARN Invalid tracking frame tracking frame number. 1-6. The tracking frame
For continuous line systems, this
warning indicates that the encoder
PNT1-068 WARN Encoder count rollover counter has detected a rollover None.
For continuous line systems, this Reduce the minimum
warning indicates that the trigger distance value to less than
Part Detect less than distance is less than a pre-determined the job spacing distance,
PNT1-069 WARN min dist value. The part detect will be ignored or replace the old part
For continuous line systems, the robot Swap the leads on the
Conveyor direction has determined the conveyor is running encoder repeater board
PNT1-070 WARN incorrect in the wrong direction. Part detects will so that the encoder
For line tracking systems only: This is a
warning that the part has tracked too Decrease the cycle time of
%s skipped-over max far to be played back. The previous job the job or decrease the
PNT1-071 WARN travel or color change took too long to play. color change cycle.
Tracking encoder The robot is detecting a problem with Check the encoder cable,
PNT1-072 PAUS disconnected the tracking encoder cable. and replace it if necessary.
The robot being used is not supported If the robot library (setup)
in PaintTool line tracking for a left hand does not offer a selection
Right-Hand Rule only arm type. The robot is not a P-Series for right or left hand
PNT1-073 WARN for this robot robot. robots, then no remedy is
Reconnect the tracking
encoder or determine if
DAL alarm(Track The tracking encoder has been the encoder connector is
PNT1-074 PAUS encoder:1) disconnected, or is faulty. faulty. The robot
The TCP (Line Tracking) or Extended Adjust the Entry Limit
Extreme entry position Axis (Rail Tracking) has been ($LNCFG.$ENTRY_XTRM),
PNT1-075 ABRT violation commanded beyond the Entry Limit or change the Tracking
The TCP (Line Tracking) or Extended Adjust the Exit Limit
Extreme exit position Axis (Rail Tracking) has been ($LNCFG.$EXIT_XTRM) or
PNT1-076 ABRT violation commanded beyond the Exit Limit change the Tracking
Check the alarm log to
Posn unreachable at An unreachable position is detected in find out at which position
PNT1-085 PAUS line %s the adjustment
An interlock precheck
signal fault or PLC E-stop motion
Correct error will occur,
the source of the
PNT1-086 PAUS PLC e-stop detected was detected. fault, and RESET the
The mechanical unit went beyond its Follow the overtravel
normal travel limits and reached an recovery procedure in the
PNT1-087 ABRT Robot overtravel overtravel limit switch. SYSTEM R-J Controller
The operator panel (SOP) EMERGENCY Release the SOP
PNT1-088 PAUS Release SOP e-stop STOP has been detected. EMERGENCY STOP, and
The teach pendant EMERGENCY STOP Turn the teach pendant
PNT1-089 PAUS Release TP e-stop has been detected. EMERGENCY STOP button,
TP enabled during The teach pendant was enabled during The teach pendant cannot
PNT1-090 PAUS production production. be enabled
Disable the during
teach pendant
PNT1-091 PAUS Disable teach pendant The teach pendant is enabled. to continue the program.
Refer to SRVO-023 SERVO Stop error Refer to SRVO-023 SERVO
excess(G:x A:x) in the FANUC Robotics Stop error excess(G:x A:x)
PNT1-092 PAUS Stop error excess SYSTEM R-J3iB Software Error Code in the FANUC Robotics
Refer to SRVO-024 SERVO Move error Refer to SRVO-024 SERVO
excess(G:x A:x) in the FANUC Robotics Move error excess(G:x
PNT1-093 PAUS Move error excess SYSTEM R-J3iB Software Error Code A:x) in the FANUC
DEADMAN switch The DEADMAN switch has been Press and hold the
PNT1-094 PAUS RELEASED released during an operation. The DEADMAN switch to
Fence open during The FENCE1 and FENCE2 circuits are Determine the cause of
PNT1-095 PAUS production open on the EMG control board. the FENCE1 and FENCE2
If you are using UOP
signals, clear the source of
UOP immediate stop The IMSTP (immediate stop) UOP input the fault. If you are not
PNT1-096 PAUS detected was not asserted. using UOP signals, press
A HOLD signal, either from the UOP or Remove the HOLD
PNT1-097 PAUS HOLD active the teach pendant, has been activated. condition,
The currentand press
cycle must be
PNT1-098 ABRT Track destination gone Destination out of window error. aborted, and then
Check the LED status on
PLC interface board. Refer
to A User's Guide to the
FANUC Robotics SYSTEM R-
PNT1-099 ABRT PC serial interface fault The PLC interface serial link has failed. J3iB Controller Remote
This Alarm is echoed to the PLC when
"SRVO-046 SERVO OVC alarm
(Group:%d Axis:%d)" is posted. Refer to Refer to SRVO-046 for the
PNT1-100 PAUS OVC alarm the Teach Pendant alarm screen for remedy.
The taught position was outside the Reteach the position.
normal work envelope of the robot. Refer to the MOTN-017
PNT1-101 ABRT Limit error One of the robot axes could not reach alarm that was triggered
This alarm is echoed to the PLC when
"MOTN-018 STOP Position not Refer to the MOTN-018
PNT1-102 ABRT Position not reachable reachable" is posted. Refer to the alarm for the remedy.
This is a pause condition. The Either reteach the
configuration (Flip/No-Flip) cannot motions using the same
change during a Cartesian (linear or configuration (Flip or No-
PNT1-103 ABRT Configuration mismatch circular) motion. Flip), orthe
Check useerror
a joint motion
message
PNT1-104 PAUS Planner error The planner encountered an error. log for details.
led to the error, record
the software version
number, and contact your
PNT1-105 ABRT Unitialized position This is a system software error. local distributor or the
"SRVO-008 SERVO Brake fuse blown" is Refer to SRVO-008 for the
PNT1-106 ABRT Brake fuse blown posted. Refer to SRVO-008 for the remedy.
"SRVO-027 WARN Robot not
mastered(Group:%d)" is posted. Refer Refer to the SRVO-027
PNT1-107 WARN Robot not mastered to the Teach Pendant alarm screen for alarm for the remedy.
The servo amplifier magnetic contactor Refer to the
PNT1-108 ABRT MCC alarm (MCC) is welded closed. troubleshooting section in
This alarm is echoed to the PLC when a
"SRVO-043 SERVO DCAL
alarm(Group:%d Axis:%d)" alarm is Refer to SRVO-043 for the
PNT1-109 PAUS Discharge current alarm posted. Refer to the Teach Pendant remedy.
"SRVO-044 SERVO HVAL
PNT1-110 ABRT High voltage alarm posted. Refer to the Teach Pendant remedy.
"SRVO-045 SERVO HCAL
PNT1-111 ABRT High current alarm posted. Refer to the Teach Pendant remedy.
"SRVO-047 SERVO LVAL
PNT1-112 ABRT Low voltage alarm posted. Refer to the Teach Pendant remedy.
"SRVO-049 SERVO OHAL1 alarm
Servo amp overheat (Grp:%d Ax:%d)" is posted. Refer to the Refer to SRVO-049 for the
PNT1-113 PAUS alarm Teach Pendant alarm screen for the remedy.
"SRVO-050 SERVO Collision Detect
alarm (G:%d A:%d)" is posted. Refer to Refer to SRVO-050 for the
PNT1-114 ABRT Collision alarm the Teach Pendant alarm screen for the remedy.
"SRVO-062 SERVO BZAL
alarm(Group:%d Axis:%d)" alarm is
Pulse coder battery posted. Refer to the teach pendant Refer to the SRVO-062
PNT1-115 WARN discon alarm alarm screen for further information on alarm for the remedy.
"SRVO-061 SERVO CKAL Refer to the SRVO-061,
alarm(Group:%d Axis:%d)", "SRVO-063 SRVO-063, SRVO-064, or
SERVO RCAL alarm(Group:%d SRVO-066 alarm for the
PNT1-116 ABRT Pulse coder alarm Axis:%d)", "SRVO-064 SERVO PHAL remedy.
"SRVO-065 WARN BLAL
alarm(Group:%d Axis:%d)" is posted.
Pulse coder battery low Refer to the teach pendant alarm Refer to the SRVO-065
PNT1-117 WARN alarm screen for further information on the alarm for the remedy.
"SRVO-067 SERVO OHAL2 alarm
(Grp:%d Ax:%d)" alarm is posted. Refer
Motor overheat to the teach pendant alarm screen for Refer to the SRVO-067
PNT1-118 ABRT occurred further information on the SRVO-067 alarm for the remedy.
"SRVO-068 SERVO DTERR alarm
(Grp:%d Ax:%d)", "SRVO-069 SERVO Refer to the SRVO-068,
Pulse coder CRCERR alarm (Grp:%d Ax:%d)", or SRVO-069, or SRVO-070
PNT1-119 ABRT communication error "SRVO-070 SERVO STBERR alarm alarm for the remedy.
"SRVO-071 SERVO SPHAL alarm
(Grp:%d Ax:%d)" alarm is posted. Refer
Pulse coder position to the teach pendant alarm screen for Refer to the SRVO-071
PNT1-120 PAUS compare error further information on the SRVO-071 alarm for the remedy.
Collision Detection "SRVO-006 SERVO Hand broken" alarm Refer to the SRVO-006
PNT1-121 ABRT (Hand Broke) is posted. Refer to the SRVO-006 alarm alarm for the remedy.
TP disabled during Test The teach pendant cannot be disabled Turn the teach pendant
PNT1-122 PAUS Cycle during Test Cycle.
The battery in the PSU or encoder is ON/OFF switch
Replace the old to ON,
battery
PNT1-123 WARN CE
Battery
switchLow
must be in low or
The zero. Mode Switch is not in
Selector with a AUTO
Select new battery.
mode from
PNT1-124 WARN AUTO AUTO. the Selector Mode Switch.
The system will pause
Operation mode AUTO The Selector Mode Switch was set to when the MODE SELECT
PNT1-125 PAUS Selected AUTO. SWITCH is changed to a
Operation mode T1 when the MODE SELECT
PNT1-126 PAUS Selected The Mode Select Switch is not in AUTO. SWITCH is change to a
Operation mode T2 The MODE SELECT SWITCH was was set when the MODE SELECT
PNT1-127 PAUS Selected to T2. SWITCH is change to a
A limit error was detected during the Check the alarm log to
adj out of limit at line Adjust Precheck process on the find the position in which
PNT1-128 PAUS %s specified line number. the limit error will occur,
I/O Hardware not The I/O hardware that was selected is Make sure I/O hardware
PNT1-129 WARN installed not physically installed. that is being selected is
Press MENUS and select
Data Error (see The I/O Auto Configurator data file File. Display FR:dterrors.ls
PNT1-130 WARN FR:dterrors.ls) contains errors. for a description of the
"SRVO-194 SERVO Servo disconnect" Refer to the SRVO-194
PNT1-131 PAUS Servo Disconnect alarm is posted. Refer to the SRVO-194 alarm for the remedy
Repair the circuit of the
chain 1 (+24V) on the
Chain 1 (+24v) hardware. Set the CHAIN
PNT1-132 PAUS abnormal A single chain 1 (+24V) failure occurred. FAILURE detection to
chain 2 (0V) on the
hardware. Set the CHAIN
PNT1-133 PAUS Chain 2 (0v) abnormal A single chain 2 (0V) failure occurred. FAILURE detection to
The Non-Teacher Enabling Device has This alarm was triggered
PNT1-134 PAUS NTED input been released. by the SRVO-232 SERVO
One of the following has occurred: 1. Turn the teach pendant
The teach pendant was disabled when Enable/Disable switch to
TP OFF in T1,T2/Door the mode switch was in T1 or T2. 2. The ON. Close the controller
PNT1-135 PAUS open
Deadman switch controller
The door is open.
teach pendant 3. The switch is
DEADMAN door. Press RESET. If the
PNT1-136 WARN released released. None.
Short term Chain "SRVO-235 SERVO Short term Chain Refer to the SRVO-235
PNT1-137 PAUS abnormal abnormal" alarm is posted. Refer to the alarm for the remedy.
The status of the Chain
Failure is changed to
PNT1-138 WARN Chain failure is repaired A chain failure has been repaired. normal when the system
Cannot reset chain Reset chain failure detection cannot be hardware, press the E-
PNT1-139 WARN failure executed. STOP button on the teach
Brake Release Switch The Brake Release switch on the Turn the Brake Release
PNT1-140 PAUS On Standard Operator Panel is ON. switch to the OFF position
The specified system color contained None. The override
Col %s range err/preset percent preset override data that was percent value was
PNT1-151 WARN %%override outside the pre-defined allowable automatically adjusted to
System color data has uninitialized If the error occurs each
percent preset override information. time the system color
Data err :Col %s preset This happens when color data created table data is accessed, it
PNT1-152 WARN %%override on a previous version of the software is might be necessary to
The effective preset/estat values (after Verify that the
applying the preset %% override factor preset/estat value in the
for a specified color, gun, and table is within the
Eff. preset range err parameter number) are outside the acceptable range for the
PNT1-153 WARN (%s) allowable range for that parameter. parameter. Check the
The controller could not access data for Create new system color
Color %s data access the specified system color. The data data using the SETUP
PNT1-154 WARN error might not have been created on this colors screen on the teach
This error should never
Illegal code in NEXT The system color number that is next in occur during normal
PNT1-159 WARN color %s the queue is illegal. PaintTool operation. The
For integral color change systems, the Check the color valve
Illegal manual color %s color valve selected by the PLC in number sent by the PLC. If
PNT1-160 WARN received manual mode has no data defined. it is correct, then define
Keep the teach pendant
enabled during
Calibration was aborted because the calibration. This will not
TP disabled - Calib. teach pendant was disabled during the be applicable to Control
PNT1-165 WARN aborted process. Reliable robot controllers,
During Auto Calibration, the feedback Change the applicator and
from the linear potentiometer revealed repair the malfunctioning
large fluctuations in the canister linear potentiometer.
Linear Potentiometer position over a short period of time. If Retry calibration with a
PNT1-166 WARN Unstable the linear potentiometer has been different applicator.
While operating in hybrid mode, Determine the cause for
Accustat determined that a discrepancy the flow discrepancy.
between the actual paint used during Check the following: *
Table not adapted, max the job and the expected paint usage Check the regulator, fluid
PNT1-167 WARN err exceeded was too high to adapt to it. This could or restrictors for a
An attempt was made to move the Request to de-dock before
robot while it was in the docking initiating robot motion.
station. This alarm occurs when The robot is at the
Dedock required, robot attempting to move the robot either in docking station and must
PNT1-168 WARN at dock manual mode, or to the purge position, run dedock before other
The position and proximity switch are Check the following: *
not functioning properly. This could be Check the position and
caused by one of the following: * The the proximity switch. *
Docking station not docking station has not retracted fast Repair the pneumatic or
PNT1-169 WARN retracted enough. * The Docking Cylinder electric circuit if
The position and proximity switch are Check the following: *
not functioning properly. This could be Check the position and
caused by one of the following: * The the proximity switch. *
Docking station not docking station has not extended fast Repair the pneumatic or
PNT1-170 WARN extended enough. * The Docking Cylinder electric circuit if
The Accustat auto calibration could not Remedy 1: Increase the
continue. This is normally the result of number of Maximum
an operation time-out. The auto Calibration Trys in the
Auto Calibration calibration can abort for several AccuStat setup. Verify
PNT1-171 WARN aborted reasons. The function of this alarm is as restrictor, regulator and
Accustat could not reach the upper Verify all equipment is
flow limit in the number of attempts working properly. Check
set at the calibration screen. This can the following: * Check the
Failed to find Upper be caused by one of the following: * Color Data upper limit. *
PNT1-172 WARN limit The upper limit flow rate can not be Check the applicator
Accustat could not reach the low flow Verify that all equipment
limit in the number of attempts set at is working properly. Check
the calibration screen. This can be the following: * Check the
Failed to find Lower caused by: * The low flow setting is too low flow on the Accustat
PNT1-173 WARN limit low to control * The flow rate or the Color Data screen. It may
Not enough time has been allowed to Check the following: *
empty the canister fully by the time Check the regulator and
specified in Beaker Fill Timeout. The gun to be sure they are
Beaker Timeout, Scale canister did not empty due to the functioning properly. *
PNT1-174 WARN Cal Aborted trigger or regulator not opening. Or, Increase the Beaker Fill
One of the following events has Check the following: *
occurred: * After the calibration table Verify that the regulator is
has been shifted or a new calibration working properly. * Verify
(%s) Non-increasing cal table created, a non-increasing table of the fluid restrictor is
PNT1-175 WARN table flow command values was detected. * suitable for the desired
Look at the calibration
The auto-calibration calculated the high results to determine if the
flow output greater than the maximum maximum flow rate is
Calculated output > output. The cal table was saved with a acceptable. If you do not
PNT1-176 WARN Max Output lower range of flow than requested. need a higher flow rate
One of the following events has Restrict fluid flow with a
occurred: * The calculated command smaller restrictor. Or,
counts are below the Applicator check the Color Data
Calculated output < Min Parameter Minimum Output value (200 Hi/Low flow range
PNT1-177 WARN Output counts, or 1600 counts hi-res). * The settings.
One of the following events has Check regulator operation
occurred: * The Tolerance Band is too and Adaptive Gain
narrow (low), or the regulator is not settings in the AccuStat
working properly. * The adaptive gain Color Data for that color
PNT1-178 WARN Failed to reach setpoint for that color might be too low, and the valve. Also, verify that the
Prior to painting the job, the can is Make sure that paint has
checked to see if enough paint has reached the docking
been put into the can (cylinder position station before starting the
counts >= TPR counts). This can occur if step to open the fill valve.
PNT1-179 WARN Canister Fill Error the "waiting for can full" condition is Try increasing the amount
Auto Calibration The Auto Calibration for the selected
PNT1-180 WARN Successful color valve has completed succesfully. None.
This alarm will be displayed if the gun Lower the Minimum
has been on for the amount of time Canister Change Counts or
specified as Canister Check Time and increase the Canister
Non-decreasing canister the amount of change in cylinder Check Time. Check the
PNT1-181 WARN position position counts has not reached the feedback from the linear
This alarm will be displayed if the Perform a scale
piston moves during a color change calibration to insure that
Canister Position cycle when it is held at the bottom of the calculated value for
PNT1-182 WARN Increasing the can for cleaning, and the cleaning the Can Empty Check
A reading of 0 counts on the analog Replace the electrical
input (AIN[1,DISP]) causes the connector on the quick
intermittent connection alarm. This is disconnect (QD) plate.
Intermittent an indicator of potentiometer trouble Verify proper grounding
PNT1-183 WARN Connection Detected during job playback, caused by an of the feedback circuit.
If the percentage of paint left in the can The paint needs to be
exceeds the total paint required (TPR) calibrated or the adaptive
by the Job Total Error Tolerance, then gain for that color valve is
Flow Error High, Valve: this alarm will post. If the paint usage too high. The regulator
PNT1-184 WARN %s exceeds the TPR by the Job Total Error might not be actuating
Applicator Disabled If the applicator is disabled at the end
PNT1-185 WARN during job of the job, then the table will not adapt None.
Check the alarm log to see
what conditions caused
The scale calibration sequence did not the calibration to abort. In
Scale Calibration complete. This can be caused by a most cases, the scale
PNT1-186 WARN Aborted timeout or fill/empty error. calibration can time out
Scale Calibration The scale calibration sequence has
PNT1-187 WARN Successful completed successfully. None.
Teach the robot path for
the de-docking operation.
No path data has been taught for The de-dock path is a
De-Docking program is DEDOCK.TP. Something has caused the special position. After
PNT1-192 WARN undefined position to become invalid. teaching, or touching up
Teach the robot path for
the docking operation.
No path data has been taught for The dock path is a special
Docking program is DOCK.TP. Something has caused the position. After teaching,
PNT1-193 WARN undefined position to become invalid. or touching up special
One of the following items has Check the path data and
occurred: * The request to enter the ensure the last position in
dock was given but the robot did not DOCK.TP has a FINE
Robot NOT at docking reach the docking position. * The dock position type. Verify that
PNT1-194 WARN position attempt did not complete and the the DOCK.TP special
Check the input as soon as
The door held input was lost during possible. If the job can still
PNT1-200 PAUS Door held input lost part held scanning. be continued, activate the
Check the sensor and fix
Door detect sensor The door held sensor was damaged or it. If the job can still be
PNT1-201 PAUS malfunction is malfunctioning. continued, activate the
This alarm can be posted for a robot or Edit the programs so the
an opener program: * A robot commucation macros
requested a second action from an match. The robot program
Illegal Opener macro opener with a "RqstRmtOpnrAct" should alternate between
PNT1-202 WARN Called macro before waiting for the opener to requesting a remote
The opener move cannot be excuted Jog the robot so that it is
PNT1-203 WARN Robot in opener path because the robot is in the opener clear of the opener, and
The robot move cannot be excuted Jog the opener so that it is
PNT1-204 WARN Opener in robot path because the opener is in the robot clear of the robot, and
Opener Bypass is The opener bypass program has not Teach (record) the opener
PNT1-205 WARN undefined been taught (recorded). bypass program
Opener Special1 The special1 opener program has not Teach (record) the
PNT1-206 WARN program is undefined been taught (recorded). special1 opener program
Opener Home program The opener home program has not Teach (record) the opener
PNT1-207 ABRT is undefined been taught (recorded). home program
Check [PASHELL]
PNT1-213 WARN Bad cal.tbl.(color[%d]-
cur_color no.[%d] cur_color number
The parameter is out
calibration of range.
table does cur_color
Check the to make
color andsure it
PNT1-214 WARN parm[%d]) not increase. parameter calibration
%s group mask(%d) != This teach pendant program group Check each robot and
tracking schedule mask does not match the group (robot opener process program
PNT1-215 ABRT group(%d) or opener) in the tracking schedule. to verify that the tracking
No defined color The color that has been sent with the You must define this color
PNT1-216 WARN (color=[%d]) current job has not been defined. in the SETUP Color Table
The first stroke that was late on the Decrease the speed at
part for this job started at this line. The which the conveyor is
WAITCONV[] late for current speed of the conveyor is too moving. Increase the
PNT1-224 WARN line %s fast for the speed of this Job and Color Target Speed or Fan
Enable Data Monitor
Operation from the
The Data Monitor subsystem has been UTILITIES Data Monitor
Data Monitor is disabled because the limit on the data screen. On the SETUP
PNT1-225 WARN disabled files set by the user has been reached. Diagnostics screen,
On the SETUP Diagnostics
screen, consider
The limit on data files that can be increasing the maximum
Maximum DMON Data stored by the Data Monitor subsystem files stored by setting Max
PNT1-226 WARN Files exceeded has been reached. Data Files Stored to a
Wait until the end of the
Data Monitor session. If in
A Data Monitor session is in progress Automatic Sampling
DMON in progress, item during an attempt to change the setup mode, this happens at the
PNT1-227 WARN locked that could affect the current session. end of the job. If sampling
To re-enable
Asynchronous Data
Asynchronous Asynchronous Data Monitoring has Monitoring, ensure that
PNT1-228 WARN DataMonitor
Asynchronousdisabled been disabled. Data Monitor has been
Asynchronous the UTILITIES Data
PNT1-229 WARN DataMonitor enabled enabled. None.
File management features have been No action required. To re-
disabled because the Max Data Files enable file management
item on the SETUP Diagnostics screen is features, you can set Max
DMON file set to 0. Stored data will be over- Data Files to a non-zero
PNT1-230 WARN management disabled written by subsequent sampling value. Ensure that the
File management features have been No action required if the
enabled because the Max Data Files destination data storage
Stored item on the SETUP Diagnostics device has adequate
DMON file screen has been set. The Data Monitor space. To disable file
PNT1-231 WARN management enabled will store as many old data files as management features, set
Sample_start builtin The KAREL built-in, SAMPLE_START, Contact your FANUC
PNT1-232 WARN exec failed returned an unacceptable status. Robotics service
Sample_end builtin The KAREL built-in SAMPLE_END Contact your FANUC
PNT1-233 WARN Monitor
exec failed
session not returned an unacceptable status. Robotics service
PNT1-234 started Data Monitor session not started. No action required.
During production, one of the glass Jog the robot away from
strands feeding through the chopper the fault location, and re-
%sGlss Breakage motor was detected to be broken by its thread the glass strand
PNT1-241 PAUS Detected corresponding microphone sensor. through the chopper
During production, the catalyst flow This can be due to a faulty
PNT1-242 PAUS %sCatalyst Flow Error stopped which is causing only the resin Kobold sensor, or
During production, an increase in This problem might be
command output was issued in order due to a clogged gun tip,
to maintain setpoint. This increase or old equipment. Clean
%s flow command surpassed the Command Warning the gun tip and check the
PNT1-243 WARN warning percentage value. An additional jump lines and equipment.
During production, a significant This problem might be
increase in command output was due to a clogged gun tip,
%s flow command issued in order to maintain setpoint. or old equipment. Clean
PNT1-244 PAUS alarm This increase surpassed the Command the gun tip, and check the
All of the conditions were set for resin Check that the gun is
fluid to be flowing, however a zero flow properly triggering. If fluid
rate was measured. This might be was observed to be
caused by: * A broken applicator flowing, check and, if
PNT1-245 PAUS %s0 res flow rate T.O. trigger * A loss of resin fluid supply necessary, replace the
With a maximum control output, the Check the following: *
flow rate was measured to be lower Check the gun tip and the
than the setpoint (requested flow). This whole gun for clogging. *
%sMax output has flow can be caused by: * The resin gun Check the resin lines for
PNT1-246 PAUS < setpoint might be clogging. * The resin or pilot pinching, especially at
With a minimum control output, the Calibrating the resin will
flow rate was measured to be higher establish a new cracking
than the flow rate setpoint. The resin pressure (minimum
%sMin output has flow fluid pressure might have become too control output) for a
PNT1-247 PAUS > setpoint high. The I/P transducer or fluid changed fluid pressure.
All of the conditions were set for glass If the glass is not feeding
to be feeding, however a zero feed rate from the chopper motor,
was measured. This might be caused check the items listed
by: * A broken applicator trigger * A above or the 32 point
PNT1-248 PAUS %s0 gls feed rate T.O. broken chopper motor sensor * A input module. If it occurs
With a maximum control output, the Check and clean the
glass feed rate was measured to be chopper motor if it is
lower than the setpoint (requested clogged. Check and
%sMax output has feed feed). The chopper motor might be replace the I/P
PNT1-249 PAUS < setpoint clogging. Note: Accuchop automatically transducer, if necessary.
With a minimum control output, the Calibrating the glass will
glass feed rate was measured to be establish a new cracking
higher than the feed rate setpoint. The pressure (minimum
%sMin output has feed motor (glass) RPM might have become control output). Check
PNT1-250 PAUS > setpoint too high. The I/P transducer might be and replace the I/P
The report file generated by Process For R-J3 controller only.
Champion has filled the RDU device to Re-enable Process
its capacity. This forces the system to Champion auto mode by
RDU Full - Proc Champ disable Process Champion auto mode setting the Set Process
PNT1-255 WARN disabled so that no further auto appending is Champion Mode item, in
HIGH SpeedDock The torque value of the SpeedDock Determine the cause of
PNT1-258 PAUS TORQUE: %s exceeded the maximum safety limit. the high torque reading,
Usually, the servo not
ready occurs when servo
SpeedDock motor not The servo power to the SpeedDock power is turned off for
PNT1-259 WARN ready motor is not ready. some reason, such as E-
Check the retract or
extend sensor at
An attempt was made to extend or SpeedDock side A or B.
retract the pusher at SpeedDock side A Ensure that the pusher
PNT1-262 PAUS Pusher at Dock %s or B, but failed. retracted or extended
extend sensor at
An attempt was made to extend or SpeedDock side A or B. If
retract the valve at SpeedDock side A it was an extended fault,
PNT1-263 PAUS Valve at Dock %s or B, but failed. ensure that the pusher
An attempt was made to extend the Check the sensors at
SpeedDock EXTEND SpeedDock docking mechanism at side SpeedDock docking
PNT1-266 PAUS Error A or B, and failed. mechanism. Ensure that
Check the sensors at the
An attempt was made to retract the SpeedDock docking
SpeedDock RETRACT SpeedDock docking mechanism at side mechanism. Ensure that
PNT1-267 PAUS Error A or B, and failed. sufficient air pressure is
Determine if the hard stop
physically retracted. If so,
An attempt was made to Retract the check the functionality of
hard stop from its normal state, but the the sensors. Ensure that
PNT1-270 PAUS Retract Hard Stop Error operation failed. the I/O is mapped
Determine if the hard stop
physically extended. If so,
An attempt was made to extend the check the functionality of
hard stop to its normal state, but the the sensors. Ensure that
PNT1-271 PAUS Extend Hard Stop Error
Exit Srv pos in prog is operation
The robot failed.
ENT_SRV program is not the I/Othe
Teach is mapped
ENT_SRV.TP
PNT1-272 ABRT Ent
undefined
Srv pos in prog is taught.
The Robot EXIT_SRV program is not program.
Teach the EXIT_SRV.TP
PNT1-273 ABRT undefined taught. program.
Error opening TPE This error should never occur during Contact FANUC Robotics
PNT1-276 WARN program normal PaintTool operation. service personnel.
An failed attempt was made to perform
a software operation on a specific
teach pendant program. This error Contact FANUC Robotics
PNT1-277 WARN TPE Built-in error should never occur during normal service personnel.
This error should never occur during Ensure that the teach
normal PaintTool operation. In the pendant program is
TPE find/read header event that this alarm was posted, installed on the controller,
PNT1-278 WARN error PaintTool was making an attempt to or contact FANUC
TPE error reading event that this alarm was posted, installed on the controller,
PNT1-279 WARN instruction PaintTool was making an attempt to or contact Fanuc service
event that this alarm was posted, installed on the controller,
TPE wrong type of PaintTool was making an attempt to or contact FANUC
PNT1-280 WARN program:%s read data from a specific teach pendant Robotics service
This error should never occur during
normal PaintTool operation. In the
TPE error closing a event that this alarm was posted, Contact FANUC Robotics
PNT1-281 WARN program PaintTool was making an attempt to service personnel.
Selected program not The job that is selected for DATA ZONE Generate the job or select
PNT1-282 WARN found EDIT or TEST RUN does not exist. a job that exists.
out of(strt,end)ext1 at The EXT1 (extended axis) of the current This will not affect the X-
PNT1-283 WARN line%s position is out of range of the EXT1 Rail smoothing process.
TPE's motion group The motion group of teach pendant Choose another teach
PNT1-284 WARN must be 1 program must be 1 when using the X- pendant program that
The teach pendant program header size Try selecting the program,
is inadequate. The program might have then selecting DETAIL,
TPE Header size been created on an older software then NEXT, then END. If
PNT1-285 WARN mismatch version. Or, the program header this does not work, create
There was an uninitialized position Ensure the robot is
found in the specified special move mastered and calibrated.
position. This could have occurred if a Re-teach the position in
Uninitialized TPE new position was recorded in one of the special move program
PNT1-286 PAUS position in program %s the special move programs when the indicated by the alarm.
There are only 20 Preset[] instructions
allowed to be programmed in each Eliminate Preset[]
PROCESS program, a combination of instructions in this
attached or standalone instructions. PROCESS program or use
Too many Preset[] when the robot wasn't mastered or multiple PROCESS
PNT1-287 instructions %s calibrated, causing an uninitialized programs.
Communication send The variable communication with Verify ethernet
PNT1-288 error %s another controller failed. communication. Make
Failed Creating Clear Error occurred creating temporary clear Review program type and
PNT1-289 Path %s path
Procesfrom
andspecifed programs.
line number clear path was position data.
PNT1-290 Clear %s intitiated from. Information only.
Macro motion group The macro could not identify as to Make sure the macro is
PNT1-292 unknown which robot called the macro running in production
Communication error The ethernet communication with Verify ethernet
PNT1-293 %s another controller failed. communication. Make
Another controller is configured for the Verify robot library setup
PNT1-294 Arm config error %s same arm IDs as this Controller. and controller number for
The vision system was being loaded
Vis. Not Supported with with a rail tracking system, which
PNT1-295 Rail Trk causes all interaction between Tracking.
Turn on the robot not
PNT1-326 WARN %sSHELL
%sRobot failed
is bypassed
to run The robot not bypassed input is OFF. bypassed input.
PNT1-327 ABRT SUBSHELL The subtask failed to run. Cold start the controller.
PNT1-328 WARN %sE-STAT unit faulted Detected a E-STAT unit fault. Clear E-STAT unit fault.
%sAutomatic CLNOUT An automatic move from the cleanin
PNT1-329 WARN on prod_entry position on production entry is None.
When a job is created, the presets for Check that the job name
%sCannot create the job are also created. In this case, is of the form JOBXXXX,
PNT1-330 WARN presets the presets for the job could not be where XXXX is a number
Check for the existence of
a file called PAPSXXXX,
%sCannot read presets The preset data for the current job where XXXX is the job
PNT1-331 WARN data file could not be found. number. This file is
The calibration status for each control Calibrate all control
PNT1-332 ABRT %s not calibrated
%sFailed to continue parameter
An attemptmust be complete
to continue before it parameters
the robot The current usedcycle within
must be
PNT1-333 ABRT robot task motion task has failed. aborted.
%sFailed to pause robot An attempt to pause the robot motion The current cycle must be
PNT1-334 ABRT task task has failed. The robot motion task aborted.
An attempt to abort the robot motion
%sFailed to abort robot task has failed. The robot motion task
PNT1-335 ABRT task might not have been running at the None.
%sRobot task has The robot task has faulted, but was not The current cycle must be
PNT1-336 ABRT faulted
%sFailed to run robot detected
An attempt bytotherun
main
thetask.
robot motion aborted.
The current cycle must be
PNT1-337 ABRT task taskinvalid
An has failed.
job number was received aborted.
PLC must init robot with a
PNT1-338 %sInvalid job received
tutone from the PLC. valid
An invalid tutone option was received PLC must job number.
init robot with a
PNT1-339 received
%sInvalid repair from
An the PLC.
invalid repair option was received validmust
PLC tutone
initoption.
robot with a
PNT1-340 received from
An the PLC.
invalid color number was received PLC validmust
repair
initoption.
robot with a
PNT1-341 %sInvalid color received from the PLC. valid color number.
Program must be loaded
PNT1-342 %sJob is not found Production run program is not loaded before attempting to run
The JOB currently beginning execution This is just a warning
PNT1-343 %sGhost Job Begin is a Ghost Job indicating
Robot NotPLC has input
Bypassed
PNT1-345 WARN %sSHELL
%sRobot failed
is bypassed
to run Robot Not Bypassed input is OFF. must be ON.
PNT1-346 ABRT SUBSHELL The subtask failed to run. Cold
Clearstart the controller.
the E-STAT unit
PNT1-347 WARN %sE-STAT unit faulted An E-STAT unit fault was detected. fault.
PNT1-348 WARN on prod_entry position on production entry is None.
PNT1-349 WARN presets the presets for the job could not be where XXXX is a number
a file PAPSXXXX, where
%sCannot read presets The preset data for the current job XXXX is the job number.
PNT1-350 WARN data file could not be found. This file is created when
PNT1-351 ABRT %s not calibrated
to continue before it parameters
the robot The current usedcycle within
must be
PNT1-352 ABRT robot task motion task has failed. aborted.
PNT1-353 ABRT task task has failed. The robot motion task aborted.
PNT1-354 ABRT task might not have been running at the None.
PNT1-355 ABRT faulted
main
thetask.
PNT1-356 ABRT task taskinvalid
An has failed.
PNT1-357 %sInvalid job received
tutone from the PLC. valid
An invalid tutone option was received PLC must job number.
init robot with a
PNT1-358 received
An the PLC.
PLC tutone
initoption.
robot with a
An the PLC.
repair
initoption.
robot with a
PNT1-362 %sGhost Job
%sHome Beginis
program is a Ghost
The robot Job
home program has not been indicating
Teach the PLC has
robot home
PNT1-364 ABRT undefined
%sEnter cleaner taught.
The robot cleanin program has not program
Teach the(HOME.TP).
robot cleanin
PNT1-365 ABRT program is undefined
%sExit cleaner program been taught.
The robot cleanout program has not program (CLNIN.TP).
Teach the robot cleanout
PNT1-366 ABRT is undefined
%sBypass program is beenrobot
The taught.
bypass program has not program
Teach the(CLNOUT.TP).
robot bypass
%sPurge program is been taught.
The robot purge program has not been program (BYPASS.TP).
Teach the robot purge
PNT1-368 ABRT undefined program is
%sMaster taught.
The robot master program has not program
Teach the(PURGE.TP).
robot master
PNT1-369 ABRT undefined1 program is
%sSpecial beenrobot
The taught.
special1 program has not program
Teach the(MASTER.TP).
robot special1
%sSpecial 2 program is been taught.
The robot special2 program has not program (SPECIAL1.TP).
Teach the robot special2
PNT1-371 ABRT undefinednot at home
%sRobot been taught. program
Move the(SPECIAL2.TP).
robot to the
PNT1-372 WARN position The robot is not at the Home position. Home position.
%sRobot at cleaner The robot must execute a
PNT1-373 WARN position The robot is positioned at the cleaner. cleanout move before
%sRobot not at cleaner The robot is not positioned at the The robot must be at the
PNT1-374 WARN position
%sEnter Maintenance cleaner.
Robot maintenance in program is not cleaner position
Teach robot before a
maintenance
PNT1-375 WARN program
%sExit is undefined
Maintenance taught.maintenance out program is not
Robot in program
Teach robot(MNTIN.TP).
maintenance
PNT1-376 WARN program is undefined taught. out program
%sRobot not at Robot is not positioned at Robot must be at the
PNT1-377 WARN maintenance position maintenance. maintenance position
%sCan't Enable Attempted to enable Interference Disable Interference
PNT1-380 Interference Check check option during special move, but Check viapath
Set clear the PLC.
using
PNT1-381 %sClear Path
%sHome Not Set
program is Clear path error recovery path not set. SetClearPath
Teach macro.
robot home
%sEnter cleaner Robot home program is not taught. program
Teach robot(HOME.TP).
cleanin
PNT1-383 ABRT program
%sExit is undefined
cleaner program Robot
The cleanin
robot program
cleanout is nothas
program taught.
not program
Teach the(CLNIN.TP).
robot cleanout
PNT1-384 ABRT is undefined
%sBypass program is been taught. program
Teach (CLNOUT.TP).
robot bypass
%sPurge program is Robot bypass program is not taught. program (BYPASS.TP).
Teach robot purge
%sMaster program is Robot purge program is not taught. program
Teach (PURGE.TP).
robot master
%sSpecial 1 program is Robot master program is not taught. program
Teach (MASTER.TP).
robot special1
%sSpecial 2 program is Robot special1 program is not taught. program (SPECIAL1.TP).
Teach robot special2
%sRobot not at home Robot special2 program is not taught. program
robot to the
PNT1-390 WARN position The robot is not at the Home position. Home position.
PNT1-391 WARN position The robot is positioned at the cleaner. cleanout move before
PNT1-392 WARN position
maintenance
PNT1-393 WARN program
%sExit is undefined
Robot in program
maintenance
PNT1-394 WARN program is undefined taught. out program
PNT1-395 WARN maintenance position maintenance. maintenance position
%sCannot Enable Attempted to enable Interference Disable Interference
PNT1-398 Interference Check check option during special move, but Check
Set viapath
clear the PLC.
using
PNT1-399 %sClear Path Not Set Clear path error recovery path not set. SetClearPath macro.
This message is displayed when the
%sApplicator enable is applicator valve enable input turns off.
PNT1-400 WARN OFF When this input is off, the GUN trigger None.
%sApplicator enable is This message is displayed when the
PNT1-401 WARN ON applicator valve enable input turns on. None.
PNT1-406 WARN OFF When this input is off, the GUN trigger None.
PNT1-407 WARN ON applicator valve enable input turns on. None.
%sError reading gun-on Some process or processes within a job Display the DETAIL page
PNT1-412 WARN time for job might have something wrong with their for every process in the
The PGOT procedure was not Perform the PGOT
performed on the processes used procedure on the desired
%sNo TPR calculated for within the selected job (style). The TPR job (style). Test cycle the
PNT1-413 WARN job is equal to zero. No Preset Gun On Time job or allow it to correct
The previous job gun on time for the Perform a PGOT test cycle
current job differs from the calculated on the job that caused the
preset gun on times used for the TPR TPR mismatch alarm. If
calculation by more than the allowed the robot has filled
tolerance. The Gun On Time stored in sufficiently for the job,
the job header does not correspond to then it will automatically
the preset on times read from the job correct the TPR when the
processes. This can be a result of job is completed. If the
process changes done on the fly. The robot has faulted due to
%sTPR Mismatch (%s) robot will not have the proper amount this alarm, then press
PNT1-414 WARN PGOT Required of paint to run the job. RESET and continue the
The calculated TPR exceeds the volume Set up for a re-dock.
of the can. The TPR for that job is too Decrease the Adaptive Fill
large. When using Accustat, if the TPR Gain parameter in the
for a job normally approaches the limit SETUP AccuStat screen.
%sTPR exceeds Can of the size of the canister, then the Reduce the size of the job
PNT1-415 WARN Volume adaptive fill tolerance might attempt to if it is larger than 1550
PNT1-420 WARN time for job might have something wrong with their for every process in the
PNT1-421 WARN job is equal to zero. No Preset Gun On Time job or allow it to correct
process changes done on the fly. When robot has faulted due to
%sTPR Mismatch (%s) this occurs, the robot will not have the this alarm, then press
PNT1-422 WARN PGOT Required proper amount of paint to run the job. RESET and continue the
The calculated TPR exceeds the can Set up for a re-dock.
volume. The TPR for that job is too Decrease the Adaptive Fill
for a job normally approaches the limit AccuStat setup screen.
PNT1-423 WARN Volume adaptive fill tolerance might attempt to if it is larger than 1550 ccs
%sApplicator test Applicator test outputs are on. These
PNT1-428 WARN outputs are ON are initiated by the PLC. None.
%sApplicator test Applicator test outputs are off. This is
PNT1-429 WARN outputs are OFF terminated by the PLC. None.
%sApplicator test Applicator test outputs are on. This is
PNT1-434 WARN outputs are ON initiated by the PLC. None.
PNT1-435 WARN outputs are OFF terminated by the PLC. None.
For continuous line systems only. This is
a warning that the robot is waiting for a
part to enter the tracking window. DO
%sWaiting for part in NOT ENTER THE ROBOT WORKSPACE;
PNT1-440 WARN window OTHERWISE YOU COULD INJURE None.
%sPart entered tracking For continuous line systems only. This is
PNT1-441 WARN window a warning that the part has entered the None.
For continuous line only. This is a Reduce the minimum
%sPart Detect less than warning that the trigger distance is less distance value to less than
PNT1-442 min dist than a pre-determined value This part the job spacing distance
For line tracking only. This is a warning Previous job or color
%s skipped-over max that the part has tracked too far to be change took too long to
PNT1-443 travel played. The robot will ignore this play.
For continuous line only. This indicates Expand robot boundaries
%sTracking que that too many parts have passed the or lower the conveyor
PNT1-444 exceeded part detect switch within the current speed.
The tracking sequence number sent Verify the PLC (Cell
%sTrack seq. does not when the part detect signal was Controller) is using the
PNT1-445 match JOB seq. asserted does not match the JOB same Track sequence
PNT1-446 WARN window OTHERWISE YOU COULD INJURE None.
PNT1-447 WARN window a warning that the part has entered the None.
The robot must be calibrated before
proceeding. Only jogging in the joint
coordinate system and the calibration
PNT1-452 WARN %sRobot not calibrated motion itself can be executed before Calibrate the robot.
The robot JOB program was continued
PNT1-453 %sJOB continued! because the robot received the Dislpay message only!
The robot JOB program was cancelled
PNT1-454 %sJOB cancelled! because the robot received the cancel Dislpay message only!
PNT1-455 %sJOB continued dry! dry because the robot received the Dislpay message only!
The robots' next JOB program was
PNT1-456 %sNext JOB cancelled! cancelled because the robot received Dislpay message only!
PNT1-457 WARN %sRobot not calibrated motion itself can be executed before Calibrate the robot.
%sInvalid instruction During program execution, a paint Edit the current program
PNT1-462 WARN argument instruction was encountered with an and verify that all
The argument to the GUN SELECT Modify the offending GUN
PNT1-463 WARN %sInvalid gun selection instruction is outside of the range SELECT argument to be
An unknown instruction was
%sUnknown mnenomic encountered during program Delete the offending
PNT1-464 PAUS instruction execution. This might happen if the instruction.
A Function instruction was used but the Load the Function
PNT1-465 PAUS %sCan't set output Function Instruction Option is not Instruction Option in
A GunSelect instruction that would
change the state of the gun(s) is not Move the Gunselect
positioned as an option on a motion instruction onto a motion
line. This instruction will not complete line, and delete the stand
any operation. Such an instruction by alone instruction line. If
itself on a line in a program can not needed, add another
%sInvalid GunSelect properly control the timing of the motion line and record an
PNT1-466 WARN position changes in the gun outputs. Note that if appropriate position.
%sInvalid instruction During program execution, a paint Edit the current program,
PNT1-471 WARN argument instruction was encountered with an and verify that all
PNT1-472 WARN %sInvalid gun selection instruction is outside of the range SELECT argument to be
PNT1-473 PAUS instruction execution. This might happen if the instruction.
A Function instruction is used while the Load the Function
PNT1-474 PAUS %sCan't set output Option is not loaded. Instruction Option in
line. This instruction will not complete line and delete the stand
any operation. Such and instruction by alone instruction line. If
itself on a line in a program can not needed add another
PNT1-475 WARN position changes in the gun outputs. Note that if appropriate position.
For integral color change systems only: Check the color change
A color change cycle cannot be cycle for the current color
PNT1-480 ABRT %s not defined executed. There are no steps defined and the next color. The
For integral color change systems only: Reset the system and
A color change pushout cycle was continue. The color
%sPushout cycle executing during production when it change logic will
PNT1-481 WARN cancelled was aborted by an E-STOP. The paint automatically do a
For integral color change systems only:
An illegal color change cycle number Make sure the PLC is
%sIllegal manual cycle was sent by the PLC. Cycle numbers 1- sending a legal color
PNT1-482 WARN received 8, and 21, 22, and 23 are legal cycle change cycle number.
For integral color change systems only: Reset the system. If in
PNT1-483 WARN %sColor cycle aborted A color change cycle was cancelled by production mode, the
During the execution of a color change Check the cycle data table
cycle, the color enable output and the and make sure the color
Purge Solvent output are not allowed enable and Purge Solvent
%sColor Valve + PrgSol to be on at the same time. If the color outputs are never on at
PNT1-484 PAUS both ON change cycles attempt to do this, the the same time.
If there is no paint in the paint lines
%sUsing default valve (current color = 0) and a color change
PNT1-485 WARN cycle data cycle is executed, the color change None.
%sSelected color valve For integral color change systems only: Define the color valve
PNT1-486 ABRT not defined The color valve selected has no data using the SETUP menus
%sApplication enable is application enable input turns off.
PNT1-487 WARN OFF When this input is off, the gun and None.
%sAttempt to use illegal This error should never occur during Contact Fanuc service
PNT1-488 ABRT cycle number normal PaintTool operation. personnel.
The cell is attempting to perform Wait for the operator to
%sManaul mode is manual operations while an operator is finish with the teach
PNT1-489 WARN locked at T.P. also performing manual operations at pendant, then try again.
%sManual mode is manual operations while an operator is finish with the CRT, then
PNT1-490 WARN locked at CRT. also performing manual operations at try again.
Purge Air output are not allowed to be enable and Purge Air
%sColor Valve + PrgAir on at the same time. If the color change outputs are never on at
PNT1-491 WARN both ON cycles attempt to do this, the cycle is the same time.
%sCC Waiting for arm The color change task is waiting for the Send the robot to the
PNT1-492 WARN to be home robot to be at the Home position Home position.
%sCC automatic cycles This indicates that a color change task
PNT1-493 WARN executing is executing a color change cycle. None.
During the manual I/O testing of color Do not attempt to turn on
%sColorEnb + PrgSol change I/O, the color enable output the outputs at the same
PNT1-494 WARN both ON and Purge Solvent output are not time.
During the manual I/O testing of color Do not attempt to turn on
%sColorEnb + PrgAir change I/O the color enable output and the outputs at the same
PNT1-495 WARN both ON the Purge Air output are not allowed to time.
PNT1-496 WARN not defined The color valve selected has no data using the SETUP menus
Manual color change from teach
pendant: Warning: the system changes
the current system color to match the
%sNo system color for fill color valve. No system color uses Temporarily change the
PNT1-497 WARN valve the current valve. The wrong system system color setup
%sApplication enable is application enable input turns on.
PNT1-498 WARN ON When this input is on, the GUN and None.
An attempt to enable solvent valve was Verify that PD, Trigger,
PNT1-499 WARN %sInvalidSolvent
%sPurge Solv/Air+State made without
Air Purge enabling
Solvent and Purgea Air
downstream
Valves IWPColor
Fix or BWP enabled
Change Cycle
PNT1-500 WARN Both ON Than One
%sMore Both ON Data or Try Again
PNT1-501 WARN Color Valve ON Multiple Color Valves ON Not Allowed
The Color Change Event programmed
for the current color change step did Check the Color Change
PNT1-502 WARN %sCC Event Timeout! not complete in the allocated time. Event requests.
%sCC Cycle does not The programmed Color Change Cycle The last Color Change
PNT1-503 WARN end @ HOME! does not send the robot to the HOME Cycle must send the robot
If this alarm is posted
during a Color Change
The IPC interlock check failed, the cycle, check the CC cycle
%sIPC Interlock check (pTRIG and pPE) or pDUMP valves must to verify the above valves
PNT1-504 failed! be opened to run the pump. are programmed on. If
Verify the pX and pY
valves are not
The pX & pY valves have been programmed ON in the
programmed ON without the S-Unit Color Change data before
%spX+pY ON away from either not at the DOCK position or not the S-Unit has been
PNT1-505 DOCK! at docking force. moved to the Dock
For integral color change systems, a Check the color change
color change cycle cannot be executed. cycle for the current color
PNT1-511 ABRT %s not defined There are no steps defined for that and the next color. The
For integral color change systems only, Reset the system and
a color change pushout cycle was continue. The color
PNT1-512 WARN cancelled was aborted by an E-STOP. The paint automatically do a
PNT1-513 WARN received 8, and 21, 22, and 23 are legal cycle change cycle number.
For integral color change systems, a Reset the system. If in
PNT1-514 WARN %sColor cycle aborted color change cycle was cancelled by an production mode, the
For integral color change systems,
during the execution of a color change Check the cycle data table
%sColor Valve + PrgSol to be on at the same time. If the color outputs are never on at
PNT1-515 PAUS both ON change cycles attempt to do this, the the same time.
For integral color change systems, if
there is no paint in the paint lines
PNT1-516 WARN cycle data cycle is executed, the color change None.
PNT1-517 ABRT not defined The color valve selected has no data using the SETUP menus
%sApplication enable is application enable input turns off.
PNT1-518 WARN OFF When this input is off, the GUN and None.
PNT1-519 ABRT cycle number normal PaintTool operation. personnel.
PNT1-520 WARN locked at T.P. also performing manual operations at pendant. Then try again.
%sManual mode is manual operations while an operator is finish with the CRT. Then
PNT1-521 WARN locked at CRT. also performing manual operations at try again.
during the execution of a color change Check the cycle data table
purge air output are not allowed to be enable and purge air
%sColor Valve + PrgAir on at the same time. If the color change outputs are never on at
PNT1-522 WARN both ON cycles attempt to do this, the cycle is the same time.
For integral color change systems, the
%sCC Waiting for arm color change task is waiting for the Send the robot to the
PNT1-523 WARN to be home robot to be at the Home position Home position.
%sCC automatic cycles For integral color change systems, this
PNT1-524 WARN executing is an indication of a color change task None.
during the manual I/O testing of color Do not attempt to turn on
%sColorEnb + PrgSol change I/O, the color enable output the outputs at the same
PNT1-525 WARN both ON and purge solvent output are not time.
For integral color change systems only,
during the manual I/O testing of color Do not attempt to turn on
%sColorEnb + PrgAir change I/O, the color enable output the outputs at the same
PNT1-526 WARN both ON and the purge air output are not time.
%sSelected color valve For integral color change systems only, Define the color valve
PNT1-527 WARN not defined the color valve selected has no data using the SETUP menu
WARNING: For manual color changes
from teach pendant, the system
changes the current system color to
%sNo system color for match the fill color valve. No system Temporarily change the
PNT1-528 WARN valve color uses the current valve. The wrong system color setup.
%sApplication enable is application enable input turns on.
PNT1-529 WARN ON When this input is on, the GUN and None.
PNT1-530 WARN %sInvalid Solv/Air+State
%sPurge Solvent Air made
Purge without enabling
downstream
Valves IWP or BWP
Fix Color enabled
Change Cycle
PNT1-531 WARN Both ON Than One
PNT1-532 WARN Color Valve ON Multiple Color Valves ON Not Allowed
for the current color change step didCheck the Color Change
PNT1-533 %sCC Event Timeout! not complete in the allocated time. Event requests.
The programmed Color Change Cycle The last Color Change
%sCC Cycle does not does not send the robot to the HOME Cycle must send the robot
PNT1-534 WARN end @ HOME! position at the completion of the cycle.
to the HOME position at
The pX and pY valves have been verify the pX and pY
programmed ON without the S-Unit valves are not
%spX+pY ON away from either not at the DOCK position or not programmed ON in the
PNT1-536 DOCK! at the Docking force. Color Change
Establish data before
the cause of the
timeout. Verify the
canister position feedback
is operating properly.
The canister position counts did not Feedback can be verified
reach the fill counts before the Color by checking the analog
Change Timeout expired. If this occurs input (AIN[1, DISP]). Check
during a Scale Calibration, then the can the paint supply system.
was not filled before the Scale Cal Step Check the color change
Time expired. This condition can exist if valve operation. Check
no paint has entered the can, or a loss the color valve, if it is a
of canister position feedback from the color change fault or the
linear potentiometer. The Color Change dock solvent if this occurs
Timeout needs to be increased. The Full during a scale calibration.
%s abort, can fill Can counts have not been properly Increase the Color Change
PNT1-542 WARN timeout calculated. Timeout. the
Establish If the gun of
cause hasthe
timeout. Verify that the
The canister position counts did not canister position feedback
reach the empty canister check counts is operating properly.
before the Color Change Timeout Feedback can be verified
expired. If this occurs during a Scale by checking the analog
Calibration, then the can was not input (AIN[1, DISP]). Check
empty before the Scale Cal Step Time the color change valve
expired. This condition can exist when operation. Check the
no paint has exited the can, or if a lossdump valve if the paint
of canister position feedback from the has not exited the
linear potentiometer has occurred. The canister. Increase the
Color Change Timeout needs to be Color Change Timeout. If
%s abort, can empty increased. The Empty Can counts have the gun has been changed
PNT1-543 WARN timeout not been properly calculated. then a scale calibration
Check the following: 1.
Verify that the TPR was
calculated properly. 2.
Verify the fill is
completing successfully. 3.
Check for other alarms
that occurred during this
job. 4. Make sure all
%s Canister Out Of The canister ran out of paint during the equipment is operating
PNT1-544 WARN Paint job. properly, such as the
Establish the cause of the
canister position feedback
is operating properly.
The canister position counts did not Feedback can be verified
reach the fill counts before the Color by checking the analog
Change Timeout expired. If this occurs input (AIN[1, DISP]). Check
during a Scale Calibration, then the can the paint supply system.
was not filled before the Scale Cal Step Check the color change
Time expired. This condition can exist if valve operation. Check
no paint has entered the can or a loss the color valve if it is a
of canister position feedback from the color change fault, or the
linear potentiometer has occurred. The dock solvent if this occurs
Color Change Timeout needs to be during a scale calibration.
%s abort, can fill increased. The Full Can counts have not Increase the Color Change
PNT1-548 WARN timeout been properly calculated. Timeout. If the
Establish the gun of
cause hasthe
The canister position counts did not canister position feedback
reach the empty canister check counts is operating properly.
before the Color Change Timeout Feedback can be verified
expired. If this occurs during a Scale by checking the analog
Calibration, then the can was not input (AIN[1, DISP]). Check
empty before the Scale Cal Step Time the color change valve
expired. This condition can exist if no operation. Check the
paint has exited the can, or a loss of dump valve if the paint
canister position feedback from the has not exited the
linear potentiometer has occurred. The canister. Increase the
Color Change Timeout needs to be Color Change Timeout. If
%s abort, can empty increased. The Empty Can counts have the gun has been changed
PNT1-549 WARN timeout not been properly calculated. then a scale calibration
Verify that the TPR was
calculated properly. Verify
the fill is completing
successfully. Check for
other alarms that
occurred during this job.
Make sure all equipment
%s Canister Out Of The canister ran out of paint during the is operating properly,
PNT1-550 WARN Paint job. such as the trigger or
The fluid pressure or fluid viscosity for Correct the fluid pressure
the current color has changed or viscosity for the current
dramatically. This change has occurred color. If the pressure or
since the last calibration of this color. viscosity was purposely
%sCal. table adapted The value exceeded the Adaptive changed, then the color
PNT1-554 WARN out tolerance tolerance parameter. can be calibrated to
This status warning indicates that the
%sCal. table adapted in conditions which caused a table
PNT1-555 WARN tolerance adapted out of tolerance alarm have None.
As a particular flow rate set point is In some way, decrease the
being output, the yield (cc/min)/cnt) yield. Use smaller
for that flow rate was larger than the restricters in the gun if the
tolerance band for it. It is not likely that high end flow rate can still
the set point will be reached. This obtained. Otherwise,
Dyn. yield > tolerance might be due to the restricters in the accept a larger tolerance
PNT1-556 WARN band (%s) gun being too large. band. If the value given in
Checks for how far the flow rate is from Check and change the
the set point have been too high. transducer, replace the
Possible causes are: * A sticking I/P fluid regulator, or service
%sFlow rate avg. error transducer * A bad fluid regulator * the surge suppression
PNT1-557 WARN excessive Frequent fluid pressure changes * A system on the fluid supply
%sCalibration Used to notify the cell controller that a
PNT1-558 WARN successful calibration has completed successfully. None.
The best remedy might be
Accuflow calibration could not found from the previous
continue. This might be due to the fluid alarm in the log. This is
lines not being filled. Check for other usually the result of
PNT1-559 WARN %sCalibration aborted alarms in the log. incorrect setup
Decrease the Gain
The low flow rate could not be reached modifier used for the
%sCal. low flow rate during Accuflow calibration. A new low color, if possible. The new
PNT1-560 WARN reset flow rate was established. low flow rate is shown as
Decrease the Gain
During Accuflow calibration, the low modifier used for the
%sCal. max. flow rate flow rate could not be reached. A new color, if possible. The new
PNT1-561 WARN reset low flow rate was established. low flow rate is shown as
Try the following: *
Accuflow timed out trying to reach the Possibly decrease the Gain
maximum flow rate. The possible modifier used for the
causes are: * A high gain * A sticking I/P color. * Retry the
%sCal. time out at max. transducer * A bad fluid regulator * calibration. * Check and
PNT1-562 WARN flow Frequent fluid pressure changes. change the transducer, if
Accuflow timed out trying to reach the Try the following: * If
loweset flow rate, typically 100 cc/min. possible, decrease the
Possible causes are: * A high gain * A Gain modifier used for the
sticking I/P transducer * A bad fluid color. * Retry the
%sCal. time out at low regulator * Frequent fluid pressure calibration. * Check and
PNT1-563 WARN flow changes change the transducer, if
All of the conditions were set for fluid If fluid can be seen
to be flowing and a zero flow rate was coming from the
measured. This might be due to no fluid applicator, check the
pressure or pilot air pressure. With a following: * Flow meter *
very low flow rate, the gain might be Flow meter pickup *
too high. One of the following items Accuflow interface * The
might be broken: * Color Valve * Color 32 point input module
%sZero fluid flow rate select board * Gun trigger * Flow meter Otherwise check the other
PNT1-564 WARN detected * Flow meter pickup * Accuflow items listed as part of the
As Accuflow steps down through the 10 Perform the following: *
points in the calibration table, it Retry the calibration. *
expects a lower flow for each decrease Check that an adequate
in the commanded flow value. In this and stable flow rate is
%sLower output did not case, the flow did not decrease. This provided by the system
PNT1-565 WARN lower flow can be caused by low or pulsing fluid for this color. *
While measuring hysteresis, time up or Retry the calibration.
%sTime out during a time down, the Accuflow system timed Check that the high flow
PNT1-566 WARN cal. test out. This indicates the high or low flow rate can be reached
With a minimum control output the Calibrating the color will
than the setpoint (requested flow). The pressure (minimum
fluid pressure might have become too control output) for a
high. The I/P transducer or fluid changed fluid pressure.
%sMin. output has flow regulator might be stuck open. There Check and replace the
PNT1-567 WARN > setpoint might be a fairly large fluid leak. Note: fluid regulator and I/P
With a maximum control output, the Check the following: *
than the setpoint (requested flow). The whole gun for clogging. *
gun might be clogging. A fluid or pilot Check the fluid lines for
air line might be pinched. The fluid pinching, especially at
%sMax. output has flow pressure might have become too low. places where they flex. *
PNT1-568 WARN < setpoint The I/P transducer might be broken. Check the fluid supply
%sFlow setpoint below The requested fluid flow output Adjust the fluid flow
PNT1-569 WARN globals command is below the calibrated range output command in the
Adjust the fluid flow
The requested fluid flow output output command in the
%sRequested flow command is above the calibrated range preset argument to be
PNT1-570 WARN above cal. table of the color. within the calibrated
A small amount of fluid flow was No immediate remedy is
%sSlow fluid flow leak detected when the gun was not turned required. The paint
PNT1-571 WARN detected on. This might be caused by a loose system will continue to
A large amount of fluid flow was The various fluid lines and
detected when the gun was not turned valves should be
on. This might be caused by the dump inspected and repaired
valve being stuck on or a broken fitting, immediately. Check and
%sFast fluid flow leak or a broken paint line. Note that each repair the dump pilot
PNT1-572 WARN detected time the fluid begins to leak fast, the valve and the dump valve,
This might be caused by pulsing paint Increase the Minimum set
pressure or a broken I/P transducer. If point (ms). If the FLUID
it occurs on most colors then the transducer is noisy,
Minimum set point (ms)might be too change it. If this occurs on
%sFailed to reach small for the specific intallation setup, specific colors, check the
PNT1-573 WARN setpoint or one of the tolerance band settings surge suppression
Check and correct the
The Accuflow softpart is not running. assignments or hardware
The I/O assigned & used by the softpart for the I/O used by
is not available or the softpart did not Accuflow. Especially the
load correctly. Additional info. is I/O points: Set Point
%sAccuflow softpart init available during controller power up at Reached, Flow Rate GIN,
PNT1-574 WARN failed the debug console (smon). and flow diag. AOUT.
All of the conditions were set for fluid Check that the gun is
to be flowing and a zero flow rate was triggering properly. If you
measured for longer than the Zero flow observe fluid to be
timeout parameter. This might be flowing, check and
caused by one of the following: * A possibly replace the fluid
broken applicator trigger * A loss of flow meter. Icrease the
fluid supply pressure * A broken fluid Zero flow timeout
%s0 fluid flow rate flow meter * A broken cable (to the parameter (by about
PNT1-575 WARN timeout flow meter) * A Zero flow timeout 25%), if possible.
This alarm occurs only during Increase the fluid
calibration. The flow rate measured at pressure. Check that the
the maximum control, and one half of transducer is functioning
the maximum control output was properly and that it has
nearly the same. Less than one half of the correct pressure
the control output range is useable. range. Change the range if
The system might still function even appropriate. The system
%sMax. flow below mid though this alarm has occurred. This might operate, but
PNT1-576 WARN point might be caused by low fluid pressure, performance can be
As a particular flow rate set point is Decrease the yield. Use
being output, the yield ((cc/min)/cnt) smaller restrictors in the
for that flow rate was larger than the gun if the high end flow
tolerance band for it. It is not likely that rate can still obtained.
CH1:Dyn. yield > the set point will be reached. This Otherwise, accept a larger
PNT1-577 WARN tolerance band (%s) might be due to the restricters in the tolerance band. If the
%sCal. table adapted The change was beyond the percentage changed, then the color
PNT1-583 WARN out tolerance value setting of the Adaptive tolerance can be calibrated to
PNT1-584 WARN tolerance adapted out of tolerance alarm have None.
tolerance band for it. It is not likely that rate can still obtained.
PNT1-585 WARN tolerance band (%s) might occur if the restrictors in the gun tolerance band. If the
the set point have been too high. transducer, replace the
Possible causes are one of the fluid regulator, or service
%sFlow rate average following: * A sticking I/P transducer * the surge suppression
PNT1-586 WARN error high A bad fluid regulator * Frequent fluid system on the fluid supply
PNT1-587 WARN successful calibration has completed successfully. None.
The best remedy might be
continue. This might occur if the fluid alarm in the log. This is
lines have not been filled. Check for usually the result of
PNT1-588 WARN %sCalibration aborted other alarms in the log. incorrect setup
Possibly decrease the Gain
During Accuflow calibration, the low modifier used for the
%sCal. low flow rate flow rate could not be reached. A new color. The new low flow
PNT1-589 WARN reset low flow rate was established. rate is shown as point 2 in
During Accuflow calibration, the Decrease the Gain
expected maximum flow rate could not modifier used for the
%sCal. max. flow rate be reached at the maximum output. A color, if possible. The new
PNT1-590 WARN reset new maximum flow was established. maximum flow rate is
Decrease the gain
Accuflow timed out trying to reach themodifier used for the
maximum flow rate. Possible causes color, if possible. Then,
are: * A high gain * A sticking I/P retry the calibration.
%sCal. time out at max. transducer * A bad fluid regulator * Check and change the
PNT1-591 WARN flow Frequent fluid pressure changes transducer if necessary,
Accuflow timed out trying to reach theDecrease the gain
loweset flow rate, typically 100 cc/min.
modifier used for the
Possible causes are one of the color, if possible. Then,
following: * A high gain * A sticking I/P
retry the calibration.
%sCal. time out at low transducer * A bad fluid regulator * Check and change the
PNT1-592 WARN flow Frequent fluid pressure changes. transducer if necessary,
All of the conditions were set for fluid
If fluid can be seen
to be flowing however, a zero flow rate
coming from the
was measured. This might be due to no applicator, check the
fluid pressure or pilot air pressure. following: * Flow meter *
With a very low flow rate, the gain Flow meter pickup *
might be too high. One of the following
Accuflow interface * The
items might be broken: * Color Valve *32 point input module.
%sZero fluid flow rate Color select board * Gun trigger * Flow
Otherwise check the other
PNT1-593 WARN detected meter * Flow meter pickup * Accuflow items listed above. If it
As Accuflow steps down through the 10 Retry the calibration.
points in the calibration table, it Check that an adequate
expects a lower flow for each decreaseand stable flow rate is
in the commanded flow value. In this provided by the system
%sLower output did not case, the flow did not decrease. This for this color. Decreasing
PNT1-594 WARN lower flow can be caused by low or pulsing fluid the leveling trys might
While measuring hysteresis time up or Retry the calibration.
%sTime out during a time down, the Accuflow system timed Check that the high flow
PNT1-595 WARN cal. test out. This indicates that the high or low
rate can be reached
With a minimum control output, the Calibrating the color will
than the setpoint (requested flow). The
pressure (minimum
fluid pressure might have become too control output) for a
%sMin. output has flow regulator might be stuck open. There Check and replace if
PNT1-596 WARN > setpoint might be a fairly large fluid leak. Note:
necessary the fluid
With a maximum control output the Check the following: *
than the setpoint (requested flow). This
whole gun for clogging. *
can be caused by: * A clogged gun. * ACheck the fluid lines for
pinched fluid or pilot air line. * Thepinching, especially at
%sMax. output has flow fluid pressure becoming too low. * A places where they flex. *
PNT1-597 WARN < setpoint broken I/P transducer. Note: Accuflow Check the fluid supply
PNT1-598 WARN globals command is below the calibrated range output command in the
PNT1-599 WARN above cal. table of the color. within the calibrated
detected when the gun was not turned required. The paint
%sSlow fluid flow leak on. This might be caused by a loose system will continue to
PNT1-600 WARN detected fitting, or a leaking dump valve. function properly. The
on. This might be caused by the dump inspected and repaired
valve being stuck on, or a broken immediately. Check and
%sFast fluid flow leak fitting, or a broken paint line. Note that repair the dump pilot
PNT1-601 WARN detected each time the fluid begins to leak fast, valve and the dump valve,
This might be caused by pulsing paint Increase the Minimum set
it occurs on most colors then there transducer is noisy,
might be a small setting of the change it. If this occurs on
%sFailed to reach Minimum set point (ms) for the specific specific colors, check the
PNT1-602 WARN setpoint intallation setup or one of the surge suppression
The Accuflow softpart is not running. Check and correct the
The I/O assigned and used by the assignments or hardware
softpart is not available, or the softpart for the I/O used by
did not load correctly. Additional Accuflow, especially the
information is available during I/O points: Set Point
%sAccuflow softpart init controller power up at the debug Reached, Flow Rate GIN,
PNT1-603 WARN Failed console (smon). and flow diag. AOUT.
to be flowing but a zero flow rate was properly triggering. If fluid
measured for longer than the Zero flow was observed to be
timeout parameter. This might be flowing, check and
caused by: * A broken applicator possibly replace the fluid
trigger * A loss of fluid supply pressure flow meter. Possibly
* A broken fluid flow meter * A broken increase the Zero flow
%s0 fluid flow rate cable (to the flow meter) * A Zero flow timeout parameter (by
PNT1-604 WARN timeout timeout value that is too short Note: about 25%).
calibration. The flow rate measured at pressure. Check that the
the maximum control, and one half of transducer is functioning
the maximum control output, was properly and that it has
the control output range is useable. range. Change it if
The system might still function even appropriate. The system
%sMax. flow below mid though this alarm has occurred. This might operate, but
PNT1-605 WARN point might be caused by low fluid pressure, performance can be
tolerance band for it. It is not likely that rate can still be obtained.
PNT1-606 WARN tolerance band (%s) might be due to the restrictors in the tolerance band. If the
The relationship of the output Check and perform the
command to the flow rate obtained has following: * Check, clean,
changed significantly since the last and possibly replace the
calibration. There is now a larger air cap. * Check for a large
output required to get the same flow loss of air supply pressure.
rate. This can be caused by: * A clogged * Check for pinched air
air cap * A clogged gun * Pinched air lines or clogged air
lines * Large losses of air supply passages in the gun. *
pressure Note that the system Recalibrate to clear the
%sCal. table adapted continues to close the loop and alarm immediately. *
PNT1-612 WARN out,output up generally maintain requested flow rates Increase the Adaptive
Just a notification that the calibration
%sCal. table adapted in table has returned to the normal
PNT1-613 WARN tolerance operating range (as defined by the None.
being output the yield (slpm/cnt) for larger diameter air lines to
that flow rate was approximately larger supply air to the cap. Use
than the percent tolerance. It is not a larger ratio booster (2:1
likely that the set point will be reached instead of 1:1) if the
%sDyn. yield > %% within the specified tolerances. This system can not supply the
PNT1-614 WARN tolerance band might be caused by the use of a flow high flow rates provided.
Comparisons of how far the measured Check and perform the
flow rate is from the setpoint had too following: * Check, clean,
large of a result. The size of the error and possibly replace the
between measured flow and the air cap. * Check for
setpoint that will cause this alarm, and oscillating air pressure on
is controlled by the Max. error from the output of the I/P
%sFlow rate avg. error setpoint parameter. Possible causes transducer. * If found,
PNT1-615 WARN excessive are: * A clogged air cap * A sticking I/P replace the transducer. *
PNT1-616 WARN successful calibration has been completed None.
AccuAir calibration could not complete. The best remedy might be
This might be due to the air supply found from the previous
being off. Check for other alarms in the alarm in the log. Request
log. This might be due to incorrect proper air flow at the cap,
PNT1-617 WARN %sCalibration aborted setup parameters, or incomplete and check that it occurs.
This is a warning not a failure. During The new flow rate is
AccuAir calibration the low flow rate shown as point 2 in the
could not be properly reached. A new calibration table. This
%sCal. low flow rate flow rate was established. The target value can be visually
PNT1-618 WARN reset flow rate is determined by the Table checked and accepted.
This is a warning, not a failure. During The new maximum flow
AccuAir calibration, the expected rate is shown as point 10
%sCal. max. flow rate maximum flow rate could not be in the calibration table.
PNT1-619 WARN reset reached at the maximum output. A This value can be visually
The AccuAir controls timed out trying Perform the following: *
to reach the maximum flow rate. Retry the calibration. *
Possible causes are: * A high gain * A Try decreasing the Gain
sticking I/P transducer * Too large of a modifier parameter. * Try
%sCal. time out at max. yield for the current tolerance band, or increasing the Percent
PNT1-620 WARN flow the system response is too slow for the tolerance band
to reach the minimum flow rate. This Retry the calibration. *
flow rate is the Table point no. 2 Try decreasing the Gain
parameter. Possible causes are: * A modifier parameter. * Try
high gain * A sticking I/P transducer * increasing the Percent
%sCal. time out at low Too large of a yield for the current tolerance band
PNT1-621 WARN flow tolerance band * Or, the system parameter. * Check and
All of the conditions were set for air to Check and perform the
be flowing, but a zero flow rate was following: * Check, clean,
measured. This might be caused by: * A and possibly replace the
broken applicator trigger * Pinched air air cap. * Check that the
lines * A loss (or near loss) of air supply gun is properly triggering.
pressure * A broken air flow sensor * A * If air was observed to be
%s0 air flow rate broken cable (to the flow sensor) * A flowing, check and
PNT1-622 WARN detected Trigger delay that is too short Note: possibly replace the air
As the AccuAir calibration steps down Check and perform the
through the 10 points in the calibration following: * Retry the
table, it expects a lower flow for each calibration. * Check that
decrease in the command flow value. In the pilot air line to the
this case the flow did not decrease. This booster has sufficient
can be caused by: * Insufficient exhaust exhaust capability. *
%sLower output did not * No quick exhaust on the pilot air line Increase the Calibration
PNT1-623 WARN lower flow * Too large of a hysteresis in control step delay parameter (by
%sTime out during a time down, the Closed loop system Check that the high flow
PNT1-624 WARN cal. test timed out. This indicates that the high rate can be reached
With a minimum control output, the
flow rate was measured to be higher
Check and perform the
Max. control out (ms) parameter following: * Check and
affects the sensitivity of this alarm. This
repair the various air
might be caused by a leaking or brokenlines. * Check and repair
air line between the flow sensor and the air booster. * Check
the applicator. The I/P transducer and repair the I/P
might be stuck open. The air booster transducer. * Increase the
%sMin. output has flow might be stuck open or leaking. This Max. control out (ms)
PNT1-625 WARN > setpoint might be caused by a faulty air flow parameter, if possible.
With a maximum control output, the Check, clean, and possibly
flow rate was measured to be lower replace the air cap. If air is
observed to be flowing
Max. control out (ms) parameter (when commanded),
possibly replace the air
is likely caused by a clogged air cap.flow sensor. Also check
%sMax. output has flow This might also be caused by: * Pinched
the following: * Check for
PNT1-626 WARN < setpoint air lines * A broken I/P transducer * A
a pinched air line. * Check
%sFlow setpoint below The requested air flow setpoint is Adjust the air flow
PNT1-627 WARN globals below the range of the current setpoint to be within the
Adjust the air flow
setpoint to be within the
The requested air flow setpoint is calibrated range of this
above the calibrated range for Fan Air. parameter. Perform the
%sRequested flow The maximum value is shown as point necessary steps to
PNT1-628 WARN above cal. table number 10 in the calibration table. increase the maximum
A small amount of air flow was No immediate remedy is
%sSlow air flow leak on. This might be caused by a leaking system will continue to
PNT1-629 WARN detected trigger valve, leaking air line, or any function properly. The
A large amount of air flow was
detected when the gun was not turned The the applicator and the
on. This might be caused by a leaking various air lines should be
%sFast air flow leak trigger valve, leaking air line, broken air inspected and repaired
PNT1-630 WARN detected line, broken applicator, or any other air immediately.
This is caused by a failure of the If the Fan Air control I/P
AccuAir system to reach the setpoint transducer is noisy or
(within the tolerance band) within the broken, change it. If the
time allowed. The time that the system calibration yield values
is allowed to take to reach the setpoint are more than half of the
is controlled by the Min. Setpoint Minimum Tolerance band,
%sFailed to reach reached (ms) parameter. This might be then increase this
PNT1-631 WARN setpoint caused by a sticking transducer, a tolerance value. If the
All of the conditions were set for air to Check and perform the
be flowing but a zero flow rate was following: * Check, clean,
measured for longer than the Zero flow and possibly replace the
timeout parameter. This might be air cap. * Check that the
caused by: * A clogged air cap * A gun is properly triggering.
broken applicator trigger * Broken air * If air was observed to be
lines * A loss of air supply pressure * A flowing, check and
%s0 air flow rate broken air flow sensor * A broken cable possibly replace the air
PNT1-632 WARN timeout (to the flow sensor) * A Zero flow time- flow sensor. * Check for a
Retry the operation by
While completing operations to setting the Equipment
measure the equipment delays, the learn to Redo, and
%sWarning, learn item equipment did not respond within the calibrate again. Check for
PNT1-633 WARN failed expected timeout. other AccuAir alarms in
being output, the yield (slpm/cnt) for larger diameter air lines to
that flow rate was approximately larger supply air to the cap. Use
than the percent tolerance. It is not a smaller ratio booster.
likely that the set point will be reached Otherwise, accept a larger
%sDyn. yield > min within the specified tolerances. This tolerance band. Increase
PNT1-634 WARN tolerance band might be caused by the use of a flow the minimum tolerance
The relationship of the output Check and perform the
command to the flow rate obtained has following: * Check that
changed significantly since the last the air cap is tight on the
calibration. There is now a smaller gun. * Check, clean, and
output required to get the same flow possibly replace the air
rate. This can be caused by: air leaks, a cap. * Check for leaks in
loose air cap, or a significant increase of air lines or at fittings. *
air supply pressure. Note that the Check for cracks or breaks
system continues to close the loop and in the gun. * Check for a
%sCal. table adapted generally maintain requested flow rates large increase of air
PNT1-635 WARN out, down even after this alarm if there are no supply pressure. *
During calibration, it was found that Check that the I/P
the maximum amount of flow occurred transducer is the right
with the command output at only the range. If not, replace it.
middle (midpoint) of the range. This Check that the booster
%sMax. flow is below indicates that there is the incorrect has the correct ratio,
PNT1-636 WARN midpt. output equipment is installed or the typcially 1 to 1. If the
Complete the procedure
to zero (tare) the air flow
When attempting to zero (tare) the air meter manually for this
flow meter automatically, the flow channel. With the air lines
%sLeak detect when reading from it was large enough to all reconnected and the
PNT1-637 WARN zeroing meter indicate a possible leak. air pressure on, if the
The automatic zero tare routine took
PNT1-638 WARN Tare timeout too long to complete. None.
The relationship of the output Check, clean, and possibly
command to the flow rate obtained has replace the air cap. Check
changed significantly since the last for a large loss of air
calibration. There is now a larger supply pressure. Check for
output required to get the same flow pinched air lines or
rate. This can be caused by: a clogged clogged air passages in
air cap, clogged gun, pinched air lines the gun. Recalibrate to
or large losses of air supply pressure. clear the alarm
Note that the system continues to close immediately. Increase the
%sCal. table adapted the loop and generally maintain Adaptive tolerance
PNT1-643 WARN out,output up requested flow rates even after this parameter to allow larger
%sCal. table adapted in The calibration table has returned to
PNT1-644 WARN tolerance the normal operating range as defined None.
As a particular flow rate set point is Perform the following: *
being output, the yield (slpm/cnt) for Decrease the yield. * Use
that flow rate was approximately larger larger diameter air lines to
than the percent tolerance. It is not supply air to the cap. *
likely that the set point will be reached Use a larger ratio booster
%sDyn. yield > %% within the specified tolerances. This (2:1 instead of 1:1) if the
PNT1-645 WARN tolerance band might be caused by the use of a flow system can not supply the
Comparisons of how far the measured Check, clean, and possibly
flow rate is from the setpoint had too replace the air cap. Check
large of a result. The size of the error for oscillating air pressure
between measured flow and setpoint on the output of the I/P
that will cause this alarm is controlled transducer. If found,
%sFlow rate avg. error by the Max. error from setpoint replace the transducer.
PNT1-646 WARN excessive parameter. Possible causes are: * A Check for a large loss of
PNT1-647 WARN successful calibration has been completed None.
AccuAir calibration could not complete. The best remedy might be
This might be due to the air supply found from the previous
being off. Check for other alarms in the alarm in the log. Request
log. This might be due to incorrect a proper air flow at the
PNT1-648 WARN %sCalibration aborted setup parameters, or incomplete cap. Check that it occurs.
This is a warning not a failure. During The new flow rate is
AccuAir calibration the low flow rate shown as point 2 in the
could not be properly reached. A new calibration table. This
%sCal. low flow rate flow was established. The target flow value can be visually
PNT1-649 WARN reset rate is determined by the Table point checked and accepted.
This is a warning, not a failure. During The new maximum flow
AccuAir calibration the expected rate is shown as point 10
%sCal. max. flow rate maximum flow rate could not be in the calibration table.
PNT1-650 WARN reset reached at the maximum output. A This value can be visually
to reach the maximum flow rate. Retry the calibration. *
Possible causes are: * A high gain * A Possibly decrease the Gain
sticking I/P transducer * Too large of a modifier parameter. *
%sCal. time out at max. yield for the current tolerance band * Increase the Percent
PNT1-651 WARN flow The system response is too slow for the tolerance band
to reach the minimum flow rate. This Retry the calibration. *
flow rate is the Table point no. 2 Decrease the Gain
parameter. Possible causes are: * A modifier parameter, if
high gain * A sticking I/P transducer * possible. * Increase the
%sCal. time out at low Too large of a yield for the current Percent tolerance band
PNT1-652 WARN flow tolerance band * Or, the system parameter. * Check and
All of the conditions were set for air to Check the following: *
be flowing, but a zero flow rate was Check, clean, and possibly
measured. This might be caused by: * A replace the air cap. *
broken applicator trigger * Pinched air Check that the gun is
lines * A loss (or near loss) of air supply properly triggering. * If air
pressure * A broken air flow sensor * A was observed to be
%s0 air flow rate broken cable (to the flow sensor) * A flowing, check and
PNT1-653 WARN detected Trigger delay that is too short Note: possibly replace the air
As the AccuAir calibration steps down Perform the following: *
through the 10 points in the calibration Retry the calibration. *
table, it expects a lower flow for each Check that the pilot air
decrease in the command flow value. In line to the booster has
this case, the flow did not decrease. sufficient exhaust
This can be caused by insufficient capability. * Increase the
%sLower output did not exhaust, no quick exhaust on the pilot Calibration step delay
PNT1-654 WARN lower flow air line, too large of a hysteresis in parameter by about
%sTime out during a time down, the Closed loop system Check that the high flow
PNT1-655 WARN cal. test timed out. This indicates that the high rate can be reached
With a minimum control output, the
flow rate was measured to be higher
Check and perform the
Max. control out (ms) parameter following: * Check and
repair the various air
might be caused by a leaking or broken
lines. * Check and repair
air line between the flow sensor andthe air booster. * Check
the applicator. The I/P transducer and repair the I/P
might be stuck open. The air boostertransducer. * Possibly
%sMin. output has flow might be stuck open or might be increase the Max. control
PNT1-656 WARN > setpoint leaking. This might be caused by a out (ms) parameter.
With a maximum control output, the Check and perform the
flow rate was measured to be lower following: * Check, clean,
and possibly replace the
Max. control out (ms) parameter air cap. * If air is observed
to be flowing (when
is likely caused by a clogged air cap.
commanded), possibly
%sMax. output has flow This might also be caused by: pinched
replace the air flow
PNT1-657 WARN < setpoint air lines, a broken I/P transducer, or a
sensor. * Check for a
%sFlow setpoint below The requested air flow setpoint is Adjust the air flow
PNT1-658 WARN globals below the range of the current setpoint to be within the
Adjust the air flow
setpoint to be within the
The requested air flow setpoint is calibrated range of this
above the calibrated range for Fan Air. parameter. Perform the
%sRequested flow The maximum value is shown as point necessary steps to
PNT1-659 WARN above cal. table number 10 in the calibration table. increase the maximum
%sSlow air flow leak on. This might be caused by a leaking system will continue to
PNT1-660 WARN detected trigger valve, leaking air line, or any function properly. The
detected when the gun was not turned The applicator and the
on. This might be caused by a leaking various air lines should be
PNT1-661 WARN detected line, broken applicator, or any other air immediately.
This is caused by a failure of the If the Fan Air control I/P
AccuAir system to reach the setpoint transducer is noisy or
within the tolerance band during the broken, change it. If the
allotted time. The time that the system calibration yield values
is allowed to take to reach setpoint is are more than half of the
controlled by the Min. Setpoint min. Tolerance band, then
%sFailed to reach reached (ms) parameter. This failure increase this tolerance
PNT1-662 WARN setpoint might be caused by a sticking value. If the Flow delay
All of the conditions were set for air to Check the following: *
be flowing but a zero flow rate was Check, clean, and possibly
measured for longer than the Zero flow replace the air cap. *
timeout parameter. This might be Check that the gun is
caused by: * A clogged air cap * A properly triggering. * If air
broken applicator trigger * Broken air was observed to be
lines * A loss of air supply pressure * A flowing, check and
%s0 air flow rate broken air flow sensor * A broken cable possibly replace the air
PNT1-663 WARN timeout to the flow sensor * Or, a Zero flow flow sensor. * Check for a
measure the equipment delays, the learn to Redo and
PNT1-664 WARN failed expected timeout. other AccuAir alarms in
As a particular flow rate set point is Perform the following: *
being output, the yield (slpm/cnt) for Decrease the yield. * Use
that flow rate was larger than the larger diameter air lines to
percent tolerance. It is not likely that supply air to the cap. *
the set point will be reached within the Use a smaller ratio
%sDyn. yield > min specified tolerances. This might be booster. * Otherwise,
PNT1-665 WARN tolerance band caused by the use of a flow rate accept a larger tolerance
The relationship of the output Check that the air cap is
command to the flow rate obtained has tight on the gun. Check,
changed significantly since the last clean, and possibly
calibration. There is now a smaller replace the air cap. Check
output required to get the same flow for leaks in air lines or at
rate. This can be caused by: air leaks, a fittings. Check for cracks
loose air cap, or a significant increase of or breaks in the gun.
air supply pressure. Note that the Check for a large increase
system continues to close the loop and of air supply pressure.
%sCal. table adapted generally maintain requested flow rates Recalibrate to clear the
PNT1-666 WARN out, down even after this alarm if there are no alarm immediately.
During calibration it was found that the Check that the I/P
maximum amount of flow occurred transducer is within the
with the command output at only the correct right range. If not,
middle (midpoint) of the range. This replace it. Check that the
%sMax. flow is below indicates that there is incorrect booster has the correct
PNT1-667 WARN midpt. output equipment installed, or the equipment ratio, typically 1 to 1. If
to zero (tare) the air flow
When attempting to zero (tare) the air meter manually for this
flow meter automatically, the flow channel. With the air lines
%sLeak detect when reading from it was large enough to all reconnected and air
PNT1-668 WARN zeroing meter
%sEstat controller indicate a possible
The external E-stat leak.
controller detected pressure
Check theon, if theofdisplay
status the
PNT1-673 WARN warning a warning.
The external E-stat controller detected external
Check theE-stat
statuscontroller.
of the
PNT1-674 PAUS %sEstat controller fault The
a fault.
E-stat disconnect or enable switch external
Turn E-stat
on the controller.
E-stat
PNT1-675 WARN %sEstats disabled is off. disconnect or enable
%sEstat controller not The E-stat local/remote switch is set to Set the local/remote
PNT1-676 WARN in remote local mode. switch on the E-stat
The robot sent the HVON signal to the Check the status of the
PNT1-677 WARN %sEstat HVON Failed E-stat controller, but did not get a external E-stat controller.
Check the voltage and set
point reached light on the
%sEstat setpoint not The E-stat controller did not set the set E-stat controller. It might
PNT1-678 WARN reached point reached output in time. be having trouble
%sEstat T.P. enable The ESTAT enable for the teach Request the ESTAT
PNT1-679 WARN %sEstat
TimeoutkV present pendant screen timed out. voltage again.
Replace the faulty
PNT1-680 while HVON=OFF A faulty electrostatic unit or cascade. equipment.
The estat controller heartbeat was Check the estat servo
PNT1-681 heartbeat lost! The
%sEstat controller lost!.external E-stat controller detected disconnect
Check and toofmake
the status the
PNT1-686 WARN warning aThe
warning.
external E-stat controller detected external E-stat controller.
Check the status of the
PNT1-687 PAUS %sEstat controller fault The
a fault.
Turn E-stat
on the controller.
E-stat
PNT1-688 WARN %sEstats disabled is off. disconnect or enable
%sEstat controller not The E-stat local/remote switch is set to Turn the local/remote
PNT1-689 WARN in remote local mode. switch on the E-stat
The robot sent the HVON signal to the
E-stat controller but did not get an Check the status of the
PNT1-690 WARN %sEstat HVON Failed HVON signal back from the E-stat unit. external E-stat controller.
%sEstat setpoint not The E-stat controller did not set the set E-stat controller. It might
PNT1-691 WARN %sEstat
reached T.P. enable pointestat
The reached output
enable in time.
for the be havingE-stat
teach pendant Request trouble
votage
PNT1-692 WARN Timeout
%sEstat kV present screen timed out. again.
Replace the faulty
PNT1-693 while HVON=OFF A faulty electrostatic unit or cascade. equipment.
PNT1-694 %sEstat heartbeat lost! lost!. disconnect and to make
The Bell Speed Control Startup Test for Check the Start Mode
%sTurbine Startup Test the turbine is not complete. This test field on the Bell Speed
PNT1-699 WARN Not Complete must be performed before running the SETUP menu to check the
A velocity change within a measured Check the hardware to
PNT1-700 PAUS %sMax.dV/dT detected time has exceeded the maximum dV/dT determine if the feedback
With a maximum control output the Check the turbine lines for
speed was measured to be lower than pinching, especially at
the setpoint (requested speed). This places where they flex.
%sMax. output has can occur if: * The gun is clogged. * The Check the turbine air
PNT1-701 PAUS speed < setpoint turbine air or turbine pilot air line is supply pressure. Check
The requested turbine speed output
command is above the range that is
%sRequested speed considered valid Adjust the turbine
PNT1-702 WARN over valid range speed command that is used in the N/A
The turbine speed failed to come
within the Tolerance Band setting
within the time setting of Min. set point
reached (ms) value. This can be caused
by noise in the speed sensor signals,
low air supply pressure or other
failures. This may occur with the alarm
Max. output has speed < setpoint . If
the Max. output has speed < setpoint
alarm is also in the alarm log follow the
remedies for that alarm. Examine the
%sFailed to reach displayed turbine speed and evaluate if
PNT1-703 WARN setpoint it is bouncing a lot. If so decrease the N/A
All of the conditions were set for the If the turbine can be seen
turbine to be spinning but a zero speed spinning, check the
was measured for a set time period. following: the speed
This might be due to no turbine air sensor interface and
pressure or pilot air pressure. One of speed sensor pickup.
%sZero turbine speed the following items might be broken: Otherwise, check the
PNT1-704 PAUS timeout the I/P transducer, speed sensor other items listed above.
While the turbine was operating the
RPM level was above the Over speed
limit . When this error occurs, braking
will be applied to bring the turbine
speed to within the acceptable
PNT1-705 PAUS %sTurbine over speed operating range. Check and replace the N/A
While the turbine was operating and
the gun was on or enabled, the RPM
level was below the Under speed limit .
Check and replace the I/P transducer if
%sTurbine under speed necessary. Check the supply and pilot
PNT1-706 WARN fault air pressures, if either one is low, N/A
While the gun was off or disabled and
the turbine was operating the RPM
level was below the Under speed limit,
Manual . Check and replace the I/P
%sTurbine under speed transducer if necessary. Check the
PNT1-707 WARN warning supply and pilot air pressures, if either N/A
Checks for how far the speed is from Check and replace the I/P
the set point have been too high. transducer if necessary.
%sSpeed avg. error Possible causes are: * A sticking I/P Check the supply and pilot
PNT1-708 WARN excessive transducer * Low supply air pressure * air pressures. If either one
The digital input signal indicating the
Bear Air is above the minimum
pressure is not ON. Check the supply
PNT1-709 PAUS %sBearing Air NOT OK pressure to the Bearing Air or verify the N/A
%sCruise Speed not The Cruise Speed determined during Redo the Bell Speed
PNT1-710 WARN established the Bell Speed Startup Test could not Startup Test to determine
%sTurbine Startup Test the turbine is not complete. This test field on the Bell Speed
PNT1-716 WARN Not Complete must be performed before running the SETUP menu to check the
PNT1-717 PAUS %sMax.dV/dT detected time has exceeded the maximum dV/dT determine if the feedback
the setpoint (requested speed). The places where they flex.
%sMax. output has gun might be clogging. The turbine air Check the turbine air
PNT1-718 PAUS speed < setpoint or turbine pilot air line might be supply pressure. Check
The requested turbine speed output
command is above the range that is
%sRequested speed considered valid Adjust the turbine
PNT1-719 WARN over valid range speed command that is used in the N/A
The turbine speed failed to come If the Max. output has
within the Tolerance Band setting speed < setpoint alarm is
within the time setting of Min. set point also in the alarm log,
reached (ms) value. This can be caused follow the remedies for
by noise in the speed sensor signals, that alarm. Examine the
%sFailed to reach low air supply pressure or other displayed turbine speed
PNT1-720 WARN setpoint failures. This might occur with the Max. and evaluate if it is
All of the conditions were set for
turbine to be spinning and a zero speed
was measured for a set time period.
This may be due to no turbine air
pressure or pilot air pressure. One of
the following items may be broken: the
I/P transducer, speed sensor pickup,
speed sensor interface. The Zero speed
%sZero turbine speed timeout may be set too short. If turbine
PNT1-721 PAUS timeout can be seen spinning, check: speed N/A
While the turbine was operating the
RPM level was above the Over speed
limit . When this error occurs, braking
will be applied to bring the turbine
speed to within the acceptable
PNT1-722 PAUS %sTurbine over speed operating range. Check and replace the N/A
While the turbine was operating and
the gun was on or enabled, the RPM
level was below the Under speed limit .
Check and replace the I/P transducer if
%sTurbine under speed necessary. Check the supply and pilot
PNT1-723 WARN fault air pressures, if either one is low, N/A
While the gun was off or disabled and
the turbine was operating the RPM
level was below the Under speed limit,
Manual . Check and replace the I/P
%sTurbine under speed transducer if necessary. Check the
PNT1-724 WARN warning supply and pilot air pressures, if either N/A
%sSpeed avg. error Possible causes are: * A sticking I/P Check the supply and pilot
PNT1-725 WARN excessive transducer * Low supply air pressure * air pressures. If either
The digital input signal indicating the
Bear Air is above the minimum
pressure is not ON. Check the supply
PNT1-726 PAUS %sBearing Air NOT OK pressure to the Bearing Air or verify the N/A
PNT1-727 WARN established the Bell Speed Startup Test could not Startup Test to determine
Pump #1 inlet pressure has been below Check the following: *
the low warning limit for a user Make sure the low
configurable period of time. This pressure warning limit is
condition is usually caused by one or appropriate. * Make sure
more of the following: * The low the low pressure
pressure warn limit is set too high. * sensitivity is appropriate.
The low pressure sensitivity is set too * Check the pilot line to
short. * The pilot line to resin color resin color that is being
valve is removed or broken. * The resin used. * Verify that the
color valve has failed. * The supply resin color valve being
pressure is too low. * The supply line used is not faulty. * Make
(hose, etc.) is removed or broken. * The sure the supply pressure is
%sPump 1 IN low resin inlet transducer has failed. * The appropriate. * Check the
PNT1-733 WARN pressure warning inlet
Pumpregulator has failed.
#1 inlet pressure has been below supply
* Makeline
surefrom
the paint
low
the low fault limit for a user pressure warning limit is
configurable period of time. This appropriate. * Make sure
condition is usually caused by one or the low pressure
more of the following: * The low sensitivity is appropriate.
pressure fault limit is set too high. * * Check the pilot line to
The low pressure sensitivity is set too resin color that is being
short. * The pilot line to resin color used. * Verify that the
valve is removed or broken. * The resin resin color valve being
color valve has failed. * The supply used is not faulty. * Make
pressure is too low. * The supply line sure the supply pressure is
%sPump 1 IN low (hose, etc.) is removed or broken. * The appropriate. * Check the
PNT1-734 PAUS pressure fault resin inlet transducer has failed. * The supply line from paint
Pump #1 inlet pressure has been above Make sure the high
the high warning limit for a user pressure warning limit is
condition is usually caused by one or the high pressure
more of the following: * The high sensitivity is appropriate.
pressure warn limit is set too low. * The * Make sure the supply
high pressure sensitivity is set too pressure is appropriate. *
short. * The supply pressure is set too Check the resin inlet
%sPump 1 IN high high. * The resin inlet transducer has transducer as follows:
PNT1-735 WARN pressure warning failed. * The inlet regulator has failed. Through the Analog I/O
the high fault limit for a user pressure fault limit is
pressure fault limit is set too low. * The * Make sure the supply
PNT1-736 PAUS pressure fault failed. * The inlet regulator has failed. Through the Analog I/O
Pump #1 outlet pressure has been Check the following: *
below the low warning limit for a user Make sure the low
The low pressure sensitivity is set too* Check the pilot line to
valve is removed or broken. * The resinused. * Verify that the
%sPump 1 OUT low pressure is too low. * The supply line used is not faulty. * Make
PNT1-737 WARN pressure warning (hose, etc.) is removed or broken. * A sure the supply pressure is
below the low fault limit for a user Make sure the low
configurable period of time. This pressure fault limit is
pressure fault limit is set too high. *sensitivity is appropriate.
short. * The pilot line to resin color the resin color that is
valve is removed or broken. * The resinbeing used. * Verify that
%sPump 1 OUT low color valve has failed. * The supply the resin color valve being
PNT1-738 PAUS pressure fault pressure is too low. * The supply line used is not faulty. * Make
above the high warning limit for a userMake sure the high
more of the following: * The high the high pressure
pressure warn limit is set too low. * The
sensitivity is appropriate.
high pressure sensitivity is set too * Make sure the pump
short. * The pump start/stop start/stop anticipates are
anticipates are not setup correctly. * appropriate. * Make sure
%sPump 1 OUT high Obstructed line, trigger, or check valve.
the lines, trigger, or check
PNT1-739 WARN pressure warning * The pilot line to mix resin valve is valve are not obstructed.
above the high fault limit for a user Make sure the high
pressure fault limit is set too low. * The
anticipates are not set up correctly. *appropriate. * Make sure
%sPump 1 OUT high Obstructed line, trigger, or check valve.
PNT1-740 PAUS pressure fault * The pilot line to mix resin valve is valve are not obstructed.
Perform a fluid flow test
on pump #1 with a beaker
The actual flow rate out of pump #1 as and verify that the beaker
measured by the fluid flow meter has amount matches the
been continuously greater than a set pump #1 size (cc/rev).
%sPump 1 fluid flow point window (a percentage) for a user Verify that the correct KFT
PNT1-741 WARN rate > set point configurable period of time. factor has been entered
been continuously less than a set point pump #1 size (cc/rev).
%sPump 1 fluid flow window (a percentage) for a user Verify that the correct KFT
PNT1-742 WARN rate < set point configurable period of time. factor has been entered
Zero fluid flow out of pump #1 is Check the mechanical
detected. This condition is usually coupling between the
caused by one or more of the motor and the pump.
%sPump 1 zero fluid following: * A loose mechanical Make sure the line from
PNT1-743 WARN flow rate detected coupling between the motor and pump to trigger is ok.
The motor velocity for pump #1 has
exceeded its operating limit. The motor
%sPump 1 motor speed will be reduced to be within Lower the flow rate to
PNT1-744 WARN velocity limit operating limit. The motor speed for within the motor limit.
%sPump 1 motor servo The servo power to pump #1 is not power is turned off for
PNT1-745 WARN not ready ready. some reason, such as E-
and verify that the beaker
The actual total flow out of pump #1 as amount matches the
measured by the fluid flow meter has a pump #1 size (cc/rev).
value that is different than the Verify that the correct KFT
%sPump 1 totals differ commanded total flow. This difference factor has been entered
PNT1-746 WARN > tolerance is larger
Pump #2than
inletthe total flow
pressure tolerance.
has been below for the fluid
Perform the flow meter*
following:
short. * The pilot line to hardener color verify the hardener color
valve is removed or broken. * The that is being used. * Verify
hardener color valve has failed. * The that the hardener color
supply pressure is too low. * The supply valve being used is not
line (hose and so on) is removed or faulty. * Make sure the
%sPump 2 IN low broken. * The hardener inlet supply pressure is
PNT1-753 WARN pressure warning transducer haspressure
Pump #2 inlet failed. * has
Thebeen
inlet below appropriate.
* Make sure the* Check
low the
the low fault limit for a user pressure fault limit is
more of the following: * The low sensitivity is appropriate.
pressure fault limit is set too high. * * Check the pilot line to
The low pressure sensitivity is set too hardener color that is
short. * The pilot line to hardener color being used. * Verify that
valve is removed or broken. * The the hardener color valve
hardener color valve has failed. * The being used is not faulty. *
supply pressure is too low. * The supply Make sure the supply
line (hose and so on) is removed or pressure is appropriate. *
%sPump 2 IN low broken. * The hardener inlet Check the supply line from
PNT1-754 PAUS pressure fault transducer has failed. * The inlet the paint kitchen. * Check
Pump #2 inlet pressure has been above Check the following: *
the high warning limit for a user Make sure the high
pressure warn limit is set too low. * The sensitivity is appropriate.
high pressure sensitivity is set too * Make sure the supply
short. * The supply pressure is set too pressure is appropriate. *
high. * The hardener inlet transducer Check the hardener inlet
%sPump 2 IN high has failed. * The inlet regulator has transducer as follows:
PNT1-755 WARN pressure warning failed. Through the Analog I/O
the high fault limit for a user Make sure the high
pressure fault limit is set too low. * The sensitivity is appropriate.
PNT1-756 PAUS pressure fault failed.
Pump #2 outlet pressure has been Through
Check thethe Analog I/O
following: *
short. * The pilot line to hardener color hardener color that is
valve is removed or broken. * The being used. * Verify that
hardener color valve has failed. * The the hardener color valve
%sPump 2 OUT low supply pressure is too low. * The supply being used is not faulty. *
PNT1-757 WARN pressure warning line
Pump (hose and sopressure
#2 outlet on) is removed or
has been Make
Check sure the supply*
the following:
pressure fault limit is set too high. * sensitivity is appropriate.
valve is removed or broken. * The being used. * Verify that
PNT1-758 PAUS pressure fault line (hose and so on) is removed or Make sure the supply
above the high warning limit for a user Make sure the high
anticipates are not setup correctly. * A appropriate. * Make sure
%sPump 2 OUT high line, trigger, or check valve is the lines, trigger, or check
PNT1-759 WARN pressure warning obstructed. * The pilot line to mix valve are not obstructed.
anticipates are not setup correctly. * A appropriate. * Make sure
%sPump 2 OUT high line, trigger, or check valve is the lines, trigger or check
PNT1-760 PAUS pressure fault obstructed. * The pilot line to mix valve are not obstructed.
The actual flow rate out of pump #2 as on pump #2 with a beaker
measured by the fluid flow meter has and verify that the beaker
been continuously greater than a set amount matches the
%sPump 2 fluid flow point window (a percentage) for a user pump #2 size (cc/rev). *
PNT1-761 WARN rate > set point configurable period of time. Verify that the correct KFT
been continuously less than a set point amount matches the
%sPump 2 fluid flow window (a percentage) for a user pump #2 size (cc/rev). *
PNT1-762 WARN rate < set point configurable period of time. Verify that the correct KFT
The servo power to pump #2 is not
%sPump 2 motor servo ready. Usually, the servo not ready Correct the condition, and
PNT1-765 WARN not ready occurs when servo power is turned off reset the controller.
The actual total flow out of pump #2 as and verify that the beaker
measured by the fluid flow meter has a amount matches the
value that is different than the pump #2 size (cc/rev). *
%sPump 2 totals differ commanded total flow. This difference Verify that the correct KFT
PNT1-766 WARN > tolerance is larger than the total flow tolerance. factor has been entered
Ensure the pumps are
PNT1-767 WARN %sCalibration aborted The IPC auto calibration aborted. operating correctly. Also
The IPC auto calibration aborted Ensure the pumps are
(%s) Non-increasing cal because the calibration table is not operating correctly.
PNT1-768 WARN table increasing with the commanded flow Ensure that the speed
The IPC auto calibration aborted. This Ensure the pumps are
can occur because zero PSI was operating correctly.
detected while the IPC system was Ensure that the speed
determining the maximum flow rate command delay (used to
during the auto calibration. This can allow the motor RPM to
also occur while the IPC system was settle) is set to a sufficient
determining one of the calibration amount. If the setup
PNT1-769 WARN (%s) Zero PSI points.
An error occurred in setting the color parameter, 'Max speed
PNT1-770 WARN (%s) Set Color Valve valve. None.
The color identified in the error Change the default ratio
%s Res:Hrd ratio is message has a default ratio (0.0:0.0) for this color in the SETUP
PNT1-771 WARN 0.0:0.0 defined.
Pump #1The
inletIPC pumpshas
pressure canbeen
only run
below Color
CheckDETAIL menu. *
the following:
(hose and so on) is removed or broken. sure the supply pressure is
%sPump 1 IN low * The resin inlet transducer has failed. * appropriate. * Check the
PNT1-778 WARN pressure warning The
Pump inlet
#1 regulator has failed.
inlet pressure has been below supply linefollowing:
Check the from the paint
*
the low fault limit for a user Make sure the low
(hose and so forth) is removed or sure the supply pressure is
%sPump 1 IN low broken. * The resin inlet transducer has appropriate. * Check the
PNT1-779 PAUS pressure fault failed. * The inlet regulator has failed. supply line from the paint
pressure warn limit is set too low. * The * Make sure the supply
PNT1-780 WARN pressure warning failed. * The inlet regulator has failed. Through the Analog I/O
pressure fault limit is set too low. * The * Make sure the supply
PNT1-781 PAUS pressure fault failed. * The inlet regulator has
Pump #1 outlet pressure has been failed. Through
Check thethe Analog I/O
following: *
valve is removed or is broken. * The used. * Verify that the
resin color valve has failed. * The resin color valve being
%sPump 1 OUT low supply pressure is too low. * The supply used is not faulty. * Make
PNT1-782 WARN pressure warning line (hose and so on) is removed or is sure the supply pressure is
valve is removed or is broken. * The used. * Verify that the
%sPump 1 OUT low resin color valve has failed. * The resin color valve being
PNT1-783 PAUS pressure fault supply pressure is too low. * The supply used is not faulty. * Make
Pump #1 outlet pressure has been * Make sure the high
above the high warning limit for a user pressure warning limit is
pressure warn limit is set too low. * The * Make sure the pump
high pressure sensitivity is set too start/stop anticipates are
short. * The pump start/stop appropriate. * Make sure
%sPump 1 OUT high anticipates are not setup correctly. * the lines, trigger, or check
PNT1-784 WARN pressure warning There is an obstructed line, trigger, or valve are not obstructed.
%sPump 1 OUT high There is an obstructed line, trigger, or the lines, trigger, or check
PNT1-785 PAUS pressure fault check valve. * The pilot line to mix resin valve are not obstructed.
%sPump 1 fluid flow point window (a percentage) for a user pump #1 size (cc/rev). *
PNT1-786 WARN rate > set point configurable period of time. Verify that the correct KFT
The servo power to pump #1 is not
ready. Usually, the servo not ready
%sPump 1 motor servo occurs when servo power is turned off Correct the condition, and
PNT1-790 WARN not ready such as during an E-stop condition, or if reset the controller.
Pump #2 inlet pressure has been below Check the following: *
valve is removed or is broken. * The being used. * Verify that
supply pressure is too low. * The supply being used is not faulty. *
line (hose and so on) is removed or is Make sure the supply
%sPump 2 IN low broken. * The hardener inlet pressure is appropriate. *
PNT1-798 WARN pressure warning transducer haspressure
Pump #2 inlet failed. * has
Thebeen
inlet below Check
Check the
the supply line*from
following:
the low fault limit for a user Make sure the low
supply pressure is too low. * The supply being used is not faulty. *
line (hose and so on) is removed or is Make sure the supply
%sPump 2 IN low broken. * The hardener inlet pressure is appropriate. *
PNT1-799 PAUS pressure fault transducer has failed. * The inlet Check the supply line from
the high warning limit for a user Make sure the high
PNT1-800 WARN pressure warning failed. Through the Analog I/O
the high fault limit for a user Make sure the high
PNT1-801 PAUS pressure fault failed. Through the Analog I/O
PNT1-802 WARN pressure warning line
Pump (hose and sopressure
#2 outlet on) is removed or is
has been Make
Check sure the supply*
the following:
pressure fault limit is set too high. *sensitivity is appropriate.
short. * The pilot line to hardener color
hardener color that is
%sPump 2 OUT low supply pressure is too low. * The supply
being used is not faulty. *
PNT1-803 PAUS pressure fault line (hose and so on) is removed or is Make sure the supply
above the high warning limit for a userMake sure the high
pressure warn limit is set too low. * The
%sPump 2 OUT high There is an obstructed line, trigger, or
PNT1-804 WARN pressure warning check valve. * The pilot line to mix valve are not obstructed.
pressure fault limit is set too low. * The
short. * The pump start/stop anticipatestart/stop anticipates are
times are not set up correctly. * Thereappropriate. * Make sure
%sPump 2 OUT high is an obstructed line, trigger, or check
PNT1-805 PAUS pressure fault valve. * The pilot line to mix hardenervalve are not obstructed.
Do a fluid flow test on
pump #2 with a beaker
been continuously greater than a set pump #2 size (cc/rev).
%sPump 2 fluid flow point window (a percentage) for a user Verify that the correct KFT
PNT1-806 WARN rate > set point configurable period of time. factor has been entered
PNT1-808 WARN flow rate detected coupling between the motor and pump to trigger is working
%sPump 2 motor servo The servo power to pump #2 is not power is turned off
PNT1-810 WARN not ready ready. because of an E-stop
Ensure pumps are
PNT1-812 WARN %sCalibration aborted The IPC auto calibration aborted. operating correctly.
The IPC auto calibration aborted Ensure pumps are
(%s) Non-increasing cal because the calibration table is not operating correctly.
PNT1-813 WARN table increasing with the commanded flow Ensure that the speed
Ensure pumps are
The IPC auto calibration aborted operating correctly.
because zero PSI was detected while Ensure that the speed
the IPC system was determining the command delay (used to
maximum flow rate during the auto allow the motor RPM to
calibration or while the IPC system was settle) is set to a sufficient
PNT1-814 WARN (%s) Zero PSI points.
There was an error in setting the color parameter, 'Max speed
PNT1-815 WARN (%s) Set Color Valve valve. None.
%s Res:Hrd ratio is message has a default ratio (0.0:0.0) for this color in the SETUP
PNT1-816 WARN 0.0:0.0 defined. The IPC pumps can only run Color DETAIL menu.
%sHIGH ServoBell The torque value of the ServoBell Determine the cause of
PNT1-823 PAUS TORQUE exceeded the maximum safety limit. the high torque reading,
%sServoBell motor not The servo power to the ServoBell motor power is turned off
PNT1-824 WARN ready is not ready. because of an E-stop
Slow down the Cal Empty
Speed. Ensure that the
PNT1-825 WARN %sCalibration Aborted The ServoBell auto calibration aborted. trigger is not clogged and
The ServoBell auto calibration aborted Ensure that all faults are
due to a time out when the system was cleared, and that the
PNT1-826 WARN %sServoBell
%sCalibrationCalibration
Time Out The
trying to determine
ServoBell the empty can
auto calibration ServoBell motor is turning
An attempt was made to move the Determine the cause of
%sBad Status from ServoBell or the SpeedDock and a bad the bad status, then
PNT1-828 ABRT set_prax_spd status from set_prax_spd was resolve the problem.
%sHIGH SpeedDock The torque value of the SpeedDock Determine the cause of
PNT1-829 TORQUE exceeded the maximum safety limit. the high torque reading
%sSpeedDock motor The servo power to the SpeedDock power is turned off for
PNT1-830 not ready motor is not ready. some reason, such as an
extend sensor at
PNT1-831 %s or B, but the attempt failed. retracted or extended
extend sensor at
SpeedDock side A or B. If
it was an extended fault,
ensure that the pusher
An attempt was made to extend or extended fully at the
retract the valve at SpeedDock side A Speed Dock side A or B. If
PNT1-832 %s or B, but failed. it was a retracted fault,
%sHIGH ServoBell Torque value of the ServoBell exceeded Determine the cause of
PNT1-833 PAUS TORQUE the maximum safety limit. the high torque reading
%sServoBell motor not The servo power to the ServoBell motor power is turned off
PNT1-834 WARN ready is not ready. because of an E-stop
The servo power to the ServoBell motor power is turned off
PNT1-835 WARN %sCalibration Aborted is not ready. because of an E-stop
The system timed out and the ServoBell Clear all faults, and verify
auto calibration aborted when it was that the ServoBell motor
PNT1-836 WARN %sServoBell
%sCalibrationCalibration
Time Out The
trying to determine
auto calibration is turning during the
PNT1-838 ABRT set_prax_spd status from set_prax_spd was resolve the problem.
%sHIGH SpeedDock The torque value of the SpeedDock Determine the cause of
PNT1-840 not ready motor is not ready. some reason, such as
extend sensor at
PNT1-841 %s or B, but failed. retracted or extended
extend sensor at
SpeedDock side A or B. If
it was an extended fault,
ensure that the pusher
An attempt was made to extend or extended fully at the
retract the valve at the SpeedDock, side Speed Dock, side A or B. If
PNT1-842 %s A or B, but failed. it was a retracted fault,
Correct the problem if the
%sOutput Press low Output pressure dropped below the warning occurs
PNT1-843 WARN warning warning level. repeatedly, or adjust the
%sOutput Press high The output pressure exceeded the high warning occurs
%sManifold Press low The output pressure exceeded the high warning occurs
%sManifold Press high The manifold pressure exceeded the warning occurs
PNT1-846 WARN warning high warning level. repeatedly, or adjust the
%sOutput Press low Output pressure dropped below alarm Correct the problem
PNT1-847 PAUS alarm level. immediately, or adjust the
%sOutput Press high Output pressure exceeded high alarm Correct the problem
%sManifold Press low Output pressure dropped below alarm Correct the problem
%sManifold Press high Manifold pressure exceeded high alarm Correct the problem
PNT1-850 PAUS alarm
%sCalibration level. immediately, or adjust the
PNT1-851 WARN successful Calibration successful. None.
Determine cause for
PNT1-852 WARN %sCalibration aborted Calibration aborted. calibration to abort and
Calibration aborted due to the Output Determine cause for the
or Manifold pressure failing to increase pressure not increasing
PNT1-853 WARN %sNon-incr cal table as the command rate increased. and correct accordingly.
Calibration aborted due to zero Output Determine cause for the
PNT1-854 WARN %sZero Pressure or Manifold pressure detected after a zero pressure and correct
%sOutput Press low Output pressure dropped below Correct problem if
PNT1-859 WARN warning warning level. warning occurs
%sOutput Press high Output pressure exceeded high Correct problem if
%sManifold Press low Manifold pressure dropped below Correct problem if
%sManifold Press high Manifold pressure exceeded high Correct problem if
PNT1-866 PAUS %sCalibration
alarm level. immediately, or adjust the
PNT1-867 WARN successful The calibration was successful. None.
Determine cause for
PNT1-868 WARN %sCalibration aborted Calibration aborted. calibration to abort and
Calibration aborted due to the output Determine the cause for
or manifold pressure failing to increase the pressure not
PNT1-869 WARN %sNon-incr cal table as the command rate increased. increasing, and correct
The calibration aborted due to zero Determine the cause for
output or manifold pressure was the zero pressure, and
PNT1-870 WARN %sZero Pressure
%sBad preset index detected
The presetafter a flow
index is outcommand was
of range (1-correct the problem.
Check Preset[] index and
PNT1-875 WARN [%d] MAX_PRESET(20)). Preset[R[]] index value
%sNo preset data No preset data for error color was Check [PAPS1] or ([PAPS2]
PNT1-876 WARN (syscolor=[%s])
%sNo estat data found. if Dualarm)
Check preset_data
[PAPSSCHG]
PNT1-877 WARN %sBad
(syscolor=[%s])
preset index No estat
The data
preset for iserror
index out color was(1-
of range found.
preset_data
Check Preset[]forindex
tableand
PNT1-882 WARN [%d] MAX_PRESET(20)). Preset[R[]] index value
PNT1-883 WARN %sNo
(syscolor=[%s])
estat data found. if Dualarm)
Check preset_data
[PAPSSCHG]
PNT1-884 WARN (syscolor=[%s]) No estat data for error color was found. preset_data for table
The wrong valve state was To correct the problem,
programmed in the color change cycle. ensure that the pDump
Wrong valve state in The valve interlocking requirements valve OR pPE + pTRIG
PNT1-889 WARN EMPTY CAN event-%s have not been satisfied for the Empty valves are in the step
programmed in the color change cycle. ensure that the pCI valve
Wrong valve state in The valve interlocking requirements is enabled in the step
PNT1-890 WARN FAST FILL event-%s have not been satisfied for the Fast Fillbefore the Fast Fill event.
PNT1-891 WARN CAN FULL event-%s have not been satisfied for the Can Full before the Can Full event.
The wrong valve state was Ensure that the pCI valve
programmed in the color change cycle. is enabled in the same
The valve interlocking requirements step as the preset
Wrong valve state in have not been satisfied for a preset instruction if retracting
PNT1-892 WARN PRESET motion-%s motion instruction. the canister. Ensure that
An attempt was made to retract the Ensure that the correct CC
canister, but the valve state was control valves are in the
Canister Dir - retracting: incorrect. This could have been during proper state. The pCI
PNT1-893 WARN %s a fill cycle or other commanded motion valve should be ON.
A fill cycle was just completed, but the Increase the Minimum Fill
Low can Pressure after fluid pressure in the can was found to Torque in the setup
PNT1-894 WARN Fill: %s be lower than the minimum expected. screen, or ensure that the
An attempt was made to extend the Ensure that the correct CC
canister but the state of the valves control valves are in the
Canister Dir - extending: were incorrect. This could have been proper state. The pDump
PNT1-895 WARN %s
Zero Flow Programmed: during
Zero Flowa cleanout cycle or other
was programmed valve
Ensureshould
in the color that abe ON,rate
flow or the
is
PNT1-896 WARN %s change. set up in the CC preset
Ensure that the canister
speed is not too fast when
spraying the job. Ensure
that the pTrig and pCE
The maximum compression force on valves are open during job
the ball screw has been exceeded. execution. Ensure that the
%sHIGH Negative When this occurs, it is usually when the injector tip is not clogged.
PNT1-897 PAUS Canister TORQUE ball screw is extending. The nozzle tip tapers to a
The maximum tensile force on the ball Ensure that the retraction
screw has been exceeded. When this speed is not too fast
occurs, it s usually when the ball screw
during the fast fill cycle.
%sHIGH Positive is retracting. There might be a vacuum Ensure that the pCI and
PNT1-898 PAUS Canister TORQUE in the canister which is causing pCC valves are open
The piston was retracted from the fluidCheck the paint supply for
after the Fill sequence and torque was the current color in the
still detected on the face of the piston.
canister to verify air is not
%sAir in Canister The torque should not exist if the being introduced into the
PNT1-899 PAUS detected canister is completely full of paint, paint supply.
The torque threshold on the canister Perform the following: 1.
motor did not reach the minimum Check the paint supply for
torque threshold value during the fill the current color in the
PNT1-900 WARN %sLow Trigger Torque through trigger step of the fill or refill
canister. 2. Reduce the
programmed in the color change cycle. ensure that the pDump
Wrong valve state in The valve interlocking requirements valve OR pPE + pTRIG
PNT1-901 WARN EMPTY CAN event%s have not been satified for the Empty valves are in the step
PNT1-902 WARN FAST FILL event%s have not been satified for the Fast Fill
before the Fast Fill event.
PNT1-903 WARN CAN FULL event%s have not been satified for the Can Fullbefore the Can Full event.
Wrong valve state in have not been satified for a preset instruction if retracting
PNT1-904 WARN PRESET motion%s motion instruction. the canister. Ensure that
canister but the valve state was control valves are in the
Canister Dir - retracting: incorrect. This could have been during proper state. The pCI
PNT1-905 WARN %s a fill cycle or other commanded motion valve should be ON.
A fill cycle was just completed, but the
Increase the Minimum Fill
PNT1-906 WARN Fill: %s be lower than the minimum expected. screen, or ensure that the
PNT1-907 WARN %s during a cleanout cycle or other valve should be ON or the
Zero Flow Programmed: Zero Flow was programmed in the color Ensure that a flow rate is
PNT1-908 WARN %s change preset data. set up in the color change
%sHIGH Negative When this occurs, its usually when the injector tip is not clogged.
PNT1-909 PAUS Canister TORQUE ball screw is extending. The nozzle tip tapers to a
occurs, its usually when the ball screw
during the fast fill cycle.
%sHIGH Positive is retracting. There might be a vacuumEnsure that the pCI and
PNT1-910 PAUS Canister TORQUE in the canister which is causing pCC valves are open
The piston was retracted from the fluid
Check the paint supply for
after the Fill sequence and torque wasthe current color in the
still detected on the face of the piston.
canister to verify that air
%sAir in Canister The torque should not exist if the is not being introduced
PNT1-911 PAUS detected canister is completely full of paint, into the paint supply.
The torque threshold on the canister Perform the following: 1.
motor did not reach the minimum Check the paint supply for
torque threshold value during the fillthe current color in the
PNT1-912 WARN %sLow Trigger Torque through trigger step of the fill or refill
canister. 2. Reduce the
Verify the robot program
calling the macro does not
identify itself in the macro
argument. Make sure
%sIllegal macro The macro argument selected an arguements are in the
PNT1-913 argument invalid arm ID. following list: Robots:
%sMacro waiting for The robot program is waiting for Cancel the robot and send
PNT1-914 aborted robot program on another robot that is it home.
%sMacro not The previous macro was not Change the teach pendant
PNT1-915 acknowledged acknowledged. program so that this waits
argument. Make sure
%sIllegal macro The macro argument selected an arguements are in the
%Check if SERVOTOOL A TP process/job is missing the After Servo Tool is
PNT1-921 END instr. exists instruction to disable Servo Tool for the enabled, ensure to disable
Determine the cause for
the Hook to lose the part.
Determine if the TP
program needs to disable
The Hood/Deck opener lost the part Part Monitoring prior to
%sHood/Deck Opener while Part Monitoring was enabled, this location. If the
PNT1-922 Lost Part Part Sensing causing the robot to fault.
%sTorque programming
Enable from the is correct,
Opener
PNT1-923 Disabled Torque Part Sensing is Disabled. Setup screen.
Determine if the TP
PNT1-927 Lost Part Part Sensing causing the robot to fault.
%sTorque programming
Opener
%sDoor held input 1 The door held input was lost during possible. If the job can still
PNT1-931 lost part held scanning. be continued activate
%sDoor detect 1 sensor The door held sensor was damaged or it. If the job can still be
PNT1-933 malfunction is malfunctioning continued activate ignore
Ensure the job orientation
%sToo much rotation The vision system detected the job is not detected beyond
PNT1-943 on JOB rotated beyond the specified condition. the specified condition or
Possible sources include:
%sEstat over uA While operating in Voltage mode, the dirty applicator covering,
PNT1-949 warning current draw is within 10% of the limit. a line not blown out
%sEstat over KV The actual Voltage is within 10% of the dirty applicator covering,
PNT1-950 warning internal safety limit. a line not blown out
While operating in current mode, the Possible sources include:
%sEstat under KV load is so great that the voltage is dirty applicator covering,
PNT1-951 warning within 110% of the low threshold. a line not blown out
A serious internal fault has occurred, or Verify the voltage was not
PNT1-955 %sEstat H/W fault the High Voltage was enabled while a enabled during a fault or
One of the parameters was sent to the Review the process setup
PNT1-956 %sEstat comm. fault power supply out of the expected and verify parameters are
applicator draws so much current that dirty applicator covering,
PNT1-957 %sEstat low KV fault the power supply was not able to attain a line not blown out
While operating in Voltage mode with Possible sources include:
DX/DT enabled, the rate of voltage rise dirty applicator covering,
PNT1-958 %sEstat DV/DT fault over time exceeded the DV/DT a line not blown out
DX/DT enabled, the rate of current rise dirty applicator covering,
PNT1-959 %sEstat DI/DT fault over time exceeded the DI/DT setpoint. a line not blown out
%sEstat min. output Either Voltage or Current feedback has Check cable(s) between
PNT1-960 fault been detected with the minimum the power supply and
Either Voltage or Current feedback was Check cable(s) between
%sEstat max. output not able to reach the setpoint before the power supply and
PNT1-961 fault reaching the maximum output of the cascade, replace the
The KV feedback from the cascade has Review the aplication to
PNT1-962 %sEstat over KV fault exceeded the internal safety limit or verify the limit is set
PNT1-963 %sEstat over uA fault exceeded the parameter uA limit. verify the limit is set
Either a short circuit or open circuit has Check the cable(s) from
been detected with the voltage or the power supply to the
PNT1-964 %sEstat cable fault current feedbcak circuit from the cascade to verify
%sEstat Over uA While operating in Voltage mode, the dirty applicator covering,
%sEstat Over KV The actual Voltage is within 10% of the dirty applicator covering,
%sEstat Under KV load is so great that the voltage is dirty applicator covering,
PNT1-980 %sEstat cable fault current feedbcak circuit from the cascade to verify
%sEstat Abn. of primary Please refer to the documentation Please refer to the
PNT1-981 over voltage specific to your Electrostatic High documentation specific to
PNT1-982 over current specific to your Electrostatic High documentation specific to
PNT1-983 cur. discontact specific to your Electrostatic High documentation specific to
%sEstat Abn. of Please refer to the documentation Please refer to the
PNT1-984 secondary cur. specific to your Electrostatic High documentation specific to
%sEstat OL upper limit Please refer to the documentation Please refer to the
PNT1-985 error specific to your Electrostatic High documentation specific to
%sEstat OL primary Please refer to the documentation Please refer to the
PNT1-986 setup error specific to your Electrostatic High documentation specific to
Please refer to the documentation Please refer to the
PNT1-987 %sEstat di/dt error specific to your Electrostatic High documentation specific to
Electrostatics was attempted to be Do not attempt to turn on
%sEstat HV ON not at turned on when not at the De-dock Electrostatics except
PNT1-988 DEDOCK! position. when at the Dedock
PNT1-989 over voltage specific to your Electrostatic High documentation specific to
PNT1-990 over current specific to your Electrostatic High documentation specific to
PNT1-991 cur. discontact specific to your Electrostatic High documentation specific to
%sEstat Abn. of Please refer to the documentation Please refer to the
PNT1-992 secondary cur. specific to your Electrostatic High documentation specific to
%sEstat OL upper limit Please refer to the documentation Please refer to the
PNT1-993 error specific to your Electrostatic High documentation specific to
%sEstat OL primary Please refer to the documentation Please refer to the
PNT1-994 setup error specific to your Electrostatic High documentation specific to
Please refer to the documentation Please refer to the
PNT1-995 %sEstat di/dt error specific to your Electrostatic High documentation specific to
Electrostatics was attempted to be Do not attempt to turn on
%sEstat HV ON not at turned on when not at the De-dock Electrostatics except
PNT1-996 DEDOCK! position. when at the
Turn on the robot
Dedocknot
PNT2-001 %sRobot failed
%sSHELL is bypassed
PNT2-002 SUBSHELL The subtask failed to run. Cold start the controller.
PNT2-003 %sE-STAT unit faulted Detected a E-STAT unit fault. Clear E-STAT unit fault.
PNT2-004 on prod_entry position on production entry is None required.
PNT2-005 presets the presets for the job could not be where XXXX is a number
PNT2-006 data file could not be found. number. This file is
PNT2-007 %s not calibrated
to continue before it The
the robot parameters
current used
cycle within
must be
PNT2-008 robot task motion task has failed. aborted.
PNT2-009 task task has failed. The robot motion task aborted.
PNT2-010 task might not have been running at the None required.
PNT2-011 faulted to run robot
%sFailed detected
An attemptbytotherun
main
thetask.
PNT2-012 task task has failed.
An invalid job number was received aborted.
PNT2-013 job received
%sInvalid tutone from
An the PLC.
invalid tutone option was received PLC validmust
job number.
init robot with a
PNT2-014 received
An the PLC.
PLC tutone
initoption.
robot with a
PNT2-015 received from the PLC. valid repair option.
An invalid color number was received PLC must init robot with a
PNT2-018 %sGhost Job Begin is a Ghost Job indicating PLC has
The robot received a restart job from The cell controller cannot
Job cannot restart, no the cell controller without a valid part restart a new job
PNT2-019 detect! detect! program,
Turn on thea restart is only
robot not
PNT2-020 %sRobot failed
%sSHELL is bypassed
current used
cycle within
must be
%sFailed detected
main
thetask.
An the PLC.
job number.
init robot with a
PNT2-033 received
%sInvalid repair from the PLC.
An invalid repair option was received valid
PLC must initoption.
tutone robot with a
An the PLC.
repair
initoption.
robot with a
%sJob cannot restart, the cell controller without a valid part restart a new job
PNT2-038 no detect! detect! program,
Turn a restart
on the is only
robot not
PNT2-039 %sRobot is bypassed
%sSHELL failed to run The robot not bypassed input is OFF. bypassed input.
PNT2-045 %s not calibrated parameter must be complete before it parameters used within
%sFailed to continue An attempt to continue the robot The current cycle must be
PNT2-049 faulted
main
thetask.
PNT2-050 task taskinvalid
An has failed.
PNT2-051 job received An
%sInvalid tutone from the PLC.
invalid tutone option was received validmust
PLC job number.
init robot with a
PNT2-052 received
%sInvalid repair from the PLC.
An invalid repair option was received valid
PLC must initoption.
tutone robot with a
An the PLC.
invalid color number was received validmust
PLC repair
initoption.
robot with a
PNT2-057 detect! detect! program,
Turn a restart
on the is only
robot not
PNT2-058 %sRobot is bypassed
%sSHELL failed to run The robot not bypassed input is OFF. bypassed input.
current used
cycle within
must be
%sFailed detected
main
thetask.
An the PLC.
job number.
init robot with a
PNT2-071 received
An the PLC.
PLC tutone
initoption.
robot with a
PNT2-072 received from the PLC. valid repair option.
An invalid color number was received PLC must init robot with a
PNT2-076 detect! program is
%sHome detect!
The robot home program has not been program,
Teach thearobot
restart is only
home
PNT2-077 undefined
Teach the(HOME.TP).
robot cleanin
PNT2-078 program is undefined been taught.
%sExit cleaner program The robot cleanout program has not program (CLNIN.TP).
PNT2-079 is undefined
The taught.
robot bypass
PNT2-080 undefinedprogram is
%sPurge beenrobot
The taught.
purge program has not been program
Teach the(BYPASS.TP).
robot purge
PNT2-081 undefined
%sMaster program is taught.
The robot master program has not program (PURGE.TP).
Teach the robot master
PNT2-082 undefined1 program is The
%sSpecial beenrobot
taught.
robot special1
PNT2-083 undefined been taught.
%sSpecial 2 program is The robot special2 program has not program (SPECIAL1.TP).
PNT2-084 undefinednot at home been taught.
%sRobot program
robot to the
PNT2-085 position The robot is not at the Home position. Home position.
PNT2-086 position The robot is positioned at the cleaner. cleanout move before
PNT2-087 position
maintenance
PNT2-088 program
%sExit is undefined Robot
Maintenance taught.maintenance out program is not in program
maintenance
PNT2-089 program is undefined taught. out program
PNT2-090 maintenance position maintenance. maintenance position
Set clear the PLC.
using
%sHome Not Set
program is Clearrobot
The path home
error recovery
program path notbeen
has not set. SetClearPath
Teach macro.
the robot home
PNT2-095 undefined
Teach the(HOME.TP).
robot cleanin
PNT2-096 program is undefined been taught.
%sExit cleaner program The robot cleanout program has not program (CLNIN.TP).
The taught.
robot bypass
PNT2-098 undefined
PNT2-099 undefined program is
%sMaster taught.
robot master
%sSpecial beenrobot
taught.
robot special1
PNT2-101 undefined been taught.
%sSpecial 2 program is The robot special2 program has not program (SPECIAL1.TP).
PNT2-102 undefinednot at home been taught.
%sRobot program
robot to the
PNT2-105 position
maintenance
PNT2-106 program
%sExit is undefined Robot
Maintenance taught.maintenance out program is not in program
maintenance
Set clear the PLC.
using
%sHome Not Set
The path home
error recovery
Teach macro.
the robot home
PNT2-113 undefined
The robot cleanin program has not program (HOME.TP).
Teach the robot cleanin
PNT2-114 program
%sExit is undefined
cleaner beenrobot
program The taught.
cleanout program has not program
Teach the(CLNIN.TP).
robot cleanout
The taught.
robot bypass
PNT2-116 undefined
PNT2-117 undefined program is
%sMaster taught.
robot master
%sSpecial beenrobot
taught.
robot special1
PNT2-119 undefined been taught. program (SPECIAL1.TP).
%sSpecial 2 program is The robot special2 program has not Teach the robot special2
PNT2-120 undefined
%sRobot not at home been taught. program
robot to the
PNT2-123 position Maintenance
%sEnter cleaner.
Robot maintenance in program is not cleanerrobot
Teach position before a
maintenance
PNT2-124 program is undefined
%sExit Maintenance taught.
Robot maintenance out program is not in program (MNTIN.TP).
Teach robot maintenance
Set clear the PLC.
using
%sHome Not Set
The path home
error recovery
Teach macro.
the robot home
PNT2-131 undefined
Teach the(HOME.TP).
robot cleanin
PNT2-132 program is undefined
%sExit cleaner program been taught.
The robot cleanout program has not program (CLNIN.TP).
The taught.
robot bypass
PNT2-134 undefined
%sPurge program is beenrobot
The taught.
purge program has not been program
Teach the(BYPASS.TP).
robot purge
PNT2-135 undefined
%sMaster program is taught.
The robot master program has not program (PURGE.TP).
Teach the robot master
PNT2-136 undefined
%sSpecial 1 program is beenrobot
The taught.
robot special1
PNT2-137 undefined
%sSpecial 2 program is been taught.
The robot special2 program has not program (SPECIAL1.TP).
PNT2-138 undefined
%sRobot not at home been taught. program
robot to the
PNT2-141 position
maintenance
PNT2-142 program
%sExit is undefined
Robot in program
maintenance
Set clear the PLC.
using
PNT2-148 %sClear Path Not Set Clear path error recovery path not set. SetClearPath macro.
PNT2-149 OFF When this input is off, the GUN trigger None required.
PNT2-150 ON applicator valve enable input turns on. None required.
PNT2-155 OFF When this input is off, the GUN trigger None required.
PNT2-156 ON applicator valve enable input turns on. None required.
PNT2-161 time for job might have something wrong with their for every process in the
PNT2-162 job is equal to zero. No Preset Gun On Time job or allow it to correct
%s TPR Mismatch PGOT robot will not have the proper amount this alarm, then press
PNT2-163 Required of paint to run the job. RESET and continue the
PNT2-164 Volume adaptive fill tolerance might attempt to if it is larger than 1550
%sTPR Mismatch PGOT robot will not have the proper amount this alarm, then press
PNT2-193 outputs are ON are initiated by the PLC. None required.
PNT2-194 outputs are OFF terminated by the PLC. None required.
PNT2-199 outputs are ON are initiated by the PLC. None required.
PNT2-200 outputs are OFF terminated by the PLC. None required.
PNT2-205 window OTHERWISE YOU COULD INJURE None required.
PNT2-206 window a warning that the part has entered the None required.
PNT2-229 %sRobot not calibrated motion itself can be executed before Calibrate the robot.
PNT2-249 argument instruction was encountered with an and verify that all
PNT2-250 %sInvalid gun selection instruction is outside of the range SELECT argument to be
PNT2-251 instruction execution. This may happen if the instruction.
PNT2-252 %sCan't set output Option is not loaded. Instruction Option inorder
PNT2-253 position changes in the gun outputs. Note that if appropriate position.
PNT2-258 argument instruction was encountered with an and verify that all
PNT2-259 %sInvalid gun selection instruction is outside of the range SELECT argument to be
PNT2-260 instruction execution. This may happen if the instruction.
PNT2-261 %sCan't set output Option is not loaded. Instruction Option in
PNT2-262 position changes in the gun outputs. Note that if appropriate position.
PNT2-267 %s not defined executed. There are no steps defined and the next color. The
PNT2-268 cancelled was aborted by an E-STOP. The paint automatically do a
%sIllegal manual cycle was sent by the PLC. Cycle numbers 1- sending a lega lcolor
PNT2-269 received 8, and 21, 22, and 23 are legal cycle change cycle number.
PNT2-270 %sColor cycle aborted A color change cycle was cancelled by production mode, the
Purge Solvent output are not allowed enable and Purge
%sColor Valve + PrgSol to be ON at the same time. If the color Solventoutputs are never
PNT2-271 both ON change cycles attempt to do this, ON at the same time.
PNT2-272 cycle data cycle is executed, the color changecycle Status message only.
PNT2-273 not defined The color valve selected has no data using the SETUP menus
%sApplication enable is application enable input turns OFF.
PNT2-274 OFF When this input is OFF, the GUN and Status message only.
PNT2-275 cycle number normal PaintTool operation. personnel.
PNT2-276 locked at T. P. also performing manual operations at pendant. Then try again.
PNT2-277 locked at CRT. also performing manual operations at try again.
%sColor Valve + PrgAir ON at the same time. If the color outputs are never ON at
PNT2-278 both ON change cycles attempt to do this, the same time.
PNT2-279 to be home robot to be at the home position home position.
%sCC automatic cycles For integral color change systems only:
PNT2-280 executing Indication of color change task Status message only.
During the manual I/O testing of color Don't attempt to turn ON
%sColorEnb + PrgSol change I/O the color enable output and the outputs at the same
PNT2-281 both ON Purge Solvent output are not allowed time.
PNT2-282 both ON the Purge Air output are not allowed to time.
PNT2-284 valve the current valve. The wrong system system color setup
%sApplication enable is application enable input turns ON.
PNT2-285 ON When this input is ON, the GUN and Status message only.
PNT2-286 %sInvalidSolvent
%sPurge Solv/Air+State
Air made without
Purge enabling
downstream
Valves IWPColor
Fix or BWP enabled
Change Cycle
PNT2-287 Both ON Both ON Data or Try Again
%sMore Than One
PNT2-288 Color Valve ON Multiple Color Valves ON Not Allowed
for the current color change step did Check the Color Change
PNT2-289 %sCC Event Timeout! not complete in the allocated time. Event requests!
%sCC Cycle does not The Color Change Cycle programmed The last Color Change
PNT2-290 end @ HOME! does not send the robot to the HOME Cycle must send the robot
PNT2-298 %s not defined executed. There are no steps defined and the next color. The
PNT2-299 cancelled was aborted by an E-STOP. The paint automatically do a
PNT2-300 received 8, and 21, 22, and 23 are legal cycle change cycle number.
PNT2-301 %sColor cycle aborted A color change cycle was cancelled by production mode, the
%sColor Valve + PrgSol to be ON at the same time. If the color outputs are never ON at
PNT2-302 both ON change cycles attempt to do this, the the same time.
PNT2-303 cycle data cycle is executed, the color changecycle Status message only.
%sApplication enable is application enable input turns OFF.
PNT2-305 OFF When this input is OFF, the GUN and Status message only.
PNT2-306 cycle number normal PaintTool operation. personnel.
PNT2-307 locked at T. P. also performing manual operations at pendant. Then try again.
PNT2-308 locked at CRT. also performing manual operations at try again.
%sColor Valve + PrgAir ON at the same time. If the color outputs are never ON at
PNT2-309 both ON change cycles attempt to do this, the the same time.
PNT2-310 to be home robot to be at the home position home position.
%sCC automatic cycles For integral color change systems only:
PNT2-311 executing Indication of color change task Status message only.
%sColorEnb + PrgSol change I/O the color enable output and the outputs at the same
PNT2-312 both ON Purge Solvent output are not allowed time.
PNT2-313 both ON the Purge Air output are not allowed to time.
PNT2-315 valve the current valve. The wrong system system color setup
%sApplication enable is application enable input turns ON.
PNT2-316 ON When this input is ON, the GUN and Status message only.
PNT2-317 %sInvalidSolvent
%sPurge Solv/Air+State made without
Air Purge enabling
downstream
Valves IWPColor
Fix or BWP enabled
Change Cycle
PNT2-318 Both ON Than One
PNT2-319 Color Valve ON Multiple Color Valves ON Not Allowed
for the current color change step did
Check the Color Change
PNT2-320 %sCC Event Timeout! not complete in the allocated time. Event requests!
%sCC Cycle does not The Color Change Cycle programmed The last Color Change
PNT2-321 end @ HOME! does not send the robot to the HOME Cycle must send the robot
PNT2-322 failed! be opened to run the pump. are programmed
Establish cause ofon. If
timeout. Verify canister
position feedback
The canister position counts did not operating properly.
reach the fill counts before the Color Feedback can be verified
Change Timeout expired. If this occurs by checking the analog
during a Scale Calibration, then the can input (AIN[1, DISP]). Check
was not filled before the Scale Cal Step paint supply system.
Time expired. This condition can exist Check color change valve
from no paint entering the can or a loss operation. Check the color
of canister position feedback from the valve, if it is a color
linear potentiometer. The Color Change change fault or the dock
Timeout needs to be increased. The Full solvent if this occurs
%s abort, can fill Can counts have not been properly during a scale calibration.
PNT2-329 timeout calculated. Increase the Color Change
Establish cause of
The canister position counts did not timeout. Verify canister
reach the empty canister check counts position feedback
before the Color Change Timeout operating properly.
expired. If this occurs during a Scale Feedback can be verified
Calibration, then the can was not by checking the analog
empty before the Scale Cal StepTime input (AIN[1, DISP]). Check
expired. This condition can exist from color change valve
no paint exiting the can or a loss of operation. Check the
canister position feedback from the dump valve in the case of
linear potentiometer. The Color Change the paint not exiting the
Timeout needs to be increased. The canister. Increase the
%s abort, can empty Empty Can counts have notbeen Color Change Timeout. If
PNT2-330 timeout properly calculated. the gun has been changed
Verify proper TPR was
calculated. Verify the fill is
completing successfully.
job. Make sure all
equipment is operating
%s Canister Out Of properly, such as the
PNT2-331 Paint Canister ran out of paint during the job. trigger orcause
Establish regulator.
of Check
timeout. Verify canister
position feedback
The canister position counts did not operating properly.
reach the fill counts before the Color Feedback can be verified
Change Timeout expired. If this occurs by checking the analog
during a scale calibration, then the can input (AIN[1, DISP]). Check
was notfilled before the Scale Cal Step paint supply system.
Time expired. This condition canexist Check color change valve
from no paint entering the can or a loss operation. Check the color
of canister position feedback from the valve, if it is a color
linear potentiometer. The Color Change change fault or the dock
Timeout needs to be increased. The Full solvent if this occurs
%s abort, can fill Can counts have not been properly during a scale calibration.
PNT2-335 timeout calculated. Increase
Establish the
causeColor
of Change
The canister position counts did not timeout. Verify canister
reach the empty canister check counts position feedback
before the Color Change Timeout operating properly.
expired. If this occurs during a scale Feedback can be verified
calibration, then the can was not by checking the analog
empty before the Scale Cal Step Time input (AIN[1, DISP]). Check
expired. This condition can exist from color change valve
no paint exiting the can or a loss of operation. Check the
canister position feedback from the dump valve in the case of
linear potentiometer. The Color Change the paint not exiting the
Timeout needs to be increased. The canister. Increase the
%s abort, can empty Empty Can counts have notbeen Color Change Timeout. If
PNT2-336 timeout properly calculated. the gun has been changed
Verify proper TPR was
calculated. Verify the fill is
completing successfully.
job. Make sure all
equipment is operating
%s Canister Out Of properly, such as the
PNT2-337 Paint Canister ran out of paint during the job. trigger or regulator. Check
%sCal. table adapted The change was beyond the percentage changed then the color
PNT2-341 out tolerance value setting of the Adaptive tolerance can be calibrated to
PNT2-342 tolerance adapted out of tolerance alarm have None Required
As a particular flow rate set point is In some way decrease the
being output, the yield ((cc/min)/cnt) yield. Use smaller
for that flow rate was larger thanthe restricters in the gun if the
the set point will be reached. This may obtained. Otherwise
CH2:Dyn. yield > be due to the restricters in the gun accept a larger tolerance
PNT2-343 tolerance band (%s) being too large. band. If the value given in
the set point have been too high transducer, replace the
Possible causes are: sticking fluid regulator or service
%sFlow rate average I/Ptransducer, bad fluid regulator the surge suppression
PNT2-344 error high frequent fluid pressure changes or a system on the fluid supply
PNT2-345 successful calibration has completed successfully. No remedy is needed.
The best remedy may be
continue. This may be due to the fluid alarm in the log. This is
PNT2-346 %sCalibration aborted alarms in the log. incorrect setup
During Accuflow calibration the low modifier used for the
PNT2-347 reset low flow rate was established. rate is shown as point 2 in
During Accuflow calibration, the Possibly decrease the Gain
%sCal. max. flow rate be reached at the maximum output. A color. The new maximum
PNT2-348 reset new maximum flow was established. flow rate is shown as
maximum flow rate. Possible causes modifier used for the
are: a high gain, a sticking I/P color. Retry the
%sCal. time out at max. transducer, a bad fluid regulator or calibration. Check and
PNT2-349 flow frequent fluid pressure changes. change the transducer if
loweset flowrate, typically 100 cc/min. modifier used for the
Possible causes are: a high gain, a color. Retry the
%sCal. time out at low sticking I/P transducer, a bad fluid calibration. Check and
PNT2-350 flow regulator or frequent fluid pressure change the transducer
measured. This may be due to no fluid applicator, check: flow
pressure or pilot air pressure. With a meter, flow meter pickup,
very low flow rate the gain may be too Accuflow interface and
high. One of the following items may the 32 point input
be broken: Color Valve, Color select module. Other- wise
%sZero fluid flow rate board, gun trigger, flow meter, flow check the other items
PNT2-351 detected meter pickup, Accuflow interface listed above. If it occurs
expects a lower flow for each decrease and stable flow rate is
PNT2-352 lower flow can be caused by low or pulsing fluid the leveling trys may help.
While measuring hysteresis, time up, or Retry the calibration.
%sTime out during a time down the Accuflow system timed Check that the high flow
PNT2-353 cal. test out. This indicates the high or low flow rate can be reached
fluid pressure may have become too control output) for a
%sMin. output has flow regulator may be stuck open. There Check and replace if
PNT2-354 > setpoint may be a fairly large fluid leak. Note, necessary the fluid
With a maximum control output the Check the gun tip and the
flow rate was measured to be lower whole gun for clogging.
than the setpoint (requested flow). The Check the fluid lines for
gun may be clogging. A fluid or pilot air pinching, especially at
line may be pinched. The fluid pressure places where they flex.
%sMax. output has flow may have become too low. The I/P Check the fluid supply
PNT2-355 < setpoint transducer may be broken. Note, pressure. Check and
PNT2-356 globals command is below the calibrated range output command in the
PNT2-357 above cal. table of the color. within the calibrated
%sSlow fluid flow leak detected when the gun was not turned required, the paint system
PNT2-358 detected on. This may be caused by a loose will continue to function
on. This may be caused by the dump inspected and repaired
%sFast fluid flow leak broken paint line, etc. Note that each repair if necessary the
PNT2-359 detected time the fluid begins to leak fast the dump pilot valve and the
This may be caused by pulsing paint Increase the Minimum set
it occurs on most colors then there may transducer is noisy change
be a small setting of the Minimum set it. If this occurs on specific
%sFailed to reach point (ms) for the specific installation colors, check the surge
PNT2-360 setpoint setup or one of the tolerance band suppression system fluid
%sAccuflow softpart init available during controller power up at Reached, Flow Rate GIN &
PNT2-361 Failed the debug console (smon). flow diag. AOUT. Reload
to be flowing and a zero flow rate was properly triggering. If fluid
measured for longer than the Zero flow was observed to be
timeout parameter. This may be caused flowing, check and
by: a broken applicator trigger ,a loss of possibly replace the fluid
fluid supply pressure, a broken fluid flow meter. Possibly
%s0 fluid flow rate flow meter, a broken cable (to the increase the Zero flow
PNT2-362 timeout flowmeter), or a Zero flow timeout timeout parameter (by
calibration. The flowrate measured at pressure. Check that the
the maximum control and one half of transducer is functioning
the maximum control output was properly and that it is has
the control output range is useable. range, change it if
The system may still function even appropriate. The system
%sMax. flow below mid though this alarm has occurred. This may operate, but
PNT2-363 point may be caused by low fluid pressure, a performance can be
%sCal. table adapted The change was beyond the percentage changed then the color
PNT2-370 out tolerance value setting of the Adaptive tolerance can be calibrated to
%sFlow rate average I/Ptransducer, bad fluid regulator the surge suppression
PNT2-373 error high frequent fluid pressure changes or a system on the fluid supply
lowest flowrate, typically 100 cc/min. modifier used for the
measured. This may be due to no fluid applicator, check: flow
pressure or pilot air pressure. With a meter, flow meter pickup,
very low flow rate the gain may be too Accuflow interfaceand the
high. One of the following items may 32 point input module.
be broken: Color Valve, Color select Other- wise check the
%sZero fluid flow rate board, gun trigger, flow meter, flow other items listed above.
PNT2-380 detected meter pickup, Accuflow interface If it occurs with very low
%sSlow fluid flow leak detected when the gun was not turned required, the paint system
PNT2-387 detected on. This may be caused by a loose will continue to function
on. This may be caused by the dump inspected and repaired
%sFast fluid flow leak broken paint line, etc. Note that each repair if necessary the
PNT2-388 detected time the fluid begins to leak fast the dump pilot valve and the
%sAccuflow softpart init available during controller power up at Reached, Flow Rate GIN &
PNT2-390 Failed the debug console (smon). flow diag. AOUT. Reload
to be flowing and a zero flow rate was properly triggering. If fluid
measured for longer than theZero flow was observed to be
timeout parameter. This may be caused flowing, check and
by: a broken applicator trigger,a loss of possibly replace thefluid
fluid supply pressure, a broken fluid flow meter. Possibly
%s0 fluid flow rate flow meter, a broken cable (to the increase the Zero flow
PNT2-391 timeout flowmeter), or a Zero flow timeout timeout parameter (by
calibration. The flowrate measured at pressure. Check that the
the maximum control and one half of transducer is functioning
the maximum control output was properly and that it is has
the control output range is usable. The range, change it if
system may still function even though appropriate. The system
%sMax. flow below mid this alarm has occurred. This may be may operate, but
PNT2-392 point caused by low fluid pressure, a faulty performance can be
The relationship of the output Check, clean and possibly
command to the flowrate obtained has replace the air cap. Check
or large losses of air supply pressure. immediately clear the
Note that the system continues to close alarm. Increase the
PNT2-399 out,output up requested flow rates even after this parameter to allow larger
being output the yield (slpm/cnt) for yield. Use larger diameter
that flow rate was approximately larger air lines to supply air to
than the percent tolerance. It is not the cap. Use a larger ratio
likely that the set point will be reached booster (2:1 instead of
%sDyn. yield > %% within the specified tolerances. This 1:1) booster (if the system
PNT2-401 tolerance band may be caused by the use of a flow rate can not supply the high
%sFlow rate avg. error I/Ptransducer, bad fluid regulator the surge suppression
PNT2-402 excessive frequent fluid pressure changes or a system on the fluid supply
All of the conditions were set for air to Check, clean and possibly
be flowing and a zero flow rate was replace the air cap. Check
measured. This may be caused by: a that the gun is properly
broken applicator trigger, pinched air triggering. If air
lines, a loss (or near loss) of air supply wasobserved to be
pressure, a broken air flow sensor, a flowing check and possibly
%s0 air flow rate broken cable (to the flow sensor), or a replace the air flow
PNT2-409 detected Trigger delay that is too short. Note, sensor. Check for a
detected when the gun was not turned required, the paint system
%sSlow air flow leak on. This may be caused by a leaking will continue to function
PNT2-416 detected trigger valve, leaking air line, or any properly. The applicator
on. This may be caused by a leaking various air lines should be
PNT2-417 detected line, broken applicator, or any other air immediately.
measured for longer than the Zero flow that the gun is properly
timeout parameter. This may be caused triggering. If air was
by: a clogged air cap, a broken observed to be flowing,
applicator trigger, broken air lines, a check and possibly replace
loss of air supply pressure, a broken air the air flow sensor. Check
%s0 air flow rate flow sensor, a broken cable (to the flow for a broken air line.
PNT2-419 timeout sensor), or a Zero flow timeout value Possibly increase the Zero
measure the equipment delays the learn to Redo and
PNT2-420 failed expected timeout. other AccuAir alarms in
than the percent tolerance. It is not the cap. Use a smaller
likely that the set point will be reached ratio booster. Otherwise
%sDyn. yield > min within the specified tolerances. This accept a larger tolerance
PNT2-421 tolerance band may be caused by the use of a flow rate band. Increase the
command to the flow rate obtained has tight on the gun. Check,
changed significantly since the last clean and possibly replace
calibration. There is now a smaller the air cap. Check for
output required to get the same flow leaks in air lines or at
loose air cap or a significant increase of or breaks in the gun.
air supply pressure Note that the Check for a large increase
%sCal. table adapted generally maintain requested flow rates Recalibrate to
PNT2-422 out, down even after this alarm if there are no immediately clear the
maximum amount of flow occurred transducer is the right
with the command output at only the range, if not replace it.
%sMax. flow is below indicates that there is wrong has the correct ratio,
PNT2-423 midpt. output equipment installed or the equipment typically 1 to 1. If the
to manually zero (tare)
When attempting to automatically zero the air flow meter for this
(tare) the air flow meter the flow channel. With the air lines
PNT2-424 zeroing meter indicate a possible leak. pressure on, if the display
The automatic zero tare routine took Check air sensor
PNT2-425 %sTare timeout too long to complete. calibration. Replace air
The relationship of the output Check, clean and possibly
command to the flow rate obtained has replace the air cap. Check
or large losses of air supply pressure. immediately clear the
Note that the system continues to close alarm. Increase the
PNT2-429 out,output up requested flow rates even after this parameter to allow larger
than the percent tolerance. It is not the cap. Use a larger ratio
likely that the set point will be reached booster (2:1 instead of
%sDyn. yield > %% within the specified tolerances. This 1:1) booster (if the system
PNT2-431 tolerance band may be caused by the useof a flow rate can not supply the high
%sFlow rate avg. error I/Ptransducer, bad fluid regulator the surge suppression
PNT2-432 excessive frequent fluid pressure changes or a system on the fluid supply
measured. This may be caused by: a that the gun is properly
broken applicator trigger, pinched air triggering. If air was
lines, a loss (or near loss) of air supply observed to be flowing
pressure, a broken air flow sensor, a check and possibly replace
%s0 air flow rate broken cable (to the flow sensor), or a the air flow sensor. Check
PNT2-439 detected Trigger delay that is too short. Note, for a pinched air line.
detected when the gun was not turned required, the paint system
%sSlow air flow leak on. This may be caused by a leaking will continue to function
PNT2-446 detected trigger valve, leaking air line, or any properly. The applicator
on. This may be caused by a leaking various air lines should be
PNT2-447 detected line, broken applicator, or any other air immediately.
All of the conditions were set for air Check, clean and possibly
tobe flowing and a zero flow rate was replace the air cap. Check
measured for longer than theZero flow that the gun is properly
timeout parameter. This may be caused triggering. If air was
by: a clogged air cap, a broken observed to be flowing,
applicator trigger, broken air lines, a check and possibly replace
loss of air supply pressure, a broken air the air flow sensor. Check
%s0 air flow rate flow sensor, a broken cable (to the flow for a broken air line.
PNT2-449 timeout sensor), or a Zero flow timeout value Possibly increase the Zero
measure the equipment delays the learn to Redo and
PNT2-450 failed expected timeout. other AccuAir alarms in
than the percent tolerance. It is not the cap. Use a smaller
likely that the set point will be reached ratio booster. Otherwise
%sDyn. yield > min within the specified tolerances. This accept a larger tolerance
PNT2-451 tolerance band may be caused by the use of a flow rate band. Increase the
command to the flowrate obtained has tight on the gun. Check,
changed significantly since the last clean and possibly replace
calibration. There is now a smaller the air cap. Check for
output required to get the same flow leaks in air lines or at
loose air cap or a significant increase of or breaks in the gun.
air supply pressure Note that the Check for a large increase
%sCal. table adapted generally maintain requested flow rates Recalibrate to
PNT2-452 out, down even after this alarm if there are no immediately clear the
maximum amount of flow occurred transducer is the right
with the command output at only the range, if not replace it.
%sMax. flow is below indicates that there is wrong has the correct ratio,
PNT2-453 midpt. output equipment installed or the equipment typcially 1 to 1. If the
to manually zero (tare)
When attempting to automatically zero the air flow meter for this
(tare) the air flow meter the flow channel. With the air lines
PNT2-454 zeroing meter indicate a possible leak. pressure on, if the display
The automatic zero tare routine took Check air sensor
PNT2-455 %sTare timeout
%sEstat controller too long
The to complete.
external E-stat controller detected calibration.
Check Replace
the status air
of the
PNT2-459 warning aThe
warning.
external E-stat controller detected external e-stat controller.
PNT2-460 %sEstat controller fault The
a fault.
Turn e-stat
on the controller.
E-stat
PNT2-461 %sEstatscontroller
%sEstat disabled not The is off.E-stat local/remote switch is set to disconnect
Put or enable
the e-stat controller in
PNT2-462 in remote local mode. remote mode.
PNT2-463 %sEstat HVON Failed e-stat controller, but did not get a external e-stat controller.
%sEstat setpoint not The e-stat controller did not set the set e-stat controller. It may
PNT2-464 reached point reached output in time be having trouble
The estat warning or fault bit was Check ITW Estat
PNT2-465 %sEstat unknown alarm asserted without any fault or warning Controller display for
%sEstat kV present Estat voltage was detected even Check estat unit wiring.
PNT2-466 while HVON=OFF though not being commanded. Replace estat unit.
Check the estat servo
PNT2-467 heartbeat lost!
%sEstat controller estat controller
The external heartbeatdetected
E-stat controller was lost! disconnect
Check and toofmake
the status the
PNT2-472 warning a warning.
The external E-stat controller detected external
Check thee-stat controller.
status of the
PNT2-473 %sEstat controller fault aThe
fault.
E-stat disconnect or enable switch external e-stat
Turn on the E-stat controller.
PNT2-474 %sEstatscontroller
%sEstat disabled not is off.E-stat local/remote switch is set to
The disconnect
Put or enable
the e-stat controller in
PNT2-475 in remote local mode. remote mode.
PNT2-476 %sEstat HVON Failed e-stat controller, but did not get a external e-stat controller.
%sEstat setpoint not The e-stat controller did not set the set e-stat controller. It may
PNT2-477 reached point reached output in time be having trouble
The estat warning or fault bit was Check ITW Estat
PNT2-478 %sEstat unknown alarm asserted without any fault or warning Controller display for
%sEstat kV present Estat voltage was detected even Check estat unit wiring.
PNT2-479 while HVON=OFF though not being commanded. Replace estat unit.
PNT2-480 %sEstat heartbeat lost! lost!. disconnect and to make
%sTurbine Startup Test the turbine is not complete, this test field on the Bell Speed
PNT2-485 Not Complete must be performed before running the SETUP menu to check the
PNT2-486 %sMax. dV/dT detected time has exceeded the maximum dV/dT determine if the feedback
%sMax. output has gun may be clogging. The turbine air or Check the turbine air
PNT2-487 speed < setpoint turbine pilot air line may be pinched. supply pressure. Check
%sRequested speed The requested turbine speed output Adjust the turbine speed
PNT2-488 over valid range command is above the range that is command that is used in
All of the conditions were set for If turbine can be seen
turbine to be spinning and a zero speed spinning, check: speed
was measured for a set time period. sensor interface, speed
This may be due to no turbine air sensor pickup. Otherwise
%sZero turbine speed pressure or pilot air pressure. One of check the other items
PNT2-490 timeout the following items may be broken: the listed above. Possibly
While the turbine was operating the Check and replace the I/P
RPM level was above the Over speed transducer if necessary.
limit . When this error occurs, braking Possibly increase the Over
PNT2-491 %sTurbine over speed will be applied to bring the turbine speed limit value.
Check and replace the I/P
While the turbine was operating and transducer if necessary.
%sTurbine under speed the gun was on or enabled, the RPM Check the supply and pilot
PNT2-492 fault level was below the Under speed limit . air pressures, if either one
While the gun was off or disabled and Check and replace the I/P
the turbine was operating the RPM transducer if necessary.
%sTurbine under speed level was below the Under speed limit, Check the supply and pilot
PNT2-493 warning Manual. air pressures, if either one
%sSpeed avg. error Possible causes are: sticking Check the supply and pilot
PNT2-494 excessive I/Ptransducer, low supply air pressure, air pressures, if either one
The digital input signal indicating the Check the supply pressure
PNT2-495 %sBearing Air NOT OK Bear Air is above the minimum to the Bearing Air or verify
PNT2-496 established the Bell Speed Startup Test could not Startup Test to determine
%sTurbine Startup Test the turbine is not complete, this test field on the Bell Speed
PNT2-502 Not Complete must be performed before running the SETUP menu to check the
PNT2-503 %sMax. dV/dT detected time has exceeded the maximum dV/dT determine if the feedback
%sMax. output has gun may be clogging. The turbine air or Check the turbine air
PNT2-504 speed < setpoint turbine pilot air line may be pinched. supply pressure. Check
%sRequested speed The requested turbine speed output Adjust the turbine speed
PNT2-505 over valid range command is above the range that is command that is used in
All of the conditions were set for If turbine can be seen
turbine to be spinning and a zero speed spinning, check: speed
was measured for a set time period. sensor interface, speed
This may be due to no turbine air sensor pickup. Otherwise
%sZero turbine speed pressure or pilot air pressure. One of check the other items
PNT2-507 timeout the following items may be broken: the listed above. Possibly
While the turbine was operating the Check and replace the I/P
RPM level was above the Over speed transducer if necessary.
limit. When this error occurs, braking Possibly increase the Over
PNT2-508 %sTurbine over speed will be applied to bring the turbine speed limit value.
Check and replace the I/P
While the turbine was operating and transducer if necessary.
%sTurbine under speed the gun was on or enabled, the RPM Check the supply and pilot
PNT2-509 fault level was below the Under speed limit. air pressures, if either one
While the gun was off or disabled and Check and replace the I/P
the turbine was operating the RPM transducer if necessary.
%sTurbine under speed level was below the Under speed limit, Check the supply and pilot
PNT2-510 warning Manual . air pressures, if either one
%sSpeed avg. error Possible causes are: sticking Check the supply and pilot
PNT2-511 excessive I/Ptransducer, low supply air pressure, air pressures, if either one
The digital input signal indicating the Check the supply pressure
PNT2-512 %sBearing Air NOT OK Bear Air is above the minimum to the Bearing Air or verify
PNT2-513 established the
PumpBell#1Speed Startup Test
inlet pressure has could not
been below Startup
Make sureTestthe
to low
determine
the low warning limit for a user pressure warning limit is
configurable period of time. This appropriate. Make sure
more of the following: 1. The low sensitivity is appropriate.
pressure warn limit is set too high. 2. Check the pilot line to
short. 3. The pilot line to resin color used. Verify that the resin
valve is removed or broken. 4. The resin color valve being used is
color valve has failed. 5. The supply not faulty. Make sure the
pressure is too low. 6. The supply line supply pressure is
%sPump 1 IN low (hose, etc. ) is removed or broken. 7. appropriate. Check the
PNT2-519 pressure warning The
Pump resin inlet pressure
#1 inlet transducer
hashas failed.
been 8.
below supply line the
Make sure fromlow
paint
pressure fault limit is set too high. 2. Check the pilot line to
PNT2-520 pressure fault The resin inlet transducer has failed. 8. supply line from paint
Make sure the high
Pump #1 inlet pressure has been above pressure warning limit is
the high warning limit for a user appropriate. Make sure
configurable period of time. This the high pressure
condition is usually caused by one or sensitivity is appropriate.
more of the following: 1. The high Make sure the supply
pressure warn limit is set too low. 2. pressure is appropriate.
The high pressure sensitivity is set too Check the resin inlet
short. 3. The supply pressure is set too transducer as follows:
%sPump 1 IN high high. 4. The resin inlet transducer has Through the Analog I/O
PNT2-521 pressure warning failed. 5. The inlet regulator has failed. menu verify the
more of the following: 1. The high sensitivity is appropriate.
pressure fault limit is set too low. 2. Make sure the supply
The high pressure sensitivity is set too pressure is appropriate.
short. 3. The supply pressure is set too Check the resin inlet
%sPump 1 IN high high. 4. The resin inlet transducer has transducer as follows:
PNT2-522 pressure fault failed. 5. The inlet regulator has failed. Through the Analog I/O
Pump #1 outlet pressure has been Make sure the low
below the low warning limit for a user pressure warning limit is
%sPump 1 OUT low color valve has failed. 5. The supply not faulty. Make sure the
PNT2-523 pressure warning pressure is too low. 6. The supply line supply pressure is
below the low fault limit for a user pressure fault limit is
%sPump 1 OUT low valve is removed or broken. 4. The resin color valve being used is
PNT2-524 pressure fault color valve has failed. 5. The supply not faulty. Make sure the
Pump #1 outlet pressure has been Make sure the high
pressure warn limit is set too low. 2. Make sure the pump
The high pressure sensitivity is set too start/stop anticipates are
short. 3. The pump start/stop appropriate. Make sure
%sPump 1 OUT high anticipates not setup correctly. 4. the lines, trigger or check
PNT2-525 pressure warning Obstructed line, trigger or check valve. valve are not obstructed.
above the high fault limit for a user pressure fault limit is
pressure fault limit is set too low. 2. Make sure the pump
PNT2-526 pressure fault Obstructed line, trigger or check valve. valve are not obstructed.
The actual flow rate out of pump #1 as pump #1 with a beaker
%sPump 1 fluid flow point window (a percentage) for a user pump #1 size (cc/rev).
PNT2-527 rate > set point configurable period of time. Verify that the correct KFT
%sPump 1 fluid flow window (a percentage) for a user pump #1 size (cc/rev).
PNT2-528 rate < set point configurable period of time. Verify that the correct KFT
%sPump 1 zero fluid following: 1. A loose mechanical Make sure the line from
PNT2-529 flow rate detected coupling between the motor and pump to trigger is ok.
PNT2-530 velocity limit operating limit. The motor speed for within the motor limit.
PNT2-531 not ready ready. some reason, such as E-
value that is different than the pump #1 size (cc/rev).
PNT2-532 > tolerance is larger
Pump #2than
inletthe total flow
pressure tolerance.
has been below factor has been
Make sure entered
the low
short. 3. The pilot line to hardener being used. Verify that the
color valve is removed or broken. 4. hardener color valve
The hardener color valve has failed. 5. being used is not faulty.
The supply pressure is too low. 6. The Make sure the supply
%sPump 2 IN low supply line (hose, etc. ) is removed or pressure is appropriate.
PNT2-539 pressure warning broken.
Pump #27.inlet
Thepressure
hardenerhasinlet
been below Check the supply
Make sure the lowline from
PNT2-540 pressure fault broken. 7. The hardener inlet Check the supply line from
pressure warn limit is set too low. 2. Make sure the supply
short. 3. The supply pressure is set too Check the hardener inlet
high. 4. The hardener inlet transducer transducer as follows:
%sPump 2 IN high has failed. 5. The inlet regulator has Through the Analog I/O
PNT2-541 pressure warning failed. menu verify the
%sPump 2 IN high high. 4. The hardener inlet transducer transducer as follows:
PNT2-542 pressure fault has failed. 5. The inlet regulator has Through the Analog I/O
%sPump 2 OUT low The hardener color valve has failed. 5. being used is not faulty.
PNT2-543 pressure warning The supply pressure is too low. 6. The Make sure the supply
PNT2-544 pressure fault The supply pressure is too low. 6. The Make sure the supply
PNT2-552 > tolerance is larger than the total flow tolerance. factor has been entered
After the calibration table has been Verify regulator is working
shifted or a new calibration table properly. Verify fluid
created, a non-increasing table of flow restrictor is suitable for
command values isdetected. Unstable the desired flow rates.
(%s) Non-increasing cal flow rates encountered. Canister Check proper feedback
PNT2-554 table position change is not proportional to fromthe linear
Ensure pumps are
PNT2-555 (%s) Zero PSI points. parameter, 'Max speed
Paint pressure not detected during
calibration. Most likely that color valve Check color valve and
PNT2-556 (%s) Set Color Valve did not come on or supply pressure supply.
%s Res:Hrd ratio is 0. message has a default ratio (0. 0:0. 0) for this color in the Setup
PNT2-557 0:0. 0 defined.
Pump #1TheinletIPC pumpshas
pressure canbeen
only run
below Color
Make Detail menu.
sure the low
PNT2-564 pressure warning The
Pump resin inlet pressure
#1 inlet transducer
hashas failed.
been 8.
below supply line the
Make sure fromlow
paint
PNT2-565 pressure fault The resin inlet transducer has failed. 8. supply line from paint
Make sure the high
Pump #1 inlet pressure has been above pressure warning limit is
the high warning limit for a user appropriate. Make sure
configurable period of time. This the high pressure
condition is usually caused by one or sensitivity is appropriate.
more of the following: 1. The high Make sure the supply
pressure warn limit is set too low. 2. pressure is appropriate.
The high pressure sensitivity is set too Check the resin inlet
short. 3. The supply pressure is set too transducer as follows:
%sPump 1 IN high high. 4. The resin inlet transducer has Through the Analog I/O
PNT2-566 pressure warning failed. 5. The inlet regulator has failed. menu verify the
short. 3. The supply pressure is set too Check the resin inlet
%sPump 1 IN high high. 4. The resin inlet transducer has transducer as follows:
PNT2-567 pressure fault failed. 5. The inlet regulator has failed. Through the Analog I/O
%sPump 1 OUT low color valve has failed. 5. The supply not faulty. Make sure the
PNT2-568 pressure warning pressure is too low. 6. The supply line supply pressure is
%sPump 1 OUT low valve is removed or broken. 4. The resin color valve being used is
PNT2-569 pressure fault color valve has failed. 5. The supply not faulty. Make sure the
PNT2-577 > tolerance is larger
Pump #2than
inletthe total flow
pressure tolerance.
has been below factor has been
Make sure entered
the low
PNT2-584 pressure warning broken. 7. The hardener inlet Check the supply line from
Pump #2 inlet pressure has been below Make sure the low
PNT2-585 pressure fault broken. 7. The hardener inlet Check the supply line from
pressure warn limit is set too low. 2. Make sure the supply
high. 4. The hardener inlet transducer transducer as follows:
%sPump 2 IN high has failed. 5. The inlet regulator has Through the Analog I/O
PNT2-586 pressure warning failed. menu verify the
%sPump 2 IN high high. 4. The hardener inlet transducer transducer as follows:
PNT2-587 pressure fault has failed. 5. The inlet regulator has Through the Analog I/O
PNT2-588 pressure warning The supply pressure is too low. 6. The Make sure the supply
PNT2-589 pressure fault The supply pressure is too low. 6. The Make sure the supply
PNT2-597 > tolerance is larger than the total flow tolerance. factor has been entered
After the calibration table has been Verify regulator is working
shifted or a new calibration table properly. Verify fluid
created, a non-increasing table of flow restrictor is suitable for
command values isdetected. Unstable the desired flow rates.
(%s) Non-increasing cal flow rates encountered. Canister Check proper feedback
PNT2-599 table position change is not proportional to fromthe linear
Ensure pumps are
PNT2-600 (%s) Zero PSI points. parameter, 'Max speed
Paint pressure not detected during
calibration. Most likely that color valve Check color valve and
PNT2-601 (%s) Set Color Valve did not come on or supply pressure supply.
%s Res:Hrd ratio is 0. message has a default ratio (0. 0:0. 0) for this color in the Setup
PNT2-602 0:0. 0 defined. The IPC pumps can only run Color Detail menu.
PNT2-609 TORQUE the maximum safety limit. the high torque reading
%sServoBell motor not The servo power to the ServoBell motor power is turned off for
PNT2-610 ready is not ready. some reason, such as E-
PNT2-611 %sCalibration Aborted The ServoBell auto calibration aborted. trigger is not clogged and
The ServoBell auto calibration aborted Ensure all faults are
due to a time out when the system was cleared. Ensure that the
PNT2-612 %sCalibration
%sCanister Calibration trying
Time Out to determine
The ServoBell the empty can
PNT2-613 Successful completed successfully. None required.
PNT2-614 set_prax_spd status from set_prax_spd was resolve the problem.
%sHIGH SpeedDock Torque value of the SpeedDock Determine the cause of
PNT2-616 not ready motor is not ready. some reason, such as E-
extend sensor at
extend sensor at
PNT2-619 TORQUE the maximum safety limit. the high torque reading
%sServoBell motor not The servo power to the ServoBell motor power is turned off for
PNT2-620 ready is not ready. some reason, such as E-
PNT2-621 %sCalibration Aborted The ServoBell auto calibration aborted. trigger is not clogged and
The ServoBell auto calibration aborted Ensure all faults are
due to a time out when the system was cleared. Ensure that the
PNT2-622 %sCalibration
%sCanister Time Out The
Calibration trying to determine
PNT2-623 Successful completed successfully. None required.
PNT2-624 set_prax_spd status from set_prax_spd was resolve the problem.
%sHIGH SpeedDock Torque value of the SpeedDock Determine the cause of
PNT2-626 not ready motor is not ready. some reason, such as E-
extend sensor at
extend sensor at
PNT2-629 warning warning level. warning occurs
PNT2-633 alarm level. immediately, or adjust the
PNT2-639 %sNon-incr cal table as the command rate increased. and correct accordingly.
PNT2-640 %sZero Pressure or Manifold pressure detected after a zero pressure and correct
PNT2-655 %sNon-incr cal table as the command rate increased. and correct accordingly.
PNT2-656 %sZero Pressure
%sBad preset index or
TheManifold pressure
preset index is outdetected
of rangeafter
(1- a zero
Checkpressure
Preset[]and correct
index
PNT2-661 [%d] MAX_PRESET(20)). andPreset[R[]] index value
PNT2-662 (syscolor=[%s])
Check preset_data
[PAPSSCHG]
%sBad preset index No estat
The data
preset for iserror
index out color was(1-
of range found. preset_data
Check forindex
Preset[] table
PNT2-668 [%d] MAX_PRESET(20)). andPreset[R[]] index value
Check preset_data
[PAPSSCHG]
PNT2-670 (syscolor=[%s]) No estat data for error color was found. preset_data for table
The wrong valve state was Ensure that the pDump
programmed in the color change cycle. valve OR pPE + pTRIG
Wrong valve state in The valve interlocking requirements valves are in the step
PNT2-675 EMPTY CAN event%s haven't beensatified for the Empty Can before the Empty Can
programmed in the color change cycle. is enabled in the step
Wrong valve state in The valve interlocking requirements before the Fast Fill event
PNT2-676 FAST FILL event%s haven't beensatified for the Fast Fill to correct the problem.
Wrong valve state in The valve interlocking requirements before the Can Full event
PNT2-677 CAN FULL event%s haven't beensatified for the Can Full to correct the problem.
Wrong valve state in haven't beensatified for a preset instruction if retracting
PNT2-678 PRESET motion%s motion instruction. the canister. Ensure that
Canister Dir - retracting: incorrect. This could have been during proper state. pCI valve
PNT2-679 %s a fill cycle or other commanded motion should be ON.
PNT2-680 Fill: %s be lower than the minimum expected. screen, or ensure that the
PNT2-681 %s
Zero Flow Programmed: during a cleanout cycle or other valve
Ensureshould
that abe ONrate
flow or the
is
PNT2-682 %s Zero Flow was programmed in CC. setup in the CC preset
PNT2-683 Canister TORQUE ball screw is extending. The nozzle tip tapers to a
occurs, its usually when the ballscrew is during the fast fill cycle.
%sHIGH Positive retracting. There may be a vacuum in Ensure that the pCI and
PNT2-684 Canister TORQUE the canister which is causing excessive pCCvalves are open during
The piston was retracted from the fluid Check the paint supply for
still detected on the face of the piston. canister to verify air in not
%sAir in Canister The torque should not exist if the being introduced into
PNT2-685 detected canister is completely full of paint, paint supply.
The torque threshold on the canister Check the paint supply for
motor did not reach the minimum the current color in the
PNT2-686 %sLow Trigger Torque torque threshold value during the canister or reduce the
The wrong valve state was Ensure that the pDump
programmed in the color change cycle. valve OR pPE + pTRIG
Wrong valve state in The valve interlocking requirements valves are in the step
PNT2-687 EMPTY CAN event%s haven't beensatified for the Empty Can before the Empty Can
Wrong valve state in The valve interlocking requirements before the Fast Fill event
PNT2-688 FAST FILL event%s haven't been satified for the Fast Fill to correct the problem.
Wrong valve state in The valve interlocking requirements before the Can Full event
PNT2-689 CAN FULL event%s haven't beensatified for the Can Full to correct the problem.
Wrong valve state in haven't beensatified for a preset instruction if retracting
PNT2-690 PRESET motion%s motion instruction. the canister. Ensure that
Canister Dir - retracting: incorrect. This could have been during proper state. pCI valve
PNT2-691 %s a fill cycle or other commanded motion should be ON.
PNT2-692 Fill: %s be lower than the minimum expected. screen, or ensure that the
PNT2-693 %s Flow Programmed:
Zero during a cleanout cycle or other valve should
Ensure that abe ONrate
flow or the
is
PNT2-694 %s Zero Flow was programmed in CC. setup in the CC preset
PNT2-695 Canister TORQUE ball screw is extending. The nozzle tip tapers to a
occurs, its usually when the ball screw during the fast fill cycle.
%sHIGH Positive is retracting. There may be a vacuum in Ensure that the pCI and
PNT2-696 Canister TORQUE the canister which is causing excessive pCCvalves are open during
The piston was retracted from the fluid Check the paint supply for
still detected on the face of the piston. canister to verify air in not
%sAir in Canister The torque should not exist if the being introduced into
PNT2-697 detected canister is completely full of paint, paint supply.
The torque threshold on the canister Check the paint supply for
motor did not reach the minimum the current color in the
PNT2-698 %sLow Trigger Torque torque threshold value during the fill canister or reduce the
argument. Make sure
%sIllegal macro The macro argument selected an arguments are in the
argument. Make sure
argument. Make sure
argument. Make sure
Determine if the TP
PNT2-716 Lost PartPart Sensing
Torque causing the robot to fault. programming
Opener
Determine if the TP
PNT2-721 Lost PartPart Sensing
Torque causing the robot to fault. programming
Opener
Determine if the TP
PNT2-726 Lost Part causing the robot to fault. programming is correct,
Determine if the TP
PNT2-731 Lost Part causing the robot to fault. programming is correct,
PNT2-778 %sEstat comm. fault power supply out ofthe expected and verify parameters are
PNT2-786 %sEstat cable fault current feedbcak circuit from the cascade toverify insulation
The KV feedback from the cascade has Review the application to
exceeded the internal safety limit or verify the limit is set
PNT2-800 %sEstat over KV fault the parameter KV limit. correctly. Clean applicator
Review the application to
The KV feedback from the cascade has verify the limit is set
PNT2-801 %sEstat over uA fault exceeded the parameter uA limit. correctly. Clean applicator
PNT2-802 %sEstat cable fault current feedback circuit from the cascade to verify
The port type code specified is invalid.
This error code can be returned by
several of the Digital I/O-related Use one the port types
PRIO-001 WARN Illegal port type code builtins (e.g., SET_PORT_ASG) when an defined in IOSETUP.KL.
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] =
PRIO-002 WARN Illegal port number Off and calls to the SET_PORT_SIM Correct the port number.
SYSTE Memory required for this operation is Delete unneeded KAREL
PRIO-003 M No memory available not available. programs and/or variables
There are not enough ports on the Correct either the first
Too few ports on specified board or module to make the port number or the
PRIO-004 WARN module specified assignments. This error code number of ports.
The specified port number in an Correct the port number
PRIO-005 WARN bad port number assignment is invalid. Port numbers so that it is within the
The specified port number in an Correct the port number
assignment (e.g., DIN[1] = ON) is so that it is within the
PRIO-006 WARN bad port number invalid. The port number must be in the valid range.
This error code is returned by the
No match in KAREL built-in SET_PORT_ASG when it
SET_PORT_ASG de- is used as ade-assign request (with a
PRIO-007 WARN assign physical port type of zero) and the Correct the port number.
physical ports not The physical port to which ports are Correct the rack number,
PRIO-008 WARN found being assigned in a SET_PORT_ASSIGN slot number, port type, or
The number of ports in a
SET_PORT_ASG call is invalid. This must Correct the number of
be in the range of 1 - 128 for digital ports, so that it is within
PRIO-009 WARN number of ports invalid port types (e.g., DIN), 1-16 for groups, the valid range.
An invalid physical port number is Correct the physical port
bad physical port specified in a call to the KAREL built-in number, so that it is
PRIO-010 WARN number SET_PORT_ASG. This must be greater greater than 0.
Correct the first port
number or number of
Assignment overlaps The port numbers in a SET_PORT_ASG ports or delete existing
PRIO-011 WARN existing one call overlap existing assignments. assignment using the
The rack and/or slot number specified
in a call of the KAREL built-in Correct the rack and/or
PRIO-012 WARN Bad board address SET_PORT_ASG is invalid or refers to an slot number.
No analog input An attempt was made to delete an Check the rack and/or slot
PRIO-013 WARN sequence for bd analog input sequence that has not number and that an
Analog input sequnce The specified analog input sequence is Supply a sequence of an
PRIO-014 WARN too long too long; sequences must have from 1 appropriate length.
PRIO-015 WARN unknown module type
PRIO-016 WARN log port already asgnd
Attempt to set the state of an input Use the I/O menu or the
PRIO-017 WARN
SYSTE I/O point not simulated port that is not simulated. SET_PORT_SIM KAREL
PRIO-018 M
SYSTE io system error
PRIO-019 M Module ID not expected
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
Indicates that an error has been numbers displayed in this
detected in communication between error message. The first
the MAIN CPU PCB and the process I/O value must be interpreted
board, Model-A I/O racks, or Model-B bit-wise. If a bit is 1, the
I/O interface units. The most common corresponding condition
causes of this are the following: o has been detected: Bit 0:
Power to a remote I/O rack or Model-B (CFER) A CRC or framing
I/O interface unit is interrupted. o The error has been detected
cable between the MAIN CPU PCB and by the SLC-2 chip on the
the process I/O board, racks, or Model- MAIN CPU PBC. This is
B interface units has been disconnected most frequently the result
or is faulty. o Electrical interference of the problems listed
between the I/O cables and other above. Otherwise, it might
cables. This can be eliminated by indicate faulty SLC-2 chip,
physically separating the I/O cables wiring between this and
from other wiring. In very electrically the JB-1B connector on
noisy environments, it might be the main PCB, or faulty
PAUSE. I/O Link comm error necessary to use optical isolators with process I/O, model-A I/O
PRIO-020 G %x, %x, %x, %x (hex) these cables. rack, or model-B interface
An unknown device is connected to the Replace the device with a
SYSTE I/O Link connector. This device is not device that is compatible
PRIO-021 M Unknown I/O hardware recognized by the current controller with the current software
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
SYSTE Too much I/O data on typically use 16 bytes of input and 16
PRIO-022 M I/O link bytes of output each. Digital modules Disconnect some devices.
There are no ports of the type (e.g., Change the port type, add
GIN) specified in an I/O statement or I/O hardware with the
PRIO-023 WARN No ports of this type built-in call. required type of ports, or
PRIO-024 WARN bad n_bits in def grp
PRIO-025 WARN port types incompatible
PRIO-026 WARN bad log asgt no
PRIO-027 WARN hot bit not on
PRIO-028 WARN ai seq bad at pwr/up
PRIO-029 WARN port namefortoo
no name long
port
PRIO-030 WARN
SYSTE type/no
SLC2 int rtn already
PRIO-031 M
SYSTE active
too many DIGITAL I/O
PRIO-032 M modules
Check that the PLC
interface board is properly
installed. Check the LED
status on PLC interface
PLC interface init. fault The PLC interface board is bad or not board. Refer to the
PRIO-033 WARN %d installed. FANUC Robotics manual,
the PLC interface board.
Refer to the FANUC
Robotics manual, A User's
PLC interface general Guide to the FANUC
PRIO-034 WARN fault %d The PLC interface board is faulted. Robotics SYSTEM R-J3
PLC interface board. Refer
to the FANUC Robotics
PLC interface serial fault manual, A User's Guide to
PRIO-035 WARN %d The serial link to a PLC has failed. the FANUC Robotics
PRIO-036 WARN Deallocation failed
SYSTE Not supported for spec. The operation is not supported for the Check the specified port
PRIO-037 M port type specified port type. type.
PRIO-038 WARN I/O point not defined
PRIO-039 WARN Illegal initval
PRIO-040 WARN no module in slot
PRIO-041 WARN phys. port alrdy asgd
PRIO-042 WARN log port not asgd
PRIO-043 WARN invalid
duplicategroup number
group
PRIO-044 WARN number
PRIO-045 WARN group no. not defined
PRIO-046 WARN non-continuous ports
PRIO-047 WARN Port data not in SLC
PRIO-048 WARN area
Check the connections
and power to the board or
One or more assignments to the rack and that the
process I/O board or module at the module(s) are firmly
Bad I/O asg: rack %d specified rack and slot was invalid when installed. If the board or
PRIO-063 WARN slot %d the controller was turned on. module has been
Install the PLC I/O (A-
B/GENIUS) software
option. Refer to the
An A-B RIO or Genius Network board is FANUC Robotics manual,
PLC interface option installed but the PLC software option is A User's Guide to the
PRIO-070 WARN not loaded not installed. FANUC Robotics SYSTEM R-
The maximum of number of concurrent Modify program logic to
PRIO-072 WARN Too many pulses active pulse output statements is 255. ensure that not over 255
PRIO-074 WARN Illegal pulse ID Specified pulse ID does not exist Check the pulse ID.
Install a PLC I/O board
into the backplane Refer
to the installation
PLC I/O hardware not A PLC I/O board is not installed in the procedure in A User's
PRIO-076 WARN installed backplane. Guide to the FANUC
This indicates that an severe error has Check other error
occured during I/O initialization at messages displayed on
PAUSE. controller power-up. Other messages in the TP alarm screen. The
PRIO-081 G I/O is not initialized the log will indicate the specific conditions indicated by
Digital output port states are not
recovered when semi-hot start is
PAUSE. Digital I/O is not enabled because I/O device
PRIO-083 G recovered configuration or assignments have Cold start the application.
SYSTE BUSY in SLC2 does not Check SLC2 on Main CPU
PRIO-085 M turn off BUSY bit in SLC2 does not turn off. board or I/O device and
Change main board or
remove PMC function. If
you need clear this alarm,
PAUSE. PMC is not supported PMC function is not supported on this please turn off K17.2
PRIO-089 G on thiscommunication
SNPX hardware main board. (SDO[10139]). PMC does
PRIO-090 WARN error Error occurs at SNPX communication. Please refer cause code.
Op panel comm Indicates that an error has been Check the cabling
PRIO-091 STOP error(ch:%d) %x, %x detected in communication between between the MAIN PCB
This indicates that an error has been Check the cabling
Force sensor comm detected in communication between between the MAIN PCB
PRIO-092 STOP errorblown
Fuse %x, %xRack:%d
(hex) the MAIN PCB and the Force sensor. and Force sensor.
PRIO-093 STOP Slot:%d
Overload Rack:%d Fuse on process I/O board is blown. replacethe
Please check the fuse.
PRIO-094 STOP Slot:%d DO:%d-%d The specified DO may be grounded. connection of the
The DO of the specified connector Check the connection of
PRIO-095 Overload %s might be grounded. the DO of the specified
Do any one of the
SNPX Connection is The number of connections has following: Wait until a
PRIO-096 full<%s> reached the set value. connection becomes
No reply was received from the Check the connection to
PRIO-097 SNPX time out<%s>
PMC communication computer to which
Failed to PMC the displayed IP
Ethernet the computer
Please back toto which
square
PRIO-098 error communication. one.
The port is initialized at PMC When use PMC Ethernet
PRIO-099 Port initialization error programmer. communication, disable
PAUSE. Model B comm fault Communication between the Model B Check the power and
PRIO-100 G %srack:%d slot:%d interface unit and DI/DO units, or cabling from Model B
The PLC Interface hardware (A-B RIO or
Cycle power to restart Genius Network PCB) is already running Turn off and then turn on
PRIO-102 WARN PLC I/O and can not be restarted without the controller. ports,
For DeviceNet
troubleshoot as follows:
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
An attempt has been made to access to daughter board is
a port assigned to a device or board installed on the Interface
which is offline. This might be the result board. 2.) There is power
PAUSE. of an error or device having been set on the network. If these
PRIO-104 G Device is off-line offline manually. do not indicate a problem,
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
An attempt was made to access a port is OFF, set it ONLINE. If
assigned to a device which is offline. the status is ERROR, check
For DeviceNet ports, troubleshoot as the following: 1.) The
follows: This might be caused by an daughter board is
PAUSE. Device with port is off- error or the device being manually set installed on the Interface
PRIO-106 G line offline. board. 2.) There is power
Power-down and up the
Timeout occurred in iosdvoff waiting controller. If the problem
Timeout waiting for for pab_built to be set. This is a system occurs again, record the
PRIO-108 WARN pab_builtto byte, not
Address error. software version and any
PRIO-110 WARN long
Address to word, not
PRIO-111 WARN long
Address to word
PRIO-112 WARN (reversed polarity), not
The specified PD The specifid PD number is not available
PRIO-113 WARN number is invalid for the specified HDB. This is a system Software problem
iomakhdb() and iofillpd() can be called
PRIO-115 Can't set HDB now at IOFC_MAKE_HDB_C only. Software problem
The specified HDB is not found, or HDB Check parameter of
PRIO-117 Can many
Too not getDIGITAL
HDB I/O is not completed yet. iogthdbp. Call
Disconnect iogthdbp.c
some DIGITAL
PRIO-119 WARN ports There are too many DIGITAL I/O ports. I/O devices.
You can not do this operation when Please stop PMC program
PRIO-121 WARN StopUOP
This PMCID program PMCspecified
is already The peogramUOP is running. execution.
ID is already used by Please use the other UOP
PRIO-123 WARN
SYSTE registered another entry. ID
The SLC2 is in an error state at the end Check SYSFAIL of the
PRIO-125 M SLC2 initialization error of initialization. other PCB. Also check the
PRIO-126 WARN No PMC program PMC program does not exit. program.
Download PMC program
PRIO-127 WARN PMC file load error PMC program format is incorrect. again.
Saving of keep relay (K), Timer (T),
PAUSE. T,C,K and D data may Counter (C) and Data table (D) at last
PRIO-128 G be lost powerfunction
Illegal down is failed.
command Current datainof Please
is found Load PARAM.PMC
check PMC file.
PRIO-129 WARN SUB%d is not supported PMC program. program.
PMC option is not Integrated PMC option (A05B-2400- Please install Integrated
PRIO-130 WARN installed J760) is not installed. PMC option.
1. File name must be LADDER.PMC ot 1. Change file name to
PARAM.PMC. The other file name is LADDER.PMC for PMC
PRIO-131 WARN PMC file name error used for save or load. 2. Device name program, PARAM.PMC for
One of the following is locked by
PMC operation is another task. PMC program edit, DI/O Please try again later, or
PRIO-132 WARN locked
PMC program size is too port simulation change, PMC program Please use thecheck
otherPMC
method.
PRIO-133 WARN big
Invalid PMC addr Step of PMC program is too big. program step
Specified PMC address is not valid for R- Please check addresssize. in
PRIO-134 WARN %s%d.%d J3 PMC. PMC program.
PMC address is not Specified PMC address is not assigned Please check address in
PRIO-135 WARN assigned
BYTE access to to any device.
Specified PMC address can not be used PMC
Pleaseprogram.
check address in
PRIO-136 WARN %s%d.%d as byte address.
Specified PMC address can not be used PMC program.
Please check address in
PRIO-137 WARN BIT access to %s%d.%d as bit address. PMC program.
Specified address can not be used in
specified function command. - F0-F255
and G0-G255 can not be used except Please check address in
PRIO-138 WARN %s%d
InvalidisCNC
usedaddr
in SUB%d MOVW. - Odd address of F0-F255 and PMC program.
Please check PMC type of
PRIO-139 WARN %x.%x(hex) Specified CNC address is invalid. FAPT LADDER II.
Can't display all PMC There are more than 10 errors in PMC Check the other PMC
PRIO-140 WARN errors program. And error display is stoped. errors.PMC program, and
Chack
PRIO-141 WARN Invalid PMC program PMC program data is invalid. load again.
Need E-STOP or CTRL To write PMC progeam to flash file, E- Press E-STOP or do
PRIO-142 WARN start SOP must be pressed or start mode is controlled start.
PAUSE. Writting PMC program You can not clear alarm status during Press wait until writing
PRIO-143 G
PAUSE. to ROM
Faild to run PMC writting PMC program program to PMC
Referprogram is
to the previous
PRIO-144 G program Faild to run PMC program. error messages.
PAUSE. Purging flash file, please Purging flash file now. It takes a few
PRIO-145 G wait
Flash file purge is minutes. Don't cut power until 'Flash It is message only.
PRIO-146 WARN completed Purge of flash file is completed. It is message only.
SYSTE The DIO configuration file (.IO) file Save the DIO
PRIO-147 M DIO config file too new loaded is in a format that is too new to configuration on a
SYSTE The DIO configuration file (.IO) file Save the DIO
PRIO-148 M DIO config file too old loaded is in a format that is too old to configuration on a
No action is neccesary;
Invalid assignment An invalid port assignment has been the invalid assignment will
PRIO-149 WARN recorded recorded not be in effect until it is
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 Look at possible causes.
PAUSE. CNET Card Init Error Bd board firmware is not supported. Remedies are mentioned
PRIO-150 G %d Restore system variables. If necessary therein.
CNET Internal Error ControlNet option encountered an Please look up the error
PRIO-151 WARN 0x%x internal error. The number is the to find the root cause.
Reload the configuration
from the config tool. For
adapter mode, verify that
CNET Invalid Scan The configuration loaded on the CNET all paramters are correct.
PRIO-152 WARN Config Bd %d daughterboard is invalid. Verify that EDS files used
Verify all connections to
CNET Conn. Ownership The target connection is already owned the target device from all
PRIO-153 WARN Conflict
PAUSE. CNET Duplicate Mac ID by some other device. scanners
Check on theof
MAC-IDs network.
all
PRIO-154 G Bd %d Duplicate MAC-ID detected devices on the network
Check wiring to the card.
PAUSE. CNET Network Error Bd The CNET card is not attached to the Check for duplicate MAC-
PRIO-155 G %d network. ID. Ensure that there is
The connection for the device Mac Refer to cause code if
PAUSE. CNET Er %s Bd %d MAC listed encountered an error. The Er listed. If not, refer to the
PRIO-156 G %d number is the ControlNet error code. ControlNet error code in
PAUSE. CNET Err Loading BIN The firmware for the card could not be Refer to cause code.
PRIO-157 G file Bd %d loaded. Verify Board sys vars to
Verify Board sysvars
PRIO-158 WARN CNET File Not Found The firmware file was not found $CN_BD_INFO[%d] are set
CNET Cycle pwr to Scan list was modified. ControlNet Cycle power to the
PRIO-159 WARN restart scan interface is stopped. controller for the changes
All connections to the card are broken. Finish the change. When
No I/O is exchanged and all ports are the network is completed,
PAUSE. CNET Connections Offline. This happens when a network the connections will be
PRIO-160 G Broken Bd %d configuration is being performed or the restored. If scan list is
Finish the change. When
CNET Network Change A config tool is performing a network the network is completed,
PRIO-161 WARN Occuring
CNET Connections change.
The CNET interface has restored the the connections
This will be
is a caution message
PRIO-162 WARN Restored Bd %dChange
CNET Network connections.
The config tool has completed the to the user.
This is a caution message
PRIO-163 WARN Complete network change. to the user.
PAUSE. CNET Scan list modified A config tool has modified the scan list At this point, a network
PRIO-164 G Bd %d of the interface card. config needs to
Verify the scan-list
configuration and match it
with the target device.
Verify the connection
paths. The connection
CNET Connection Not The interface could not establish a path expected by the scan-
PRIO-165 WARN Found connection as it was not found. list can be found in the
CNET Invalid Use correct EDS file in the
PRIO-166 WARN Connection Type Invalid connection type in scanlist. scan-list config tool and
CNET Vend ID/Prod. The vendor ID of the device in the scan- Use correct EDS file and
PRIO-167 WARN Code Mismatch list and that of the actual device do not reconfigure the scan-list
CNET Invalid The connection size of the device in the Verify correct size and
PRIO-168 WARN Connection Size scanlist does not match the target reload the scan-list using
CNET Device Not Run a network
PRIO-169 WARN Configured The connection has not been scheduled configuration tool such as
CNET Product Type The Product Type of the device in the Use correct EDS file and
PRIO-170 WARN Mismatch scan-list and that of the actual device reconfigure the scan-list
CNET Maj/Min Revision The Major/Minor revison of the device Use correct EDS file and
PRIO-171 WARN Mismatch
CNET Target App Out of in
Thethe scan-list
target anddoes
device thatnot
of the actual
have reconfigure the scan-list
Close some connections
PRIO-172 WARN Conn. enough connections to target device.
CNET Needs Network Run a network
PRIO-173 WARN Config. The connection has not been scheduled configuration tool such as
Check network
The connection to the remote device is connections. Check to see
PRIO-174 WARN CNET Connection Lost lost. that the remote device is
Run a network
The device is not in correct state to configuration tool such as
PRIO-175 WARN CNET Bad Device State respond to this connection request. RSNetworx and configure
CNET Connection Remote device refused the connection. Verify that the correct EDS
PRIO-176 WARN Request Failed This could be due to an invalid file is being used for the
Check the configuration
CNET Invalid The Card has an invalid scan-list on the scanner config
PRIO-177 WARN configuration configuration. tool. Verify correct EDS
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 = Review software
number of lost scans; if n2 is less than configuration to
5, this may not be a serious problem; determine how loading
PRIO-178 WARN Blk scns lost; %d %d %d n3 = total scans since pwr up since can be reduced.
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 Review software
processor; n2 = number of lost scans; if configuration to
Run scns lost; %d %d n2 is less than 20, this may not be a determine how loading
PRIO-179 WARN %d serious problem; n3 = total scans since can be reduced.
An element could not be added to the Verify all I/O is valid.
system I/O scan When this error is Check all CNET devices
posted, ControlNet I/O is not and ensure the sizes are
Operational. Possible causes are: * resonable. Max I/O is
CNET Sys Err %d %d Invalid Configuration of scanner scan limited by that allowed for
PRIO-180 WARN 0x%x list * Too many I/O points for any given the system.
Verify that the target
CNET Conn. Req. Target device did not respond to the device is online and the
PRIO-181 WARN Timeout connection request. status is OK. Verify that
CNET CCO Change Network change was aborted.
PRIO-182 WARN Aborted Connections will be restored and I/O This is a caution message.
Unknown port type Unrecognized port type name supplied Supply name from
PRIO-183 WARN name to tpptnptc element
Check the remote scanner
The target (adapter) connection is idle. configuration. Check the
A scanner has not connected yet. All sizes and other
the ports corresponding to this device configuration parameters
PRIO-184 WARN CNET Connection Idle There
will beisoffline.
an error with the Scan-list such as vendor ID,
PRIO-185 WARN CNET Config Er %d %d configuration. Refer to the cause code.
Enter a valid header size.
The input header size in case of scanner The valid header is less
CNET Invalid Header mode or the output header size in case that or equal to the total
PRIO-186 WARN size of adapter is invalid. connection size. The total
Verify the configuration in
CNET Invalid Num of The number of slots for the device in the scanner config tool
PRIO-187 WARN Slots the scan is invalid. and reload the
There is no output defined for the Define the Simulated
Sim. Skip output not Simulated Input Skip featue and a WAIT Input Skip output using
PRIO-188 PAUSE defined instruction containing a skipped input the System Config menu.
The input used in this WAIT instruction None. This is only a
is simulated and is designated as Skip warning to indicate that a
(%s^4, %d^5) WAIT will When Simulated. This WAIT instruction Simulated Input Skip will
PRIO-189 WARN time out will timeout and program exection will occur.
PMCADR.HTM format PMCADR.HTM has format error. Check
PRIO-190 error. Line %d the line of this file. Correct the format error.
There was a problem initializing the AB- - No Board : check that
RIO hardware. The PRIO-191 alarm board is installed and dip
code will include a cause code with the switches are set properly. -
PRIO-191 AB-RIO Board Init Error reason. Failed to load/start/clear
code will include a cause code with the switches are set properly. -
PRIO-192 AB-RIO No Board Found reason. Failed to load/start/clear
AB-RIO Failed to Load code will include a cause code with the switches are set properly. -
PRIO-193 FW reason. Failed to load/start/clear
AB-RIO Failed to Start code will include a cause code with the switches are set properly. -
PRIO-194 FW reason. Failed to load/start/clear
AB-RIO Failed to Clear code will include a cause code with the switches are set properly. -
PRIO-195 Config reason. Failed to load/start/clear
There was a problem with a rack
configuration. The slot will indicate
which rack configuration. The problem
might be one of the following: - The Correct the rack
AB-RIO Config Error, rack number is not between 0 & 31 - configuration on the AB-
PRIO-196 Slot %d The rack size or ending rack boundary RIO user interface.
The I/O connection associated with this
slot is not actively exchanging I/O. Note
that the alarm severity (STOP or WARN) Check the wiring, baud
is affected by the error severity setting rate, and PLC
PRIO-197 AB-RIO Slot %d Idle on the AB-RIO configuration screen. configuration.
The plc is in test mode, program mode,
or the connection might be inhibited in
the PLC. Note that the alarm severity Check that the PLC is in
(STOP or WARN) is affected by the run mode and that the
AB-RIO Slot %d in error severity setting on the AB-RIO connection is not
PRIO-198 PAUSE. Test/Prog configuration screen. The last state inhibited in the PLC setup.
PRIO-200 G FIPIO System Error %d
PRIO-201 WARN
PAUSE. FIPIO PCB not installed
PRIO-202 G
PAUSE. PCB Abnormal
FIPIO Duplicate FIP
PRIO-203 G
PAUSE. Address
PRIO-204 G
PAUSE. Send Buffer
FIPIO Receive Error
Buffer
PRIO-205 G
PAUSE. Error
PRIO-206 G
PAUSE. Physical Reset
FIPIO BadPrm; CMD
PRIO-207 G
PAUSE. %x,%x
FIPIO NRDY; CMD %d
PRIO-208 G
PAUSE. LNG
FIPIO%dConnection
PRIO-209 G
PAUSE. Broken
FIPIO Cnf/Adj not
PRIO-210 G
PAUSE. available
FIPIO Bad Cnf/Adj
PRIO-211 G
PAUSE. status
FIPIO Connection
PRIO-212 G TimeOut
FIPIO Connection
PRIO-213 WARN Established
FIPIO Connection
PRIO-214 WARN Recovered
FIPIO Configuration
PRIO-215 WARN accepted
FIPIO Adjustment
PRIO-216 WARN accepted
FIPIO Configuration
PRIO-217 WARN refused
FIPIO Adjustment
PRIO-218 WARN refused
FIPIO SetControl
PRIO-219 WARN received
EGD Producer name/IP EGD Producer name/IP address is not On the EGD screen, type
PRIO-220 WARN not init initialized. the robot IP address in the
EGD Consumer size The amount of input consumed does Check the EGD producer
PRIO-221 WARN misconfigured not match the configured size. and make sure the
EGD Consumer init The EGD Consumer task initilization The consumer module is
PRIO-222 WARN failed failed. The consumer module is not not loaded on the robot.
implies that the Ethernet
or TCP/IP interface is not
EGD Producer socket The EGD Producer was unable to create set up correctly. For
PRIO-223 WARN error a UDP network socket. example,
Turn off theif no IP address
controller,
PRIO-224 WARN EGD System Error An EGD System Error has occurred. then turn it on again.
error. Check the EGD
Producer device to verify
The EGD Consumer timed-out while that it is functioning
EGD Consumer timeout - waiting for an I/O message from an properly. Check the EGD
PRIO-225 WARN Id:%d EGD Producer. Consumer timeout value.
EGD Consumer socket The EGD Consumer was unable to set up correctly. For
PRIO-226 WARN create error create a UDP network socket. example, if no IP address
EGD Consumer socket The EGD Consumer was unable to bind set up correctly. For
PRIO-227 WARN bind error to a UDP network socket. example, if no IP address
EGD System error - EGD System Error. A general system Turn off the controller,
PRIO-228 WARN Code:%x failure has occurred. then turn it on again.
Alarm severity can be
The Ethernet/IP Adapter Connection modified on the
running on the robot is enabled and EtherNet/IP adapter
Ethernet/IP Adapter has an error. Refer to additional cause configuration screen on a
PRIO-230 WARN Error (%d) code text for further details. per connection basis, and
The Ethernet/IP Adapter connection is
enabled but no scanner has been Configure the scanner (eg.
connected to it. Note that it is normal PLC) to connect to the
to see this message when the controller robot. Press RESET to
first is turned on since the scanner (eg. clear alarm. An alarm will
Ethernet/IP Adapter PLC) might not connect to the robot be reposted if the
PRIO-231 WARN Idle immediately after the robot has been connection is still idle.
Ethernet/IP Not The Ethernet/IP Adapter was not able set up correctly. For
PRIO-232 WARN Initialized to initialize. example, if no IP address
Ethernet/IP Scn Not in An EtherNet/IP scanner is connected to Put the scanner in run
PRIO-233 WARN
PAUSE. Run Mode System
IO LinkII(S) the robot adapter in IDLE mode. No I/O mode, and retry the
PRIO-240 G error(%d)
IO LinkII(S) PCB not
PRIO-241 WARN
PAUSE. installed
IO LinkII(S) PCB
PRIO-242 G
PAUSE. abnormal(%d)
IO LinkII(S) Parameter
PRIO-243 G
PAUSE. error
IO LinkII(S) Link
PRIO-244 G Down(%d)
PRIO-245 WARN IO LinkII(S) Detect Abort
CRC
PRIO-246 WARN Error
IO LinkII(S) Incorrect
PRIO-247 WARN BitData
IO LinkII(S) RX Buf
PRIO-248 WARN overflow
IO LinkII(S) Overrun
PRIO-249 WARN Error
PAUSE. IO LinkII(M) System
PRIO-260 G error(%d)
IO LinkII(M) PCB not
PRIO-261 WARN
PAUSE. installed
IO LinkII(M) PCB
PRIO-262 G
PAUSE. abnormal(%d)
IO LinkII(M) Parameter
PRIO-263 G
PAUSE. error
IO LinkII(M) Link
PRIO-264 G Down(%d)
IO LinkII(M) Detect
PRIO-265 WARN Abort
IO LinkII(M) Detect CRC
PRIO-266 WARN Error
IO LinkII(M) Incorrect
PRIO-267 WARN BitData
IO LinkII(M) RX Buf Fail to run Cell Finder Motn Cannot Clear all the errors before
PRIO-268 WARN
PAUSE. overflow start the Cell Finder motion. executing Cell Finder.
PRIO-280 G FL-net System Error(%d)
PRIO-281 WARN
PAUSE. FL-net PCB not installed
PRIO-282 G
PAUSE. Abnormal(%d)
FL-net IP Address
PRIO-283 G
PAUSE. Incorrect
FL-net Token Interval
PRIO-284 G
PAUSE. Error
PRIO-285 G Init Error
FL-net Wait Frame
PRIO-286 WARN
PAUSE. Status
FL-net My Node
PRIO-287 G
PAUSE. Dupulicate
FL-net No. Leave
My Node
PRIO-288 G network
FL-net My Node Enter
PRIO-289 WARN
PAUSE. network
FL-net My Node
PRIO-290 G
PAUSE. Dupulicate
FL-net NodeAdr%d Leave
PRIO-291 G network
FL-net Node %d Enter
PRIO-292 WARN
PAUSE. network
FL-net Dupulicate Area
PRIO-293 G Adr %d
FL-net Multiple PCBs Multiple FL-net boards are inserted into Remove additional FL-net
PRIO-294 detected the control unit. boards. Only one can be
FL-net register is too FL-net sending register is too large or Change the register to
PRIO-295 large too small to change to integer. smaller or larger
Please use value
internal port or
PRIO-296 board
FL-net rcv regcan't
is toouse Setting is to use internal port for FL-net
set to
Set use board
FL-net receive register
PRIO-297 large FL-net receive register is too large. under 200.
CC-LK System Contact FANUC?s service
PRIO-320 STOP error(ID=%x)(%d)
CC-LK Board not An internal
No system error
CC-Link Remote Deviceoccurred. site. The
Station PCB Install theIDCC-Link
numberRemote
in the
PRIO-321 WARN installed is installed. Device Station PCB.
CC-LK St.No out of A station number out of the range (1 to Change the Station No. or
PRIO-322 STOP range(%d) 64) was occupied. Number of Stations on the
Confirm the connection of
CC-Link cable and terminal
PRIO-323 WARN CC-LK CRC error(%d) A CRC error was detected. registers, and
This Remote Device station left the CC-Link cable and the
data link. The CC-Link cable were status of the Master
CC-LK Data link disconnected or the Master station was station. NOTE If you turn
PRIO-324 STOP error(%d) turned off. on the R-J3iB/R-J3iB Mate
Confirm the status of the
sequencer. NOTE This
CC-LK Seq. CPU alarm is detected
PRIO-325 STOP stopped(%d) The sequencer CPU stopped. correctly only while the
Confirm the status of the
sequencer. NOTE This
CC-LK Seq. CPU alarm is detected
PRIO-326 STOP abnormal(%d) The sequencer CPU is abnormal. correctly only while the
CC-LK Reg index Change Number of
PRIO-327 STOP error(%d) A non-existent register was used. Registers or Reg start
CC-LK AO/R too Too many AOs or Registers were Change the Number of
PRIO-328 STOP many(%d) assigned to RWr. AOs and Number of
CC-LK AI/R too Too many AIs and Registers were Change Number of AIs
PRIO-329 STOP many(%d) assigned to RWw. and Number of Registers
CC-LK PNTtoUOP not The number of points of RX/RY to be Change the Number of
PRIO-330 STOP enough(%d) assigned to UOP are not enough. Stations on the CC-Link
"CC-Link function of robot
CC-LK Reg data A numerical value set to a remote supports only unsigned or
PRIO-331 invalid(%d) register was not a 16 bit integer. signed 16 bit word data.
CC-LK no comm. to CC-Link cable and terminal
PRIO-332 master(%d) Channel carrier detection error. registers,a and
Contact noise
FANUC service
PRIO-333 CC-LK comm task failed An internal system error has occurred. representative.
A. Three or more CC-Link daughter Robot controller supports
CC-LK too many boards boards are installed. B. Three or more only two CC-Link
PRIO-334 found CC-Link Remote Device Station communication boards.
The type of CC-Link
CC-LK different board Two differnt types of CC-Link Remote Remote Device Station
PRIO-335 types Device Station PCBs are installed. PCBs must be the same.
Alarm severity can be
modified using the
The Ethernet/IP Scanner Connection EtherNet/IP advanced
running on the robot is enabled and scanner configuration
Ethernet/IP Scanner has an error. Refer to additional cause screen on a per
PRIO-350 WARN Error (%d) code text for further details. connection basis, and last
Ethernet/IP Cannot The EtherNet/IP Scanner was not able set up correctly. For
PRIO-351 WARN Open Socket to open a TCP or UDP network socket. example, if no IP address
Ethernet/IP Cannot The EtherNet/IP Scanner was not able set up correctly. For
PRIO-352 WARN Bind Socket to bind a TCP or a UDP network socket. example, if no IP address
The EtherNet/IP Scanner was not able or TCP/IP interface is not
to send information on a TCP or UDP set up correctly. For
PRIO-353 WARN Ethernet/IP Send Error network socket. example, if no IP address
Verify the Name/IP
Address entered in the
Scanner Configuration
Screen is valid. Try to ping
the address from the main
Ethernet/IP Cannot The EtherNet/IP Scanner could not EtherNet/IP screen. If
PRIO-354 WARN Resolve Name resolve the Adapter host name. using DNS, verify the DNS
Verify the Robot and the
Adapter device are both
The EtherNet/IP Scanner was not able connected to the
Ethernet/IP Connect to connect to the adapter device on a network. Check the
PRIO-355 WARN Error TCP network socket. adapter device and verify
Verify the Robot and the
Adapter device are both
connected to the
The EtherNet/IP Scanner did not network. Check the
Ethernet/IP List Serv receive a List Services Reply message adapter device and verify
PRIO-356 WARN Failed from the adapter. it is running properly and
Ethernet/IP Reg Sess The EtherNet/IP Scanner did not Check the adapter device
PRIO-357 WARN Failed receive a Register Session Reply and verify that
Verify the Scanner
settings in the Scanner
The EtherNet/IP Scanner either did not Configuration screen are
receive a ForwardOpen Reply message correct. Review the
from the adapter, or the Scanner adapter manual for the
received a ForwardOpen Reply message correct settings. Verify
Ethernet/IP Fwd Open indicating a failure to establish an I/O that the adapter does not
PRIO-358 WARN Failed (0x%x) connection. currently have a duplicate
Ethernet/IP I/O The EtherNet/IP Scanner timed-out Press RESET to restart the
PRIO-359 WARN Timeout Error while waiting for an I/O message from scanner connection.
The EtherNet/IP adapter to which the
Ethernet/IP Adp Not in robot scanner is connected is in IDLE Put the adapter in RUN
PRIO-360 WARN Run Mode mode. No input data will be mode.
EtherNet/IP System An unexpected system level error has Document the events that
PRIO-369 Error occurred. led to the error, and call
The Modbus TCP Server running on the Alarm severity and last
robot is enabled and has an error. Refer state behavior can be
Modbus TCP Server to additional cause code text for modified using the
PRIO-490 Error further details. Modbus TCP Slave
The Modbus TCP Server was not able to set up correctly. For
PRIO-493 Modbus Socket Error open and use a TCP network socket. example, if no IP address
A Modbus TCP master device is trying
to establish a connection with the
robot Modbus slave, but the server is
already using all available connections.
This is a warning alarm and will only be
posted the first time this happens after
each power-cycle. Per the Modbus TCP Increase the number of
protocol, when a new connection connections using the
PRIO-494 Modbus Active Close request arrives and there are no Modbus TCP screen.
The Modbus TCP server timed-out Check the Modbus TCP
while waiting for an I/O message from a client to verify it is
PRIO-495 Modbus Timeout Modbus TCP client. functioning properly.
Turn off the controller,
Modbus TCP System Error. A general then turn it on again. If
PRIO-499 Modbus System Error system failure has occurred. the error still occurs,
PMC:Invalid Override Setting of Override is invalid. Override Reduce number of PMCs
PRIO-520 setting
PMC:Invalid seqence can be set for only tree nummber of setting Ovreride.
PRIO-521 numbers
PMC:Invalid memory Setting of Sequence number is invalid. Check Sequence number.
PRIO-522 types
PMC%d:memory types Setting of Memory Type is invalid. Check Memory Type.
PRIO-523 are mismatchexecution Setting of Memory Type is invalid
PMC:Invalid Check Memory Type.
PRIO-524 rates Setting of Execution Rates is invalid. Check Execution Rates.
PMC%d:PARAM%d.PM PARAM*.PMC was not loaded. PMC Please confirm setting of
PRIO-525 C was not loaded adress values are not replaced. max PMC-path number.
PMC%d:Keep data was
PRIO-526 not
PMC:Erestored
relay data was Keep data was not restored. Try the operation again.
PRIO-527 not restored E relay data was not restored Try the operation again.
PMC%d:Step Sequence Step Sequence program cannnot be Please load this PMC
PRIO-528 cannot be used used. It can be used only PMC1. program as PMC1.
PMC:PMC interface PMC interface adress(M,N) setting is Please change setting of
PRIO-529 setting is invaled invalid PMC interface on PMC
PMC%d:Function Block Multi-Path PMC Option(J763) is not Please delete functions
PRIO-530 cannot be use
PMC%d:Invalid orderd.
Some To use statements
function some function,
can J763 is
for J763.
not be
Please delete invvalid
PRIO-531 statements exist used. functions from PMC
PMC%d:Int.I/O[%d] IO index setting is overlaped with otherPlease change setting of
PRIO-532 setting is overlaped IO
PMC%d:Int.I/O[%d] device. IO index of Int.I/O can not be Int.I/O change
Please . setting of
PRIO-533 is invalid IO index setting of Int.I/O is invalid. Int.I/O .
PMC%d:Int.I/O[%d] size PMC address setting of Int.I/O is Please change setting of
PRIO-534 is invalid
PMC%d:Int.I/O[%d] invalid.
PMC PMC address
address must
setting of be set
Int.I/O is as 2
Int.I/O change
Please . setting of
PRIO-535 address is invalid of
PMC%d:Number invalid. Int.I/O.
Please change setting of
PRIO-536 Int.I/O is limitvalue
PMC:%s[%d] Number
Error of System
of Int.I/O CopyInt.I/O
Mode. is Register
limit. is
Int.I/O change
Please . setting or
PRIO-537 cannot be power to
PMC:Cycle not integer. changecycle
Please register value.
power to
PRIO-538 change setting PMC Setting is changed. change PMC setting
PMC:Temporary Please change PMC
PRIO-539 Memory is lack Temporary Memory to use PMC is lack. memory area size or use
PMC%d:PMC programs Setting of max path PMC number is Please set back mac path
PRIO-540 are deleted at cycle changed. PMC program will be deleted PMC number not to
PMC:LADDER%d.PMC PMC program was deleted, because
PRIO-541 was deleted setting of max path PMC number is None.
PMC No ext. I/O The device that set to External I/O of Please check setting of
PRIO-542 rack:%d slot:%d PMC is not found. PMC External I/O. Check
PMC:Can not use Ext. Internal I/O assignment X and Y address Please delete setting of
PRIO-543 I/O assignment and External I/O assignment can not be PMC External I/O. Or
PMC:Can not use Internal I/O assignment X and Y address Please change setting of
PRIO-544 memory common mode and setting of memory common mode memory type. Or please
PMC:Override cannot PMC address assigned to Internal I/O Please use simulate value
PRIO-545 set thisDCS
Invalid address
PMC cannot
DCS PMCsetprogram
as Override. of I/O screen.
has invalid address Please check DCS PMC
PRIO-546 program
Can not run/stop Safety or function code.
Safety PMC execution state can not be program.
PRIO-547 PMC changed. This is just notification
PNIO board not PCI motherboard with CP1616 is not Check that the PCI
PRIO-600 installed installed. motherboard or CP1616
PROFINET software on the robot Cycle power the robot
PRIO-601 PNIO watchdog alarm controller is not working controller. Consult a
Consult FANUC
PNIO system representative. Note the
PRIO-602 error(ID=%x)(%d) An internal system error has occured. numeric values displayed
Consult FANUC
representative. Note the
PRIO-603 %s An internal system error has occured. numeric value displayed
Consult FANUC
representative. There is
another error message
that shows the cause of
PRIO-604 PNIO system error System error. this alarm. Open alarm
The value in the error
message is error code
from CP1616. Refer to the
ProfiNet I/O Operator's
PNIO(D) open error Failed to start PROFINET I/O Device Manual for more
PRIO-605 %04x function. information. If value is not
PNIO(D) abort PROFINET I/O communication is This is just a notification
PRIO-606 indication %x aborted by I/O Controller. to the operator.
PNIO(D) offline PROFINET I/O communication is This is just a notification
PRIO-607 indication %x stopped by I/O Controller. to the operator.
The reported module with slot number Check the setting in the
PNIO(D) mismatch slot and subslot number does not match setup module detail
PRIO-608 %d %d the configuration of project file screen. Check the project
PNIO: Need reset for Remote stop of PROFINET CP1616 Please press reset the
PRIO-609 restart interface by remote configuration tool. controller after remote
The value in the error
message is error code
from CP1616. Refer to the
ProfiNet I/O Operator's
PNIO(C) open error Failed to start PROFINET I/O Device Manual for more
PRIO-610 %04x
PNIO(C) alarm function. information. If value is not
This is just a notification
PRIO-611 indication
PNIO(C) %x
offline Alarm is indicated by CP1616. to the
This is operator.
just a notification
PRIO-612 indication Operating mode is changed to offline. Thisto the
is operator.
just a notification
PRIO-613 PNIO(C) clear indication Operating mode is changed to clear. to the operator.
PNIO watchdog start Watchdog of CP1616 could not be Consult FANUC
PRIO-614 failed started. representative. Report the
PNIO: can't find the Specified station number is not found
PRIO-615 stationattach/detach
PNIO: whenswitching
Then the switching TP instruction
TP instruction is
has timed Check ifthe station
the targetnumber.
station
PRIO-616 Timeout out. is properly connected.
Check the module
PNIO(D) mod plug I/O Device function failed because the specified by the two
PRIO-617 failed %x %x specified module is wrong. numbers included in the
Check the module
PNIO(D) submod plug I/O Device function failed because the specified by the two
PRIO-618 failed %x %x specified submodule is wrong. numbers included in the
The stored configuration of the module Check the parameters of
that is specified by station number, slot the module that is
PNIO(C) mismatch st %d number and subslot number does not specified by station
PRIO-619 slot %d %d match the current configuration when number, slot number and
PNIO(C) station %d The device whose station number is Check the station
PRIO-620 deactivated displayed in the error is deactivated. specified by the station
"Disable the I/O Device if
the I/O Device function is
not used. If the I/O Device
function is used, check if
The start up of I/O Device has not there are any error
PNIO(D) device is not completed or was terminated by an related to the I/O Device.
PRIO-621 running error. Check if I/O Controller
Disable the I/O Controller
if the I/O Controller
function is not used. If the
The start up of I/O Controller has not I/O Controller function is
PNIO(C) controller is completed or was terminated by an used, check if there are
PRIO-622 not running error. any errors related to the
PNIO(C) not in The start up of I/O Controller has Change the start mode to
PRIO-623 operation mode completed but the start up mode is not OPERATION, and cycle
The number of modules in the stored Check if the project
PNIO(C) mod number configuration is different from the downloaded to CP1616
PRIO-624 mismatch current configuration when the start matches the current
PROFINET network configuration has This is just notification of
PNIO(C) read in been read in successfully when start completion of read in.
PRIO-625 complete mode is READ IN. Check PROFINET I/O
PNIO: please power PROFINET setting of the robot Cycle the power of the
PRIO-626 OFF/ON
PNIO: controller
set to operation Start modewas changedtoand
is changed cycling
operation robotis controller.
This just notification of
PRIO-627 mode group is not
PNIO(C) mode. completion
Restore of mode
group status
PRIO-628 recovered Group status could not be recovered. manually.
Restore group status
PRIO-629 Restore group manually Group status could not be recovered. manually.
Data of a module is out of the areas Check the setting of area
PNIO(C) mod data out that are mapped to robot I/O. The in I/O Controller Setup
PRIO-630 of area address of the data is displayed by the screen. Modify the
This is an additional
PRIO-631 IN: address (%d - %d) Error related to input data of a module. information of a previous
Error related to output data of a This is an additional
PRIO-632 OUT: address (%d - %d) module. information of a previous
PNIO: Updating Firmware update of PROFINET board is Wait until firmware
PRIO-633 Firmware started.
Firmware update is completed update is completed.
PRIO-634 PNIO: FW. updated successfully. Cold start the controller.
Firmware update is failed.
If the firmware is lost, set
PRIO-635 PNIO: FW. update failed Firmware update is failed. $PNIO_DL.$NO_FIRM_ST
PRIO-636 PNIO: XDB downloaded XDB configuration file is downloaded This is sure
Make just an
theinformation.
file name
PRIO-637 PNIO: Can't open file The specified file can't be opened. with device name is
PNIO: Not enough There is not enough memory in COMM Please contact FANUC
PRIO-638 memory processor for this operation. customer support.
Please show the cause
PNIO: Unsupported Configuration of unsupported feature is code to know what is not
PRIO-639 feature found. supported. Change the
IOPS=bad:api %x,st %d, I/O producer status of the specified Check the specified
PRIO-640 %d,%d module of PROFINET I/O has turned to module.
IOPS=good:api %x,st I/O producer status of the specified This is only a notification
PRIO-641 %d, %d,%d
Alarm %x:api %x,st %d,moduleindication
Alarm of PROFINET I/O has turned
of PROFINET I/O hasto of recovery.
Check the alarm data of
PRIO-642 %d,%d station %d
PNIO(C) come.
The device specified by the alarm the specified module
PRIO-643 activated message is activated. This is just a notification.
PNIO msg too long The length of a PROFINET message Check if the limit
PRIO-644 ch=%d(%d/%d) from I/F board exceeds the limit. parameter is adequate.
The number of unread alarm indication
gets too large. Probably there is no Set $READ=2 of
PNIO: many unread KAREL program that reads it out. Alarm PNIO_ALM.VR to read out
PRIO-645 alarm ind. indication should be read out because alarm indication.
IOCS=bad:api %x,st %d, I/O consumer status of the specified Check the specified
PRIO-646 %d,%d module of PROFINET I/O has turned to module.
IOCS=good:api %x,st I/O cosumer status of the specified This is only a notification
PRIO-647 %d, %d,%d module of PROFINET I/O has turned to of recovery.
PNIO(C) Too many Too many devices exist in PROFINET Decrease the number of
PRIO-648 devices
Too many I/O project. stations, I/O modules
Delete some and
unnecessary
PRIO-650 comments Too many I/O comments were set. I/O coments.
The memory size allocated in Delete old programs not
PROC-001 Allocated memory full. $PRCREP.$maxmem_siz has been filled. used anymore to clear old
Memory too LOW for There is not enough FROM or DRAM to Delete old programs not
PROC-002 logging. log any new process data. used anymore to clear old
Process Data remotely This is a notification that process data
PROC-003 cleared. was remotely cleared. No remedy required.
Process Data cleared This is a notification that process data
PROC-004 from TP. was cleared from the TP. No remedy required.
%s out of tol for PROG Alarm monitoring for specified item is Check your process to
PROC-005 %s, PROCESS ID=%d enabled, and logged value is not within verify it is within tolerance
Upp=%.1f,Low=%.1f,Act This is the CAUSE code for PROC-005. Check your process to
PROC-006 =%.1f This shows the limits and the actual verify it is within tolerance
Remedy: Delete old
PROC-007 Internal Error Software Internal Error programs not used
PAUSE. Document the events that
PROF-000 G System error(%d)
PROFIBUS PCB not System internal error led to the
Please error,
install and call
PROFIBUS
PROF-001 WARN PROFIBUS
PAUSE. installed PCB PROFIBUS is not installed PCB. exchange
Please
PROF-002 G
PAUSE. abnormal(%d) PROFIBUS PCB is abnormal. PROFIBUS
Please PCB
change
PROF-003 G
PAUSE. Slave Config data error Configuration data is abnormal. configuration
Please changedata on
parameter
PROF-004 G
PAUSE. Slave Param
Master Slavedata error Parameter data is abnormal.
Param data onchange
Please MasterSlave
PROF-005 G error(%d)
PAUSE. Another Master Slave Parameter sets is abnormal. Parameter
Please change setsslave
on R-J2
PROF-006 G
PAUSE. Lock(%d) Setting of slave is abnormal. setting.
Please change slave
PROF-007 G
PAUSE. Parameter
Invalid SlaveFault(%d) Setting of slave is abnormal. setting.
Please change slave
PROF-008 G Responce(%d)
PAUSE. Slave not Setting of slave is abnormal. setting.
Please change slave
PROF-009 G
PAUSE. supported(%d) Setting of slave is abnormal. setting.
Please change slave
PROF-010 G
PAUSE. Config Fault(%d) Setting of slave is abnormal. setting.
Please change slave
PROF-011 G
PAUSE. Slave not ready(%d) Setting of slave is abnormal. setting.
Please change slave
PROF-012 G
PAUSE. Slave not existent(%d) Setting of slave is abnormal. setting.
Please exchange
PROF-013 G
PAUSE. CMI error(code = %d) Master firmware is abnormal. PROFIBUS PCB
Please exchange
PROF-014 G
PAUSE. error(code
DP sub = %d)
error(code = Master firmware is abnormal. PROFIBUS
Please PCB
exchange
PROF-015 G
PAUSE. %d) communicatin
Slave Master firmware is abnormal. PROFIBUS
Please PCB
exchange
PROF-016 G
PAUSE. stop PROFIBUS PCB is abnormal. PROFIBUS PCB cable to
Please connect
PROF-017 G Slave disconnected Slave is disconected. Slave.
PAUSE. A status message exists in the slave Please invstigate the
PROF-018 G Exist specific diag(%d)
Multi-boards are not specific diagnostic area in
Multiple Profibus boards are not the received specific
Please setdiagnostic
only onedata.
PROF-019 STOP supported supported. Profibus board.
PROG-000 WARN Unknown error (PG0)
ABORT. Invalid pointer is RESET keys. 3. While still
PROG-001 LABORT. specified
Invalid task name is This indicates an internal system error. pressing the SHIFT and
PROG-002 L
ABORT. specified
Invalid prog name is The task name specified is invalid. Check the task name.
PROG-003 L
ABORT. specified
Invalid wait type is The program name specified is invalid. Check the program name.
PROG-004 L specified The specified program cannot be
PROG-005 WARN Program is not found found.
The specified line number cannot be Check the program name.
PROG-006 WARN Line is not found
Program is already found.
The specified program is already being Check the line number.
PROG-007 WARN Inrunning executed. cannot be started in sub-
a rtn when creating a Execution Check the program name.
PROG-008 WARN task routine program. Check the line number.
Line not same rtn as Resumption was attempted at a
PROG-009 WARN paused at different line from the paused line. Check the line number.
Resumption was attempted in a
PROG-010 WARN Not same prg as paused different program from the paused Check the program name.
PAUSE. Cannot get the motion enable switch and other
PROG-011 L control Motion control cannot be obtained. running programs to
All groups not on the There is paused motion later than Resume the motion
PROG-012 WARN top motion that was attempted to resume. paused the last time.
This motion was paused by the Use RESUME MOTION
Motion is stopped by MOTION PAUSE instruction. Only the instruction in the
PROG-013 WARN program RESUME MOTION program instruction program.
The number of programs you Abort dispensable
Max task number attempted to start exceeded the programs or perform a
PROG-014 WARN exceed
Cannot execute maximum number. CTRL
Do start
not useand select
backward
PROG-015 WARN backwards Backward execution cannot be used. execution at this point
Check the task name. The
task name is always the
The specified task is not running or name of the program that
PROG-016 WARN Task is not found paused. was run. The task name
PROG-017 WARN Motion
ABORT. Task is not running
stack The specified task is not running. Check the
Resume ortask name.
abort some
PROG-018 G overflowed Too many programs are paused. programs.
The request to pause the program was Change the NOPAUSE task
PROG-019 WARN Ignore pause request ignored.
The specified program was already attribute or use the KCL
PROG-020 WARN Task is already aborted aborted. Check the program name.
The request to abort the program was Change the NOABORT
PROG-021 WARN Ignore abort request ignored. task attribute or use the
PROG-022 WARN Invalid request type
PROG-023 WARN Not
Taskhave
is notmotion
paused The specified program is not paused. Pause
Do notthe program.
attempt
PROG-024 WARN history
Cannot execute The motion path record is lost. backwards
Do not use execution
backwardsat
PROG-025 WARN backwards Backward execution cannot be used. execution here.
Backward execution cannot be used Do not use backwards
PROG-026 WARN No more motion history any more. The current line is on top of execution here.
PROG-027 WARN Invalid task number The task number specified is invalid. Check the task number.
PROG-028 WARN Invalid buffer size
Buffer size is not RESET keys. 3. While still
PROG-029 WARN enough This indicates an internal system
The specified task attribute is not error. pressing the SHIFT and
PROG-030 WARN Attribute is write
not found The
found.
specified task attribute is write Check
Do notthe
try attribute.
to change the
PROG-031 WARN Invalid
protectedvalue for protected.
The value for the specified attribute is attribute.
PROG-032 WARN attribute
Arrived at the end of invalid. Check the attribute value.
PROG-033 WARN task Check the routine name
PROG-034 WARN Routine not found The specified routine cannot be found. and verify it is loaded.
Not locked the specified Motion control for the specified group enable switch and other
PROG-035 WARN group cannot be locked. running programs to
The length of trace Not enough memory or the task Set the trace buffer length
PROG-036 WARN array is 0
No data in the trace attribute is not set correctly.
There is no execution record in using thetracing
Turn on KCL SET TASK
using the
PROG-037 WARN array memory. KCL SET TRACE ON
Inconsistency in task
PROG-038 WARN status
Motion control for the specified group Check the teach pendant
was reserved, but it cannot be enable switch and other
PROG-039 WARN locked, but not get mctl obtained. running programs to
PAUSE. Already locked by other Motion control for the specified group Check the other running
PROG-040 L task was already reserved by another programs to determine
Motion control is released. The teach
mctl denied because pendant currently has motion control. Disable the teach
PROG-041 WARN released The robot cannot be started until pendant.
If you had expected that
the task may have already
PROG-042 WARN Already released Motion control was already released. released the group, this
Motion control was already released by the task may have already
PROG-043 WARN Already released by you request of this program. released the group, this
Arm has not been the task may have already
PROG-044 WARN released yet Motion control was not released yet. locked the group, this may
Other than requestor Motion control was already released by another task may have
PROG-045 WARN released the request of another program. already released the
PAUSE. TP is enabled while The teach pendant was enabled while Disable the teach pendant
PROG-046 L running (%s^7) the program is executing. and resume the program.
PAUSE. TP is disabled while The teach pendant was disabled while Enable the teach pendant
PROG-047 L running (%s^7) the program is executing. and use shift-FWD to
PAUSE. Shift released while The shift key was released while the Hold the shift key and
PROG-048 L running (%s^7) program is executing. press the FWD key to
Cannot release, robot Motion control cannot be released Check the status of robot
PROG-049 WARN moving because the robot is moving. motion.
Wait a second. If this error
continues to occur,
perform a cold start: 1.
The program is in the process of being and hold the SHIFT and
PROG-050 WARN Abort still in progress aborted. RESET keys. 3. While still
Cannot skip the return The specified lines to which a move was
PROG-051 WARN stmt attempted exceed the number of lines Check the line number.
The user application task was forced to
ABORT. Process is aborted while abort while the application is This requires no special
PROG-052 L executing executing. The AMR may not have been action for the user.
ABORT. The user application task was not Start the user application
PROG-053 LPAUSE. User AX is not running
FWD released while executed.
FWD key was released while the task
Holdbefore
the FWDexecuting
key withthe
PROG-054 L
PAUSE. running
BWD (%s^7)while
released program
BWD key iswas
executing.
released while the shift key
Hold the to
BWDresume
key with
PROG-055 L running (%s^7) program is executing. shift key to resume
ABORT. Motion data out is Motion data output function is enable Please disable motion
PROG-056 L enable instead of machin lock id disable. data output in test cycle
Power Fail Recover The backup of the execution memory Cycle power to the
PROG-057 memory is cleared failed. Then, the system restarted controller.
Pausing when using M-TP. This error Push the OK button,
PROG-058 Pause[P] happens only when using the M- restart the program, or
Abnormal Abnormal communication with the M- Power OFF and ON the
PROG-059 communication[P] TP. This error happens only when using controller.
Don't set FANUC's An attempt was made to set FANUC's Don't set FANUC's uframe
PROG-060 uframe[P] uframe. This error happens only when when using the M-TP.
GD variable which is used by SHIFT-ON
command is not set. This error happens
PROG-061 Set GD[%s][P] only when using the M-TP(J897) option. Set the GD variable.
This error happens only when using the
PROG-062 Using in SHIFT-ON[P] M-TP(J897) option. Set the GD variable.
This error happens only when using
PROGRAM/JOG OVERRIDE Stop jog operation is
PROG-063 Robot is moving by JOG function(J579). PROGRAM was executed.
This error is caused when a internal Write down the exact
problem has occurred within the Paint error number and
Plug In software. This fault is almost message shown. Write
always caused by style paths which do down exactly what your
things which were not anticipated robot was doing at the
when this software was written. The time of the failure. Make
reasons for this could be: 1. The path is sure you include: Program
too fast 2. The instructions (PPS and name, line number,
Paint Plug-In internal PPE) are too close together 3. The delay robot's location in the
PTPG-000 error and timing values specified in your work cell, any cell I/O or
This error is caused when a internal Write down the exact
problem has occurred within the Paint error number and
Plug In software. This fault is almost message shown. Write
reasons for this could be: 1. The path is sure you include: Program
too fast 2. The instructions (PPS and name, line number,
PPE) are too close together 3. The delay robot's location in the
PTPG-001 %s and timing values specified in your work cell, any cell I/O or
Karel Application Task A citical task required to run the Paint Contact your FANUC
PTPG-002 Failure Plug In software is missing or not America Corporation
A TP Event Instruction was called
(PPS[x] or PPE), but the corresponding Ensure the missing TP
PTPG-003 Missing %s TP program This
TP program
error is or sub-program
usually caused bywas not
a system program
Check TPEisinstructions.
loaded.
PTPG-004 Critical IO is invalid failure. Cycle power on controller.
The schedule index value of the current Check the index value of
PTPG-005 Index incorrect instruction execution is invalid. instruction.
The current Job has been aborted due Correct the cause of this
PTPG-006 Job %s aborted to a fatal error. error, which is usually
The Group Mask attribute in the TP Ensure that the Group
PTPG-007 %s:Invalid Group Mask header of the specified program is set. mask is NOT set for the
%s:Unknown Paint The Paint Plug-In detected an unknown Determine the cause for
PTPG-008 Event Paint Event, which caused the system this unknown event to
%s:Event TP Prog An Event TP program did not complete Ensure that the TP
PTPG-009 Timeout processing within the specified time. program instruction is
The Paint Plug-In detected a Paint Ensure that a PPE
Start(PPS[]) TP instruction without a instruction is included at
PTPG-010 No PPE Instruction matching Paint End (PPE) instruction. the end of the job.
%s No PPS Instruction The Paint Plug-In detected a Paint End Ensure that a PPS
PTPG-011 before PPE (PPE) instruction without a Paint Start instruction is included
A user with Install level access logged This is a status message
PWD-001 WARN Login (%s) Install in. you can use for tracking
A user with Install level access logged This is a status message
PWD-002 WARN Logout (%s) Install out. you can use for tracking
A user with Setup level access logged This is a status message
PWD-003 WARN Login (%s) Setup in. you can use for tracking
A user with Setup level access logged This is a status message
PWD-004 WARN Logout (%s) Setup out. you can use for tracking
A user with Program level access logged This is a status message
PWD-005 WARN Login (%s) Program in. you can use for tracking
A user with Program level access logged This is a status message
PWD-006 WARN Logout (%s) Program out. you can use for tracking
A user was logged out because of a Log in, if required. Adjust
PWD-007 WARN Password Timeout (%s) password timeout. the timeout value if it is
PWD-008 WARN Create program %s.TP A teach pendant program was created. you can use for tracking
PWD-009 WARN Delete program %s.TP A teach pendant program was deleted. you can use for tracking
A teach pendant program was This is a status message
PWD-010 WARN Rename %s.TP as %s.TP renamed. you can use for tracking
Set %s.TP subtype from A teach pendant program subtype was This is a status message
PWD-011 WARN %s to %s changed. For example, a .TP program you can use for tracking
A teach pendant program comment This is a status message
PWD-012 WARN Set %s.TP comment was edited. you can use for tracking
The group mask of a teach pendant This is a status message
PWD-013 WARN Set %s.TP group mask program was changed. you can use for tracking
Set %s.TP write protect Write protection was enabled for the This is a status message
PWD-014 WARN on program. This helps prevent mistaken you can use for tracking
Set %s.TP write protect Write protection was disabled for the This is a status message
PWD-015 WARN off program. The program can be edited. you can use for tracking
Set %s.TP ignore pause The ignore pause feature was enabled This is a status message
PWD-016 WARN on for the program. you can use for tracking
Set %s.TP ignore pause The ignore pause feature was disabled This is a status message
PWD-017 WARN off for the program. you can use for tracking
A teach pendant program line was This is a status message
PWD-018 WARN Write line %d, %s.TP edited. you can use for tracking
A teach pendant program line was This is a status message
PWD-019 WARN Delete line %d, %s.TP deleted. you can use for tracking
A teach pendant program position was This is a status message
PWD-020 WARN Write pos %d, %s.TP recorded. you can use for tracking
A teach pendant program position was This is a status message
PWD-021 WARN Delete pos %d, %s.TP deleted. you can use for tracking
Renumber pos %d as A teach pendant program position This is a status message
PWD-022 WARN %d, %s.TP number was changed. you can use for tracking
For some tool products, a teach This is a status message
Set application data pendant program may contain you can use for tracking
PWD-023 WARN %s.TP application related data. This message operations performed by
For some tool products, a teach This is a status message
Delete application data pendant program may contain you can use for tracking
PWD-024 WARN %s.TP application related data. This message operations performed by
PWD-025 WARN Load %s The named file was loaded. you can use for tracking
The named file was loaded. The This is a status message
PWD-026 WARN Load %s as Program %s program name may differ from the file you can use for tracking
A schedule was edited. Press HELP for This is a status message
PWD-027 WARN Edit %s Sch %d %s more information. you can use for tracking
The data in a schedule was copied to This is a status message
PWD-028 WARN Copy %s Sch %d to %d another schedule. you can use for tracking
The schedule was cleared, meaning the This is a status message
PWD-029 WARN Clear %s Sch %d values were set to zero. you can use for tracking
This message is used to provide This is a status message
detailed information for PWD-027. For you can use for tracking
PWD-030 WARN (%s to %s)%s example: PWD -027 Edit Weld Sch 1 operations performed by
The Operator password level does not Press the TP MENUS
have access to the FULL MENUS. Either hardkey and select SETUP
a timeout occurred or a user logged PASSWORDS. Log in with
PWD-031 WARN QUICK MENUS forced out. either the Install, Setup,
Login (%s) Install from A user with Install level access logged in This is a status message
PWD-032 WARN SMON from SMON. you can use for tracking
PWD-033 WARN KCL from KCL. you can use for tracking
PWD-034 WARN Teach Pendant from Teach Pendant. you can use for tracking
PWD-035 WARN CRT/Keyboard from CRT/Keyboard. you can use for tracking
Logout (%s) Install from A user with Install level access logged This is a status message
PWD-036 WARN SMON out from SMON. you can use for tracking
PWD-037 WARN KCL out from SMON. you can use for tracking
PWD-038 WARN Teach Pendant out from SMON. you can use for tracking
PWD-039 WARN CRT/Keyboard out from SMON. you can use for tracking
Login (%s) Setup from A user with Setup level access logged This is a status message
PWD-040 WARN KCL in. you can use for tracking
PWD-041 WARN Teach Pendant in. you can use for tracking
PWD-042 WARN CRT/Keyboard in. you can use for tracking
Logout (%s) Setup from A user with Setup level access logged This is a status message
PWD-043 WARN KCL out from KCL. you can use for tracking
PWD-044 WARN Teach Pendant out from Teach Pendant. you can use for tracking
PWD-045 WARN CRT/Keyboard out from CRT/Keyboard. you can use for tracking
Login (%s) Program A user with Program level access logged This is a status message
PWD-046 WARN from Teach Pendant in from Teach Pendant. you can use for tracking
Login (%s) Program A user with Program level access logged This is a status message
PWD-047 WARN from CRT/Keyboard in from CRT/Keyboard. you can use for tracking
Logout (%s) Program A user with Program level access logged This is a status message
PWD-048 WARN from Teach Pendant out from Teach Pendant. you can use for tracking
Logout (%s) Program A user with Program level access logged This is a status message
PWD-049 WARN from CRT/Keyboard out from CRT/Keyboard. you can use for tracking
Pwd Timeout (%s) from A user was logged out because of a Log in, if required. Adjust
PWD-050 WARN SMON password timeout from SMON. the timeout value if it is
PWD-051 WARN KCL password timeout from KCL. the timeout value if it is
PWD-052 WARN Teach Pendant password timeout from Teach Pendant. the timeout value if it is
PWD-053 WARN CRT/Keyboard password timeout from CRT/Keyboard. the timeout value if it is
Login (%s) %s from A user with Install level access logged in This is a status message
PWD-054 WARN Internet from the Internet. you can use to track
Logout (%s) %s from A user with Install level access logged This is a status message
PWD-055 WARN Internet out from the Internet. you can use to track
Pwd Timeout (%s) from A user was logged out because of a Log in if required.
PWD-060 WARN Internet password timeout from the Internet. Lengthen the timeout
As a result of a user login, the pendant This is a status message
PWD-061 FULL MENUS
Login from USBforced
device is using Full Menus instead of Quick you can use to track
PWD-062 is cancelled
User (%s) already You cannot
Another userlogin to thislogged
is already device.in to this
Check the cause code.
PWD-063 logged
User in time
(%s) device.
The user password timeout has been Log out the other user.
PWD-064 extended extended. No action required.
Password USB device A password USB device has been This is a status message
PWD-065 inserted inserted. you can use to track
For the first cause, check
the password USB device.
There are 2 causes for this alarm. The Your INSTALL user may
first is that the password USB device have to add your
has incorrect username and password. username and password
This will be the cause code for PWD- using the SETUP
062 Login from USB device is cancelled. Passwords menu. For the
The second is that a password second cause, the INSTALL
configuration file, FRS:PASSWORD.DT, user should IMPORT a
PWD-066 Bad password data is invalid. correct password
You must log in using the
You attempted to perform an SETUP Passwords menu. If
Edit operation not operation that was password the operation is still not
PWD-067 WARN allowed protected. allowed, you might need
SETUP Passwords menu. If
Menu access is not You attempted to display a menu that the operation is still not
PWD-068 WARN allowed was password protected. allowed, you might need
You attempted to perform an SETUP Passwords menu. If
Operation password operation that was password the operation is still not
PWD-069 WARN protected protected. allowed, you might need
To enable passwords, go
PWD-070 WARN Passwords disabled Passwords have been disabled. to the SETUP Passwords
This operation is protected in TP
PWD-071 Protected in TP disable disable by password autologin function. Enable TP.
Protected in AUTO This operation is protected in AUTO
PWD-072 mode mode by password autologin function. Change to T1 or T2 mode.
PWD-073 Auto login (%s) %s Auto login is executed. None.
PWD-074 Auto logout (%s) %s Auto logout is executed. None.
A teach pendant storage attribute was This is a status message
PWD-075 Set %s.TP Storage to %d changed. you can use for tracking
An attempt was made to add entry to a Use GET_QUEUE to
QMGR-001 WARN Queue is full queue when the queue was full. remove entries or use a
An Attempt to use GET_QUEUE when
there are no entries in the queue This is
the normal result when no entries have
QMGR-002 WARN Queue is empty been added or all have been removed No remedy is required.
A bad sequence_no value is used in an
INSERT_QUEUE or DELETE_QUEUE call.
The value may be less than 1 or greater
QMGR-003 WARN Bad sequence no than
n_skip the sequenceinnumber
parameter of the last
COPY_QUEUE call Correct
Use zerotheor value
a positive
QMGR-004 WARN Bad n_skip value is less than zero value
If this continues to
System network timing has been lost. happen, the physical
The system has automatically been Network wiring
RIPE-001 WARN Time is resynchronized reestablished. configuration and setup
FRS:ROSIPCFG.XML not System network timing has been lost If this continues to
RIPE-002 WARN found but the system has automatically happen, the configuration
FRS:ROSIPCFG.XML has The syntax of ROSIPCFG.XML is not Consult TD:RIPINIT.TXT for
RIPE-003 WARN %d warnings correct. detailed warnings and
RIPE-004 WARN Tracking error An internal error has occurred. led to the error, and call
The rosipcfg.xml is different among the Make sure that all
RIPE-005 %s bad configuration controllers in the RING controllers have identical
RIPE-006 WARN Bad destination CPU ID An internal error has occurred. led to the error, and call
This is a notification that a robot has
gone offline. This is posted whenever a
RIPE-007 WARN %s is offline member robot is turned off or None
RIPE-008 WARN %s is online member robot is turned on or plugged None
Information about a member is
Member data is updated. This is only posted in a system
RIPE-009 WARN updated which is not automatically None
The indicated robot has had its
RIPE-010 WARN %s has been reset protocol reset. This might be the cause None
This robot is not in the The IP address of this robot is not The configuration must
RIPE-011 WARN ring found anywhere in FRS:ROSIPCFG.XML. include the correct IP
Initial time An initial tick time synchronization has
RIPE-012 WARN synchronization occured. This message is posted after None
Robot not found in ring A robot specified in a destination is not The configuration must
RIPE-013 WARN data part of the ring defined in include information on all
The system has attempted to send a Document the events that
RIPE-014 WARN Packet is too large packet which is too large. The limit is led to the error, and call
Packet cannot round A packet sent to all robots cannot be a Document the events that
RIPE-015 WARN trip round trip packet. led to the error, and call
Robot time not A call was made to get network tick Wait for the synchronized
RIPE-016 WARN synchronized before the system ticks are message before
Time tracking A call was made to get network tick Wait for the synchronized
RIPE-017 inconsistent before the system ticks are message before
RIPE-018 Robot is offline member robot is turned off or None
More than 48 requests are queued to Check the network
RIPE-019 Overrun condition RIPE have not been processed hardware. Structure the
The ROSIPCFG.XML file is not the same Make the ROSIPCFG.XML
RIPE-020 Bad configuration among the robots. file the same.
A robot has had its protocol reset This is for information
RIPE-021 Robot has been reset similar to going online and offline. only but could be the
Messages were received out of Power cycle may be
RIPE-022 Robot has resequenced sequence. This could be due to bad required to reset
Robot resequence Messages were received out of Power cycle may be
RIPE-023 response sequence.
CPU This
is busy, could
RIPE maybe due to bad
experience required to reset
RIPE-024 RIPE CPU busy %d difficulties. Check/reduce CPU load.
ROUT-001 WARN
ROUT-002 WARN
ROUT-003 WARN
ROUT-004 WARN
ROUT-005 WARN
ROUT-006 WARN
ROUT-007 WARN
ROUT-008 WARN
ROUT-009 WARN
ROUT-010 WARN
ROUT-011 WARN
ROUT-012 WARN
ROUT-013 WARN
ROUT-014 WARN
ROUT-015 WARN
ROUT-016 WARN
ROUT-017 WARN
ROUT-018 WARN
ROUT-019 WARN
ROUT-020 WARN
ROUT-021 WARN
PAUSE. Incorrect number is specified for ORD Specify a number less
ROUT-022 G Bad index in ORD builtin routine. than the string length.
PAUSE. Incorrect number is specified for Specify a number less
ROUT-023 G Bad index in SUBSTR SUBSTR builtin routine. than the string length.
PAUSE. SUBSTR length less than Negative number is specified for length
ROUT-024 G
ABORT. 0
Illegal semaphore argumentnumber
Incorrect for SUBSTR builtin routine.
is specified for positive number.
Specify a number
ROUT-025 G number semaphore id. betweenexisiting
Specify 1 and 32.
group
ROUT-026 WARN Illegal group number Invalid group number is specified. number.
String size not big Specified string variable does not have specify larger size string
ROUT-027 WARN enoughfile attribute
ABORT. Illegal enough room to hold the return data. variable.correct file
Specify
ROUT-028 G
ABORT. number
Illegal file attribute id waswas
Incorrect file attribute value specified. attribute
Specify id. attribute
correct
ROUT-029 G value
Non existent register specified.
A non-existent register number is value.
Specify a correct register
ROUT-030 WARN number specified. number.
Specify the correct
ROUT-031 WARN
ABORT. Illegal register type Incorrect register type is specified.
Position type is not correct for the register type forposition
Specify correct the
ROUT-032 G
ABORT. Position type mismach operation. type. correct attribute
Specify
ROUT-033 G Illegal attribute type Illegal attribute id was specified. id.
Specify a program name
ROUT-034 WARN Not a TPE program A non-tpe is specified. other than a Karel
Specify a value within the
ROUT-035 WARN
ABORT. Value is out of range The specified value is out of range. range.
ROUT-036 G
ABORT. Illegal port id value Incorrect
Value used port id was used
in SET_HEAD_TPE for Specify correct
Use buffer port
size in theid.
ROUT-037 G Bad TPE header size bfr_size is invalid. range 1-255.
PAUSE. Uninitialized TPE Attempt to access position data or type Record position data using
ROUT-038 G position from
CannotTPE program
unlock when
group whilethemotion
position
is the
WaitTPP TOUCHUP
until executing
ROUT-039 WARN Executing motion exists executing. motion has completed.
Cannot unlock group while stopped Resume stopped motion
ROUT-040 WARN Stopped motion exists motion exists. and wait until motion has
Variable displayed for dynaoic display is Copy constant or local
not a static variable. Parameter may be variable to static variable
ABORT. Dym. disp. var. not a local or constant. Neither of these is and use this
ROUT-041 G static permitted as the displayed variable in inINI_DYN_DIS* call.
TPE parameters do not The parameter designated by Confirm the param_no
ROUT-042 WARN exist param_no does not exist. and the parameter in
TPE parameter %s The parameter data type does not Confirm the parameter
ROUT-043 WARN wrong data type match the CALL/MACRO argument data data type in CALL/MACRO
Tag name supplied in MSG_CONNECT, Use tag name not over 12
ROUT-044 WARN Tag name too
Dictionary long
name too MSG_DISCO,
Dictionary or MSG_PING
name supplied incall was too
built-in call characters.
Use name of 4 or less
ROUT-045 WARN long is too long. characters.
Option array not Call to apnd_mtn_opt, write_xyzwpr, Initialize the array by
ROUT-046 WARN initialized or write_joint with option array not calling INIT_MTN_OPT
Stream instruction program buffer is Wait for stream program
ROUT-047 WARN Stream buffer full full. streaming program is not currently
The execution
Issue to complete
the function on an
ROUT-048 WARN Stream not active running. active stream program.
The motion option data supplied in the
motion write routine call is not valid, or Initialize and fill the
ROUT-049 WARN Invalid motion options does not match the specified motion motion options correctly.
A string containing over 16 characters
SET comment builtin passed as comment argument in Use comment string of 16
ROUT-050 WARN string too long SET_TPE_CMT call. Argrument or fewer characters.
Can't encode The client could not encode its
RPC-001 WARN arguments arguments in a remote procedure call. Check the cause code.
The client could not decode the results
RPC-002 WARN Can't decode result of a remote procedure call. Check the cause code.
The client could not send the data for a
RPC-003 WARN Unable to send remote procedure call. Check the cause code.
The client could not receive a reply
RPC-004 WARN Unable to receive from a remote procedure call. Check the cause code.
The client timed out while waiting for a Check the server
RPC-005 WARN Call timed out reply from a remote procedure call. connection.
Incompatible versions The server received an older version of Update the client
RPC-006 WARN of RPC the RPC protocol. software to use the same
The client or server received an
RPC-007 WARN Authentication error unauthorized remote procedure call. Check the cause code.
The server received a remote Update the server
RPC-008 WARN Program unavailable procedure call for a program which it software.
Program/version The server received a remote Update the client or
RPC-009 WARN mismatch procedure call which uses the wrong server software.
The server received a remote Update the server
RPC-010 WARN Procedure unavailable procedure call for a procedure which it software.
Server can't decode The server could not decode the
RPC-011 WARN arguments arguments of a remote procedure call. Check the client software.
RPC-012 WARN Remote system error
The client could not determine the Check the system
RPC-013 WARN Unknown host server for the remote procedure call. variables which configure
RPC-014 WARN Port mapper failure
RPC-015 WARN Program not registered
Remote procedure call
RPC-016 WARN failed The remote procedure call failed. Check the cause code.
RPC-017 WARN Unknown protocol
The server received a remote
procedure call which uses the wrong Update the client or
RPC-018 WARN Low = %d, High = %d version of a program. The versions server software.
Install the PC Interface
PC Interface option not This operation requires the PC Interface software option on the
RPC-019 WARN loaded option to be loaded on the controller. controller. Refer to the
RPC-021 WARN Invalid client credential
Server rejected
RPC-022 WARN credential
RPC-023 WARN Invalid client verifier
RPC-024 WARN Servercredential
Client rejected verifier
too
RPC-025 WARN weak
RPC-026 WARN Invalid server verifier
RPC-027 WARN Authentication failed The value for Set
RPM-001 WARN n_buffers invalid $RPM_CONFIG.$N_BUFFERS
The value for is invalid $RPM_CONFIG.$N_BUFFE
Set
RPM-002 WARN record_size invalid $RPM_CONFIG.$DATA_SIZE is invalid $RPM_CONFIG.$DATA_SIZ
RPM-003 WARN n_segments invalid
RPM-004 WARN
SYSTE n_recordsallocation
memory invalid
RPM-005 M
PAUSE. failed
RPM-006 G
PAUSE. invalid record no.
RPM-007 G
PAUSE. no data blocks left
RPM-008 G program id is different
PAUSE. Attempt to playback a segment that is Check that RECORD is
RPM-009 G
PAUSE. segment not in buffer not recorded in the specified buffer active for this segment
RPM-010 G
PAUSE. invalid record_offset
RPM-011 G
PAUSE. all segments
segment usedin
already
RPM-012 G buffer
PAUSE. Use a buffer number in
RPM-013 G
PAUSE. invalid buffer no Buffer number specifed is invalid the range 1-
RPM-014 G record not stored This segment was not recorded Re-record the whole path
RPM-015 WARN use of RPM SP's bef. init
RPM-016 WARN change in pitch mode
RPM-017 WARN change in distance
RPM-018 WARN not in playback mode
RPM-019 WARN all data records used There is no rpm data is stored in this Check the position
RPM-020 WARN read record not stored segment number Or re-record
RPM-021 WARN not in record mode
RPM-022 WARN store in same record
RPM-023 WARN
PAUSE. no TIR
No datafor
inmotion
specified
RPM-024 G
PAUSE. buffer
Unexpected restart
RPM-025 G
PAUSE. dest. Time pitch value have to
RPM-026 G
PAUSE. Pitch value too small. Pitch value is too small equal
Use or greater
motion than arc
attached 100
RPM-027 G Illegal arc instruction. Stand alone arc start used start instruction
PAUSE. The segment for RPM is either zero Zero length RPM motion is
RPM-028 G Segment too short length move or too short not allow
ERR_ST Incompatible RPM RPM data has coordinated motion but Use same coordinated
RPM-039 OP_C data:nonCD/CD TPE doesn't have. Or RPM data has non- motion type (CD or non-
The system may have
Internal PLAN error. This class of error or additional software not
Internal PLAN error (G: should not be encountered during on the original software
RRMC-001 %d^2) normal operation distribution media is the
The system may have
Internal INTR error (G: should not be encountered during on the original software
RRMC-002 %d^2) normal operation distribution media is the
The system may have
Internal RRMC error. This class of error or additional software not
Internal RR error (G: should not be encountered during on the original software
RRMC-003 %d^2) not Supported normal operation
Feature distribution
Disable media isand
the feature the
RRMC-004 (G: %d^2) RRMC does NOT support this feature. try again
RRMC ran out of memory during Check the memory
RRMC-005 Out of memory
Simulated Hold (G: initialization. configuration Use a larger
RRMC-006 %d^2)
Simulated E-Stop (G: RRMC simulated Hold. Reset and cycle start.
RRMC-007 %d^2) RRMC simulated
EPC[sch_id] doesE-Stop.
not have legal Reset and
Please reset cycle start
a legal
RRMC-008 Illegal schedule number
Invalid position in number.
The schedule does not have valid number in the instruction
Please set up the schedule
RRMC-009 schedule
Please set up the position defined. correctly
Please set up the schedule
RRMC-010 schedule The schedule has not been set yet correctly
LNSCH num mismatch The Line tracking program schedule Please set up the schedule
RRMC-011 L:%d^5 number does not match the track correctly
The commanded elbow point moves Please modify taught
RRMC-012 Cross constraint L:%d^5 from one side of constraint to other point accordingly or
Can't meet constraint The specified constraints cannot be Please modify the
RRMC-015 L:%d^5 satisfied at this moment. constraint correctly
EP changes too large (G: The elbow point of the redundant
RRMC-020 %d^2)
Too Large Jnt Cmd robot changes
Internal toomotion
Error: Jnt large incommand
one ITP cycle re-execute
is Report the the
issue!motion
Abort
RRMC-021 (G:%d^2 A:%s^7) too large the program and try again
Invalid constraint type The specified constraint schedule does Please set up the schedule
RRMC-022 L:%d^5
Limit error (G: %d^2 not define a valid Plane type. correctly.
Please adjust taught
RRMC-023 A:%s^7)
EP T1 spd excess (G: The axis joint angle exceeds limit point(s)this
Report accordingly.
issue right
RRMC-024 %d^2) Elbow point speed is high under T1. away.
PAUSE. Wrist joint orient type resume is not Change
RTCP-001 G
PAUSE. Wrist Joint is not allow allow in RTCP motion. $MCR_GRP[*].$RSM_ORIE
Change UTool No. for
RTCP-002 G
PAUSE. not calibrated
VRTCP Invalid UTool Invalid UTool for VRTCP. VRTCP.
Use different Leader GP
RTCP-003 G
PAUSE. No. overlapped
VRTCP Some VRTCPs have same Remote Leader GPTCPNo. Use
No. different Remote TCP
RTCP-004 G
PAUSE. Leader Group
VRTCP overlapped RTCP No. No.
RTCP-005 G
SYSTE No. pulse to angle
VRTCP Conversion
A conversionfailure
failurefrom pulse from
occurred to angle. Do COLD start.
RTCP-006 M conv. pulse to angle. Perform a Cold start.
DRTCP use FINE for DRTCP use FINE as term type for a Change the termination
RTCP-007 STOP transition DRTCP transition. type to FINE for the
DRTCP Joint pos not Data recorded can not be a joint Re-Record the position
RTCP-008 STOP allow represenation type for a DRTCP
DRTCP Joint move not DRTCP coordinate jog does not allow line. with
Use aCartisian
Cartesiantype.move
RTCP-009 STOP allow joint jog. instead.
DRTCP INC move not DRTCP does not allow incremental Use absolute recording
RTCP-010 STOP allow instruction position
RESET keys. 3. While still
RTCP-011 STOP DRTCP Internal Error 1 DRTCP internal error 1. pressing the SHIFT and
RTCP-012 STOP DRTCP Internal Error 2 DRTCP internal error 2 pressing the SHIFT and
RTCP-013 STOP DRTCP Internal Error 3 DRTCP internal error 3 pressing the SHIFT and
Program with RTCP option was
RTCP not supported executed while COORD option is loaded Remove RTCP option from
RTCP-014 STOP with COORD on controller. RTCP cannot be used TP program.
This option (Weave, Touch sensing, Remove the RTCP option
Option+RTCP not TAST , RPM..) is enabled with a RTCP from the teach pendant
RTCP-015 supported
DRTCP C move not Motion RTCP cannot be used when this program.
RTCP-017 allow DRTCP does not allow Circular Motion Use Arc motion.
SCIO-000 WARN ?????
SCIO-001 WARN constants type is illegal
SCIO-002 WARN data size is illegal
You cannot add the instruction to the Please reduce the
same line. The size of mnemonic code instruction like a
SCIO-003 WARN Cannot teach any more. exceeds maximum size of one line data. parameter string.
SCIO-004 WARN write
top offlag is illegal.
string is not $ in
SCIO-005 WARN scwrtpar
read line is illegal when
SCIO-006 WARN call mmreadln
opw_sw is illegal in
SCIO-007 WARN xxmov routine
SCIO-008 WARN interp. type
string size is is illegal
illegal in
SCIO-009 WARN xxstr routine
string size is illegal in
SCIO-010 WARN xxlbl routine
SCIO-011 WARN xxcal routine
SCIO-012 WARN xxpar routine
SCIO-013 WARN xxpro routine
SCIO-014 WARN opt_sw
pos typeisisillegal
illegal in
SCIO-015 WARN xxmov routine
Determine what options
are installed on the
controller on which the
program was saved
(source cpntroller) and
The TPP program being loaded uses an are not installed on the
option which is not installed on the target controller Then, on
Prog uses un-installed controller where the program is being the source controller,
SCIO-016 WARN option. loaded (target controller). check which of these is
checksum did not
SCIO-017 WARN match
SCIO-018 WARN option switch
chechk is illegal
sum error
SCIO-019 WARN pos_id =%d
LBL[%d] exists in line Select another label
SCIO-020 WARN %d: This label number exists in another line. number.
SCIO-021 WARN EPT_idx is different
SCIO-022 WARN from before power
Line number is 0, when
SCIO-023 WARN screcov is called
SCIO-024 WARN recov_sw is illegal
JOINT motion in slave Robot Link slave program and slave Record this line as LINER
SCIO-030 WARN program alone program can not use JOINT or CIRCULAR motion
JOINT position in slaveRobot Link slave program and slave Record this line as
SCIO-031 WARN program alone program can not use JOINT CARTESIAN position
Current Tool frame number of Master Change Tool frame
robot is different from Master Tool number of Master Robot
SCIO-032 WARN Master UT mismatch Number specified in Program detail or change master tool
Slave can have ony one Robot link Slave program can have only Please teach only one line
SCIO-033 WARN motion line one motion line. in slave program.
The program might be
Illegal fn code of TUI FN An illegal FN code is found in the TUI broken. The system
SCIO-034 instruction FN instruction. software might be older
[STSTEPON] Single Step KAREL program of System Design Tool This message is reference
SDTL-001 ON request to turn single step to ON. only. No action is
[STSTEPOF] Single Step KAREL program of System Design Tool This message is reference
SDTL-002 OFF request to turn single step to OFF. only. No action is
Failed to switch English dictionary from Do not execute
stlangeg. Probably English dictionary is STLANGEG.PC or add the
SDTL-003 No English dictionary not installed. order of English
Do not execute
Failed to switch Japanese from stlangjp. STLANGJP.PC or add the
SDTL-004 No Japanese dictionary Probably Japanese is not installed. order of Japanese
Language was changed to English by This message is reference
SDTL-005 Changed to English stlangeg. This is just warning. only. No action is
Language was changed to English by This message is reference
SDTL-006 Changed to Japanese stlangjp.
SpecifiedThis is just
DT file warning.
is invalid in TPP only. No action is
SDTL-007 Invalid file list MEMORY ASSIT.
Device name was not found in the Input correct DT file
:\ after device
SDTL-008 :\\ not found parameter. name.
SDTL-009 Too long name Specified
NULL nameparameter was too
was specified as along. Shorten the DT file name.
SDTL-010 No name
TPE parameter %s parameter Input correct name.
SDTL-011 wrong data type Invalid parameter was specified. Set correct parameter.
SDTL-012 Not STRING Parameter type not STRING Set correct type.
SDTL-013 Not INTEGER Parameter type not INTEGER Set correct type.
SDTL-014 Not REAL Parameter type not REAL Set correct type.
SDTL-015 %s not found Program not found Set program
Maybe the program listed
SDTL-016 Failed to save %s Failed to save program. in specified dt file is
SDTL-017 Failed to load %s Failed to load. in specified dt file is
SDTL-018 Failed to delete %s Failed to delete in
Setspecified
file list todtspecified
file is
SDTL-019 %s not found File list not found device as parameter.
SDTL-020 File reading error File reading error. Refer to whether
Confirm cause code the
SDTL-021 TPE parameter not exist TPE parameter not exist. parameter is correct.
SDTL-022 Failed to load %s Failed to load specified program See cause code
Specified program is in The program you specified for load or Specified program is
SDTL-023 use delete
The is opened
program youfor another
specified forfunction.
load or opened. Abort
Specified the is
program
SDTL-024 Paused delete is paused. paused. Abort the
The program you specified for load or Abort the program. If
delete cannot be loaded or deleted. It teach pendant displays 2
was not because the program was used or more screens and one
by another function. It was not because of them displays the
SDTL-025 %d the program was paused. This alarm is program, display another
SDTL-026 Failed to delete %s Specified program cannot be deleted. See cause code
Not enough TEMP Contact your FANUC
SDTL-027 memory used by other
Variable TEMP does not have enough space. Americaother
Delete Corporation
program
SDTL-028 program Variable is used by another which references these
SDTL-029 register
Failed to set to position regsiter
Failed to set the value to position Refer to the Cause code.
SDTL-030 register register Refer to cause code.
Refer to cause code and
Failed to get the robot remove cause of it. If
SDTL-031 position
Failed to get max Failed to get real position cause code is not
SDTL-032 currentconverting to
Failed Failed to get max current Refer to cause code.
SDTL-033 REAL value Failed converting to REAL value Refer to cause code.
Check Current (GTCURCUR.PC), Check
Servo Hand Grip Status (CKSVHCUR.PC),
Get Max Current (GTMAXCUR.PC), Get
Real Position (GTRELPOS.PC), Set
Failed to get TPE Current Position to Register
SDTL-034 parameter %s (STPOSREG.PC) or Set Current Position Refer to cause code.
Check Current (GTCURCUR.PC), Check
Servo Hand Grip Status (CKSVHCUR.PC),
Get Max Current (GTMAXCUR.PC), Get
Real Position (GTRELPOS.PC), Set
TPE parameter %s Current Position to Register Refer to cause code and
SDTL-035 wrong data type (STPOSREG.PC) or Set Current Position remove cause of it.
Specified parameter is not string. This
SDTL-036 Not STRING alarm is cause code of SDTL-035. Input string as parameter.
Specified parameter is not integer. This Input integer as
SDTL-037 Not INTEGER alarm is cause code of SDTL-035. parameter.
Specified parameter is not real number. Input real value as
SDTL-038 Not parameter
TPE REAL %s is out This alarm is cause code of SDTL-035. parameter.
SDTL-039 of range
TPE parameter %s TPE parameter %s is out of range Set correct parameter.
SDTL-040 wrong data type Invalid parameter was specified. Set correct parameter.
Specified parameter is not integer. This Input integer to the
SDTL-041 Not INTEGER alarm is cause code of SDTL-040. parameter of group
Specify correct
SDTL-042 Illegal group number Invalid group number is specified. number.correct axis
Specify
SDTL-043 Illegal axis number Invalid axis number is specified. number.
String size not big Specified string variable does not have Specify larger size string
SDTL-044 enough type is not
Variable enough room
Specified to hold
system the return
variable data.
is not string variable.string type
Specify
SDTL-045 compatible type. variable.
SDTL-046 Illegal variable Illegal variable is specified. See cause code.
TPE parameter %s Specified parameter of Set String to Set correct string or string
SDTL-047 wrong data type System Variable (STSYSSTR.PC) is wrong register index to the
Displayed line of specified
file has problem. String at
which X_DYNDAT
Execution of X_DYNDAT causes this detected error is
Wrong data type(Line error. Wrong data type (identifier) is displayed, too. Even if the
SDTL-048 %s) specified in CSV file. string is valid identifier for
Execution of X_DYNDAT causes this Check displayed line of
Illegal terminator(Line error. Terminator is expected at the CSV file. Confirm data
SDTL-049 %s) end of a line of CSV file but it was not format and add
Check displayed line of
Execution of X_DYNDAT causes this CSV file. String at which
error. Wrong index is specified in CSV X_DYNDAT detected error
SDTL-050 Illegal index(Line %s) file. is displayed, too. Check
error. Wrong formatted data is found CSV file. String at which
SDTL-051 Illegal group(Line %s) where group number should be X_DYNDAT detected error
SDTL-052 Illegal data(Line %s) error. Unexpected data is found at CSV file. Check data type
error. Position register of Cartesian CSV file. String at which
SDTL-053 Illegal config(Line %s) data type needs configuration data. X_DYNDAT detected error
error. Integer value in CSV file was out CSV file. Wrong value,
SDTL-054 Out of range(Line %s) of range. minimum value and
error. CSV file doesn't have empty field CSV file. String at which
(field that doesn't have character) X_DYNDAT detected error
Empty field does not where it is expected. If data for an is displayed, too. Check
SDTL-055 exist(Line %s) identifier is composed of 2 or more data type and its data
Execution of X_DYNDAT causes this
error. Very large (or small) value is
specified as real value of register. It was
Converted to real of out interpreted as value of out of range. Make absolute value
SDTL-056 of range(Line %s) Data should be larger than -1.0E16 and smaller.
Execution of X_DYNDAT without
argument causes this error. In this case,
path of CSV file is decided by string Check value of
register. Index of string register is [X_DYNDAT]IDEFSRIDX.
Index of SR is decided by KAREL variable, Change its value to valid
SDTL-057 wrong(%s) [X_DYNDAT]IDEFSRIDX (KAREL variable index of string register.
String of file path doesn’t include :\\. Include :\\ in file path
SDTL-060 :\\ not found (%s) %s shows specified file path. string.
Specified file path is not proper. %s
SDTL-061 Illegal file path (%s) shows specified file path. Correct file string path.
The last character of file path string is
SDTL-062 Last char is not \\ (%s) not \\. %s shows specified file path. Correct file path string.
File copy failed. %s shows destination Check whether specified
SDTL-063 Failed to copy (%s) file name. file device and sub
TP Program does not Specified TP program does not exist on Please specify program
SDTL-064 exist (%s) the controller.%s shows specified TP that exists on controller.
Program name was not specified. If Check argument. If integer
Program name is not string register is specified, information value is used, value of
SDTL-065 specified %s of the string register is displayed. SR[1] SR[the integer] is used as
Program name for STWRPRT and
SDTL-066 * cannot be used (%s) CRWRPRT contains "*". You cannot use Correct program name.
Write protection could not be turned Displayed program is
Failed to turn write on. %s shows program name. If string used. Try again in a state
SDTL-067 protect on(%s) register is specified, information of the that displayed program is
Specify string register that
exist on the controller.
KAREL variable can be
used to specify index. If it
Index of SR is Index of string register is wrong. %s is the case, KAREL variable
SDTL-068 wrong(%s) shows specified index is displayed. should be modified to
Write protection could not be turned Dipslayed program is
Failed to turn write off. %s shows program name. If string used. Try again in a state
SDTL-069 protect off(%s)
Specified program is register is specified, information of the that displayed program is
SDTL-070 not TP(%s) Specified program is not TP program. Specify TP program.
This alarm is posted by execution of
KAREL program, STPAYLOD. Payload
center is out of range. It is specified by Check index of register
Payload center position register. Suppose the 3rd argument of and its value. Set proper
SDTL-077 is out of range(%s) STPAYLOD is 101. Center of gravity of value
This alarm is posted by execution of
KAREL program, STPAYLOD. Inertia of
payload is out of range. It is specified
by register. Suppose the 3rd argument Check index of register
Payload inertia is out of of STPAYLOD is 101. Inertia of payload and its value. Set proper
SDTL-078 range(%s) around X axis is specified by R[105]. If value
TPE parameter %s This alarm is posted by execution of
SDTL-079 wrong data type KAREL program, STPAYLOD. Data type Set correct parameter.
Failed to get TPE This alarm is posted by execution of Modify TP program to set
SDTL-080 parameter %s KAREL program, STPAYLOD. Failed to proper parameter
Register for payload This alarm is posted by execution of The 3rd argument of
SDTL-081 does not exist(%s). KAREL program, STPAYLOD. Register for STPAYLOD is index of
This alarm is posted by execution of Suppose the 3rd
Register for payload KAREL program, STPAYLOD. Register for argument of STPAYLOD is
center(%s) does not payload center does not exist. n. STPAYLOD uses R[n],
SDTL-082 exist. coordinate (X or Y or Z) and index are R[n+1], ...... R[n+6] Modify
Register for payload This alarm is posted by execution of Suppose the 3rd
inertia (%s) does not KAREL program, STPAYLOD. Register for argument of STPAYLOD is
SDTL-083 exist. payload inertia does not exist. n. STPAYLOD uses R[n],
This error is caused when Dispensetool Write down the exact
encounters a problem it is unable to error number and
solve internally. This fault is almost message shown. Write
reasons for this could be: 1. The sealing sure you include: Program
Dispensetool internal path is too fast 2. The sealing name, line number,
SEAL-000 ABORT error instructions (SS and SE) are too close robot's location in the
path is too fast 2. The sealing name, line number,
SEAL-001 WARN %s instructions (SS and SE) are too close robot's location in the
path is too fast. 2. The sealing name, line number,
instructions (SS and SE) are too close robot's location in the
SEAL-002 WARN Flow rate update failed together. 3. The delay and timing work cell, any cell I/O or
SEAL-003 WARN Digital I/O update failed instructions (SS and SE) are too close robot's location in the
Dispensetool error at path is too fast 2. The sealing name, line number,
SEAL-004 WARN %d instructions (SS and SE) are too close robot's location in the
Dispensetool error at path is too fast 2. The sealing name, line number,
SEAL-005 WARN %s instructions (SS and SE) are too close robot's location in the
path is too fast. 2. The sealing name, line number,
SEAL-006 WARN Memory request failed instructions (SS and SE) are too close robot's location in the
SEAL-007 WARN Condition handler failed instructions (SS and SE) are too close robot's location in the
SEAL-008 WARN System call failed instructions (SS and SE) are too close robot's location in the
SEAL-009 WARN Data missing: %s instructions (SS and SE) are too close robot's location in the
SEAL-010 WARN
SEAL-011 WARN
SEAL-012 WARN
SEAL-013 WARN
SEAL-014 WARN
SEAL-015 WARN
SEAL-016 WARN
SEAL-017 WARN
SEAL-018 WARN
SEAL-019 WARN
SEAL-020 WARN
In the Schedule number listed, the Gun There is no real danger in
On signal has been set up to turn on or this condition. You should
off too long after the node the SS[] or be aware that if you try to
SE is attached to. Currently, if this turn the gun on or off
signal is set up to turn on or off greater after 100ms AFTER the
than 100ms after the node, this node, the signal will
warning will be posted and the signal always be fired 100ms
will fore 100ms after the node. These after the node and this
are the formulas used to determine warning will be posted. To
Gun on/off too late: Sch when the gun will be turned on or off correct this problem,
SEAL-021 WARN %d relative to the node
In the Schedule for seal
number schedule
listed, the Start make
There the
is no real danger in
Meter signal has been set up to turn on this condition. You should
or off too long after the node the SS[] be aware that if you try to
or SE is attached to. Currently, if this turn this signal on or off
signal is set up to turn on or off greater after 100ms AFTER the
than 100ms after the node, this node, the signal will
will fire 100ms after the node. These after the node and this
when this signal will be turned on or off correct this problem,
relative to the node for seal schedule make the
Meter on too late: Sch 'n': For SS[n]: Time_Before = pre/de_pressure_delay or
SEAL-022 WARN %d PRE_PRESSURE_DELAY + equipment_delay more
In the Schedule number listed, the There is no real danger in
Atomizing Air signal has been set up to this condition. You should
turn on or off too long after the node be aware that if you try to
the SS[] or SE is attached to. Currently, turn this signal on or off
if this signal is set up to turn on or off after 100ms AFTER the
greater than 100ms after the node, this node, the signal will
will fire 100ms after the node. These after the node and this
when this signal will be turned on or off correct this problem,
relative to the node for seal schedule make the
Air on/off too late: Sch 'n': For SS[n]: Time_Before = atomizing_on/off/_delay
SEAL-023 WARN %d ATOMIZING_ON_DELAY
The high performance I/O + triggering or
Goequipment_delay
to the Equipmentmore
system (Motion Trigger) has returned a Output menu and verify
bad status. When this occurs, the that all the Gun on, Start
redundant triggering system will take Meter, and Atomizing Air
over, but the quality of the SSs and SEs outputs are correctly
will be poor. This condition is usually defined or their indexes
caused by one or more of the are set to zero. If the
following: 1. A Gun On output is VALUE of a output port is
assigned to a output point which is '****', then the index
nonzero and does not exist. 2. A Start number must be set to
Meter output is assigned to a output zero and the robot must
Error in motion point which is nonzero and does not be cold started. You must
SEAL-024 WARN triggering exist. 3. A Atomizing Air output is cold start the robot after
SEAL-025 WARN
SEAL-026 WARN
SEAL-027 WARN
SEAL-028 WARN
SEAL-029 WARN
SEAL-030 WARN
SEAL-031 WARN %s made for customer regarding specific changes
PAUSE. The system ready signal(DI) turns off Check the system ready
SEAL-041 G Seal not ready when the sealant is dispensed. signal of the sealing
Check wiring of group I/O
Part ID mismatch Transmitted and received part IDs to line for part ID and part ID
SEAL-042 WARN detected dispensing equipments do not match. acknowledge signals.
The pressure signal is above its upper Check the pressure signal
PAUSE. limit for set time when the sealant is of the sealing equipment,
SEAL-043 G High pressure dispensed. disable to check the high
The pressure signal is below its lower Check the pressure signal
limit for set time when the sealant is of the sealing equipment,
SEAL-044 WARN Low pressure (E%d) dispensed. disable to check the low
limit for set time when the sealant is of the sealing equipment,
SEAL-045 WARN High pressure (E%d) dispensed. disable to check the high
Check the gun full open
PAUSE. The gun full open signal(DI) has been signal of the sealing
SEAL-046 G Seal not start on for the set time since sealing start. equipment, disable the
PAUSE. The gun full open signal(DI) has been signal of the sealing
SEAL-047 G Seal interrupt on for the set time since sealing start. equipment, disable the
ABORT. Dispenser mode Dispenser switch position does not Check key switch on the
SEAL-048 G mismatch (E%d) match equipment set up dispensing equipment and
ABORT. Calibrations not One or more calibration procedures are Visit equipment SETUP
SEAL-049 G
ABORT. complete
Shot meter(E%d)
not full not complete
The dispenser should be full at this menu and
Check thatcomplete all
the dispenser
SEAL-050 G (E%d) point, and is not. is full for this operation.
ABORT. Both Drums are empty Check sealant supply
SEAL-051 G (E%d) Both drums are empty drums to be sure they are
ABORT. Same fault posted Check dispensing
SEAL-052 G repeatedly (E%d) Same fault occurs repeatedly equipment and clear the
Robot is in dry run Set DRY RUN parameter
SEAL-053 WARN mode Dry run parameter is ON. to OFF and run calibration
Set ROBOT LOCK
SEAL-054 WARN Robot lock mode is ON Robot lock parameter is ON. parameter to OFF and run
The Part ID in the JOB header is out of Make sure the Part ID in
SEAL-055 WARN Dispenser
Part ID outnot
of range
ready the allowed
Dispenser range
ready for this
input robot.
signal from the JOBdispenser
Check header ismanual
SEAL-056 WARN (E%s) dispenser is OFF. for further information.
Perform the standard
A fault was detected at the dispensing dispenser fault recovery
SEAL-057 WARN Dispenser fault (E%s) controller. procedure. See the
The dispenser has detected a See the dispensing
abnormally low or high material flow equipment manual for
SEAL-058 WARN Flow rate fault (E%s) rate. This could be caused by a plugged more information. You
Not calibrated warning One or more calibration procedures are Visit equipment SETUP
SEAL-059 WARN (E%s) not complete menu and complete all
The high pressure signal(DI) has been Check the sealing
on for the configured time during equipment high pressure
SEAL-060 WARN High pressure (E%d) sealing. signal, disable the check
The system ready signal(DI) turns off Check the sealing
SEAL-061 WARN Seal not ready when sealant
There is being
is a reload dispensed.
problem with the equipment ready signal or
SEAL-062 WARN Reload fault (E%d) meter Check the shot meter
The high pressure signal(DI) has been Check the sealing
on for the configured time during equipment high pressure
SEAL-063 WARN High pressure sealing. signal, disable the check
Make sure the robot
SEAL-064 WARN Not at purge position Robot is not at purge position returns to purge position
The Auto Purge feature has determined Increase the maximum
that the robot should purge now, but number of purges allowed
Maximum purge count the maximum number of purges it is or remove the disposable
SEAL-065 WARN reached allowed to perform in a row (as set in mixing tip from the gun,
The gun full open signal(DI) has been signal of the sealing
SEAL-066 WARN Seal not start on for the set time since sealing start. equipment, disable the
Gun full open signal(DI) has been on for signal of sealing
SEAL-067 WARN Seal interrupt too long while dispensing. equipment, disable the
Flow command Flow command output voltage is larger Decrease the motion
SEAL-068 WARN excessive%s than the maximum output. speed or increase the
Dispenser malfunction The dispensing equipment controller Perform maintenance and
SEAL-069 WARN (E%d) has detected a fault in its hardware. debug procedures as
A dispensing gun malfunction has been Perform dispensing gun
SEAL-070 WARN Gun malfunction (E%d) detected by the dispensing controller. maintenance and debug
Check the pressure
Gun full open too long A low pressure condition has been sensors at all points in the
SEAL-071 WARN (E%d) detected by the dispensing controller system. Perform standard
A high pressure condition has been Reduce system pressure if
detected in the dispensing gun nozzle. it is permissible. Select a
High nozzle pressure In specific, nozzle pressure signal is nozzle pressure
SEAL-072 WARN (E%d) greater than (NOZZLE SENSOR transducer with a wider
High dispensed volume The volume of material dispensed on Verify that the volume
SEAL-073 WARN (E%d) the previous job was above the preset limits are correct for the
Low dispensed volume The volume of material dispensed on Verify that the volume
SEAL-074 WARN (E%d) the
A previous
error job was below
was detected the preset
in the flow meter limits are
Verify thatcorrect for the
the flowmeter
SEAL-075 WARN Flow meter fault (E%d) readings.
Bead defect detected An incorrect bead condition was is operating correctly.
Perform dispensing gun
SEAL-076 WARN (E%d) detected. maintenance procedures.
Check the dispensing
Sealer equipment fault An unknown error code was received controller for an error
SEAL-077 WARN (E%d) from the dispensing controller. condition. Also check the
Dispenser comm fault An error was encountered reading fault Check the
SEAL-078 WARN (E%d) data from the dispenser communications link
An Emergency Stop condition was Clear the fault and
SEAL-079 WARN Dispenser E-stop (E%d) detected at the dispensing controller perform the proper
Perform the standard
A fault was detected at the dispensing dispenser fault recovery
SEAL-080 WARN Dispenser fault (E%d) controller. procedure. See the
Volume comp at Interim value for volume has exceeded Re-learn part or increase
SEAL-081 WARN maximum (E%d) maximum interim limit. maximum limit.
This is a warning to the
SEAL-082 WARN Drum A empty (E%d) The first of the two drums is empty operator that the drum
This is a warning to the
SEAL-083 WARN Drum B empty (E%d) The second of the two drums is empty. operator that the drum
Reload of shot meter took longer than Check your dispensing
SEAL-084 WARN Reload timed out (E%d) the specified time. equipment for faults, to
Calibration aborted due to user request If unknown cause -- see
SEAL-085 WARN Calibration aborted or possible fault. next most recent alarm
Volume strobe timeout Volume present signal not received Run calibration again -
SEAL-086 WARN (E%d) from Pro-Flo unit. check Pro-Flo unit for
Volume above limit The volume of material dispensed on Verify that the volume
SEAL-087 WARN (E%d) the previous job was above the preset limits are correct for the
Material cal timeout Material cal complete signal not Check Pro-Flo for
SEAL-088 WARN (E%d) received from Pro-Flo unit. malfunction or increase
Volume below limit The volume of material dispensed on Verify that the volume
SEAL-089 WARN (E%d) the previous job was below the preset limits are correct for the
The problem is either the nozzle Use on-board diagnostics
pressure is greater than setpoint for on the dispensing
Nozzle over pressure more than time limit or the upstream controller to verify that
SEAL-090 WARN (E%d) hose is ruptured and is leaking the nozzle pressure sensor
Matl weight input = 0 User input was zero for material Run calibration again - do
SEAL-091 WARN (E%d) weight. not enter zero for
Specific gravity = 0 Assign a nonzero value for
SEAL-092 WARN (E%d)
Volume read is zero User input was
Zero volume waszero for specific
detected fromgravity.
Pro-Flo specific gravity.forRun cal
Check Pro-Flo
SEAL-093 WARN (E%d) analog signals. malfunction.
Dispense time is zero Assign a nonzero value for
SEAL-094 WARN (E%d) User input was zero for dispense time. dispense time. Run cal
Use on-board diagnostics
Nozzle pressure has dropped below on the dispenser
SEAL-095 WARN Nozzle worn
Matl press out (E%d)
entered=0 setpoint
User value
input wasfor more
zero than time limit.
for material controller
Check whyto verify that
material
SEAL-096 WARN (E%d) pressure. pressure is zero during
Pressure read is zero No change in analog signal from Check pressure transducer
SEAL-097 WARN (E%d) pressure transducer. and ensure varying
on the dispenser
Upstream over pressure Upstream pressure is greater than controller to verify that
SEAL-098 WARN (E%d)
Air pressure entered=0 setpoint for more than time limit. the upstream
Check why air pressure
pressure is
SEAL-099 WARN (E%d)
NO scale factor/bias User input was zero for air pressure. zero during
Perform thecalibration.
calibration
SEAL-100 WARN (E%d) The Scale factor or bias is zero procedures
Volume strobe timeout Check dispensing
SEAL-101 WARN (E%d) The volume timer expired equipment for faults, or
Press calib incomplete Pressure calibration has not been Perform pressure
SEAL-102 WARN (E%d) completed. calibration before running
Dispenser not in AUTO Dispenser Auto Mode signal to the Make sure dispenser
SEAL-103 WARN (E%d) robot has dropped. mode selection is set to
Analog cal incomplete Analog voltage calibration has not been Perform analog
The Dispenser On signal (from the
SEAL-105 WARN Dispenser not ON (E%d) dispenser to the robot) has dropped. Turn on the dispenser.
Upstream under press Upstream pressure has dropped below on the dispenser
SEAL-106 WARN (E%d) setpoint value for more than time limit. controller to verify that
Matl calib incomplete Material learn calibration has not been Perform material
Material timeout = 0 Set timeout to nonzero
SEAL-108 WARN (E%d) Material learn timeout value is zero value before running this
Low press>=high press Low pressure atomizing air input was Check atomizing air
SEAL-109 WARN (E%d) greater or equal to high pressure equipment
System/drive not ready System and Drive Ready signal (from Perform standard
SEAL-110 WARN (E%d) volume read the dispenser to the robot) has
Negative dispenser
Check maintenance
dispensing
SEAL-111 WARN (E%d)
Vol read was
sig cal incomplete Volume signal negative.has not been Perform
calibration equipment and run
volume signal
SEAL-112 WARN (E%d) completed.
I/O config incomplete At least one I/O signal assignment is calibration.
Set proper I/O ports for all
SEAL-113 WARN (E%d)
Dispenser not ready zero.
Dispenser ready input signal from necessary
Check dispenser
dispenser I/O.
manual
SEAL-114 WARN (E%d) dispenser is OFF. for further information.
Too low material flow abnormally low or high material flow equipment manual for
SEAL-115 WARN (E%d) rate. This could be caused by a plugged more information. You
Flow command output voltage is lower Increase the motion
SEAL-116 WARN Flow command too low than the minimum output. speed or decrease the
SEAL-117 WARN (E%d) the dispenser to the robot) has dispenser maintenance
SEAL-118 WARN (E%d) robot has dropped. mode selection is set to
Check system pressure.
A low pressure warning has been Check the pressure
SEAL-119 WARN Low pressure (E%d) detected by the dispensing controller sensors in the system.
SEAL-120 WARN Dispenser not ON (E%d) dispenser to the robot) has dropped. Turn on the dispenser.
Perform dispenser
maintenance procedures
The Dispensing signal (from the to determine why
Dispense signal fault dispenser to the robot) should be high dispensing is not
SEAL-121 WARN (E%d) during dispensing, but it is not. occurring as it should.
Only one sealing task may
You tried to run a JOB or PROC TPP be running at any time.
Sealing task already while another JOB or PROC TPP is This means that only one
SEAL-122 WARN active already running in another task. JOB or PROC may be
The current Job has been aborted due Correct the cause of this
SEAL-123 WARN Job aborted to a fatal error. error, which is usually
Make sure that all inputs
This error is usually caused by an IO and outputs on the
point which is required by Dispensetool Dispenser IO screen are
ABORT. being set to an invalid index number or set to valid IO points (the
SEAL-124 G
ABORT. Critical IO
Sealing is invalid
system type. VALUE is not shown as
SEAL-125 G
ABORT. error(125)
Sealing system
SEAL-126 G
ABORT. error(126)
Sealing system
SEAL-127 G
ABORT. error(127)
SEAL-128 G
PAUSE. System error(%d)(%d) The index value of seal start instruction Check the index value of
SEAL-129 G
ABORT. Index incorrect
Sealing system is invalid. this SS instruction.
SEAL-130 G error(130)
This error is caused by timing problems
Make sure there is
with Sealing commands (SS or SE). adequate time for each SS
Timing problems could occur if the and SE to execute. You
robot does not have enough time to may do this by making
plan for a sealing instruction before the
sure you have only the
robot passes that point in the path. For
minimum number of
example: If the user is using a sealing
points in your path that
schedule with a gunon delay of 1000ms you require. Dispensetool
and a gunoff delay of -1000ms and the works best with as few
ABORT. robot executes the seam in 1500ms, points as possible. Also,
SEAL-131 G SS/SE timing invalid the Dispensetool will detect the logicmake sure none of your
Step through your sealing
PROCess program, making
There was not enough time between a sure there is at least a
Seam segment too SS and the next SS or SE for the flow centimeter between the
SEAL-132 WARN
ABORT. short
Sealing system rate computations to be done. points attached to each
SEAL-133 G
ABORT. error(133)
Sealing system
ABORT. Sealing system
SEAL-135 G
ABORT. error(135)
Sealing system
SEAL-136 G
ABORT. error(136)
Sealing system
SEAL-137 G
ABORT. error(137)
Sealing system
SEAL-138 G
ABORT. error(138)
Sealing system
SEAL-139 G
ABORT. error(139)
Sealing system
SEAL-140 G
ABORT. error(140)
SEAL-141 G Speed data invalid
SEAL-142 WARN
ABORT. Speed data invalid Robot moved with joint motion during Change motion type from
SEAL-143 G Joint motion sealing.
Robot moved with joint motion during joint
Changeto linear
motionortype
circular.
from
SEAL-144 WARN
ABORT. Joint motion
Sealing system sealing. joint to linear or circular.
SEAL-145 G
ABORT. error(145)
Sealing system
PAUSE. Equipment does not Check the equipment
SEAL-147 G
ABORT. exist This equipment is not exist. number in the program
SEAL-148 L No SE Instruction SE instruction is not exist. Add an SE instruction.
PAUSE. No equipment number Set the equipment
SEAL-149 G set Equipment is not set on this program. number in the program
PAUSE. Equipment is already Other program is using this equipment Change the equipment
SEAL-150 G busy now. number or check interlock
Check program header if
TPP not created The teach pendant program is not the teach pendant
SEAL-151 WARN correctly created properly program is either a JOB or
If you wish to use this I/O
port, set the port index
and I/O type to the
I/O not correctly The index value or type of this I/O port correct values. Verify that
SEAL-152 WARN assigned is incorrectly assigned. a valid value is shown on
You can not set volume set point while Volume set points must
SEAL-153 WARN Program is running a program is running be established after
SEAL-154 WARN No SS Instruction Check SS instruction on
SEAL-155 WARN before SE There is no SS instruction before SE. this program.
MOV_ TPP execution Unsuccessful execution of a MOV_ type Ensure MOV_ program is
SEAL-156 WARN failure program. executable. Reset holds
Seal schedule data is Desired volume or bead width for first Enter a valid setting for
SEAL-157 WARN zero sealing schedule was zero. desired volume or bead
Tool offset calib Tool offset calibration aborted due to If unknown cause -- see
SEAL-158 WARN aborted user request
Current utooloris possible fault.
zero - has not been next
Teachmost
utoolrecent alarm
before
SEAL-159 WARN UTOOL #1 is not taught taught. REFPOS has not been taught -
Current running
Teach this calibration.
REFPOS before
SEAL-160 WARN REFPOS is not taught is zero. running OFFSET
Difference between REFPOS and Check for damaged tool,
SEAL-161 WARN OFFSET out of range OFFSET positions was too large. change tip and run
OFFSET config Difference exists between REFPOS and Run calibration again
SEAL-162 WARN mismatch OFFSET position configurations. while
Performmaintaining
cold start REFPOS
or
SEAL-163 WARN File is not closed File to be executed is not closed. temporarily SELECT a
SEAL-164 WARN File does not exist File to be executed does not exist. Create and teach the file.
SEAL-165 WARN
SEAL-166 WARN
SEAL-167 WARN
SEAL-168 WARN
SEAL-169 WARN
Check supply air to the
SEAL-170 WARN Invalid tool
Gripper not position
opened Commanded tool position is not valid tool Check
Check proximity
to see if release
SEAL-171 WARN (GP%s) not closed
Gripper All grippers are not opened mechanism
Check to seeisifworking
clamping
SEAL-172 WARN (GP%s) All grippers on this valve are not closed mechanism is working
Check sensor correct
SEAL-173 WARN Part not present (GP%s)
Sensors not reporting part present operation
Check sensor correct
SEAL-174 WARN Part Present (GP%s) Sensors
Variablereporting part present
$sltlstup[1].valve is not operation
Go to Tool Setup and
SEAL-175 WARN Un-assigned
IO mode is notBit maskassigned
IO port is not set up as a setup
Set upgripper
IO port as a
SEAL-176 WARN complementary complementary port complementary port
The Four Position End of Arm tool was Check air supply to the
moved, but the FLIP sensor reports that four position tool. Check
the tool is not in the correct proximity sensors on the
FLIP/UNFLIP position (could be ON or four position tool. If the
SEAL-177 WARN EOAT timed out: Flip OFF) after the timeout period set on tool is slow, increase the
moved, but the UNFLIP sensor reports four position tool. Check
that the tool is not in the correct proximity sensors on the
UNFLIP/FLIP position (could be ON or four position tool. If the
SEAL-178 WARN EOAT timed out: Unflip OFF) after the timeout period set on tool is slow, increase the
moved, but the EXTEND sensor reports four position tool. Check
that the tool is not in the correct proximity sensors on the
EXTEND/RETRACT position (could be four position tool. If the
SEAL-179 WARN EOAT timed out: Extend ON or OFF) after the timeout period set tool is slow, increase the
moved, but the RETRACT sensor four position tool. Check
reports that the tool is not in the proximity sensors on the
EOAT timed out: correct RETRACT/EXTEND position four position tool. If the
SEAL-180 WARN Retract (could be ON or OFF) after the timeout tool is slow,
Calibrate increase
robot the
and run
SEAL-181 WARN Invalid
Robot iskinimatic
not calibrated Robot is not calibrated. calibration again.
SEAL-182 WARN solution
Tool offset internal Current robot position invalid. Run calibration
Contact FANUC again.
Robotics
SEAL-183 WARN error Internal tool offset calibration error. Hotline.
SEAL-184 WARN
SEAL-185 WARN
SEAL-186 WARN
SEAL-187 WARN
SEAL-188 WARN
SEAL-189 WARN
The high performance I/O triggering Go to the Equipment
system (Motion Trigger) has returned a Output menu and verify
bad status. When this occurs, the that all the Gun on, Start
Disabling motion redundant triggering system will take Meter, and Atomizing Air
SEAL-190 WARN triggering over, but the quality of the SSs and SEs outputs are correctly
In the Schedule number listed, the Gun There is no real danger in
On signal has been set up to turn on or this condition. You should
off too long after the node the SS[] or be aware that if you try to
Gun on/off too late: Sch SE is attached to. Currently, if this turn the gun on or off
SEAL-191 WARN %d signal is set up to turn on or off greater after 100ms AFTER the
Cannot change during While the robot is sealing, specified Please change it after
SEAL-192 WARN sealing item cannot be chnaged. sealing is finished
Cannot use with motion The Atomizing Air cannot be used with Please disable Motion
SEAL-193 WARN trigger the high performance I/O triggering Trigger function
The analog output command of Decrease the atomizing
Air command exceeds Atomizing Air exceeds the Maximum air pressure of sealing
SEAL-194 WARN max limit Analog Voltage (air) which is set in the schedule or increase the
The analog output command of Increase the atomizing air
Air clamped minimum Atomizing Air is clamped by Minimum pressure of sealing
SEAL-195 WARN voltage Analog Voltage (air) which is set in the schedule.
Calibration aborted due to user request If unknown cause -- see
SEAL-196 WARN Calibration aborted or possible fault. next most recent alarm
PAUSE. Atomizing air cal Calibration of Atomizing Air has not Perform the Caribration of
SEAL-197 G
ABORT. incomplete process is been done yet. The calibration must be
Application the Atomizing
Please change Air
thein the
SEAL-198 L changed during sealing Application is changed during sealing. program.
Flow command The analog output command for Flow Increase the flow
clamped minimum control is clamped by Minimum Analog command in sealing
SEAL-199 WARN voltage Output (flow) which is set in the setup schedule.
PAUSE. Dispenser malfunction The dispensing equipment controller Perform maintenance and
SEAL-200 G (E%s) has detected a fault in its hardware. debug procedures as
PAUSE. A dispensing gun malfunction has been Perform dispensing gun
SEAL-201 G Gun malfunction (E%s) detected by the dispensing controller. maintenance and debug
Check the pressure
Gun full open too long A low pressure condition has been sensors at all points in the
SEAL-202 WARN (E%s) detected by the dispensing controller system. Perform standard
A high pressure condition has been Reduce system pressure if
detected in the dispensing gun nozzle. it is permissible. Select a
PAUSE. High nozzle pressure In specific, nozzle pressure signal is nozzle pressure
SEAL-203 G (E%s) greater than (NOZZLE SENSOR transducer with a wider
High dispensed volume The volume of material dispensed on Verify that the volume
SEAL-204 WARN (E%s) the previous job was above the preset limits are correct for the
Low dispensed volume The volume of material dispensed on Verify that the volume
SEAL-205 WARN (E%s) the previous
A error job was below
was detected the preset
in the flow meter limits
Verify are
thatcorrect for the
the flowmeter
SEAL-206 WARN Flow meter
Bead defectfault (E%s) An
detected readings.
incorrect bead condition was is operating
Perform correctly.
dispensing gun
SEAL-207 WARN (E%s) detected. maintenance procedures.
Volume comp at max Interim value for volume has exceeded Re-learn part or increase
SEAL-208 WARN (E%s) maximum interim limit. maximum limit.
The problem is either the nozzle Use on-board diagnostics
pressure is greater than setpoint for on the dispensing
Nozzle over pressure more than time limit or the upstream controller to verify that
SEAL-209 WARN (E%s) hose is ruptured and is leaking the nozzle pressure sensor
Nozzle under press Nozzle pressure has dropped below on the dispenser
SEAL-210 WARN (E%s) setpoint value for more than time limit. controller to verify that
on the dispenser
Upstream over press Upstream pressure is greater than controller to verify that
SEAL-211 WARN (E%s) setpoint for more than time limit. the upstream pressure
Upstream under press Upstream pressure has dropped below on the dispenser
SEAL-212 WARN (E%s) setpoint value for more than time limit. controller to verify that
Check the dispensing
Sealer equipment fault An unknown error code was received controller for an error
SEAL-213 WARN (E%s) from the dispensing controller. condition. Also check the
abnormally low or high material flow equipment manual for
SEAL-214 WARN No material flow (E%s) rate. This could be caused by a plugged more information. You
Reload of shot meter took longer than Check your dispensing
SEAL-215 WARN Reload fault
timedoccured
out (E%s) the specified
There time.
is a reload problem with the equipment for faults, to
SEAL-216 WARN NO
(E%s)
scale factor/bias meter Check thethe
Perform shot meter
calibration
SEAL-217 WARN (E%s) The Scale factor or bias is zero procedures
Check dispensing
SEAL-218 ABORT Same fault posted (E%s) Same fault occurs repeatedly equipment and clear the
Volume strobe timeout Check dispensing
SEAL-219 WARN (E%s) The volume timer expired equipment for faults, or
The volume dispensed in the last job This warning is normal if it
was out of the normal volumetric range was caused by
of material dispensed for this job. This terminating a job early. If
could be caused by terminating the job this error happens during
Volume out of range early, causing much less material to be normal production,
SEAL-220 WARN (E%s) dispensed. This could also be caused by examine the quality of the
A significant bubble was dispensed with Make sure any new
the material during the job. This is material is loaded
usually caused by improper loading of properly into the supply
new material. NOTE: This will often pump. Make sure all
SEAL-221 WARN Bubble detected (E%d) cause poor quality sealing. Examine the excess air has been
SEAL-222 WARN Dispenser not ON (E%s) dispenser to the robot) has dropped. Turn on the dispenser.
SEAL-223 WARN (E%s) robot has dropped. mode selection is set to
SEAL-224 WARN (E%s) the dispenser to the robot) has dispenser maintenance
Low pressure warning A low pressure warning has been Check the pressure
SEAL-225 WARN (E%s) detected by the dispensing controller sensors in the system.
High pressure warning limit for set time when the sealant is of the sealing equipment,
SEAL-226 WARN (E%s) dispensed. disable to check the high
Low pressure fault A low pressure warning has been Check the pressure
SEAL-227 WARN (E%s) detected by the dispensing controller sensors in the system.
High pressure fault limit for set time when the sealant is of the sealing equipment,
SEAL-228 WARN (E%s) dispensed. disable to check the high
Calibration incomplete One or more calibration procedures are Visit equipment SETUP
SEAL-229 WARN (E%s) not complete menu and complete all
High Dispensed Volume Refer to Nordson Pro-Flo
SEAL-230 WARN (E%d) High Dispensed Volume. II dispenser equipment
Low Dispensed Volume Refer to Nordson Pro-Flo
SEAL-231 WARN (E%d) Low Dispensed Volume. II dispenser equipment
High Material Supply Refer to Nordson Pro-Flo
SEAL-232 WARN Pressure (E%d) High Material Supply Pressure. II dispenser equipment
Low Material Supply Refer to Nordson Pro-Flo
SEAL-233 WARN Pressure (E%d) Low Material Supply Pressure. II dispenser equipment
No Material Supply Refer to Nordson Pro-Flo
SEAL-234 WARN Pressure (E%d) No Material Supply Pressure. II dispenser equipment
Nozzle Clog or Down Refer to Nordson Pro-Flo
SEAL-235 WARN Stream Blockage (E%d) Nozzle Clog or Down Stream Blockage. II dispenser equipment
Refer to Nordson Pro-Flo
SEAL-236 WARN Gun Cable Failure (E%d) Gun Cable Failure. II dispenser equipment
Flowmeter/Booster Refer to Nordson Pro-Flo
SEAL-237 WARN Pump Failure (E%d) Flowmeter/Booster Pump Failure. II dispenser equipment
Nozzle Pressure Refer to Nordson Pro-Flo
SEAL-238 WARN Transducer Failure Nozzle Pressure Transducer Failure. II dispenser equipment
Flowmeter cable Failure Refer to Nordson Pro-Flo
SEAL-239 WARN (E%d) Flowmeter cable Failure. II dispenser equipment
Upstream Pressure Refer to Nordson Pro-Flo
SEAL-240 WARN Transducer Failed (E%d) Upstream Pressure Transducer Failed. II dispenser equipment
Upstream Pressure Upstream Pressure Transducer Cable Refer to Nordson Pro-Flo
SEAL-241 WARN Transducer Cable Failed Failed. II dispenser equipment
Robot Signal Out of Refer to Nordson Pro-Flo
SEAL-242 WARN Sequence (E%d) Robot Signal Out of Sequence. II dispenser equipment
SEAL-243 WARN Gun Failure (E%d) Gun Failure. II dispenser equipment
Bead Defect Detected Refer to Nordson Pro-Flo
SEAL-244 WARN (E%d) Bead Defect Detected. II dispenser equipment
Joint Motion While Joint motion is used between SS and SE Use Linear or Circular
SEAL-245 WARN Dispensing instructions motion between SS and
Style ID communication Style ID was sent, but timeout occurred Determine the reason
SEAL-246 timeout (E%s) waiting for Dispenser why Dispenser did not set
High Dispensed Volume Refer to Nordson Pro-Flo
SEAL-250 WARN (E%s) High Dispensed Volume. II dispenser equipment
Low Dispensed Volume Refer to Nordson Pro-Flo
SEAL-251 WARN (E%s) Low Dispensed Volume. II dispenser equipment
High Material Supply Refer to Nordson Pro-Flo
SEAL-252 WARN Pressure (E%s) High Material Supply Pressure. II dispenser equipment
Low Material Supply Refer to Nordson Pro-Flo
SEAL-253 WARN Pressure (E%s) Low Material Supply Pressure. II dispenser equipment
No Material Supply Refer to Nordson Pro-Flo
SEAL-254 WARN Pressure (E%s) No Material Supply Pressure. II dispenser equipment
Nozzle Clog or Down Refer to Nordson Pro-Flo
SEAL-255 WARN Stream Blockage (E%s) Nozzle Clog or Down Stream Blockage. II dispenser equipment
SEAL-256 WARN Gun Cable Failure (E%s) Gun Cable Failure. II dispenser equipment
Flowmeter/Booster Refer to Nordson Pro-Flo
SEAL-257 WARN Pump Failure (E%s) Flowmeter/Booster Pump Failure. II dispenser equipment
Nozzle Pressure Refer to Nordson Pro-Flo
SEAL-258 WARN Transducer Failure Nozzle Pressure Transducer Failure. II dispenser equipment
Flowmeter cable Failure Refer to Nordson Pro-Flo
SEAL-259 WARN (E%s) Flowmeter cable Failure. II dispenser equipment
Upstream Pressure Refer to Nordson Pro-Flo
SEAL-260 WARN Transducer Failed (E%s) Upstream Pressure Transducer Failed. II dispenser equipment
Upstream Pressure Upstream Pressure Transducer Cable Refer to Nordson Pro-Flo
SEAL-261 WARN Transducer Cable Failed Failed. II dispenser equipment
Dispense IO Sequence Refer to Nordson Pro-Flo
SEAL-262 WARN error (E%s) Robot Signal Out of Sequence. II dispenser equipment
SEAL-263 WARN Gun Failure (E%s) Gun Failure. II dispenser equipment
Bead Defect Detected Refer to Nordson Pro-Flo
SEAL-264 WARN (E%s) Bead Defect Detected. II dispenser equipment
Major Dispenser Fault A Major Fault was detected on the Refer to dispensing
SEAL-265 STOP on (E%s) dispensing equipment. equipment for fault
Minor Dispenser Fault A Minor Fault was detected on the Refer to dispensing
SEAL-266 WARN on (E%s) dispensing equipment. equipment for fault
Volume dispensed out Volume OK signal NOT received from Refer to dispensing
SEAL-267 STOP of range (E%s) dispensing equipment. equipment for fault
This error is reported when the process Refer to dispensing
SEAL-268 WARN Flow rate is zero (E%d) mode is wet and the computed flow equipment for fault
This error is reported when the Refer to dispensing
Flow command below computed flow rate command is less equipment for fault
SEAL-269 WARN minimum (E%d) than the minimum flow rate specified details.
This error is reported when the
computed flow rate command is great Refer to dispensing
Flow command above than the user specified (or calibrated) equipment for fault
SEAL-270 WARN maximum (E%d) maximum flow rate, which is specified details.
This error is reported when the process Refer to dispensing
Channel 2 analog is zero mode is wet and the computed equipment for fault
SEAL-271 WARN (E%d) Channel 2 analog command is equal to details.
computed Channel 2 analog command Refer to dispensing
Channel 2 analog is is less than the minimum Channel 2 equipment for fault
SEAL-272 WARN below set point (E%d) analog output specified by the user details.
computed Channel 2 analog is great Refer to dispensing
Channel 2 analog is than the user specified (or calibrated) equipment for fault
SEAL-273 WARN above set point
Dispenser not (E%d) maximum Channel 2 analog output, details.
Refer to dispensing
SEAL-274 WARN Dispenser
pressurizedmeter
(E%s)not full Dispenser is not pressurized equipment
Refer for fault
to dispensing
SEAL-275 WARN Dispense
(E%s) meter not Dispenser meter is not full equipment
Refer for fault
to dispensing
SEAL-276 WARN pressurized (E%s) Dispense meter is not pressurized equipment for fault
Refer to dispensing
SEAL-277 WARN Auto
Drumpurge
emptyrequested
(E%s) Drum is empty equipment
Refer for fault
to dispensing
SEAL-278 WARN (E%s)
primer check passed Auto purge is requested equipment for fault
Refer to dispensing
SEAL-279 WARN Primer
(E%s) check failed Primer check passed (E%s) equipment
Refer for fault
to dispensing
SEAL-280 WARN (E%s) Primer check failed equipment
Refer for fault
to dispensing
SEAL-281 WARN Felt not advanced (E%s) Felt not advanced equipment for fault
This warning is posted when the system 1. Reposition the meter
detects that the meter has reached to prior to start dispensing
Meter Empty (E%d, Mtr its stroke limit during dispensing. After for the seam. 2. Lower the
SEAL-282 WARN %s) this condition, the system flow rate so that it can
This warning is posted when the system
detects that both meters have reached
to their stroke limit during dispensing.
This situation occurs if the material
supply pressure is too low. After this
1. Increase the material
condition, the system automatically supply pressure. 2. Lower
SEAL-283 WARN Both Meters Empty stops dispensing, but the robot keepsthe flow rate.
Plugged Tip Detected The system has detected that the 1. Check and clean the
SEAL-284 WARN (E%d) material flow has been blocked. gun tip.
Premature Reload Term One meter could not complete 1. Increase the material
SEAL-285 WARN (E%d) reloading
This error before
message theis other meter has
supply pressure 2. Lower
not currently not
SEAL-286 WARN Low Air Pressure (E%d) implemented N/A
Cmd prs NOT achieved The material pressure did not reach the 1. Check the IPD air supply
SEAL-287 WARN (E%d) specified pressure within the specified
pressure 2. Increase the
Perform a controlled start,
Application setup not The application specific TPPs and then select SETUP
SEAL-288 WARN done macros have not been loaded. APPLICATION under the
Dispenstool has attempted to install Reduce number of macros
additional macros, but the macro table needed and remove them
SEAL-289 STOP Macro table already full (under menu SETUP:Macros) was from the macro table or
SL__INST has been called, but there Do not run SL__INST as a
was no valid macro index number in program, only call
SEAL-290 STOP Invalid call to SL__INST register 32. SL__INST from a macro
The PNS Ack Verified input, which is Set up a PNS Ack Verified
No start sealing input needed with the current in the Cell Input I/O menu
SEAL-291 WARN defined communication configuration, has not and restart the robot.
Go into controlled start,
Press MENU-0, then
choose PROGRAM SETUP.
In setting up the Default error table the Change the Error Severity
Max Error table entry maximum number of error table entries Table entry to be a larger
SEAL-292 STOP exceeded ($ERRSEV_NUM) was exceeded. number in order to
No SLSHELL has been Document the events that
SEAL-293 loaded!!! The dispense shell is not loaded. led to the error, and call
Style bit is out of range The style bit in your JOB program is Set up a bigger maximum
SEAL-294 WARN (E%s) either less than 0 or great than the style bit or change the
You must set the port
The key dispenser input such as index and the type of the
SEAL-295 WARN I/O not assigned Eq%s dispenser ready is not assigned. dispener input to the
No action is required, but
Configurable error table The Dispenstool configurable error user should be aware that
SEAL-296 STOP empty table is empty. configurable fault
This warning is posted when the system 1. Reload the meter prior
Dispenser meter near detects that the meter near empty to start dispensing for the
SEAL-297 WARN empty (E%s) signal is asserted during dispensing. seam. 2. Lower the flow
%s option has not been The option required to setup this equip- Please load the required
SEAL-298 WARN loaded ment has not been loaded. option, and then try to set
Enc Belt slip (E%d, Mtr System has detected that the encoder
SEAL-299 WARN %s) to meter belt linkage is slipping. Tighten the belt tension.
%s I/O not mapped Specified I/O point has not been Assign specified I/O point
SEAL-300 WARN correctly assigned. before attempting
Make sure that the Input
OK to reload timeout Timed out waiting for the OK to reload signal for OK to Reload is
SEAL-301 WARN (E%d) signal from the Cell controller. mapped and is coming on
IPD mastering and/or calibrations have
ISD not configured not been completed. IPD cannot leave Complete IPD mastering
SEAL-302 WARN (ISD%d) SHUTOFF mode unless they are and calibrations.
Robot was unable to go back the full 1. Shorten the resume
Unable to go FULL resume distance because the last distance. 2. Re-teach
SEAL-303 WARN resume dist taught point was reached before full points so that there is
Force FFR Process Fast Fault Recovery has ended and Choose a process specific
SEAL-304 WARN Recov items process specific recovery options must recovery option
Dispense complete Fast Fault Recovery has ended and Choose a process specific
SEAL-305 WARN timeout (E%s) process specific recovery options must recovery option
The ISD configuration has not been Visit the ISD config menu,
Visit ISD config menu completed. You cannot map to an ISD and configure all defined
SEAL-306 first dispenser until ALL ISDs have been ISDs.
Unsupported eq. type The equipment you have selected is not At Control Start, select a
SEAL-307 (E%s) supported. supported equipment
Fault Reset Timeout The dispenser was unable to clear the Check the dispenser
SEAL-308 WARN (E%s) fault. controller, and clear the
IN_PROCESS ON before The IN_PROCESS dispenser signal is ON Check the dispenser
SEAL-309 WARN Job before the styleID communication controller, and make sure
IN_PROCESS OFF before The IN_PROCESS dispenser signal is OFF Check the dispenser
SEAL-310 STOP DispComp before the DispenseComplete controller, and make sure
VOL_OK ON before The VolumeOK dispenser signal is ON Check the dispenser
SEAL-311 STOP DispComp before the DispenseComplete controller, and make sure
Err while Flo Meas. This is a message to indicate the error
SEAL-312 Bypassed (E%s) ignored while the Flow measurement None.
VOL_OK ON before VolumeOK dispenser signal is ON Consult the dispenser
SEAL-313 WARN sending style ID before sending the style ID to the controller, and make sure
Rmt Strt/Purge req. The dispense ready signal was not Consult the dispenser
SEAL-314 WARN Flow
timeout (E%s)
meter disabled received
Flow within
meter has the
beenRemote Start/Purge
disabled via setup controller, and clear the
SEAL-315 WARN (E%s) menu item. Enable setup menu item.
Real-time adaption has been disabled
SEAL-316 WARN Adaption disabled (E%s) via setup menu item. Enable setup menu item.
Parameter checking has determined Check variable indicated
SEAL-317 WARN %s that the value is too high or low. for source of the problem.
A significant bubble was dispensed with Make sure any new
the material during the job. This is material is loaded
usually caused by improper loading of properly into the supply
new material. NOTE: This will often pump. Make sure all
SEAL-318 WARN Bubble detected (E%s) cause poor quality sealing. Examine the excess air has been
SSG servo not ready The servo power is turned
SEAL-319 (E%d) Servo Sealing Gun servo is not ready. off for some reason such
Needle mastering Needle mastering for Servo Sealing Gun Perform needle mastering
SEAL-320 incomplete (E%d) has not been completed. for Servo Sealing Gun.
Needle stroke limit Target position of Servo Sealing Gun No action is required. The
SEAL-321 (E%d) needle is out of range. target position will be
Q-N/V setup Q-N table setup for Servo Sealing Gun
SEAL-322 incomplete (E%d) has
Q-Nnot
databeen completed.
for Servo Sealing Gun is Set up the Q-N table.
SEAL-323 Q-N/V data error (E%d) invalid. Correct the Q-N data.
Needle mastering failed Needle mastering for Servo Sealing Gun Disconnect and reconnect
SEAL-324 (E%d) failed. the pulse coder cable,
General override is less than 100%
Override less than when the system executes SS with TCPP Set the general override
SEAL-325 100%% flow type in wet and non-step mode. to 100%.
Line Tracking not Line Tracking is NOT allowed with Use Select->Detail menu
SEAL-326 allowed. Dispensing in SpotTool+. to disable tracking
The remedies for the 4
scenarios above are: 1. Do
This is only a warning message to not use CLRQUE key. 2. Do
indicate that all of the triggers / part not set Clear Track Que
detects in the tracking queue have input high. 3. Also see
been cleared. There are 4 different remedy for SEAL-330
causes: 1. The CLRQUE key has been error. Since the detect
used on the MANUAL FUNCTIONS Line queue was full, this shows
Track menu. 2. The Clear Track Que one of 2 possibilities: A.
input on the Cell Inputs menu has been The maximum queue size
set high. 3. The detect queue was full is not sufficient to handle
and another detect was received. In the number of detects
this case a SEAL-330 error will also be needed in the queue. To
posted to indicate that the queue was increase the queue size,
full. The queue is cleared because an set
extra trigger was detected so the data $SPTK_CFG[x].MAX_QUE_
Tracking detect queue in the queue cannot be trusted. 4. A SIZE and cycle power on
SEAL-327 cleared (G:%s) Tracking queue read error was posted. the robot. B. Extra part
If the GET_PART macro is called and The detect wait condition
there are no triggers in the part detect is satisfied once a valid
queue then the macro waits for a valid part detect is placed into
detect to be placed into the queue. If the queue. If desired, the
the time that the robot is waiting for a amount of wait time
Waiting for tracking detect exceeds a specified value then before this message is
SEAL-328 part detect (G:%s) this warning message is generated. posted can be changed by
Since extra part detects
are being sent to the
robot, two remedies are:
This is a message to indicate that the 1. The Part Detect input
distance the part / conveyor has signal must be debounced
travelled since the previous part detect by the cell controller. 2. A
has not met / exceeded a minimum system variable exists
defined distance. This debounce logic which defines the
Tracking detect ignored - prevents unwanted detects from being minimum distance that
SEAL-329 min distance (G:%s) added to the part detect queue. the part / conveyor must
All related programs
cannot be resumed and
must be aborted. Any jobs
being tracked (jobs that
have passed the part
detect switch/sensor)
should be aborted and
not be processed. Since
the detect queue was full,
this shows one of 2
This message indicates that the part possibilities: 1. The
detect queue was full and another maximum queue size is
detect was received. In this case a SEAL- not sufficient to handle
337 error will also be posted to indicate the number of detects
that the queue was subsequently needed in the queue. To
cleared because an extra trigger was increase the queue size,
Tracking detect queue detected - so the data in the queue set
SEAL-330 full (G:%s) cannot be trusted. $SPTK_CFG[x].MAX_QUE_
The tracking encoder
should be set up such that
the encoder counts are
increasing as the conveyor
moves in the forward
direction. Consequently,
the Enc Scale Factor in the
The Enc Scale Factor in the Tracking Tracking Setup menu
Tracking encoder scale Setup menu is not set to a value should be set to a value
SEAL-331 not > 0 (G:%s) greater than 0. that is greater than 0.
An error was encountered while Document the events that
reading trigger data from the part led to the error and
detect queue. An error will also be contact your FANUC
posted to indicate the specific queue technical representative.
Tracking queue read error encountered. A SEAL-337 error All related programs
SEAL-332 error (G:%s) will also be posted to indicate that the cannot be resumed and
not be processed. 1.
Verify that triggers are
The trigger that was read from the part being added to and read
detect queue is stale. This indicates from the part detect
that the conveyor has already travelled queue correctly as the
Tracking detect is stale far beyond the limits where the trigger conveyor moves forward
SEAL-333 (G:%s) would be usable. and the job program
While the conveyor was moving the This is only a warning
Tracking encoder encoder value passed from the message and no remedy is
SEAL-334 rollover (G:%s) maximum positive integer value the needed. All operation
not be processed. The
Tracking encoder scale The Enc Scale Factor in the Tracking tracking encoder should
SEAL-335 is 0 (G:%s) Setup
A checkmenu is notmade
has been set toofa the
value of 0.0
current be
Seeset up such
causes thattothe
above
detect value before adding it to the determine the specific
part detect queue. It is compared to problem and possible
the previous detect value in light of the inferred solution. If the
Enc Scale Factor in the Tracking Setup problem persists, then the
menu to ensure it is sensible. When minimum part detect
posted, an additional code is also distance check can be
posted to provide further detail. Causes disabled as follows: A
for codes are as follows: Key: PD = system variable exists
Previous Detect CD = Current Detect +S which defines the
= Positive Enc Scale Factor -S = Negative minimum distance that
Enc Scale Factor ROL = Rollover Ps0 = the part / conveyor must
Passed 0 count Er1: PD>0 CD>0 +S travel since the last detect
CD<PD Er2: PD>0 CD>0 -S CD>PD Er3: in order to allow a new
PD<0 CD<0 +S PD>CD Er4: PD<0 CD<0 - detect into the queue.
Tracking detect count S CD<PD Er5: PD>0 CD=0 +S PD>CD Er6: This variable is
SEAL-336 invalid (G:%s) PD=0 CD>0 -S CD>PD Er7: PD<0 CD=0 -S $SPTK_CFG[x].MIN_PD_DI
For the Process logger option, some Set the DATA_TYPE or
user configurable system variables have DATA_INDEX fields to
been set up to monitor I/O via refer to a valid I/O point.
$SLSETUP[x].PLSETUP.REC_INT_ARY[n] If you do not wish to
Proc logger I/O read or monitor an I/O point then
SEAL-343 failure (E%d) $SLSETUP[x].PLSETUP.REC_REAL_ARY[n set the ITEM field to a
For the Process logger option, some Document the events that
user configurable system variables have led to the error and
been set up to monitor a data register contact your FANUC
Proc logger reg data via technical representative.
SEAL-344 invalid (E%d) $SLSETUP[x].PLSETUP.REC_INT_ARY[n] Please refer to the
For the Process logger option, some Set the DATA_INDEX field
user configurable system variables have to refer to a valid data
been set up to monitor a data register register. If you do not
via wish to monitor a data
Proc logger reg read $SLSETUP[x].PLSETUP.REC_INT_ARY[n] register then set the ITEM
SEAL-345 failure (E%d) or field to a different value
For the Process logger option, some Only variables of type
user configurable system variables have INTEGER, REAL, or
been set up to monitor other system BOOLEAN are supported.
variables via Change the VAR_STRING
$SLSETUP[x].PLSETUP.REC_INT_ARY[n] field to refer to a system
Proc logger sysvar data or variable of one of these
SEAL-346 invalid (E%d) $SLSETUP[x].PLSETUP.REC_REAL_ARY[n types only. If you do not
For the Process logger option, some Change the VAR_STRING
user configurable system variables have field to refer to a valid
been set up to monitor other system system variable. If you do
variables via not wish to monitor a
Proc logger sysvar read $SLSETUP[x].PLSETUP.REC_INT_ARY[n] system variable then set
SEAL-347 failure (E%d) or the ITEM field to a
For the Process logger option, some Change the ITEM field to
user configurable system variables have refer to a valid item type.
been set up to monitor items via: Valid values for ITEM are:
$SLSETUP[x].PLSETUP.REC_INT_ARY[n] 0 for no use 1 for I/O
or (signed short) 2 for I/O
Proc logger item field $SLSETUP[x].PLSETUP.REC_REAL_ARY[n (unsigned short) 3 for
SEAL-348 invalid (E%d) ]. The item type referred to by the ITEM Data number register 4
For the Process logger option, when a Document the events that
program is executed (planned) a led to the error and
process_id # is assigned to the TP contact your FANUC
program line containing a SE technical representative.
statement. This unique identifier will be Please refer to the
set to the position number or, if it is a SpotTool+ Setup and
Proc logger process_id standalone SE statement without Operations manual for
SEAL-349 not found (E%d) motion then it will be set equal to the further information.
Record the error string
parameters. Document
Proc logger internal This is an internal error for the Process the events that led to the
SEAL-350 error %d (E%d) logger option. error and contact your
Clear the operator panel
Outputs and / or parameters associated emergency stop and reset
with the dispensing equipment number the robot. Also refer to
Disp shutoff: OP E-stop indicated have been shut off due to an the alarm history for any
SEAL-359 (E%s) operator panel emergency stop. other errors that may be
Clear the teach pendant
Disp shutoff: TP E-stop indicated have been shut off due to a the alarm history for any
SEAL-360 (E%s) teach pendant emergency stop. other errors that may be
Reset the servo
Outputs and / or parameters associated disconnect and reset the
with the dispensing equipment number robot. Also refer to the
Disp shutoff: Servo off indicated have been shut off due to a alarm history for any
SEAL-361 (E%s) servo disconnect input. other errors that may be
Outputs and / or parameters associated Reset the Non Teacher
with the dispensing equipment number Enabling Device (NTED)
indicated have been shut off due to a and reset the robot. Also
Disp shutoff: NTED Non Teacher Enabling Device (NTED) refer to the alarm history
SEAL-362 (E%s) input. for any other errors that
Outputs and / or parameters associated Press the deadman switch
with the dispensing equipment number and reset the robot. Also
indicated have been shut off due to the refer to the alarm history
Disp shutoff: Deadman deadman switch being released while for any other errors that
SEAL-363 release (E%s) the teach pendant is enabled. may be present. Please
Reset the fence input and
Outputs and / or parameters associated reset the robot. Also refer
with the dispensing equipment number to the alarm history for
Disp shutoff: Fence indicated have been shut off due to the any other errors that may
SEAL-364 open (E%s) fence input. be present. Please refer to
Reset the hand broken
Outputs and / or parameters associated input and reset the robot.
with the dispensing equipment number Also refer to the alarm
Disp shutoff: Hand indicated have been shut off due to the history for any other
SEAL-365 broken (E%s) hand broken input. errors that may be
Clear the external
Disp shutoff: Ext E-stop indicated have been shut off due to an the alarm history for any
SEAL-366 (E%s) external emergency stop. other errors that may be
Outputs and / or parameters associated Reset the user operator
with the dispensing equipment number panel (UOP) IMSTP input
indicated have been shut off due to the and reset the robot. Also
Disp shutoff: IMSTP user operator panel (UOP) IMSTP refer to the alarm history
SEAL-367 (E%s) signal. for any other errors that
Clear the cause of the
Outputs and / or parameters associated fault and reset the robot.
with the dispensing equipment number Also refer to the alarm
Disp shutoff: robot indicated have been shut off due to the history for any other
SEAL-368 faulted (E%s) controller being faulted. errors that may be
Clear the cause of the
Outputs and / or parameters associated hold condition and reset
Disp shutoff: robot held indicated have been shut off due to the the alarm history for any
SEAL-369 (E%s) controller being held. other errors that may be
Enable Data Monitor
Operation from the
Utilities- Data Monitor
Data Monitor subsystem has been screen. On Setup-
disabled, by user choice or Diagnostics screen,
Data Monitor is automatically because limit on data consider increasing Max
SEAL-370 disabled files set by the user has been reached Data Files Stored or
On Setup-Diagnostics
screen, consider
The limit on data files that may be increasing Max Data Files
Maximum DMON Data stored by the Data Monitor subsystem Stored or setting Disable
SEAL-371 Files exceeded has been reached. After Max Files to NO. See
Wait till the end of Data
Monitor session. If in
Data Monitor session is in progress and Automatic Sampling
DMON in progress, item user tried to change setup that could mode, this happens at job
SEAL-372 locked affect the current session. end. If sampling in
To re-enable, ensure that
Asynchronous Asynchronous Data Monitoring has Utilities-Data Monitor-
SEAL-373 DataMonitor disabled
Asynchronous been disabled Data Monitor has been
Asynchronous Data Monitor Operation is
SEAL-374 DataMonitor enabled enabled N/A
File management features have been No action required. To re-
disabled because user set Setup- enable, you may set Max
DMON file Diagnostics-Max Data Files Stored to 0. Data Files to non-zero
SEAL-375 management disabled Stored data will be over-written by value Ensure that
File management features have been No action required if
enabled because user set Setup- destination data storage
DMON file Diagnostics-Max Data Files Stored device has adequate
SEAL-376 management enabled
Sample_start builtin value. Data Monitor
Karel builtin will storereturned
SAMPLE_START as manya space.
ContactToyour
disable,
FANUCset
SEAL-377 exec failed builtin
Sample_end bad status.
Karel builtin SAMPLE_END returned a service representative.
Contact your FANUC
SEAL-378 exec failed bad status. service representative.
Ensure that these items
Monitor session not on the Dispense
SEAL-379 started Data Monitor session not started. Diagnostics Setup menu
If sldiagdb.dt has been
modified, then verify that
it has been created and
Dispense Diagnostics encountered an loaded correctly. Refer to
Processing error for error while processing the sldiagdb.dt FR:DGERRORS.LS for a
SEAL-380 sldiagdb.dt to set up the option. summary of any errors
Processing OK for Dispense Diagnostics encountered NO
SEAL-381 sldiagdb.dt errors while processing the sldiagdb.dt No action
Refer required.
to cause code on
this alarm for failure
reason. If -File not found-
is also posted then please
set Max data files stored
to zero on the Dispense
Diagnostics menu and try
again. If -Device is full- is
also posted then the RAM
Disk free area is too small
Dispense Diagnostics encountered an to accommodate the file.
error while attempting to copy the You may also try to power
SEAL-382 SYSTE Copy to rd:diag.dt failed output DT file to rd:diag.dt. down the controller to
SENS-000 M Unknown error System internal error Notify FANUC
PAUSE. During data reception, parity, overrun Check that the
SENS-001 G Hardware error occured and framing errors occurred. communication setting
PAUSE. DSR off when An attempt was made for data Check that the
SENS-002 G
PAUSE. transmission transmission,
The undefinedbutTCCDSR
wassignal at the
received specification
from Check and
the data sent from
SENS-003 G
PAUSE. Undefined TCC received the sensor.
BCC of thereceived data from the the sensor.
Check the data sent from
SENS-004 G
PAUSE. Invalid software parity The
sensor is wrong.
format of the received data is the sensor.
Check the data sent from
SENS-005 G Invalid data format wrong. the sensor.
PAUSE. The answer from the sensor is not Check that the sensor side
SENS-006 G Response time over received within the allowable time. does not stop due to an
PAUSE. The interval of characters sent from the Check that the sensor side
SENS-007 G
PAUSE. Interval time over sensor exceeded
Calculating the allowable
transform matrix is time. does not
Check thestop due to an
compensation
SENS-008 G
SYSTE Calculate matrix error impossible. data sent from the sensor.
SENS-009 M
SYSTE
SENS-010 M
SYSTE
SENS-011 M
SYSTE
SENS-012 M
SYSTE
SENS-013 M
SYSTE
SENS-014 M
SYSTE
SENS-015 M
SYSTE
SENS-016 M
SYSTE
SENS-017 M
SYSTE
SENS-018 M
SYSTE
SENS-019 M
KW ovrd reg. is out of The value of Kerf Width is not in a valid Set the kerf width in a
SHAP-000 range. range. range of 0 to 4.99. If a
Speed ovrd reg. out of The value in the register for TRAVEL Set the travel speed in the
SHAP-001 range. SPEED override is not in a valid range. speed override register to
The registers for each shape function
such as kerf width override, speed Insure that each register is
Values cannot be override, and so forth in the Shape not used more than one
SHAP-002 duplicated. Setup menu must be unique. If you try time.
Corner radius is too The scheduled corner radius is larger Reduce the scheduled
SHAP-003 large. than the computed working radius of corner radius or increase
Slot Len. must be > than The scheduled width for the slot is Make the slot width
SHAP-004 wid. larger than the scheduled length for smaller than the length or
The Shape Template FOR A CUT Undo the modifications if
Shape Template was MACRO (ex: CUT_CIR.TP) has been you can or if you have a
SHAP-005 modified!! modified and is no longer valid for this back up copy of this shape
Invalid schedule The passed in schedule number for the Set the value in the range
SHAP-006 number used. shape in the teach pendant program is of 1 to 100.
The shape program requested could The shape program might
Error Opening Cut not be opened or the shape cut have been deleted. If you
SHAP-007 Shape Macro program was modified and an expected have a back up copy of
Error Writing to Shape Could not update the shape macro with If you have a back up copy
SHAP-008 Macro. values in the shape schedule. of this shape macro,
Blend-in distance too The blend-in distance is too large for Decrease the blend-in
SHAP-009 large. the specified shape. distance.
Length must be > Major The length for the key shape must be Increase the length of the
SHAP-010 dia. larger than Major diameter of the key key shape or decrease the
Maj dia must be > Min The key shape major diameter, must be Increase the size of the
SHAP-011 dia. larger than the key shape minor key shape major diameter
Program name must be The shape shift utility was executed Select a valid program for
SHAP-012 set first. without the name of the program the shift function.
Position num must be The shape shift utility was executed Select a valid position for
SHAP-013 set first. without the position number entered the shift function.
Shift must be cleared Program name column was modified or Clear the shape shift
SHAP-014 first. position num column was modified. schedule.
Position doesn't exist in The selected position does not exist in Verify that you have the
SHAP-016 prog. the selected program. correct program selected
Posn [REPRE] must be The position type of the position Change the position type
SHAP-017 cartesian. register being used, has been changed back to Cartesian.
Center posn PR[1] The center position for the Custom Record the center
SHAP-021 uninitialied shape, has not been taught in the position for the custom
%s - Joint moves not The Custom Shape cut program has Change the joint move to
SHAP-022 allowed joint motions which are not allowed. a linear move.
The controller will try to
set up the macro table
again at the next
SHAP-031 Macro %s not set The macro table was not set correctly. Controlled start. It is
The program is not of a circular type. Select a program that was
Program is not of The program is either a non-shape generated as a circular
SHAP-040 circular type generated program or the program is type.
The program is not of a slot type. The
Program is not of slot program is either a non-shape Select a program that was
SHAP-041 type generated program or the program is generated as a slot type.
Program is not of hexagon type. The Select a program that was
Program is not of program is either a non-shape generated as a hexagon
SHAP-042 hexagon type generated program or the program is type.
The program is not of a rectangle type. Select a program that was
Program is not of The program is either a non-shape generated as a rectangle
SHAP-043 rectangle type generated program or the program is type.
The program is not of a key type. The
Program is not of key program is either a non-shape Select a program that was
SHAP-044 type generated program or the program is generated as a key type.
the program is not of a pommel type. Select a program that was
Program is not of The program is either a non-shape generated as a pommel
SHAP-045 pommel type generated program or the program is type.
The program is not of a custom type. Select a program that was
Program is not of The program is either a non-shape generated as a custom
SHAP-046 custom type generated program or the program is type.
The diameter must be > 0. The value for Set the value higher than
SHAP-047 Diameter must be > 0 the diameter is 0 and a shape can not 0.
The diameter must be > kerf width
(KW). The diameter is smaller than the Set the value larger than
SHAP-048 Diameter must be > KW current kerf width and this size of the kerf width.
The length must be > 0. The value for Set the value higher than
SHAP-049 Length must be > 0 length is 0 and a shape can not be 0.
The width must be > 0. The value for Set the value higher than
SHAP-050 Width must be > 0 width is 0 and a shape can not be 0.
The width must be > kerf width (KW)
The width is smaller than the current Set the value larger than
SHAP-051 Width must be > KW kerf width and this size of shape can the kerf width.
NumPts must be a multiple of 2. In
NumPts must be order for the proper number of circular Set the numbers of points
SHAP-052 multiple of 2 points to be generated, this value to be in multiples of 2.
Easy Normal is not loaded. The optional Load the optional Easy
SHAP-053 EZ Normal is not loaded Easy Normal feature, is not loaded on Normal feature.
Program is write The program is write protected. The Turn off protection if you
SHAP-054 protected program selected is write protected want to use this program.
Not supported for Not supported for custom. Move to the Go to the created
SHAP-055 custom center position is not supported for a program and use step
The motion system is The motion system is not ready. To test Reset the motion system
SHAP-056 not ready the program, the motion system must so that the program can
Edge distance must be < diameter/2 + Make sure the edge
Edge distance must be kerf width (KW). The edge distance is distance does not exceed
SHAP-057 < diameter/2 + KW larger than the diameter of the circle the diameter/2 + kerf
Single step is not Single step is not support for test Turn off single step or go
SHAP-058 supportedsocket not
Specified mode. to program SELECT and
SP-001 WARN defined Specified software does not exist. Load necessary software.
SP-002 WARN Data is out of range
Undefined Specified software does not exist. Load necessary software.
SP-003 WARN function_code
Specified sp not Specified software does not exist. Load necessary software.
SP-004 WARN connected Specified software does not exist. Load necessary software.
SP-005 WARN IIlegal socket
Allocate data type
already Specified software does not exist. Load necessary software.
SP-006 WARN exist Can not access memory correctly. System error.
SP-007 WARN Allocate data not exist Can not access memory correctly. System error.
SP-008 WARN Do not use spcall Specified software does not exist. Load necessary software.
SP-009 WARN Illegal
Not variable
create size
memory Can not access memory correctly. System error.
SP-010 WARN array
Not delete memory Can not access memory correctly. System error.
SP-011 WARN array
TOP or BOTTOM Can not access memory correctly. System error.
SP-012 WARN pointer Illegal software selected. Select correct
Request correctsoftware.
SP-013 WARN Command not found Illegal command request. command.
Check serial port setting.
SP-014 WARN File not found Specified file does not exist. Check if file
Request exists.
correct
SP-015 WARN Illegal command Illegal command request. command.
SP-016 WARN Illegal process Specified software does not exist. Load necessary software.
SP-017 WARN memory not allocated Can not access memory correctly. System error.
SP-018 WARN F-ROM not writenot
source address Specified software is not loaded. Check F-ROM module.
SP-019 WARN even Specified software is not loaded. System error.
SP-020 WARN Not compatible version Specified software is not loaded. Check software version.
SP-021 WARN CST not connected Specified software does not exist. Load necessary software.
SP-022 WARN INF space
ABORT too small
Statement INF area in MST insufficient. System error.
SP-023 WARN Executed ABORT Statement Executed System error.
SPOT-000 WARN Unknown error (SWG0) An internal error has occured. Cold start the controller
The backup state spot welding Make sure that the
instruction BU=* was used before a backup state is closed
weld, but the backup state was in the when using the BU=*
open (BU=O) position at the time the command. Either change
instruction was executed. Note: BU=* BU=* to BU=C, or insert a
ABORT. indicates that the backup state remains BACKUP=CLOSE statement
SPOT-001 L Backup not closed %s unchanged from the last position. To before this statement.
The isolation contactor on the specified Verify the contactor state.
weld controller is in a fault condition. If Make sure that the
no program is running, then this correct contactor
message is posted if either the Iso instruction has been
contactor output is high or the Iso programmed in the teach
ABORT. contactor input is high. If a program is pendant program. Verify
SPOT-002 L Iso contactor fault %s running or a manual weld is being the input status and
Verify the water flow and
water saver operation.
ABORT. Verify the input
SPOT-003 L Water saver OK fault %s The water saver input is low. configuration and status
Verify the water flow and
sensor operation. Verify
PAUSE. the input configuration
SPOT-004 L Water flow OK fault %s The water flow OK input is low. and status from the Spot
Verify the weld
transformer status. Verify
PAUSE. the input configuration
SPOT-005 L X-former OK fault %s The transformer OK input is low. and status from the Spot
Check the Weld Enable
status from the Soft Panel
menu and compare it with
the weld controller Weld
Enable status. These must
The weld enable status from the weld be the same. The Soft
PAUSE. Weld enable mismatch controller does not match the weld Panel can be accessed
SPOT-006 L %s enable status on the robot. using the teach pendant.
Check the weld controller
for reason for the alarm.
Check the Weld I/O menu,
as well as the equipment
I/O wiring. Using the
The robot timed out waiting for the teach pendant: 1. Press
PAUSE. Weld in process Weld in Process input from the weld I/O. 2. Press F1, [TYPE]. 3.
SPOT-007 L timeout %s controller. Select Weld Interface. If
for the reason for the
alarm. Check the Weld I/O
menu, as well as the
equipment I/O wiring.
The robot timed out waiting for the Using the teach pendant:
PAUSE. Weld complete timeout Weld Complete input from the weld 1. Press I/O. 2. Press F1,
SPOT-008 L %s controller. [TYPE]. 3. Select Weld
Check the length of the
The Weld Complete input was detected weld controller's Weld
PAUSE. Got weld complete before the Weld in Process input was complete output. Verify
SPOT-009 L early %s received. the input configuration in
for the reason for the
alarm. Verify the input
configuration and status
in the Weld Interface I/O
PAUSE. Major alarm detected screen. Using the teach
SPOT-010 L %s A Major Alarm was received. pendant: 1. Press I/O. 2.
for reason of alarm. Verify
the input configuration
and status in the Weld
Interface I/O screen. Using
PAUSE. Minor alarm detected the teach pendant: 1.
SPOT-011 L %s A Minor Alarm was received. Press I/O. 2. Press
Check the S= value of the
current line of the teach
pendant program. The
smallest schedule number
allowed is 0. For digital
weld controllers, the the
largest schedule number
An inavlid weld schedule was allowed depends on the
PAUSE. programmed in the teach pendant width of the Weld
SPOT-012 L Bad schedule (S=*) %s program. Schedule group output. If
The valve pressure spot welding
instruction P=* was encountered in a
teach pendant program, but no Be sure to include a direct
PAUSE. Undefined pressure previous pressure value had been pressure value instead of
SPOT-013 L (P=*) assigned. Note: P=* indicates that the using "*".
Check the gun operation
and sensor states. Check
the Equipment I/O menu
and verify signal status, as
well as the equipment I/O
The robot timed out waiting for the wiring. Using the teach
backup close detect input. This input pendant: 1. Press I/O. 2.
PAUSE. BACKUP CLOSE DETECT indicates that the gun has reached the Press F1, [TYPE]. 3. Select
SPOT-014 L timed out %s backup close position. Spot Equip. If the input is
the Equipment I/O menu,
The robot timed out waiting for the gun teach pendant: 1. Press
PAUSE. GUN CLOSE DETECT close detect input. This input indicates I/O. 2. Press F1, [TYPE]. 3.
SPOT-015 L timed out %s that the gun has closed. Select Spot Equip. If the
The robot timed out waiting for the I/O wiring. Using the
Backup Open Detect input. This input teach pendant: 1. Press
PAUSE. BACKUP OPEN DETECT indicates that the gun has reached the I/O. 2. Press F1, [TYPE]. 3.
SPOT-016 L timed out %s backup open position. Select Spot Equip. If the
The robot timed out waiting for the gun teach pendant: 1. Press
PAUSE. GUN OPEN DETECT open detect input. This input indicates I/O. 2. Press F1, [TYPE]. 3.
SPOT-017 L timed out %s that the gun has opened. Select Spot Equip. If the
Ensure that all cables to
the serial port are
PAUSE. A serial communications error was properly connected, and
SPOT-018 L Serial comm error %s detected. that the weld controller is
A timeout occured while polling the Ensure that all cables to
PAUSE. serial weld controller for status the serial port are
SPOT-019 L Serial polling timeout information. properly connected, and
PAUSE. Not in safe starting the position where the teach pendant teach pendant was
SPOT-020 L position was enabled. enabled, abort the
The Gun Close Detect input is high at and sensor states. Verify
PAUSE. GUN CLOSE DETECT the same time that the Gun open the input status and
SPOT-021 L input is on %s detect input is to be checked. configuration from the
The Gun Open Detect input is high at and sensor states. Verify
PAUSE. GUN OPEN DETECT the same time that the Gun Close the input status and
SPOT-022 L input is on %s Detect input is to be checked. configuration from the
BU CLOSE DETECT is on the same time that the Gun Close the input status and
SPOT-023 WARN %s Detect input is to be checked. configuration from the
BU OPEN DETECT is on the same time that the Gun Close the input status and
SPOT-024 WARN %s Detect input is to be checked. configuration from the
In the teach pendant
program, check the valve
pressure spot welding
instruction P= value. Note:
The smallest valve
pressure allowed is 0. For
digital weld controllers,
An invalid binary valve pressure was the largest pressure
PAUSE. programmed in the teach pendant number allowed depends
SPOT-025 L Bad pressure (P=*) %s program. on the width of the Valve
for reason of alarm. Verify
the input status and
configuration in the Weld
PAUSE. Reset welder timeout The robot timed out waiting for the Interface I/O screen. Using
SPOT-026 L %s weld controller to reset a major fault. the teach pendant: 1.
A system failure has caused internal
PAUSE. Serial sequence not synchronization problems. Serial
SPOT-027 LPAUSE. started
Serial initialization interface task with welder did not Cold
Makestart
surethe
thatcontroller.
the port
SPOT-028 L
PAUSE. failed Serial portoptions
Incorrect specification
loadedisfor
invalid exists sure serial options
serial weld
Make
SPOT-029 L Serial option not loaded control properly loaded.
Verify the contactor state.
The specified gun contactor is in a fault Make sure that the
condition. If a program is running, or a correct contactor
manual weld is being executed, then instruction has been
the output, if defined, must be high, programmed in the teach
PAUSE. and the input, if defined, must be high pendant program. Verify
SPOT-030 L Gun contactor fault %s too. the input status and
Check the setting of the
shot pin. Make sure the
This error is only posted for set/reset shot pin has been made
type guns. The shot pin was not set before attempting to
PAUSE. correctly, so the gun could not be close the gun. Check the
SPOT-031 L Gun open fault %s opened. Equipment I/O and verify
The Gun Close Detect input was not the Equipment I/O and
received within the specified timeout verify that the input is
SPOT-032 PAUSE Gun close fault %s period. assigned correctly. Verify
The BU (backup) open detect input was the Equipment I/O and
not received within the specified verify that the input is
SPOT-033 PAUSE Backup open fault %s timeout period. assigned correctly. Verify
The BU (backup) close detect input was the Equipment I/O and
not received within the specified verify that the input is
SPOT-034 PAUSE Backup close fault %s timeout period. assigned correctly. Verify
The current number of
equipment for which the
system is configured is
message. Only use the
Invalid equipment (%s An invalid equipment number was value one up to and
SPOT-035 PAUSE defined) specified. including the number
weld controllers for which
the system is configured is
Invalid weld controller An invalid weld controller number was value one up to and
SPOT-036 PAUSE (%s defined) specified. including the number
Gun contactors are
defined at Controlled
start, from the Spot
Config menu. If extra gun
contactors are defined at
Controlled start, then the
The Gun contactor teach pendant Equipment I/O menu will
No gun contactors instruction was programmed, but no allow you to define the
SPOT-037 WARN defined gun contactors are defined. I/O for the gun contactor.
The stud low detect prox switch in the Refill the hopper, or, if it is
feed hopper for the current Power unit not low, check the
SPOT-038 WARN Stud feeders low has indicated that the hopper needs function of the prox.
The welder power unit air pressure
System air pressure detect switch has indicated that the Increase system air
SPOT-039 PAUSE below 85psi system air has fallen below the pressure.
The Ready Relay for the current stud
welding power unit is off. This is caused
SPOT-040 WARN Stud Welder Not Ready by the unit having a fault that has not Reset the fault
Make sure that the proper
tool is attached to the
A TPE instruction was programmed to arm before attempting to
use a tool change equipment, but that use it. Tool changes are
SPOT-041 WARN Tool not attached %s tool was not attached to the arm. done with TPE macros.
The robot detected a Stud Welder Time Once the robot is paused,
Out Fault from the current controller carefully pry the gun and
during a weld. This fault occurrs when the stud apart, then reset
Stud Welder Time Out the controller does not detect a fault on weld controller
SPOT-042 WARN Fault completed weld or a bad weld after the and resume the program.
The Stud Weld controller has signaled The stud checker will
the robot that a weld fault has occured.
automaticly verify the
This indicates that insuficient current
quality of the weld. If bad,
SPOT-043 PAUSE Stud Welder Weld Fault was passed during the weld, check the position of the
This fault is signaled by the Stud Weld
The stud checker will
Stud Welder Arc controller if the voltage sensor reports
automaticly verify the
SPOT-044 WARN Voltage Fault too little arc voltage during the weldquality of the weld. If bad,
The robot did not see the current Check the weld controler
No Current detected: sensor input go high throughout the to verify that the schedule
SPOT-045 WARN %s weld, indicating no current does include a heat
The Auto Retry Weld feature This is just a warning to let
encountered a weld fault and retried the operator know that a
the weld the indicated number of weld was retried, and to
Weld auto retried %s times. This warning is posted for every.
alert the operator that
SPOT-046 WARN time(s) SPOT instruction encountered in which weld controller
Carefully jog the robot
away from the interfering
objects, or free the weld
gun from the Tip Stick.
Verify that the Collision
Guard option is not set
A Collision Detection Alarm has been too sensitive. Using the
detected. The robot might have teach pendant: 1. Press
Collision Detection collided with an object, or a Tip Stick MENUS. 2. Select SETUP.
SPOT-047 WARN Alarm might have occurred. 3. Press F1, [TYPE]. 4.
No Coll. Guard Reg. No register has been defined for use Use the Collision Guard
SPOT-048 PAUSE Defined with the Collision Guard Update macro. SETUP screen to define a
The data contained in the Collision Enter the correct data
Coll. Guard Reg. Data Guard macro register is not an integer into the Collision Guard
SPOT-049 PAUSE Error or is not in the range of 1 to 200. macro register.
In the teach pendant
program, check the
equalization pressure spot
welding instruction EP=
value. Note: The smallest
valve pressure allowed is
0. For digital weld
An inavlid binary equalization pressure controllers, the largest
was programmed in the teach pendant pressure number allowed
SPOT-050 PAUSE Bad Pressure (EP=*) %s program. depends on the width of
The equalization pressure spot welding
instruction EP=* was encountered in a
teach pendant program, but no Be sure to include a direct
Undefined Pressure previous pressure value had been equalization pressure
SPOT-051 PAUSE (EP=*) %s assigned. Note: EP=* indicates that the value instead of using "*".
Check the stud that
A faulty stud weld has occurred. A generated the error and
SPOT-052 PAUSE Suspect Weld pressure value has been used. remove it if necessary.
The stud feeder for gun 1 is low on Add more studs to the
SPOT-053 WARN Feeder Low - Gun1 studs. feeder for gun 1 at an
The stud feeder for gun 2 is low on Add more studs to the
SPOT-054 WARN Feeder Low - Gun2 studs. feeder for gun 2 at an
Check the stud welding
A weld controller fault has occured on controller for the reason
SPOT-055 WARN Stud Controller Fault1 gun 1. for this fault. Reset the
Press SHIFT-GUN to return
the studwelding gun to its
retracted position. Reset
the fault, then choose the
Weld Head Not Studwelding gun 1 has not been appropriate type of fault
SPOT-056 PAUSE Retracted-Gun1 retracted. recovery. Verify input
Press SHIFT-GUN to return
the studwelding gun to its
retracted position. Reset
the fault, then choose the
Weld Head Not Studwelding gun2 has not been appropiate type of fault
SPOT-057 PAUSE Retracted-Gun2 retracted. recovery. Verify input
The studwelding controller detected
Studwelder - Air that the air pressure has fallen below Increase the system air
SPOT-058 WARN Pressure Low the minimum operating level of 85 psi. pressure.
Check the stud welding
A weld controller fault has occurred on controller for the reason
SPOT-059 PAUSE Stud Controller Fault2 gun 2. for this fault. Reset the
Jog the robot to a valid
Robot Not At Home The robot is not at a valid HOME HOME position taught in
SPOT-060 WARN Position position. the Reference Position
SYSTE A request was sent to the timer card, Retry the request. The
SPOT-061 M Request Failed but no response was received. timer card might be busy
SYSTE Please retry function A request was sent to the timer card, Retry the request. The
SPOT-062 M again but no response was received. timer card might be busy
A weld fault has happened on the weld Please refer to manual for
SPOT-063 WARN %s controller. weld controller for
A weld alert has happened on the weld Please refer to manual for
SPOT-064 WARN %s controller.
A weld event has happened on the weldiscontroller
This for
logging information
SPOT-065 WARN %s weld controller. only. No remedy is
Unable to perform operation due to Refer to the specific IWC
SPOT-066 WARN Iwc NOT ready IWC status. error status, and follow
Define a DO[] for the
No Shunt Trip output The Shunt Trip output has not been Shunt Trip in the Weld
SPOT-067 PAUSE for WC:%s
Weld done input not defined.
The weld done input has not been Interface I/O screen. Using
SPOT-068 mapped %s
Studwelder mapped.
The maintenance input from the Define check
Please weld done
the io
SPOT-069 Maintenance on studwelder is on. studwelder for the cause
SPOT-070 PAUSE Internal Error (system) Internal system error. led to the error and call
The number of bits required for the Reduce the equalization
Equalization press equalization pressure condition is pressure condition, or
SPOT-071 PAUSE condition > max gout larger than the width of the group increase the dimension of
Equalization pressure The I/O assignment (mapping) for the Map the I/O properly, or
SPOT-072 PAUSE IO error equalization pressure output is invalid, put the I/O back online.
Dresser speed not The dresser did not achieve the Check the dresser for
SPOT-073 acheived. requested dress speed in time. mechanical issues.
Tdress sched speed The speed specified in the dresser Reduce the dresser speed
SPOT-074 exceeds dresser speed. schedule exceeds the speed limit of the in the dresser schedule.
Max cutter counts The number of cuts the dresser has Change the cutter blade
SPOT-075 exceeded. done has exceeded the cutter limit for and reset the cutter
Max tip dresses on Gun The number of dresses on the tips has Change the caps and reset
SPOT-076 #%d exceeded. exceeded the dress limit for the tips. the dress count.
Tdress min Torque not The minimum torque required for dress Verify teach position of
SPOT-077 acheived. determination was not acheived. gun, and force in
Tdress max Torque The maximum torque required for valid Verify teach position of
SPOT-078 exceeded. dress determination was not exceeded. gun, and force in
The Tip Dress schedule specified in the Edit the TIPDRESS
TIPDRESS instruction was greater than instruction and verify the
SPOT-079 Bad Tip Dress Schedule. the number of available tip dress schedule value does not
Invalid process axis for The process axis number for the Verify that
SPOT-080 dresser. dresser for the current gun is invalide. $sgtdset[dresser_number]
Max free torque The free spinning torque of the dresser Verify operation of the
SPOT-081 exceeded. has exceeded the user specified dresser. This alarm could
Got weld inprocess The Weld In process input was Check the weld controller
SPOT-082 early %s detected before the Weld was initiated. to make sure the weld
1. Gun tips may have hit dresser blade 1.Re-teach the tip
earlier than expected. 2. Gun or dresser dressing position or adjust
Early/LATE Blade may be out-of-position slightly. 3. Tips dresser position 2.Confirm
Contact (PT=%2.1f, may be out of alignment. 4. Gun zero part thickness value and
SPOT-083 BC=%2.1f) position may not be correct. (In this gun zero position are
The dresser number specified does not Verify that the dresser
SPOT-084 Invalid dresser number. exist. number specified is
Speed to low during Verify that the dressing
dress. Check for motor The dresser motor speed was too low pressure schedule is
SPOT-085 stalling. during phase 1 of the dress. correct and not too high.
Line Tracking not Line Tracking is NOT allowed with Use Select->Detail menu
SPOT-086 allowed. Spotwelding. to disable tracking
The number of above-mentioned ** Refer to Nadex DeviceNet
indicate the fault code of weld weld controller manual
SPOT-091 91**: XXXX controller. And, XXXX indicates an for more information
Change of ELCB auxiliary contact was Refer to Nadex DeviceNet
SPOT-092 ELCB signal detection detected. weld controller manual
Illegal equipment An illegal equipment number has been Inspect the teach pendant
SPOT-270 PAUSE number specified. program header and enter
SPOT-271 PAUSE Illegal gun index The gun index is invalid. led to the error, and call
SPOT-272 PAUSE Illegal PX index The PX index is invalid. led to the error, and call
Illegal pressure profile Document the events that
SPOT-273 PAUSE state The pressure profile state is invalid. led to the error, and call
This is a warning to inform you that
weld simulation has been enabled. This Disable weld simulation, if
message is posted one time when weld weld mode simulation is
SPOT-300 WARN Weld sim Enabled simulate enable has changed from not desired.
This is a warning to inform you that Set weld mode to disable,
weld enable mode has been activated and re-enable weld
while weld simulate mode is active. simulate if you still want
Weld enabled during Weld simulate is only available when to use weld simulate;
SPOT-301 WARN spot sim weld mode is disabled. Therefore, weld otherwise no action is
This warning informs you that weld Set weld mode to disable,
simulation has been disabled. This and re-enable weld
message is posted one time, when simulate if you still want
SPOT-302 Weld sim Disabled $spotcofig.$sim_enb changes from to use weld simulate;
This message is posted to identify a Set $spotcofig.$sim_warn
spot that executed while weld = FALSE, to simulate welds
simulation was active. The message will without the SPOT-303
look like: SPOT-303: SimWld warning. Set
(Progname,Line#). Note that this $spotcofig.$sim_enb =
SPOT-303 %s message is only posted if FALSE, to disable weld
The weld retry function is enabled, and If you want to complete
$spotconfig.$stroke_enable changed the weld enable stroke,
from TRUE to FALSE during the retry and press FAULT RESET to
Stroke disabled during process. In this case, a weld was continue. If you do not
SPOT-304 WARN weld retry %s started, but not completed. SPOT-304 want to complete the
1. Review the vision
At least two of the models contained results using either the
SPOT-306 Found duplicate model the same Model ID. Runtime screen or Vision
1. Verify that the
Gun Tip Test missing The Gun Tip base or tip model was not enclosure LED is
SPOT-307 model found by vision. operational 2. Verify that
1. Verify that the
Robot Tip Test missingThe Robot Tip base or tip model was enclosure LED is
SPOT-308 model not found by vision. operational 2. Verify that
One or more of the four models 1. Verify that the
Tip Alignment missing required to make an alignment check enclosure LED is
SPOT-309 model was missing. operational 2. Verify that
The Gun tip wear exceeded the user set 1. Change Cap and reset
SPOT-310 Gun Tip Wear exceeded threshold nominal condition 2.
results using either the
Gun Cap Changed The Gun Tip tip model displacement Runtime screen or Vision
SPOT-311 Length Exceeded exceeded the user set threshold Setup screen 2. Verify the
The Gun Tip base model displacement Runtime screen or Vision
SPOT-312 Gun Shank Displaced exceeded the user set threshold Setup screen 2. Verify the
1. Check cap for material
The Gun cap length increased beyond on tip face 2. Verify the
SPOT-313 Gun Tip Increase Error the user set threshold. user set threshold 3. Cap
Robot Tip Wear The Robot tip wear exceeded the user 1. Change Cap and reset
SPOT-314 exceeded set threshold nominal condition 2.
Robot Cap Changed The Robot Tip tip model displacement Runtime screen or Vision
SPOT-315 Length Exceeded exceeded the user set threshold Setup screen. 2. Verify the
The Robot Tip base model results using either the
displacement exceeded the user set Runtime screen or Vision
SPOT-316 Robot Shank Displaced threshold Setup screen. 2. Verify the
1. Check cap for material
Robot Tip Increase The Robot cap length increased beyond on tip face 2. Verify the
SPOT-317 Error the user set threshold. user set threshold 3. Cap
Tip Alignment exceeds 1. Adjust equipment to
SPOT-318 Threshold The tips were out of alignment realign weld caps 2.
Gun tip did not match the tip dressed 1. Re-dress the weld caps
SPOT-319 Gun Tip Dress failed model 2. Adjust the Vision
Robot tip did not match the tip dressed 1. Re-dress the weld caps
SPOT-320 Robot Tip Dress failed model 2. Adjust the Vision
1. Change Gun Cap 2.
Gun Cap Change/Type Gun Cap did not match the new cap Verify that the correct cap
SPOT-321 failed model type is on the weld gun 3.
1. Change Robot Cap 2.
Robot Cap Change/Type Robot Cap did not match the new cap Verify that the correct cap
SPOT-322 failed model type is on the weld gun 3.
Test message for This is a message for testing purposes Please contact your
SPOT-323 Recovery only.
User chose to Continue from a tip FANUC representative.
SPOT-324 Tip Inspection Continue inspection
User chosefault
to Retry from a tip NONE. Notification only.
SPOT-325 Tip Inspection Retry inspection fault
User chose to Abort from a tip NONE. Notification only.
SPOT-326 Tip Inspection Abort inspection fault NONE. Notification only.
No Recovery Option User did NOT choose any recovery from
SPOT-327 Selected a tip inspection fault NONE. Notification only.
If an IWC board was
expected, this indicates
that there is probably a
No IWC boards were found on the serious hardware problem
SPOT-350 WARN IWC board not found controller. and that the board should
The IWC driver is waiting for the This is a system
PC/104 motherboard to complete its programming error.
SPOT-351 WARN IWC driver not running reset cycle. Document the events that
This is a system
The specified IWC board is not programming error.
SPOT-352 WARN Invalid IWC index installed. Document the events that
A message cannot be sent to the IWC This is a system
IWC message in because a previous message programming error.
SPOT-353 WARN progress transaction is still in progress. Document the events that
The buffers sent for a message This is a system
transaction are not valid in number programming error.
SPOT-354 WARN Invalid IWC msg buffers and/or length. Document the events that
This is a system
Invalid IWC function The function request to the IWC driver programming error.
SPOT-355 WARN code is invalid. Document the events that
The IWC reported a checksum error Document the events that
Checksum error, IWC during a message send operation. This led to the error, and call
SPOT-356 WARN msg send might indicate a problem with the your FANUC Robotics
The IWC reported an invalid buffer Document the events that
Invalid buffer, IWC msg during a message send operation. This led to the error, and call
SPOT-357 WARN send might indicate a problem with the your FANUC Robotics
An invalid checksum was computed on Document the events that
Checksum error, IWC a message segment received from the led to the error, and call
SPOT-358 WARN msg recv IWC board. This might indicate a your FANUC Robotics
An invalid buffer tag was detected on a Document the events that
Invalid buffer, IWC msg message segment received from the led to the error, and call
SPOT-359 WARN recv IWC board. This might indicate a your FANUC Robotics
The buffer passed to the IWC driver Document the events that
SPOT-360 WARN IWC buffer too small was too small to hold the message led to the error, and call
Ack timeout, IWC msg The IWC did not acknowledge a Document the events that
SPOT-361 WARN send message segment that was sent to it. led to the error, and call
The IWC did not send a response Document the events that
SPOT-362 WARN Timeout, IWC msg recv message within the allowable time led to the error, and call
The IWC driver was unable to Document the events that
SPOT-363 WARN IWC motherboard error communicate with the PC/104 led to the error, and call
IWC has invalid DPRAM An IWC board was detected, but the Make sure that the
SPOT-364 WARN signature contents of the dual-port RAM area is correct type of IWC board
An IWC board was detected, but the Install an IWC with a
Unsupported IWC version and/or revision level of its dual- compatible version level,
SPOT-365 WARN version/rev level port RAM is not supported by the or check to see if there is
Unable to register IWC The driver was unable to register an Document the events that
SPOT-366 WARN interrupt interrupt for the IWC board. led to the error, and call
Only 29 functions The user tried to insert more than 29 Do not insert more than
SPOT-367 WARN allowed in a schedule functions into the schedule. Only 29 29 functions in a schedule.
Imp. can only come The user tried to insert an impulse Insert the impulse
SPOT-368 WARN before weld FCTN function(function 60) before a non- function directly before a
FCTN not supported by The user directly entered an invalid Choose another function
SPOT-369 WARN the timer function number to be inserted. from the choice list, or
Try cycling controller
Could not download The schedule failed 2 download tries to power. If the error still
SPOT-370 WARN schedule %d the timer. exists, document the
Could not download The stepper failed 2 download tries to power. If the error still
SPOT-371 WARN stepper %dread
Could not the
The timer.
sequence file could not be read exists,
Make sure document the
the sequence
SPOT-372 WARN sequence file %d from the FROM. exists on FROM.
Could not download The setup data failed 2 download tries power. If the error still
SPOT-373 WARN setup data to the timer. exists, document the
Could not download The dynamic data failed 2 download power. If the error still
SPOT-374 WARN Dynamic
Could notdata
read stepper triesstepper
The to the timer.
file could not be read from exists,sure
Make document the
the stepper
SPOT-375 WARN file %dnot read setup
Could the FROM.
The setup file could not be read from exists on
Make sureFROM.
the setup file
SPOT-376 WARN file %s the FROM.
The named file could not be read from exists on FROM.
Make sure the file exists
SPOT-377 WARN Could not read file %s the Device. on the Device.
The ID jumpers on the IWC card(s) are If there is one card in the
IWC ID jumpers not set so that the cards can be system, its ID must be set
SPOT-378 WARN incorrect identified
The IWC slaveas card #1bit
busy and cardin#2.
is set the to 1. Ifthe
Retry there are twoafter
operation
SPOT-379 WARN IWC slave busy status word. a short delay.
The firmware versions on the timer Make sure that the
card must be the same if there are 2 firmware version and
Invalid IWC Firmware timers. Either the firmware version revision level match for
SPOT-380 WARN Version itself is different, or the revision level of both cards. It could be
Write down the number
of the error and contact a
Service Representative: -1,
2 or 13: The temporary
pool area might be almost
exhausted -3: The timer
IWC(DG) system A communication problem with the board could not be
SPOT-381 error(%d) timer board has occurred. initialized successfully -4:
An illegal value for the SN (Stepper Change the instruction to
IWC(DG) illegal stepper Number) field in the reset stepper use a value that is
SPOT-382 PAUSE number(%s) instruction was used for the Dengensha between 0 and 4.
-Remove the cause of the
leak. - Refer to the Weld
IWC(DG) leak input Interface I/O screen and
SPOT-384 (%d) The Leak Input signal is on. verify that the Leak Input
You have entered an illegal value for
IWC(DG) illegal counter the "SN=" field in the RESET STEPPER The system variable value
SPOT-385 PAUSE specified(%s) instruction while using the IWC must be between 0 and 2.
Reset stepper timeout The weld controller did not Check that the weld
SPOT-386 PAUSE Studwelding
%s resume acknowledge the reset stepper controller is functioning
SPOT-397 not
IWCallowed
FIRMWARE Studwelding
The resume
IWC firmware hasis been
not allowed.
upgraded None.
SPOT-399 WARN UPGRADED on the timer card. None.
WTC E01: Controller This is a fault from the WTC weld Review the error code
SPOT-401 PAUSE Failure controller. remedy information in the
weld controllers that the
system is configured for is
IWC(DG) timer now in An invalid weld controller number was value one up to and
SPOT-490 weld %d specified. including the number
Invalid destination Maximum speed for rampping is Change ths command
SPRM-000 WARN speed. 500mm/sec. speed and destination
Power off to recover. If
SPRM-001 WARN Internal system error. Ramp internal system error. problem persistes,
Specification. Rampplease
does
SPRM-002 WARN Ramp is disabled. is disabled
Ramp does dor backward
not support deg/secmotion. not support
for its Change speedbackward
unit to
SPRM-003 WARN No support for deg/sec speed unit. mm/sec cm/min or
No time base speed Ramp does not support time based Change speed unit to
SPRM-004 WARN Ramp
unit. system loading speed
The unit(msec
ramp or is
software sec)
loaded mm/secreload
Please cm/mintheor
SPRM-005 WARN error. incorrectly. controller.
Current position has large
Ramp disabled, Ramp is disabled for rotation orientation change. Please
SPRM-006 WARN Rotation motn dominated motion. re-record the position
The current motion
travels in short distance,
Ramp disabled. Short not enough for ramp
SPRM-007 WARN motion. Ramp is disabled for short motion. motion to speed up.
Max Speed is not Max Speed is not supported. Ramp Change speed unit to
SPRM-008 WARN No
supported. does not
Ramp resume in hot Ramp support
resume max speed
is disabled forinitshot Do
when mm/sec, cm/min,
not resume or
speed
SPRM-009 start.
S. PORT ILLEGAL start mode.
Illegal function code was specified. ramp in
SRIO-001 WARN FUNCTION CODE System error. Systemserial
Open error.
port before
SRIO-002 WARN SERIAL PORT NOT OPEN Serial port is not opened. using it.
SERIAL PORT ALREADY Serial port has already been opened, Do not try to open the
SRIO-003 WARN SERIAL
OPEN PORT NOT and it was tried to be opened again. serial port
Initialize which
the serialhas
port
SRIO-004 WARN INITIALIZE Serial port is not initialized. before using it.
Check if serial port setup
is correct. Check if cable is
SRIO-005 WARN SERIAL PORT DSR OFF Serial port DSR is off. broken. Check if there
SERIAL PORT PARITY is correct. Check if cable is
SRIO-006 WARN ERROR Serial port parity error occured. broken. Check if there
SERIAL PORT OVERRUN is correct. Check if cable is
SRIO-007 WARN ERROR Serial port overrun error occured. broken. Check if there
SERIAL PORT FRAME is correct. Check if cable is
SRIO-008 WARN ERROR Serial port frame error occured. broken. Check if there
S. PORT PARITY & Serial port parity error and overrun is correct. Check if cable is
SRIO-009 WARN OVERRUN error occured. broken. Check if there
S. PORT PARITY & Serial port parity error and frame error is correct. Check if cable is
SRIO-010 WARN FRAME occured broken. Check if there
S. PORT OVERRUN & Serial port overrun error and frame is correct. Check if cable is
SRIO-011 WARN FRAME error occured. broken. Check if there
S. PORT PRTY & OVRRN Serial port parity error, overrun error, is correct. Check if cable is
SRIO-012 WARN & FRM and frame error occured. broken. Check if there
is correct. Check if cable is
S. PORT DSR OFF & Serial port DSR is off and harware error broken. Check if there
SRIO-013 WARN HARDWARE
S. ERR
PORT ILLEGAL occured.
Serial port request count is illegal. exists a noise source near
SRIO-014 WARN REQUEST COUNT System error. System error.
Cancel current serial port setup. This
SRIO-015 WARN SERIAL PORT CANCEL code does not appear at normal time. System error.
S. PORT POWER Initialize serial port at power failure
SRIO-016 WARN FAILURE CANCEL recovery. This code does not appear at System
1. Twisterror.
the operator
panel EMERGENCY STOP
button clockwise to
release it, then press
RESET. 2. Check the wires
connecting the
EMERGENCY STOP switch
connector CRM51 for
continuity. If an open wire
The EMERGENCY STOP button on the is found, replace the
PAUSE. operator panel or operation box is entire harness. 3. With
SRVO-001 G Operator panel E-stop pressed. the EMERGENCY STOP
1. Twist the teach
The EMERGENCY STOP button on the pendant EMERGENCY
SRVO-002 SERVO Teach pendant E-stop teach pendant was pressed. STOP button clockwise to
1. Twist the teach
Deadman switch The EMERGENCY STOP button on the pendant EMERGENCY
SRVO-003 SERVO released teach pendant was pressed. STOP button clockwise to
If the RDY LED (green) is
lit: 1. If a safety fence is
connected, close the door
of the fence. 2. Check the
switch and cable
connected to 5 (EAS1) - 6
(EAS11) and 7 (EAS2) - 8
(EAS21) on TBOP4. 3.
When this signal is not
used, make a connection
between 5 (EAS1) - 6
(EAS11) and between 7
(EAS2n) - 8 (EAS21). 4.
On the terminal block TBOP4 of the Replace the operator
panel board, no connection is made panel board. In case the
between 5 (EAS1) - 6 (EAS11) and RDY LED (green) is not lit:
between 7 (EAS2) - 8 (EAS21). If a 1. Check whether FUSE1
safety fence is connected between 5 on the operator panel
(EAS1) - 6 (EAS11) and between 7 board has blown. If it has
(EAS2) - 8 (EAS21), the door of the blown, remove the cause
safety fence is open. If the SYST-067 and then replace the fuse.
(Panel HSSB disconnect) alarm is also Otherwise, check the
generated, or if the LED (green) on the external voltage on
panel board is turned off, EXT24V and EXT0V
communication between the main (TBOP6). If external 24V
board (JRS11) and the panel board and 0V is not used, check
(JRS11) is abnormal. The connectors of the jumper pins between
the cable between the main board and EXT24V - INT24V and
the panel board might be loose or the EXT0V - INT0V (TBOP6). 2.
cable, panel board, or main board Replace the operator
SRVO-004 SERVO Fence open might be faulty. panel board. 3. Replace
1. Select [System OT
release] on the overtravel
release screen to release
each robot axis from the
overtravel state. * Press
the SHIFT key, and press
the alarm release button
to reset the alarm
condition. * While
continuously pressing the
SHIFT key, jog the robot to
bring all axes into the
movable range. 2. Replace
The robot has moved beyond a the limit switch. 3. Check
hardware limit switch on the axes. It is the FS2 fuse on the servo
factory-placed in the overtravel state amplifier. If the SRVO-214
for packing purposes. If the overtravel Fuse blown alarm is also
signal is not in use, it might have been generated, the FS2 fuse
disabled by a jumper connector (short- has blown. 4. Check the
circuit) in the base of the mechanical end effector connector. 5.
SRVO-005 SERVO Robot overtravel unit. Verify the following for
1. Press the SHIFT key,
and press the alarm
release button to reset
The safety joint (if in use) might have the alarm condition.
been broken. Alternatively, the HBK While continuously
signal on the robot connection cable pressing the SHIFT key, jog
might be experiencing a ground fault the tool to the work area.
(0V) or a cable disconnection. If the * Replace the safety joint.
Hand broken signal is not in use, it can * Check the safety joint
be disabled by a software setting. Refer cable. 2. Check the FS2
to the Controller Maintenance Manual, fuse on the servo
Section III CONNECTIONS, Subsection amplifier. If the SRVO-214
5.5.3 How to Disable/Enable HBK, for Fuse blown alarm is also
information on how to disable the generated, the FS2 fuse
SRVO-006 SERVO Hand broken Hand broken signal. has blown.
In case 3. Verify
the RDY LED the
(green) is lit: 1. If an
external emergency stop
switch is connected,
release the switch and
press RESET. 2. Check the
switch and cable
connected to TBOP4
terminals 1 (EES1) - 2
(EES11) and terminals 3
(EES2) - 4 (EES21). 3.
On the TBOP4 terminal block of the When this signal is not
operator panel board, no connection is used, make a connection
made between terminals 1 (EES1) - 2 between TBOP4 terminals
(EES11) and between terminals 3 (EES2) 1 (EES1) - 2 (EES11) and
- 4 (EES21). If an external emergency between terminals 3
stop switch is connected between (EES2) - 4 (EES21). 4.
terminals 1 (EES1) - 2 (EES11) and Replace the operator
between terminals 3 (EES2) - 4 (EES21), panel board. In case the
then the switch is pressed. If the SYST- RDY LED (green) is not lit:
067 (Panel HSSB disconnect) alarm is 1. Check whether FUSE1
also generated, or if the RDY LED on the operator panel
(green) on the operator panel board is board is blown. If FUSE1 is
turned off, communication between blown, replace FUSE1
the main board (JRS11) and the after removing the cause.
operator panel board (JRS11) is Otherwise, check the
abnormal. The cable connectors external 24 VDC supply on
between the main board and the panel the operator panel board,
board might be loose or the cable, terminals EXT24V and
External emergency panel board, or Main board might be EXT0V (TBOP6). If the
SRVO-007 SERVO stops faulty. external 24 VDC is not
Replace the fuse. Check
The brake fuse is blown on the EMG the LED (FALM) on the
SRVO-008 SERVO Brake fuse blown Control PCB. printed circuit board for
1. If an abnormal air
pressure is detected,
check your air supply. 2.
Verify the following for
connector RP1 at the base
of the robot: * There are
no bent or dislocated pins
in the male or female
connectors. * The
connector is securely
connected. Then verify
An abnormal air pressure was detected. that connector CRF7 on
The input signal is located on the end the servo amplifier is
effector of the robot. Refer to the securely connected. Also
Pneumatic pressure Maintenance Manual for your robot for verify that the RP1 cable is
SRVO-009 SERVO alarm more information. in good condition, and
1. If the belt is found to be
defective in any way,
repair it and then press
the RESET key. 2. When
The belt broken robot digital input the belt is found to be
SRVO-010 SERVO Belt broken (RDI7) is asserted. normal, the signal RDI[7]
The teach pendant attachment switch Reconnect the teach
TP released while on the operator panel was operated pendant cable to continue
SRVO-011 SERVO enabled while the teach pendant was enabled. operation.
This is just a notification.
SRVO-012 SERVO Power failure recovery Normal power on (hot start). You do not have to do
Upon power-up with power restoration
enabled (hot start), the configuration of
SYSTE Srvo module config the DSP modules on the axis control Turn on the power in cold
SRVO-013 M changed printed circuit board and the multi- start mode.
A fan motor in the control unit is Check the fan motors and
abnormal. One of the following fan motor connection
Fan motor abnormal numbers indicates the location of the cables. Replace any faulty
SRVO-014 WARN (%d) fan: 1: Main board rack fan 2: Option fan motor(s) and/or
1. If the ambient
temperature is higher
than the specified
temperature (45 degrees
C), cool down the ambient
temperature. 2. Check
The temperature of the control unit that the fans are
SRVO-015 SERVO System over heat
Cooling water volume exceeds the specified value. operating
Consult yournormally.
FANUCIf not,
SRVO-016 SERVO drop
No robot internal Cooling water volume dropped. Roboticsyour
Consult technical
FANUC
SRVO-017 SERVO mirror No robot internal mirror. Robotics technical
Check the following: 1.
Verify that the RM1 cable
that carries the signal
The brake current has exceeded the wires from the controller
SRVO-018 SERVO Brake abnormal specification. to the robot is securely
On the terminal block on the printed
circuit board of the operator panel, no Establish a connection
connection is established between between *SVON1 and
SRVO-019 SERVO SVON input signals *SVON1 and *SVON2. When an *SVON2.
The teach pendant cable is
disconnected or a momentary break
occurred in any one of the TP Check the teach pendant
SRVO-020 SERVO SRDY off (TP) emergency
The HRDY (hardware ready) signal is on cable
stop circuits: TP emergency andsure
1. Make connections.
that
and the SRDY (servo ready) signal is off. connectors CP2, CRM64
The main board uses the HRDY signal to and CNMC3 of the E-Stop
direct the servo system to turn on or unit and connector
off the servo amplifier magnetic CRM64 of the servo
contactor. The servo system uses the amplifier are securely
SRDY signal to inform the main board connected. 2. Check
that the magnetic contactor is turned whether an instantaneous
on. If the servo amplifier magnetic disconnection from power
contactor cannot be turned on when has occurred. It is possible
directed so, it is most likely that a servo that a brief disconnection
SRDY off (Group:%d amplifier alarm has occurred. If a servo from power can cause this
SRVO-021 SERVO Axis:%d) amplifier alarm has been detected, the alarm. 3. Replace the
The SRDY (servo ready) signal was
already on when the main board made
an attempt to turn on the servo
amplifier's magnetic contactor using
the HRDY (hardware ready) signal.
HRDY is the signal used by the host
(main board) to direct the servo system
SRDY on (Group:%d to turn on or off the servo amplifier's Replace the servo
SRVO-022 SERVO Axis:%d) magnetic contactor. SRDY is the signal amplifier.
If the brake is not
released: 1. Check the
continuity of the brake
line in the robot
connection cable and the
robot internal cable. 2. If a
disconnection is not
found, replace the servo
amplifier or the servo
motor. If the brake is
releasing: 1. Check to see
if any obstacles are
disturbing the robot
motion. 2. Make sure
connectors CNJ1A - CNJ6
are securely attached to
the servo amplifier. 3.
Check the continuity of
the power cable in the
robot connection cable. 4.
Check to see if the load is
greater than the rating. If
When the servo stopped, the position it is greater, reduce it to
error was abnormally large. Check to within the rating. (If the
see if the motor's brake (indicated by load is too great, the
the alarm message) is releasing. You torque required for
should be able to hear the brake acceleration/deceleration
release. If not, place a hand on the becomes higher than the
motor (indicated by the alarm capacity of the motor. As
Stop error excess(G:%d message) and feel for a vibration a result, the motor
SRVO-023 SERVO A:%d) caused by the brake releasing. becomes unable to follow
When the robot moved, the servo
positional error exceeded a previously
specified value
($PARAM_GROUP.$MOVER_OFFST or
Move error $PARAM_GROUP.$TRKERRLIM). For Take the same action as
SRVO-024 SERVO excess(G:%d A:%d) example, this error will occur if the for SRVO?023.
Motn dt overflow (G:%d The value entered with a command is RESET keys. 3. While still
SRVO-025 SERVO A:%d) too large. pressing the SHIFT and
An attempt was made to exceed the This is just a notification.
Motor speed limit(G:%d maximum rated motor speed However, you should
SRVO-026 WARN A:%d) ($PARAM_GROUP.$MOT_SPD_LIM). attempt to eliminate this
Robot not An attempt was made to calibrate the
SRVO-027 WARN mastered(Group:%d) robot, but the necessary adjustment Master the robot.
SRVO-028 WARN Servo reset (Group:%d)
Robot calibrated No longer occurs.
SRVO-029 WARN (Group:%d) No longer occurs.
When the temporary stop alarm Disable [TEMPORARY
function ($SCR.$BRKHOLD_ENB=1) is STOP/SERVO OFF] on the
Brake on hold enabled, this alarm is issued whenever general item setting
SRVO-030 SERVO (Group:%d) a temporary stop is made. When this screen [6 GENERAL
A user servo alarm was issued. This This is just a notification.
User servo alarm alarm is raised when the system You do not have to do
SRVO-031 SERVO (Group:%d)
Force follow-up end variable $MCR_GRP[i].$SOFT_ALARM is anything for this warning
SRVO-032 WARN (Grp:%d) No longer occurs. Calibrate the robot: 1.
Supply power to the
controller. 2. Using the
teach pendant: * Press
MENUS. * Select SYSTEM.
* Press F1, [TYPE]. * Select
Master/Cal. * Select
Calibrate. Set up a
An attempt was made to set up a simplified adjustment
reference point for a simplified reference point: 1. Press
Robot not adjustment, but the robot has not been MENUS. 2. Select SYSTEM.
SRVO-033 WARN calibrated(Grp:%d) calibrated. 3. Press F1, [TYPE]. 4.
Set up a simplified
adjustment (Quick
Master) reference point
on the positioning menu.
1. Press MENUS. 2. Select
SYSTEM. 3. Press F1,
An attempt was made to perform a [TYPE]. 4. Select
Ref pos not set simplified adjustment, but the Master/Cal. 5. Select SET
SRVO-034 WARN (Group:%d) reference point has not been set up. QUICK MASTER REF. Note:
A value higher than the maximum axis Decrease the axis speed
Joint speed limit(G:%d speed ($PARAM_GROUP.$JNTVELLIM) value to be within limit
SRVO-035 WARN A:%d) was specified. Each actual axis speed is specified in
If the brake is not
released: 1. Check the
continuity of the brake
line in the robot
connection cable and the
robot internal cable. 2. If a
disconnection is not
found, replace the servo
amplifier or the servo
motor. If the brake is
releasing: 1. Check to see
if any obstacles are
disturbing the robot
motion. 2. Make sure
connectors CNJ1A - CNJ6
are securely attached to
the servo amplifier. 3.
Check the continuity of
the power cable in the
robot connection cable. 4.
Check to see if the load is
greater than the rating. If
The robot did not reach the designated it is greater, reduce it to
area ($PARAM_GROUP.$STOPTOL) within the rating. (If the
even after the position check load is too great, the
monitoring time torque required for
Inpos time over (G:%d ($PARAM_GROUP.$INPOS_TIME) acceleration/deceleration
SRVO-036 SERVO A:%d) elapsed. becomes higher than the
The *IMSTP signal, which is a Turn on the *IMSTP
SRVO-037 SERVO IMSTP input (Group:%d) peripheral device I/O signal, is applied. Check
signal. the alarm history. *
If you see the ?SRVO?222
Lack of Amp (Amp : i)?
alarm, refer to the
troubleshooting of
SRVO?222. * If the brake
number is set to the
non?brake motors, this
alarm might occur. Check
the software setting of
The pulse count obtained when power the brake number. * If the
is turned off does not match the pulse robot has been moved by
count obtained when power is turned using the brake release
back on. This alarm is asserted after unit while the power is off
changing the pulse coder or the back or when restoring the
up battery for pulse coder data, or back?up data to the main
SERVO Pulse mismatch (G:%d when loading back up data into the board, this alarm will
SRVO-038 2 A:%d) Main Board. occur. In this case,
Motor speed CMC cannot work because the Reduce the motion speed
SRVO-039 SERVO excess(G:%d A:%d) calculated motor speed exceeded the 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
Mastered at mark Zero position master is done with mark position master is not
SRVO-040 WARN pos(G:%d) position (not with zero position). done with zero pos for S-
SERVO MOFAL alarm (Grp:%d A value specified with a command is Document the events that
SRVO-041 2 Ax:%d) too large. led to the error and call
This alarm means that the contacts of 1. Check the magnetic
the magnetic contactor have stuck contactor, and replace it if
together. The alarm condition occurs if necessary. 2. If the
the magnetic contactor is already on contacts of the magnetic
when an attempt is made to turn it on. contactor have stuck to
The alarm condition is detected each other, turn off the
MCAL alarm(Group:%d between the time the contact sticking circuit breaker. If the
SRVO-042 SERVO Axis:%d) occurs, and the time an attempt is power is switched off
1. This alarm might occur
if the axis is subjected to
frequent
acceleration/deceleration
or if the axis is vertical and
The regenerative discharge energy was generates a large amount
too high to be dissipated as heat. To of regenerative energy. If
run the robot, the servo amplifier this alarm has occurred,
supplies energy to the robot. When relax the service
going down the vertical axis, the robot conditions. 2. Check fuse
operates from the potential energy. If a FS3 in the servo amplifier.
reduction in the potential energy is If it has blown, remove
higher than the energy needed for the cause, and replace the
acceleration, the servo amplifier fuse. One of the probable
receives energy from the motor. A causes of a blown fuse is a
similar phenomenon occurs even when ground fault in the servo
no gravity is applied, for example, at amplifier for the auxiliary
deceleration on a horizontal axis. The axis. 3. The ambient
energy that the servo amplifier receives temperature is excessively
from the motor is called the high or the regenerative
regenerative energy. The servo resistor can not be cooled
amplifier dissipates this energy as heat. effectively. Check the fan
If the regenerative energy is higher unit, and replace it if it
than the energy dissipated as heat, the stops. Clean up the fan
DCAL alarm(Group:%d difference is stored in the servo unit, the regenerative
SRVO-043 SERVO Axis:%d) amplifier, causing an alarm. resistor, and the louver if
1. Check the three?phase
input voltage at the servo
amplifier. If it is 240 VAC
or higher, check the line
voltage. (If the
three?phase input voltage
is higher than 240 VAC, a
high
acceleration/deceleration
can cause this alarm.) 2.
Verify that the load
weight is within the
The DC voltage (DC link voltage) of the rating. If it is higher than
HVAL alarm(Group:%d main circuit power supply is abnormally the rating, reduce it so
SRVO-044 SERVO Axis:%d) high. that it falls within the
1. Turn off the power, and
disconnect the power
cable from the servo
amplifier indicated by the
alarm message. Also
disconnect the brake
cable (CRR64 on the servo
amplifier) to avoid the axis
from falling unexpectedly.
Turn on the power and
see if the alarm occurs
again. If the alarm occurs
again, replace the servo
amplifier. 2. Turn off the
power and disconnect the
power cable indicated by
HCAL alarm(Group:%d An abnormally high current flowed in the alarm message from
SRVO-045 SERVO Axis:%d) the main circuit of the servo amplifier. the servothe
1. Check amplifier. Then
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
This alarm is issued to protect the robot such that the rated
motor when there is a danger of values are not exceeded.
thermal destruction when the root- 2. Check each interphase
mean-square current value, calculated voltage of the three-phase
SERVO OVC alarm (Group:%d internally by the servo system, exceeds voltage (200 VAC) applied
SRVO-046 2 Axis:%d) the maximum permissible value. to the servo amplifier
The control power supply voltage (+5 V, 1. Replace the servo
LVAL alarm(Group:%d etc.) supplied from the power supply amplifier according to the
SRVO-047 SERVO Axis:%d)
MOH alarm (Group:%d circuit in the servo amplifier is alarm message. 2. Replace
SRVO-048 2 Axis:%d) Never occurs on R-Model J. None applicable.
1. Check the operating
condition of the robot and
relax the service condition
if possible. 2. Check the
fan unit, and replace it if it
has stopped working. 3.
Clean the fan unit, the
regenerative discharge
resistor and the louver if
The thermostat is working. However, they are dirty. 4. Check to
OHAL1 alarm (Grp:%d fuse F1 or F2 located on the servo see if error code
SRVO-049 SERVO Ax:%d) amplifier has blown. SRVO?214 Fuse blown
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
An excessively large disturbance torque rating. If the rated load is
Collision Detect alarm is estimated by the servo software. A exceeded, reduce the
SRVO-050 SERVO (G:%d A:%d) collision was detected. applied load. If the robot
SERVO CUER alarm(Group:%d The offset of the current feedback Replace the servo
SRVO-051 2 Axis:%d)
Discharge excess value is abnormally high. amplifier.
SRVO-052 WARN (Amp:%d) Not used. None needed.
Disturbance estimated in the software If operation is allowed to
exceeded the threshold value. There is continue, a detection
Disturbance a possibility that the load held in the error might result. On the
SRVO-053 WARN excess(G:%d A:%d) wrist exceeded the robot specification. status screen containing
An access to the servo module memory
failed. Note: 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 board if the memory has
SYSTE DSM memory error been lost. Otherwise, you could injure Replace the axis control
SRVO-054 M (DSM:%d) personnel, damage equipment, or lose card on the main board.
1. Check the
communication cable
(optical fiber) between
the main board and servo
amplifier. Replace it if it is
A communication error has occurred faulty. Note: Before
SERVO FSSB com error 1 (G:%d between the main board and servo executing the next step,
SRVO-055 2 A:%d) amplifier. perform a complete
1. Check the
communication cable
amplifier. Replace it if it is
A communication error has occurred faulty. Note: Before
SERVO FSSB com error 2 (G:%d between the main board and the servo executing the next step,
SRVO-056 2 A:%d) amplifier perform
1. Check awhether
complete
fuse F3
in the power supply unit
has blown. 2. Check
whether fuse FS1 in the
servo amplifier has blown.
3. Check the
communication cable
Communication was interrupted amplifier. Replace it if it is
SERVO FSSB disconnect (G:%d between the main board and the servo faulty. Note: Before
SRVO-057 2 A:%d) amplifier. executing the nextfuse
1. Check whether step,F3
in the power supply unit
has blown. 2. Turn off the
power and disconnect the
CRF7 connector on the
servo amplifier. Then turn
on the power and check
whether this alarm occurs
again. (Ignore the alarm
SRVO?068 because of
disconnecting the CRF7
connector.) If this alarm
does not occur, the RP1
robot connection cable or
the internal cable of the
robot might be
short?circuited to ground.
Check the cables and
replace them if necessary.
3. Check whether the LED
(P5V and P3.3V) on the
servo amplifier is lit. If the
LEDs are not lit, the DC
power is not supplied to
the servo amplifier. Make
sure connectors CP6 and
Communication was interrupted CRM67 on the E?stop unit
SYSTE between the main board and servo and the connector CRM67
SRVO-058 M FSSB %d init error (%d) amplifier. on the servo amplifier are
1. Check the
SYSTE communication cable
SRVO-059 M Servo amp init error Servo amplifier initialization has failed. (optical fiber) between
optical cable between the
additional axis board and
the additional axis
amplifier is securely
connected. 2. Replace the
additional axis board. 3.
Replace the additional
Communication between the additional axis amplifier. Note:
SYSTE axis board and the additional axis Before executing the next
SRVO-060 M FSSB 2 init error amplifier was interrupted. step, perform a complete
If this alarm occurs along
with a SRVO-068 DTERR,
SERVO CKAL alarm(Group:%d The clock for the rotation counter in SRVO-069 CRCERR, or
SRVO-061 2 Axis:%d) the pulse coder is abnormal. SRVO-070 STBERR,
This alarm is issued when the battery Correct the cause of the
for backing up the absolute position alarm, then turn on power
SERVO BZAL alarm(Group:%d data of the pulse coder is not again after setting the
SRVO-062 2 Axis:%d) connected. The battery cable inside the system variable
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.
SERVO RCAL alarm(Group:%d The built-in rotation counter on the Master the robot. 2.
SRVO-063 2 Axis:%d) pulse coder is abnormal. Replace
1. Replacethethe
pulse coder.
pulse
coder, and remaster the
robot.Note: Ignore this
alarm if it accompanies
the DTERR, the CRCERR,
or the STBERR alarms.
Verfiy that your
equipment is properly
grounded. If the problem
continues, perform the
This alarm occurs if the phase of the following steps. 2. Make
SERVO PHAL alarm(Group:%d pulses generated in the pulse coder is sure that the CRF7
SRVO-064 2 Axis:%d) abnormal. connector located on the
Replace the battery.Note:
If this alarm occurs, turn
on the AC power and
replace the battery as
BLAL alarm(Group:%d The battery voltage for the pulse coder soon as possible. A delay
SRVO-065 WARN Axis:%d) is lower than an allowable value. in battery replacement
If this alarm occurs along
with a SRVO-068 DTERR,
SERVO CSAL alarm(Group:%d The pulse coder ROM checksum data is SRVO-069 CRCERR, or
SRVO-066 2 Axis:%d) abnormal. SRVO-070 STBERR,
1. Check the operating
conditions of the robot
The temperature inside the pulse coder and relax the service
or motor is abnormally high, and the conditions. Note To relax
SERVO OHAL2 alarm (Grp:%d built?in thermostat has begun to the service conditions you
SRVO-067 2 Ax:%d) regulate the temperature. can either reduce the
CRF7 connector on the
servo amplifier is securely
connected. 2. Check that
the shielding of the robot
The serial pulse coder did not return interconnection cable (for
SERVO DTERR alarm (Grp:%d serial data in response to a request the pulse coder) and the
SRVO-068 2 Ax:%d) signal. peripheral equipment
CRF7 connector located
on the servo amplifier is
securely connected. 2.
Check that the shielding
of the robot
SERVO CRCERR alarm (Grp:%d The serial data has been disturbed interconnection cable (for
SRVO-069 2 Ax:%d) during communication. the pulse coder) and the
CRF7 connector located
on the servo amplifier is
Check that the shielding
of the robot
SERVO STBERR alarm (Grp:%d The start and stop bits of the serial data interconnection cable (for
SRVO-070 2 Ax:%d) are abnormal. the pulse coder) and the
1. Check the alarm
history. If this alarm
SERVO SPHAL alarm (Grp:%d occurs together with the
SRVO-071 2
SERVO Ax:%d)alarm(Group:%d
PMAL The feedback speed is abnormally high. Replace
PHAL alarm
the (SRVO?064),
pulse coder,
SRVO-072 2 Axis:%d) The pulse coder is abnormal. and remaster the robot.
The pulse coder might be faulty, or 1. According to the alarm
SERVO CMAL alarm(Group:%d noise might be causing the pulse coder message, ensure that the
SRVO-073 2 Axis:%d) to malfunction. motor flange is grounded.
1. Reset the pulse coder
alarm a. Press MENUS. b.
Select SYSTEM. c. Press
SERVO LDAL alarm(Group:%d F1, [TYPE]. d. Select
SRVO-074 2 Axis:%d) The LED in the pulse coder is broken. MASTER/CAL. e. Press F3,
Pulse not The absolute position of the pulse Reset the alarm, and jog
SRVO-075 WARN established(G:%d A:%d) coder cannot be established. the axis on which the
robot has collided with a
foreign object. If a
collision has occurred,
reset the system, then jog
the robot to avoid the
collision. Or, check
whether the machinery
load of the corresponding
axis has increased. 2.
Check whether the load
settings are valid. Refer to
An excessive disturbance was the robot maintenance
monitored in the servo software at the manual for more
start of operation. This means that an information. 3. Check
abnormal load was detected. This whether the brake of the
alarm can occur in welding applications corresponding axis is
if the electrode tips of the weld gun released. 4. Check
Tip Stick stick to the part when the robot begins whether the load weight
SRVO-076 SERVO Dynamic
Detection(G:%d
brake A:%d) The
to move.
line tracking pulse count is withinyour
Contact the rated
FANUC range.
SRVO-077 SERVO alarm(G:%d
Servo param A:%d) overflowed.
The servo parameter has been Robotics technical
SRVO-078 SERVO update(G:%d A:%d) updated. Press RESET and continue.
The gun tip position during the Check the master position
pressuring operation (SPOT or and close stroke limit for
PRESS_MOTN) exceeded the stroke the gun. If these values
Stroke exceeded during limit for the gun. The squeezing are incorrect, then update
SRVO-079 press(G:%d A:%d) operation stopped because the gun them.
1. CheckIf these values
whether theare
duty
and applied load exceed
the rating. If so, reduce
The root-mean-square current value the duty or applied load.
which is calculated internally by the 2. Check whether the
servo system exceeds the maximum robot is pushed or pulled
permissible value. This alarm is issued by external force. If so,
to protect the motor and amplifier remove the external force
from a damage of thermal destruction. to the robot or modify the
Probable cause: 1. Overload 2. External taught point. 3. Check
force to the robot 3. Disconnection of whether the brake
the brake cable 4. Insufficient torque cable/connector are
by low voltage of power supply 5. Brake connected correctly. 4.
failure (includes mis-setting of brake Measure the supplied
number for auxiliary axis) 6. Aux. brake voltage. Then, check
unit failure for aux. axis 7. Amplifier whether the voltage is
OVC alarm (Group:%d failure 8. Motor failure 9. Motor power matched to the controller
SRVO-080 Axis:%d) cable or brake cable failure specification. 5. Check
condition of the line
tracking module exceeds
EROFL alarm (Track The pulse counter for line tracking the limitation. For more
SRVO-081 WARN enc:%d) module has overflowed. information refer to the
1. Check the connection
cable at each end (the line
tracking interface board
and the pulse coder). 2.
DAL alarm(Track The line tracking pulse coder has not Check whether the
SRVO-082 WARN encoder:%d) been connected. shielding of the
CKAL alarm (Track The clock for the rotation counter in Refer to the SRVO-061
SRVO-083 WARN enc:%d) the line tracking pulse coder is remedy.
This alarm occurs if the backup battery 1. Check the battery and
for the absolute position data of the battery cable, and replace
BZAL alarm (Track pulse coder has not been connected, is them if necessary. 2. Set
SRVO-084 WARN enc:%d) dead, or the connection cable has been the system variable
RCAL alarm (Track The built-in rotation counter on the line
SRVO-085 WARN enc:%d) tracking pulse coder is abnormal. Refer to SRVO-063.
PHAL alarm (Track This alarm is issued when the phase of Refer to the description
SRVO-086 WARN enc:%d) a pulse signal generated by the pulse for the SRVO-064 PHAL
This alarm occurs if the backup battery Replace the battery. Note:
voltage for the absolute position data If this alarm occurs, turn
of the pulse coder is low. See the on the AC power and
BLAL alarm (Track description of the BLAL alarm replace the battery as
SRVO-087 WARN enc:%d) (SRVO?065). soon as possible. A delay
CSAL alarm (Track The line tracking pulse coder ROM Refer to SRVO-066
SRVO-088 WARN OHAL2
enc:%d)alarm (Track checksum data is abnormal. remedy.
Refer to the description of
SRVO-089 WARN enc:%d) The motor has overheated. the SRVO-067 OHAL2
DTERR alarm (Track An error occurred during the Refer to the description of
SRVO-090 WARN enc:%d) communication between the pulse the SRVO-068 DTERR
tracking interface board,
Communication between the pulse and the pulse coder). 2.
CRCERR alarm (Track coder and the line tracking interface Check whether the
SRVO-091 WARN enc:%d) board is abnormal. shielding of the
tracking interface board
Communication between the pulse and the pulse coder). 2.
STBERR alarm (Track coder and the line tracking interface Check whether the
SRVO-092 WARN enc:%d) board is abnormal. shielding of the
1. If this alarm occurs
together with the PHAL
alarm (SRVO?086), this
alarm does not
correspond to the major
cause of the failure. 2. In
This alarm occurs if the current position any case, replace the
SPHAL alarm (Track data from the pulse coder is higher pulse coder. 3. Check the
SRVO-093 WARN enc:%d)
PMAL alarm (Track than the previous position data. connection cable at each
SRVO-094 WARN enc:%d) The pulse coder is abnormal. Replace the pulse coder.
1. According to the alarm
CMAL alarm (Track The pulse coder is either abnormal or it message, ensure that the
SRVO-095 WARN enc:%d)
LDAL alarm (Track has malfunctioned due to noise. motor has a good earth
SRVO-096 WARN enc:%d) The LED in the pulse coder is broken. Replace the pulse coder.
Pulse not The absolute position of the pulse Reset the alarm, and jog
SRVO-097 WARN established(Enc:%d) coder cannot be established. the axis on which the
-Check connection of the
connector of the
connecting cable. -Check
The acceleration sensor has not been the shielding of the above
connected. Otherwise, an error cable is connected
occurred during communication securely to the grounding
ACC sensor DTERR between the acceleration sensor and plate. -Replace the above
SRVO-098 alarm the main board. cable. -Replace the
ACC sensor CRCERR Data changed during transfer from the Refer to the SRVO-098
SRVO-099 alarm acceleration sensor. Remedy.
ACC sensor STBERR A stop bit error of the data from the Refer to the SRVO-098
SRVO-100 alarm
Robot acceleration
A sensorlimit
robot overtravel occurred.
switch has Remedy.
SRVO-101 SERVO overtravel(Robot:%d)
Hand broken beenhand
The pressed.
broken (*HBK) robot input is Refer to SRVO-005.
SRVO-102 SERVO (Robot:%d) asserted. Refer to SRVO-006.
Air pressure The pneumatic pressure (PPABN) robot
SRVO-103 SERVO alarm(Rbt:%d) input is asserted. Refer to SRVO-009.
No longer occurs. Welding electrode of Contact your FANUC
SRVO-104 SERVO Welding electrode controller. This might occur only for the Robotics technical
1. When the door is open,
close it. If there is no door
switch mounted, go to
Step 3. 2. Check the door
switch and door switch
connection cable. If the
switch or cable is faulty,
replace it. 3. Check that
connectors CRM67,
CRM70, and CRM71 on
the E?Stop unit are
Replace the teach
SRVO-105 SERVO Door open or E.Stop The cabinet door is open. pendant. 5. Replace the
The controller door has been opened, Close controller door and
Door emergency stop signals have been press RESET. If the reset is
SRVO-106 SERVO open/E.Stop(Robot:%d) detected for a short time, or a not effective, correct the
Check the brake for zero
The FET current for brake of an or abnormally low
Ext brake extended axis (brake number 2 or impedance. Then check
SRVO-107 SERVO abnormal(Rbt:%d) greater) exceeded the specification. the brake cable. Then
Press RESET to enable When the Enable/Disable switch is Press the RESET key to
SRVO-108 SERVO robot changed to enable, a reset is necessary enable the robot.
-Check connection of the
connector of the
connecting cable. -Check
the shielding of the above
cable is connected
-The acceleration sensor has not been securely to the grounding
ACC sensor ID mismatch connected. -A sensor other than plate. -Replace the above
SRVO-109 %d acceleration sensor is detected. cable. -Replace the
-Please set servo
parameter No.290 of the
axis GS3D-ACC sensor is
assigned with correct
channel number on your
-Pulse module channel setting is wrong pulse module(1-8), and
on the axis. -GS3D-ACC sensor is cycle power. -Please set
disabled on the axis. -The axis servo parameter
assignment is already used on Line- No.10/Bit7=ON of the axis
tracking or Full-closed control. -Setting GS3D-ACC sensor is
GS3D-ACC disabled %d for GS3D-ACC sensor is wrong on the assigned, and cycle
SRVO-110 (G:%d A:%d)
Softfloat time axis.
Follow-up time is over. when softfloat power.$SFLT_FUPTIM
Make -You cannot assign
SRVO-111 SERVO out(G:%d)
PAUSE. Softfloat time is OFF.
Follow-up time is over. when softfloat larger.
Make $SFLT_FUPTIM
SRVO-112 G out(G:%d) is OFF. larger.
Find and remove the
cause of the position error
While Cartesian Softfloat is being becoming greater. Or,
executed, the position error on the make the tolerance larger,
rectangular coordinates becomes turn off and then turn on
Cart. error excess(G:%d greater than the tolerance that is set by the controller. The
SRVO-113 SERVO %s) the user. tolerance is the value of
A singularity was detected during robot Re-teach the program
SRVO-114 Singularity Detected motion.
The linear path passes outside of the points,
Re-teachuse WJNT, or
program use
points,
SRVO-115 Limit error (G:%d, A:%s) axis limit. or use JOINT MOTYPE
One or more of the robot axes have Jog the robot within the
Axis Limit Exceeded exceeded an axis soft limit while limits to resume. Adjust
SRVO-116 (G:%d A:%d) executing SOFFLOAT. the program or process to
Machinelock has been set on a group - Set machinelock for all
that is using the same brake number as groups using the common
SRVO-117 Brake Number Conflict a different group that is not brake. - Change brake
Perform an action
according to the number
that is displayed in the
alarm message. 5: The
schedule number is not
specified or abnormal
schedule number other
This error indicates that an error occurs than 1~10 integral value is
SRVO-118 SFIGET err %s during SFIGET
Override is notexecution.
100 % when execute specified.
Set Specify
override 100%theand re-
SRVO-119 OVR not 100%% SFIGET program. execute SFIGET program
The difference between the integrator Execute SFIGET program
SFIVAL abnml(Scd:%d torque just before soft float execution again, or set $SFLT_GRP.
SRVO-120 G:%d A:%d)
Excessive acc/dec starts and $SFLT_GRP. $SFLT_IVAL $SFIVALLIM
Contact yourmore
FANUClarger.
SRVO-121 SERVO time(G:%d) Acceleration time is much longer. Robotics technical
Bad last The last angle update request does not Contact your FANUC
SRVO-122 SERVO ang(internal)(G:%d) match the current angle. Robotics technical
-Check the fan motor and
The rotation speed of fan motor on its cables. Replace them if
backplane unit has slowed down. necessary. -Replace the
Number in the bracket indicates which backplane unit. Before
fan is abnormal.(1): fan above the executing the remedy 3,
Fan motor rev slow slot1(2): fan above the slot2(3): both perform a complete
SRVO-123 down(%d) fans controller back up as
Check HardStop if If 'SRVO-024 Move Error excess' Alarm Refer to the Remedy of
SRVO-124 Hit(G:%d A:%d) occurs and the group is not calibrated, SRVO-024
Quick stop speed over Motion speed is too high to perform
SRVO-125 WARN (G:%d) quick stop. was over in the process of
The program Reduce the motion speed.
SRVO-126 SERVO OHAL1(PSM)
Quick stop error (G:%d)
alarm a quick stop. Press RESET.
Refer to the maintenance
SRVO-130 SERVO (G:%d A:%d) The servo amplifier (PMS) overheated. manual.
The DC voltage on the main power
LVAL(PSM) alarm(G:%d circuit of the servo amplifier is lower Refer to the maintenance
SRVO-131 SERVO A:%d) than the specification, even though manual.
HCAL(PSM) alarm(G:%d The current in the main power circuit of Refer to the maintenance
SRVO-132 SERVO A:%d) the servo amplifier exceeded manual.
FSAL(PSM) alarm (G:%d The cooling fan for the Power Supply Check the cable
SRVO-133 SERVO A:%d) Module (PSM) stopped. connection or replace the
Check the cables and
connections between the
DCLVAL(PSM) alarm The back-up charge circuit for the amplifier (CN1) and the
SRVO-134 SERVO (G:%d A:%d) amplifier has trouble. MCC. Check
Check the fuse
the cable
SRVO-135 SERVO FSAL alarm (G:%d A:%d) The amplifier cooling fan stopped. connection or replace the
Check that the input
voltage to the controller is
DCLVAL alarm (G:%d The servo amplifier DC current (DC link within the rated voltage,
SRVO-136 SERVO A:%d) voltage) is abnormally low. and
Refernotophase is lacking.
the maintenance
SRVO-137 SERVO DAL alarm (G:%d A:%d) DAL alarm of an amplifier. manual.
1. If the alarm disappears
by cycling the controller
The feedback data from the pulse power, make sure the
coder was abnormal. This is probably cable shields are
caused by noise on the pulse coder. grounded. 2. Reset the
SDAL alarm (G:%d Otherwise, the interpolation circuit of pulse coder alarm a. Press
SRVO-138 SERVO OHAL1(CNV)
A:%d) alarm the
A pulse coder built-in
servomotor's is broken.
thermostat was MENUS. b. Select SYSTEM.
SRVO-141 SERVO (G:%d A:%d) actuated. Refer to SRVO-049.
If the robot is overloaded
or the duty cycle exceeds
specification, this alarm
occurs. Check the
regenerative discharge
OHAL1(INV) alarm transistor. Check the
SRVO-142 SERVO PSFLAL(CNV)
(G:%d A:%d) alarm The servo
Input poweramplifier
appliedoverheated.
to the amplifier thermostat
Check on the servo
the connections
SRVO-143 SERVO (G:%d A:%d) has been lost. and cables of the input
LVAL(INV) alarm (G:%d The DC voltage of the main circuit
SRVO-144 SERVO A:%d) power supply is excessively low. Refer to SRVO-047.
LVAL(CNV-DC) This alarm indicates a problem with the
SRVO-145 SERVO alarm(G:%d A:%d) back-up charge circuit for the amplifier. Refer to SRVO-147.
Check each interphase
voltage of the three-phase
voltage (200 VAC) applied
LVAL(INV-DC) The DC voltage of the main circuit to the servo amplifier. If
SRVO-146 SERVO alarm(G:%d A:%d) power supply is too low. the applied voltage is
1. Check the cable
between the servo
amplifier (CN1) and the
MCC. Replace it if
LVAL(DCLK) alarm This alarm indicates a problem with the necessary. 2. For a model
SRVO-147 SERVO (G:%d A:%d) back-up charge circuit for the amplifier. using the B cabinet, check
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
The current in the main power circuit of shorted, determine if the
HCAL(CNV) alarm (G:%d the servo amplifier exceeded cable or motor is bad.
SRVO-148 SERVO A:%d) specification. Check the resistance
HCAL(INV) alarm (G:%d An excessively high current flowed
SRVO-149 SERVO A:%d)
FSAL(CNV) alarm (G:%d through the fan
The cooling main
forcircuit of a servo
the control circuit Refer
Checkto SRVO-045.
the fan. Replace it if
SRVO-150 SERVO FSAL(INV)
A:%d) alarm (G:%d stopped.
The cooling fan for the control circuit necessary.
SRVO-151 SERVO A:%d) stopped. Check
1. The or
IPMreplace
might the
be fan.
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,
IPMAL(INV) alarm disconnect the motor
SRVO-152 SERVO (G:%d A:%d) The IPM module has trouble. connector power lines
1. A short circuit might
have occurred in the DC
CHGAL(CNV) alarm The main circuit could not be charged link. Check the
SRVO-153 SERVO (G:%d A:%d) within the specified time. connection. 2. The
HVAL(CNV-DC) alarm The DC voltage of the main circuit
SRVO-154 SERVO (G:%d A:%d) power supply is abnormally high. Refer to SRVO-044.
DCAL(CNV) alarm (G:%d The energy produced by regenerative
SRVO-155 SERVO A:%d) discharge is excessive. Refer to SRVO-043.
1. Turn off the controller
power, and disconnect
the power cable from the
servo amplifier indicated
by the alarm message.
Disconnect the brake
cable (CRR64 on the servo
amplifier) to keep the axis
from falling unexpectedly.
Supply power to the
controller and see if the
alarm occurs again. If the
alarm occurs again,
replace the servo
amplifier. 2. Turn off the
controller power and
Abnormally high current flowed disconnect the power
IPMAL alarm (G:%d through the main circuit of the servo cable from the servo
SRVO-156 SERVO A:%d) amplifier. amplifier indicated by the
The DC link might cause a
short-circuit. Check the
CHGAL alarm (G:%d Charging of the main circuit could not connections. Electric
SRVO-157 SERVO A:%d) finish within the specified time. resistance to restrict
The emergency stop button on the Release the emergency
operator panel was pressed, or the stop button. If the
external emergency stop function was external emergency stop
activated. EMGIN1 and EMGINC are not function has been
strapped to each other. Or, EMGIN2 activated, remove the
and EMGINC are not strapped to each cause. If no cause can be
SRVO-160 SERVO Panel/External E-stop other. found, and no jumper is
Fence open or The teach pendant deadman switch is Press teach pendant
SRVO-161 SERVO Deadman SW released or the fence circuit is open. deadman switch or
The deadman switch is released, the
Deadman/Fence or fence circuit is open, the operator Remove the cause then
SRVO-162 SERVO Panel/External E-stop panel ESTOP button is pressed, or the press RESET.
SYSTE DSM hardware Different DSM (Digital Servo Module) Change the DSM
SRVO-163 M mismatch are mounted on the controller hardware to be same.
The DSM (Digital Servo Module) type is Change the current DSP-IV
SYSTE DSM/Servo param mismatched to the servo parameter module to DSP_V or
SRVO-164 M mismatch version. initialize the robot library
The operator panel emergency stop Power off. Correct the
SYSTE Panel(SVON abnormal) push button is pressed and miswiring wiring on SVON2 or
SRVO-165 M E-stop on SVON2 or EMG2 is detected. EMG2. Power on. Twist
The teach pendant emergency stop Power off. Correct the
SYSTE TP(SVON abnormal) E- push button is pressed and miswiring wiring on SVON2 or
SRVO-166 M stop on SVON2 or EMG2 is detected. EMG2. Power on. Twist
The teach pendant deadman switch is Power off. Correct the
SYSTE Deadman switch (SVON released while the teach pendant is wiring on SVON2 or
SRVO-167 M abnormal) enabled. And miswiring on SVON2 or EMG2. Power on. Press
SYSTE External/SVON (SVON Refer to SRVO-007 or SRVO-019. And Power off. Correct the
SRVO-168 M abnormal) E-stop miswiring on SVON2 or EMG2 is wiring on SVON2 or
Ext.E- The external emergency stop signal or - Release the external
stop/SVOFF/ServoDisco the servo disconnect signal or SVOFF emergency stop signal
SRVO-169 nnect signal is asserted. and press RESET. - If the
1. Check the software axis
The number of DSPs on the axis card is config (FSSB line number).
SRVO-170 Lack of DSP (ID:%d) lacking. 2. Replace the axis card
MotorSpd The motor cannot rotate as fast as the This is just a notification.
SRVO-171 WARN lim/DVC(G:%d A:%d) calculated speed required for the You do not have to do
SRVO-172 WARN lim/DVC0(G:%d A:%d) calculated speed required for the You do not have to do
SRVO-173 WARN lim/DVC1(G:%d A:%d) calculated speed required for the You do not have to do
MotorAcc The motor cannot accelerate as much This is just a notification.
SRVO-174 WARN lim/DVC(G:%d A:%d) as the calculated acceleration required You do not have to do
Internal motion error.
SRVO-176 SERVO CJ/Illegal Mode %d,%d The wrong CJ mode was used. Contact your FANUC
SRVO-177 WARN
SYSTE CJ error %d,%d,%d,%d
SRVO-178 M CJ error %d,%d,%d,%d
Motor torque The robot was going to move while Press RESET. Be careful
SRVO-179 WARN limit(G:%d A:%d) identifying the payload. not to move the robot
Controllable axis does not exist on any Please execute aux axis
SRVO-180 Control axis not exist group. setting at controlled start.
Mcmd input while The robot was going to move while Press RESET. Be careful
SRVO-181 SERVO estimating(G:%d) identifying the payload. not to move the robot
Perform Power OFF/ON:
Internal system error. The initialization 1. Turn off the robot. 2.
PAUSE. Needed init. has not of the system variable or the internal Turn on the robot. If the
SRVO-182 G been done work memory has not been done. error is not cleared,
PAUSE. Remove the cause of
SRVO-183 G ROBOT isn't ready Servo ready is off. Servo ready not being on.
PAUSE. The data region this command is going Wait the other task
SRVO-184 G Other task is processing to use is already locked by an other finishing the process. And,
PAUSE. The data this command is going to use Get the data of the group
SRVO-185 G Data is for other group is another group's data. that this command is to
PAUSE. Needed Data has not There is no data that this command will Get the needed data. And,
SRVO-186 G been got use, or, the data in the buffer is not the retry.
PAUSE. The mass parameter is needed in order Specify the mass
SRVO-187 G Need specfing Mass to estimate the current payload's parameter when
PAUSE. The free memory is too small to be Please increase
SRVO-188 G Memory is lacking allocated. Controller's memory
The error may have occurred in See the error message
SRVO-189 I/O-Link livecode error communication of the force sensor. about the force sensor.
1. Check connection of
the connector of the
connecting cable. 2. Check
the shielding of the above
cable is connected
securely to the grounding
Pulsecoder ID mismatch
A sensor other than Serial Pulsecoder is plate. 3. Replace the
SRVO-190 %d detected. above cable. 4. Replace
SYSTE Illegal Joint SpeedThe motion command exceeded Internal motion error.
SRVO-191 M (G:%d A:%d) specification. Contact your FANUC
The fence circuit is open or the SVON Close the fence circuit or
SRVO-192 SERVO Fence open/SVON input input circuit is open. SVON input circuit, and
Close SVON input circuit,
SRVO-193 SERVO SVON input The SVON input circuit is open. and then press RESET.
lit: 1. If a servo disconnect
switch is connected,
release the switch. 2.
Check the switch and
cable connected to 5
(SD4) ? 6 (SD41) and 7
(SD5) ? 8 (SD51) on
terminal TBOP3 located
on the operator panel
board. 3. When this signal
is not used, make a
connection (jumper)
between 5 (SD4) - 6
On the terminal block TBOP3 of the (SD41) and 7 (SD5) - 8
panel board, no connection is made (SD51). 4. Replace the
between 5 (SD4) - 6 (SD41) or between panel board. If the RDY
7 (SD5) - 8 (SD51). If a servo disconnect LED (green) is not lit: 1.
switch is connected between 5 (SD4) - 6 Check whether FUSE1 on
(SD41) or between 7 (SD5) - 8 (SD51), the operator panel board
then the switch is pressed. If the SYST- is blown. If FUSE1 is
067 (Panel HSSB disconnect) alarm is blown, replace FUSE1
also generated, or if the RDY LED after removing the cause.
(green) on the panel board is turned Otherwise, check the
off, communication between the main external 24 VDC supply on
board (JRS11) and the panel board the operator panel board,
(JRS11) is abnormal. The cable terminals EXT24V and
connectors between the main board EXT0V (TBOP6). If the
and the panel board might be loose or external 24 VDC is not
the cable, panel board, or main board used, verify that there are
SRVO-194 SERVO Servo disconnect might be faulty. jumpers between EXT24V
Press the Non Teacher
The Non Teacher Enabling Device is Enabling Device or
SRVO-195 SERVO NTED/Servo disconnect released or servo is disconnected. connect servo, and then
SYSTE Fence open/SVON input The fence circuit is open or the SVON Power off. Correct the
SRVO-196 M (SVON abnormal) input circuit is open and mis-wiring on wiring on SVON. Close the
SYSTE SVON input (SVON The SVON input circuit is open and mis- Power off. Correct the
SRVO-197 M abnormal) wiring on SVON is detected. wiring on SVON. Close the
Power off. Correct the
wiring on SVON. If using
The external emergency stop push external emergency stop,
SYSTE External E-stop (SVON button is pressed and mis-wiring on clear the source of the
SRVO-198 M abnormal) SVON is detected. fault, and press RESET. If
After this alarm, a fence
PAUSE. open or SVON input alarm
SRVO-199 G Control Stop A Control Stop is detected. is detected. Perform the
Control box fan Check and/or replace the
SRVO-200 WARN abnormal The control box fan motor has failed. fan. Refer to the
lit: 1. Do not press the
EMERGENCY STOP button
slowly on the operator
panel/operation box. 2.
Check the EMERGENCY
STOP button on the
operator panel/operation
box. If the switch has any
problem, replace the
switch unit or the
operator panel/operation
box. 3. Replace the panel
board. 4. Replace the
E?Stop unit. 5. Replace
the servo amplifier. If the
RDY LED (green) is not lit:
1. Replace the cable
connecting between the
main board (JRS11) and
The EMERGENCY STOP button on the the panel board (JRS11).
operator panel/operation box was 2. Replace the panel
Panel E-stop or SVEMG pressed, but the emergency stop circuit board.Note: Before
SRVO-201 SERVO abnormal was not disconnected. executing the next step,
1. Do not press the
on the teach pendant
The EMERGENCY STOP button on the slowly. 2. Replace the
operator panel/operation box was teach pendant. 3. Replace
TP E-stop or SVEMG pressed, but the emergency stop circuit the teach pendant cable.
SRVO-202 SERVO SVON
SYSTE abnormal
input(SVEMG was not disconnected. 4. Replace the operator
SRVO-203 M abnormal)
lit: 1. Check the switch
and cable connected to 1
(EES1) ? 2 (EES11) and 3
(EES2) - 4 (EES21) on
terminal TBOP4. 2.
Replace the panel board.
3. Replace the E?Stop
unit. 4. Replace the servo
amplifier. 5. Replace the
connection cable between
the E?Stop unit and the
panel board. If the RDY
LED (green) is not lit: 1.
Replace the cable
The switch connected across EES1 - main board (JRS11) and
EES11 and EES2 - EES21 on terminal the panel board (JRS11).
TBOP4 located on the panel board was 2. Replace the panel
SYSTE External(SVEMG pressed, but the emergency stop circuit board.Note: Before
SRVO-204 M abnormal) E-stop was not disconnected. executing the next step,
(EAS1) - 6 (EAS11) and 7
(EAS2) - 8 (EAS21) on
terminal TBOP4. 2.
Replace the cable
connecting the main
The switch connected across terminals board (JRS11) to the panel
EAS1 - EAS11 and EAS2 - EAS21 on board (JRS11). 2. Replace
terminal TBOP4 located on the panel the panel board.Note:
SYSTE Fence open(SVEMG board was pressed, but the emergency Before executing the next
SRVO-205 M abnormal) stop circuit was not disconnected. step, perform a complete
The DEADMAN switch was released 1. Replace the teach
while the teach pendant was turned pendant. 2. Replace the
SYSTE Deadman switch on, but the emergency stop circuit was teach pendant cable. 3.
SRVO-206 M (SVEMG abnormal) not disconnected. Replace the operator
The SVEMG signal is detected while the Close the controller door.
fence is opened and the teach pendant If door is not opened,
is enabled and the Deadman switch is correct the wiring on
TP switch abnormal or not released. Or, the controller door is SVEMG. Or correct the
SRVO-207 SERVO Door open opened while the fence is opened and enable switch and
Check the brake for zero
or abnormally low
The FET current for the brake of an impedance. Then check
Extended axis brake extended axis (brake number 2 or the brake cable. Then
SRVO-208 SERVO abnormal greater) exceeded the specification. check 200VAC. Then check
Power off. Correct the
Robot-%d SVEMG Mis-wiring of the SVEMG signal on wiring of SVEMG on the
SRVO-209 SERVO abnormal Robot 2 is detected. controller of the second
EX_robot SVEMG Mis-wiring of SVEMG signal on Power off. Correct the
SRVO-210 SERVO abnormal Extended robot is detected. wiring on SVEMG on
Teach Pendant is disabled when mode Change the TP
switch is T1 or T2 and Robot1 and Enable/Disable switch to
SRVO-211 SERVO TP OFF in T1,T2 Robot2 are disconnected Or mis-wiring ON And press
Replace RESET
fuse on If the
6 Panel
SRVO-212 SERVO Trans over heat The fuse on Panel PCB is blown PCB
1. Check whether FUSE1
board is blown. If FUSE1 is
blown determine the
cause, and replace FUSE1.
Otherwise, check the
external 24 VDC supply on
the operator panel board,
terminals EXT24V and
EXT0V (TBOP6). If the
external 24 VDC is not
used, verify that there are
jumpers between EXT24V
? INT24V and EXT0V ?
INT0V (TBOP6). 2. Replace
the cable connecting the
main board (JRS11) and
the panel board (JRS11).
3. Replace the panel
board. Note: Before
executing the next step,
perform a complete
controller backup to save
all of your programs and
SRVO-213 SERVO Fuse blown (PanelPCB) A fuse on the panel board has blown. settings. Refer to the
If fuse F1 or F2 has blown:
1. Replace the servo
amplifier. If fuse FS2 or
FS3 has blown: 1.
Fuse blown Eliminate the cause of the
SRVO-214 SERVO (Amp,Robot:%d) A fuse in the servo amplifier has blown. blown fuse and replace it.
Fuse blown Total current of is over the limit. Change program speed to
SRVO-215 SERVO (Brake,Robot:%d) Because robot motion is too aggressive be slow
1. Slow the motion of the
robot where possible.
Check the robot operating
conditions. If the robot
operating conditions
exceed the duty or load
weight rating, reduce the
duty and/or load
The current (total current for six axes) conditions to be within
SRVO-216 SERVO OVC(total) (%d) flowing through the motor is too large. the allowable range.
1. Check whether fuse
FUSE1 on the emergency
stop board has blown. If
the fuse has blown, check
and correct the cause
then replace the fuse. 2.
The emergency stop board is not found Check the cable between
when the controller power is turned emergency stop board
SRVO-217 E-STOP Board not found on. and main board. Replace
- Release the external
Ext.E- The external emergency stop signal or emergency stop signal
SRVO-218 stop/ServoDisconnect the servo disconnect signal is asserted. and press RESET. - If the
Replace the fuse on the
main board or main board
SRVO-220 SDI fuse blown The fuse for SDI has blown. itself. Refer to the Mate
1. Check whether the set
number of axes is valid. If
the number is invalid, set
it to the correct number.
2. Replace the axis control
card with a card
Lack of DSP (G:%d An axis control card corresponding to corresponding to the set
SRVO-221 SERVO A:%d) the set number of axes is not mounted. number of axes. Note:
1. Verify that the optical
cable is securely
connected to the SVM
The FSSB optical cable is not connected amplifier. 2. Replace the
SRVO-222 SERVO Lack of Amp (Amp:%d) to an SVM amplifier. optical
Performcable. 3. Check
an action
according to the first
number that is displayed
in the alarm message. 1:
This is a warning due to
$scr.$startup_cnd=12.
2,3,4,7: Replace a servo
card. 5,6: Invalid ATR
A servo DSP initialization failure setting. Specified
occurred and the software entered DSP hardware start axis might
dry run mode. The first number be wrong. 8,10: FSSB init
indicates the cause of the failure. The error occurs
SRVO-223 SERVO DSP dry run (%d,%d) second number is extra information. simultaneously. Follow
Please verify this change is
Slot changed Hardware slot of the auxiliary axis valid. If this change is due
SRVO-224 (AuxBrd%d,%d>%d) board has been changed. to a simple mistake,
1. Repair the circuit of the
chain 1 on the hardware.
Chain 1 abnormal 2. Set CHAIN FAILURE
SRVO-230 SERVO %x,%x A single chain 1 failure occurred. detection to TRUE on the
1. Repair the circuit of the
chain 2 on the hardware.
Chain 2 abnormal 2. Set CHAIN FAILURE
SRVO-231 SERVO %x,%x A single chain 2 failure occurred. detection to TRUE on the
1. Grip the non-teacher
enabling device. 2. Check
the 24V (NTED1 - NTED11)
and 0V (NTED2 - NTED21)
connections for the NTED
input on connector
CRM65 located on the
The non-teacher enabling device is operator panel board. 3.
SRVO-232 SERVO NTED input released. Replace the mode switch.
1. Enable the teach
pendant while performing
a teaching operation.
Otherwise, the mode
switch should be in AUTO
mode. 2. Close the
controller door, if open.
Otherwise, check the door
The teach pendant is disabled when the switch, and replace it if
TP OFF in T1,T2/Door mode switch is set to T1 or T2, or the necessary. 3. Replace the
SRVO-233 SERVO Deadman
open switch controller
The door is opened.
teach pendant deadman switch is teach pendant. 4. Replace
SRVO-234 WARN released released. This is just a notification.
1. To reset the detecting
circuit for a single chain
failure, re?operate the
A short-term single chain failure EMERGENCY STOP button
condition is detected. A short-term of the operator
single chain failure is: * If any cause for panel/operation box or
stopping the robot is issued for a short the EMERGENCY STOP
time, the detecting circuit for the single button of the teach
chain failure detects a single chain pendant or the DEADMAN
fault. In this case, the software does switch according to the
not detect the cause of the stop, so this previous operation
alarm is distinguished from SRVO?230 (whatever you did to
(Chain 1 +24V) and SRVO?231 (Chain 2 cause the alarm). If this
0V) single chain faults. Cause of this alarm is reset, the
alarm is: * Half release of the message ?SRVO?236
DEADMAN switch. * Half operation of Chain failure is repaired?
the EMERGENCY STOP button on the is displayed. 2. Check the
operator?s panel/operation box or half input requirement for the
operation of the EMERGENCY STOP external emergency stop.
button on the teach pendant. Short- This error might be
term single chain failures that occur on caused by a timing issue.
the EMERGENCY STOP button of 3. Replace the panel
operator?s panel/operation box, the board. 4. Replace the
EMERGENCY STOP button of the teach E?Stop unit. 5. Replace
pendant and the DEADMAN switch are the servo amplifier. 6.
Short term Chain all recoverable by issuing a correct stop Replace the connection
SRVO-235 SERVO abnormal operation. cable between the panel
The status of the chain
failure has changed to
SRVO-236 WARN Chain failure is repaired A chain failure was repaired. normal when the system
Note: If the single chain
failure occurred because
of the operator?s panel
EMERGENCY STOP button,
the teach pendant?s
or the teach pendant?s
DEADMAN switch, the
failure can be recovered
by a Correct Stop Action
or by cycling the
controller power. The
Correct Stop Operation
requires you to press and
release either the
operator panel
the teach pendant
or the DEADMAN switch.
If the single chain failure
occurred anywhere else,
you must also perform the
Special Reset Operation to
reset the alarm. See
below. Caution 1. This
alarm is controlled by the
software and requires a
special reset procedure
Cannot reset chain (Special Reset Operation).
SRVO-237 WARN failure A chain failure could not be repaired. After resolving the cause
Repair the circuit of chain
A single chain 1 (+24V) failure occurred 1 (+24V) on the SVON
Chain 1 (SVON) when the SVON (Servo ON/OFF switch) hardware. Set CHAIN
SRVO-238 SERVO abnormal input was asserted. FAILURE detection to
A single chain 2 (0V) failure occurred chain 2 (0V) on SVON the
Chain 2 (SVON) when a SVON (Servo ON/OFF switch) hardware. Set CHAIN
SRVO-239 SERVO abnormal input was asserted. FAILURE
1. Check detection to
the 24V safety
fence connection on
terminals 5 (EAS1) - 6
(EAS11) on TBOP4 located
panel board. 3. Replace
the E?Stop unit. 4.
Replace the servo
Although the circuit connected amplifier. 5. Replace the
between EAS11 - EAS1 on terminal connection cable between
TBOP4 located on the panel board was the panel board and the
disconnected, the emergency stop line E? stop unit (CRM64), or
Chain 1 (FENCE) was not disconnected. The emergency between the E?Stop unit
SRVO-240 SERVO abnormal stop circuit is faulty. and the servo amplifier
1. Check the 0V safety
fence connection
between 7 (EAS2) - 8
(EAS21) on TBOP4 located
the E?Stop unit. 4.
Replace the servo
Although the circuit connected amplifier. 5. Replace the
between EAS21 - EAS2 on termianl connection cable between
TBOP4 located on the panel board was the panel board and the
disconnected, the emergency stop line E?Stop unit (CRM64), or
Chain 2 (FENCE) was not disconnected. Therefore, the between the E?Stop unit
SRVO-241 SERVO abnormal emergency stop circuit is faulty. and the servo
1. Check amplifier
the 24V external
emergency stop
connection between 1
(EES1) - 2 (EES11) on
TBOP4 located on the
operator panel board. 2.
Although the external emergency stop connection cable between
circuit was disconnected, the the panel board and the
emergency stop line (+24V) was not E?Stop unit (CRM64), or
Chain 1 (EXEMG) disconnected. Therefore, the between the E?Stop unit
SRVO-242 SERVO abnormal emergency stop circuit is faulty. and the servo
1. Check amplifier
the 0V external
emergency stop
connection 3 (EES2) - 4
(EES21) on TBOP4 located
the E?Stop unit. 4.
Replace the servo
Although the external emergency stop connection cable between
circuit was disconnected, the the panel board and the
emergency stop line (0V) was not E?Stop unit (CRM64), or
Chain 2 (EXEMG) disconnected. Therefore, the between the E?Stop unit
SRVO-243 SERVO abnormal emergency stop circuit is faulty. and the servo amplifier
Chain 1 hardware. Set CHAIN
SRVO-244 SERVO abnormal(Rbt:%d) A single chain 1 (+24V) failure occurred. FAILURE detection to
chain 2 (0V) on the
Chain 2 hardware. Set CHAIN
SRVO-245 SERVO abnormal(Rbt:%d)
Chain 1 A single chain 2 (0V) failure occurred. FAILURE detection to
SRVO-246 SERVO Chain
abnormal(EX_robot)
2
SRVO-247 SERVO abnormal(EX_robot)
- Release both deadman
switches at once. If SRVO-
236 Chain failure is
repaired occurred, there
is no hardware problem.
This alarm could occur
when deadman switch is
pressed halfway. - When
SRVO-236 does not occur,
please replace hardware
in following order. - Teach
Deadman switch status The status of two DIs of DEADMAN pendant - Cable between
SRVO-248 abnormal switch do not match. teach pendant and the
SVEMG/MAINON1 Status of MAINON1 signal is still OFF Repair the circuit of
SRVO-250 SERVO abnormal
DB relay even if SVEMG
The dynamic is ONrelay
brake It is in
abnormal
the of E.Stop hardware Power
SRVO-251 SERVO abnormal(G:%d A:%d) amplifier is abnormal. Replace the amplifier.
Current detect The current detection circuit in the
SRVO-252 SERVO abnl(G:%d A:%d) amplifier is abnormal. Replace the amplifier.
Amp internal over An amplifier internal overheat was Check that the cooling fan
SRVO-253 PAUSE heat(G:%d
E-STOP A:%d)
circuit abnormal detected.occurs at a relay in E-STOP
Welding is working properly, or
SRVO-254 (KA5)
E-STOP circuit abnormal circuit.
Welding occurs at relay in E-STOP Replace an E-STOP unit.
SRVO-255 (KM2)control circuit
MCC circuit.
MCC control output is abnormal in the an E-STOP
Replace the 6ch. unit
SRVO-256 abnormal (AMP) 6ch. amplifier. amplifier.
Although the non?teacher enabling 1. Replace the panel
device disconnected the NTED circuit in
the T1/T2 mode, the emergency stop E?Stop unit. 3. Replace
Chain 1 (NTED) line (24V) was not disconnected. Thethe servo amplifier. 4.
SRVO-260 SERVO abnormal emergency stop circuit is faulty. Replace the connection
Although the non?teacher enabling 1. Replace the panel
device disconnected the NTED circuit in
the T1/T2 mode, the emergency stop E?Stop unit. 3. Replace
Chain 2 (NTED) line (0V) was not disconnected. The the servo amplifier. 4.
Although the SVDCT circuit was board. 2. Replace the
disconnected, the emergency stop line E?Stop unit. 3. Replace
Chain 1 (SVDISC) (24V) was not disconnected. The the servo amplifier. 4.
Although the SVDCT circuit was board. 2. Replace the
disconnected, the emergency stop line E?Stop unit. 3. Replace
Chain 2 (SVDISC) (0V) was not disconnected. The the servo amplifier. 4.
CRM67 and CRM72
connectors on the E?Stop
SYSTE E.STOP circuit abnormal An error occurred in the emergency unit are connected
SRVO-264 M 1 stop circuit. securely. 2. Check
E.STOP circuit abnormal When the servo entered the activated 1. Replace the E?Stop
SRVO-265 SERVO 2 state, MON3 was in the on state. The unit. 2. Replace the servo
1. Check the +24 V
connection (between
EAS11 and EAS1) for the
fence. 2. Check the fence
switch. 3. Replace the
panel board. Note:
Eliminate the cause of the
abnormal chain, and then
execute the ?Special Reset
FENCE1 status Operation? to release the
SRVO-266 SERVO abnormal The fence circuit is abnormal. alarm. Caution Do not
1. Check the 0 V
connection (between
EAS21 and EAS2) for the
fence. 2. Check the fence
switch. 3. Replace the
panel board. Note:
Eliminate the cause of the
abnormal chain, and then
execute the ?Special Reset
FENCE2 status Operation? to release the
SRVO-267 SERVO abnormal The fence circuit is abnormal. alarm. Caution Do not
1. Check the +24 V
connection (between
EGS11 and EGS1) for the
SVOFF circuit. 2. Check
the SVOFF switch. 3.
Note: Eliminate the cause
of the abnormal chain,
and then execute the
SVOFF1 status ?Special Reset Operation?
SRVO-268 SERVO abnormal The SVOFF circuit is abnormal. to release the alarm.
1. Check the 0 V
connection (between
EGS21 and EGS2) for the
SVOFF circuit. 2. Check
the SVOFF switch. 3.
SVOFF2 status ?Special Reset Operation?
SRVO-269 SERVO abnormal The SVOFF circuit is abnormal. to release the alarm.
1. Check the +24 V
connection (between
ESPB11 - ESPB1) for the
EXEMG circuit. 2. Check
the EXEMG switch. 3.
EXEMG1 status ?Special Reset Operation?
SRVO-270 SERVO abnormal The EXEMG circuit is abnormal. to release the alarm.
1. Check the 0 V
connection (between
ESPB21 - ESPB2) for the
EXEMG circuit. 2. Check
the EXEMG switch. 3.
EXEMG2 status ?Special Reset Operation?
SRVO-271 SERVO abnormal The EXEMG circuit is abnormal. to release the alarm.
1. Check the +24 V
connection (between
SD41 and SD4) for the
SVDISC circuit. 2. Check
the SVDISC switch. 3.
SVDISC1 status ?Special Reset Operation?
SRVO-272 SERVO abnormal The SVDISC circuit is abnormal. to release the alarm.
1. Check the 0 V
connection (between
SD51 and SD5) for the
SVDISC circuit. 2. Check
the SVDISC switch. 3.
SVDISC2 status ?Special Reset Operation?
SRVO-273 SERVO abnormal The SVDISC circuit is abnormal. to release the alarm.
1. Check the +24 V
connection (between
NTED11 and NTED1) for
the NTED circuit. 2. Check
the NTED switch. 3.
?Special Reset Operation?
SRVO-274 SERVO NTED1 status abnormal The NTED circuit is abnormal. to release the alarm.
1. Check the 0 V
connection (between
NTED21 and NTED2) for
the NTED circuit. 2. Check
the NTED switch. 3.
?Special Reset Operation?
SRVO-275 SERVO NTED2 status abnormal The NTED circuit is abnormal. to release the alarm.
Check the wiring of
SVEMG. If the wiring of
The operator panel emergency stop SVEMG is not connected,
push button is pressed and miswiring correct the wiring of
SRVO-276 SERVO Disable on T2 mode on SVEMG is detected. SVEMG. If the wiring has
Check the wiring of
SVEMG. If the wiring of
The teach pendant emergency stop SVEMG is not connected,
SYSTE Panel E-stop(SVEMG push button is pressed and miswiring correct the wiring of
SRVO-277 M abnormal) on SVEMG is detected. SVEMG. If the wiring has
Status of MON1,MON2,MON3 signals Repair the circuit of
SYSTE TP E-stop(SVEMG are abnormal on COLD START Value MON1,MON2,MON3 on
SRVO-278 M
SYSTE abnormal) shows
SVOFF MON1,MON2,MON3 signal
(Servo OFF signal) input E.STOP unitthe cause to
Determine
SRVO-279 M Circuit abnormal 3 (%d) asserted. input SVOFF
If the RDY LEDand repair.is
(green)
lit: 1. If a switch is
connected, release the
switch. 2. Check the
switch and cable
connected to 9 (EGS1) ?
10 (EGS11) or 11 (EGS2) ?
12 (EGS21) on terminal
TBOP4. 3. When this
signal is not used, make a
connection between 9
(EGS1) - 10 (EGS11) and
between 11 (EGS2) - 12
(EGS21). 4. Replace the
Check whether FUSE1 on
the operator panel board
is blown. If FUSE1 is
blown, replace FUSE1
after removing the cause.
Otherwise, check the
external 24 VDC supply on
the operator panel board,
On the terminal block TBOP4 located terminals 9 (EXT24V) and
on the panel board, no connection is 12 (EXT0V) located on
made between 9 (EGS1) - 10 (EGS11) or terminal TBOP6. If the
between 11 (EGS2) - 12 (EGS21). If a external 24 VDC is not
switch is connected between 9 (EGS1) - used, verify that there are
10 (EGS11) or between 11 (EGS2) - 12 jumpers between 9
SRVO-280 SERVO SVOFF input (EGS21), then the switch is pressed. (EXT24V) ? 10 (INT24V)
(EGS1) - 10 (EGS11) and
11 (EGS2) - 12 (EGS21) on
operator panel terminal
TBOP4. 2. Replace the
the E?Stop unit. 4.
Replace the servo
Replace the cable
When the SVOFF signal was asserted, main board (JRS11) and
SYSTE SVOFF input(SVEMG an SVEMG error was detected. The the panel board (JRS11).
SRVO-281 M abnormal) emergency stop circuit is faulty. 2. Replace the panel
1. Check the 24V servo
Although the switch connected on/off connection
between EGS11 and EGS1 on terminal between 9 (EGS1) - 10
TBOP4 located on the panel board was (EGS11) on TBOP4 located
pressed, the emergency stop line (24V) on the operator panel
Chain 1 (SVOFF) was not disconnected. The emergency board. 2. Replace the
SRVO-282 SERVO abnormal stop circuit is faulty. panel board. 3. Replace
Although the switch connected of the 0V servo on/off
between EGS21 and EGS2 on terminal switch between 11 (EGS2) -
TBOP4 located on the panel board was 12 (EGS21) on TBOP4
pressed, the emergency stop line (0V) located on the operator
Chain 2 (SVOFF) was not disconnected. The emergency panel board. 2. Replace
SYSTE E.STOP circuit abnl stop
A weldcircuit is faulty.
occurred on the EMERGENCY the
Repairpanel
theboard.
MON33.circuit
SRVO-286 M 1(G:%d) STOP unit. on the EMERGENCY STOP
E.STOP circuit abnl The status of MON3 is abnormal. The Repair the MON3 circuit
SRVO-287 SERVO DClink
2(G:%d)HC alarm(G:%d MON3 status is ON when servo is on the EMERGENCY STOP
SRVO-290 SERVO A:%d) IPM over heat alarm occured
IPM over heat (G:%d The IPM in the servo amplifier has amplifier fan stops. 2.
SRVO-291 SERVO A:%d)
EXT.FAN alarm (G:%d overheated.
The cooling fan for the external Reduce
Check the thecable
override
SRVO-292 SERVO A:%d) amplifier fan stopped. connection or replace the
DClink(PSM) HCAL(G:%d The three?phase input power supply is 1. Check the three?phase
SRVO-293 SERVO EXT.FAN(PSM)
A:%d) abnormal
The or the
external fan PSM is faulty.
for the ~PSM or input power supply. 2.
SRVO-294 SERVO alarm(G:%d A:%d) ~PSMR is faulty. Replace the external fan.
SVM COM alarm(G:%d The cable between the PSM and SVM 1. Replace the cable
SRVO-295 SERVO A:%d) might be faulty, or the PSM or SVM between the PSM and
The operating conditions are too hard 1. Reduce the taught
PSM DISCHG alm(G:%d or the regenerative resistance cooling feedrate because the
SRVO-296 SERVO A:%d) fan for the PSMR has stopped. operating conditions are
PSM LowVolt alm(G:%d The three?phase input voltage might 1. Check the three?phase
SRVO-297 SERVO A:%d) have dropped or the PSM or SVM might input power supply. 2.
A safety hand broken is detected when Press reset key to clear
SYSTE SRVO velocity alm(G:%d setting of HBK is disabled. The most alarm. Verify whether
SRVO-298 M A:%d) likely cause is the HBK signal of a robot robot has hand broken
1. Press RESET on the
teach pendant to release
the alarm. 2. Check
whether the hand broken
Hand broken/HBK Although HBK was disabled, the HBK signal is being used on the
SRVO-300 SERVO disabled signal was asserted. robot. When the hand
A signal of safety hand broken is not Change Hand broken to
Hand broken/HBK detected when setting of HBK is Enable. Press reset key to
SRVO-301 SERVO dsbl(Rbt:%d) disabled. Setting of Hand broken is not clear alarm.
1. Press RESET on the
teach pendant to release
the alarm. 2. Check
whether the hand broken
Set Hand broken to Although HBK was disabled, the HBK signal is being used on the
SRVO-302 SERVO ENABLE signal was input. robot. When the hand
An HBK alarm occurs when $HBK_ENBL Two remedies are
= FALSE (HBK disabled) and the HBK available for this alarm: *
Set HBK to signal is ON (a +24V signal exists at the Set $HBK_ENBL = True
SRVO-303 SERVO ENABLE(Rbt:%d) HBK input). (HBK enabled) for the
C-flex: manual brake The manual brake mode enable signal Change the manual brake
SRVO-304 SERVO enabled is detected. modeoff
Turn to and
disable. Press
on the
SRVO-305 Unit Change(G%d,%s) The robot model was changed. controller power supply.
CPU ready Timeout Displayed robot arm did not start up Please confirm the robot
SRVO-306 (Rbt:%d)
ABC Unexpected within a fixed time. arm ishave
Must displayed with
at least two
SRVO-310 SERVO Motion(G:%d) Isolated offset destination points
MPDT failed(G:%d The Magnetic Phase Detection (MPDT) This is an internal error.
SRVO-315 PAUSE A:%d) process failed. Contact your FANUC
Increase the
$SCR.$MPDT_TIMLMT
MPDT time is up(G:%d The Magnetic Phase Detection (MPDT) value 1000 by 1000 until
SRVO-316 PAUSE A:%d) process time is up. this alarm does not occur.
MPDT cannot The Magnetic Phase Detection (MPDT) Disable the machine lock
SRVO-317 PAUSE start(Machine Lock) process cannot start because machine for that group.
MPDT cannot Magnetic Phase Detection (MPDT) Clear the reason of SRDY
SRVO-318 PAUSE start(SRDY Off) process cannot start because the servo off.
- Release the SVOFF signal
and press RESET. -
SRVO-322 SVOFF input / E.STOP The SVOFF (Servo off signal) is input. Document the events that
Torque limit (G%d A%d Torque limit reached. The third number Modify TP program to be
SRVO-323 L%d) indicates the line number of the TP less aggressive.
-Check whether the
payload (mass, center of
gravity, and inertia) are
Disturbance estimated in the software set correctly. -Check
exceeds the threshold value. There is whether the applied load
Disturbance possibility that SRVO-050 occurs when exceed the rating. If so,
SRVO-324 excess(G%d A%d L%d) the robot runs leaving this warning. reduce the applied load. -
The different between motion Internal motion error.
Abnormal Mcmd (G:%d command and machine pulse exceeded Document the events that
SRVO-326 A:%d) specified threshold. led to the error, and
It is likely that the
Pulsecoder has
malfunctioned due to
noise or the Pulsecoder is
The retry count of the Pulsecoder abnormal. 1. Check if
Retry count err(G:%d exceeded a limit value of $PLS_ER_LIM there exists a noise source
SRVO-328 A:%d Enc:%d) when $PLS_ER_CHK=1. near the Pulsecoder. 2.
It is likely that the
Pulsecoder has
malfunctioned due to
The position feedback compensation noise or the Pulsecoder is
count of the Pulsecoder exceeded a abnormal. 1. Check if
FB comp cnt err(G:%d limit value of $PLS_CMP_LIM when there exists a noise source
SRVO-329 A:%d Enc:%d) $PLS_ER_CHK=1. near the Pulsecoder. 2.
Retry count err(G:%d The retry count of the pulse coder Document the events that
SRVO-330 SERVO A:%d) exceeded a limit value of $PLS_ER_LIM led to the error, and call
the position feedback compensation Document the events that
FB comp cnt err(G:%d count of the pulse coder exceeded a led to the error, and call
SRVO-331 SERVO A:%d) limit value of $PLS_CMP_LIM when your FANUC Robotics
Turn off/on the controller,
Power off to reset You must cycle power in order to reset and then perform single
SRVO-332 SERVO CMAL the CMAL alarm. axis mastering on the axis.
SYSTE You must turn the controller off, then Turn off the controller,
SRVO-333 M Power off to reset on again to update the parameters. then turn it on again.
SRVO-334 I/O-Link
DCS internal
OFFCHK error
alarm I/O-Link
A failure software
was detectedinternal error.
in the safety contact your FANUC
SRVO-335 SERVO %x,%x
DCS RAMCHK alarm signal input circuit. Replace the CPU panelcard
board.
or
DCS PRMCHK alarm An error occured in the RAM safetyself test. main board.
Set the modified safety
SRVO-337 SERVO %x,%x parameter
An self test.
error occured in the software parameter
Check again.alarms
the other
SRVO-338 SERVO DCS FLOW alarm %x,%x sequence self test. for more
Check theinformation.
other alarms
SRVO-339 SERVO DCS MISC
T1 TCPalarm %x,%x
speed(G%d) A software
The internal
TCP speed error250mm/sec
exceeds has occurred.in for more information.
DCS T1 flange T1 mode.
The flange speed exceeds 250mm/sec Make the override lower.
SRVO-341 SERVO speed(G%d)
DCS Cartesian%x,%x in T1
An mode.
error occurred in the DCS Cartesian Make the
Check the override
programlower.
or
SRVO-342 SERVO position(G%d)
DCS Cartesian %x,%x position
An error check.
occurred in the DCS Cartesian operation.
Check the program or
SRVO-343 SERVO speed(G%d)
DCS %x,%x
GRP alarm(G%d) speed check. operation.
Check the other alarms
DCS Joint A software internal
error occurred error
in the hasJoint
DCS occurred. for
Checkmoretheinformation.
program or
SRVO-345 SERVO position(G%d,A%d)
DCS Joint position
An error check.
occurred in DCS Joint speed operation.
Check the program or
SRVO-346 SERVO speed(G%d,A%d)
DCS AXS %x,%x check. operation.
SRVO-347 SERVO alarm(G%d,A%d) %x,%x A software internal error has occurred. for more information.
1. Replace the E-stop unit.
A command was issued to turn off the 2. Replace the panel
DCS MCC OFF alarm magnetic contactor, but the magnetic board. 3. If a signal is
SRVO-348 SERVO %x,%x contactor was not turned off. connected to the
A command was issued to turn on the 1. Replace the E-stop unit.
DCS MCC ON alarm magnetic contactor, but the magnetic 2. Replace the panel
SRVO-349 SERVO %x,%x contactor was not turned on. board.
Replace3.the Replace the or
CPU card
SRVO-350 SERVO DCS CPU alarm %x,%x An error occurred in the RAM self test. main board.
An error occurred in the safety Load the system software
SRVO-351 SERVO DCS CRC alarmalarm
COUNT1 %x,%x software
The safetyCRC test. does not run with
software or replace
Check the alarms
the other
DCS COUNT2 alarm the proper
The timing. does not run with
safety software for more
other alarms
SRVO-353 SERVO %x,%x the proper timing. for more information.
The safety software does not run with Check the other alarms
SRVO-354 SERVO DCS DICHK alarm
ITP_TIME %x,%x
alarm the
The proper timing. does not run with
other alarms
DCS ITP_SCAN alarm the proper
The timing. does not run with
other alarms
SRVO-356 SERVO %x,%x the proper timing. for more information.
- When 'Position/speed process' in DCS
menu is DISBALED, Cartesian position
check, Cartesian speed check, Joint
position check or Joint speed check is
ENABLED. - Cartesian position check, Disable Cartesian position
Cartesian speed check, Joint position check, Cartesian speed
DCS ENABLED alarm check or Joint speed check is ENABLED check, Joint position check
SRVO-357 SERVO %x,%x for the group that does not exist. - Joint or Joint speed check
- Safety parameter DICHK_LIM1 is
greater than 50. - Safety parameter
ITP_TIME is less than 1. - Safety
parameter NUM_GRP is less than 0 or
greater than 8. - Safety parameter
NUM_AXS is less than 0 or greater than
9. - Safety parameter NUM_ROB_AXS is
DCS INVPRM alarm less than 0 or greater than 9. - Safety Check the safety
DCS SYSTEM alarm parameter NUM_ROB_AXS is greater parameter.
DCS CC_TCP A software internal error has occurred. for more
other alarms
SRVO-360 SERVO alarm(G%d)
DCS %x,%x
CC_FP alarm(G%d) Results of 2 CPU are different. for more
other alarms
DCS CC_TCPS Results of 2 CPU are different. for more information.
DCS CC_FPS %x,%x
alarm(G%d) Results of 2 CPU are different. for more
other alarms
DCS PRMCRC Results of 2 CPU are different. for more information.
DCS FB_CMP%x,%x Results of 2 CPU are different. for more
other alarms
SRVO-365 SERVO alarm(G%d,A%d)
DCS FB_INFO %x,%x Results of 2 CPU are different. for more information.
DCS CC_JPOS %x,%x Safety parameter FB_INFO is invalid. Set FB_INFO.
DCS CC_JSPD %x,%x Results of 2 CPU are different. for more
other alarms
SRVO-368 SERVO alarm(G%d,A%d) %x,%x Results of 2 CPU are different. for more information.
A chain alarm was detected with the
SRVO-370 SERVO SVON1 status abnormal panel board internal signal (SVON). Replace the panel board.
A chain alarm was detected with the
SRVO-371 SERVO SVON2 status abnormal panel board internal signal (SVON). Replace the panel board.
A chain alarm was detected with the 1. Replace the panel
OPEMG1 status emergency stop switch on the board. 2. Replace the
SRVO-372 SERVO abnormal operator's panel. teach pendant cable. 3.
A chain alarm was detected with the 1. Replace the panel
OPEMG2 status emergency stop switch on the board. 2. Replace the
SRVO-373 SERVO abnormal operator's panel. teach pendant cable. 3.
MODE11 status A chain alarm was detected with the 1. Check the mode switch
SRVO-374 SERVO abnormal mode switch signal. and its cable. Replace
circuitry connected to the
OPSFTY11 status A chain alarm was detected with the dual input signal (OPSFTY)
SRVO-378 SERVO abnormal OPSFTY signal. is faulty. 2. Check whether
Softfloat stroke OPSFTY signal. is
Usefaulty. 2. Check
soft float withwhether
a wide
SRVO-386 lim(G:%d)
Softfloat Certain axes reached stroke limit. margin.
Use soft float in the
SRVO-387 impossible(G:%d)
Softfloat The position or schedule is not proper. proper
Use softposition anda wide
float with
SRVO-388 singularity(G:%d
Start diag data Certain axes reached singularity. margin.
SRVO-389 recording.
End diag data Beginning to record diagnostic data. None required.
SRVO-390 recording. Diagnostic data recording is finished. None required.
SRVO-391 Start diag data saving. Beginning to save diagnostic data. None required.
SRVO-392 End diag
Other data saving.
diagnosis data is Diagnostic data has been saved. Noneuntil
Wait required.
the recording is
SRVO-393 being recorded. Other diagnosis data is being recorded. finished.
Reducer iRDiagnostics- Robot Condition Check the mechanical part
SRVO-394 Abnormal(G%d,A%d) Detection Function has detected of the corresponding axis.
This is a notification that Torsion When ID is 0: master and
Compensation failed to execute. This calibrate the robot. When
message is shown by Tool Torsion ID is 1: specify valid
Compensation option etc.When ID is 0: schedule number. When
robot is not mastered or not calibrated ID is 2: specify valid tool
yet. When ID is 1: an invalid schedule number in current
number is specified. When ID is 2: an schedule. When ID is 3 or
TorsionCompException( invalid tool number is specified in 4: in these schedules, start
SRVO-399 ID:%d
CIP Safety comm. error current schedule. When ID is 3 or 4: compensation
Check CIP Safety while TCP is
SRVO-401 %x,%x CIP Safety communication error occurs. connection
Cartesian Position Check function If the robot is actually out
DCS Cart. pos. detected that a model is out of a safe of the safe zone, press
limit(%d,G%d,M%d) zone. The first value : Cartesian Position SHIFT key and RESET key,
SRVO-402 %02x Check No. G : Group number M : User and jog the robot to the
Cartesian Speed Check function
DCS Cart. speed detected over speed. The first value :
SRVO-403 limit(%d,G%d) %02x Cartesian Speed Check No. G : Group Decrease TCP speed.
DCS Joint pos. Joint Position Check function detected If the robot is actually out
limit(%d,G%d,A%d) that an axis is out of a safe zone. The of the safe zone, press
SRVO-404 %02x first value : Joint Position Check No. G : SHIFT key and RESET key,
DCS Joint speed Joint Speed Check function detected
limit(%d,G%d,A%d) over speed. The first value : Joint Speed
SRVO-405 %02xSSO SVOFF input
DCS Check No. G : Group number A : Axis Decrease
Check SafeJoint
I/O speed.
connect
SRVO-406 %x,%x
DCS SSO Fence Open SSO[1:C_SVOFF] is OFF setting.
Check Safe I/O connect
SRVO-407 %x,%x
DCS SSO Ext Emergency SSO[2:C_FENCE] is OFF setting.Safe I/O connect
Check
SRVO-408 StopSSO
DCS %x,%x
Servo SSO[3:C_EXEMG] is OFF setting.Safe I/O connect
Check
SRVO-409 Disconnect %x,%x
DCS SSO NTED input SSO[4:C_SVOFF] is OFF setting.
Check Safe I/O connect
SRVO-410 %x,%x SSO[5:C_NTED] is OFF setting.
SRVO-411 invalid mode
DCS COUNT3 alarm%x,%x Invalid mode. Select the
Check AUTO, T1 alarms
other or T2.
SRVO-412 %x,%x DCS servo on process is stopped. for more information.
Results of Safe I/O process by 2 CPU are Check the connection of
different. This alarm sometimes occurs the safety input signals on
when the safety input signals on the the emergency stop board
DCS CC_SAFEIO alarm emergency stop board and Safe I/O and Safe I/O board. Check
SRVO-413 %x,%x board such as External E-STOP or SFDI the other alarms for more
DCS WORK CRC alarm Check the other alarms
SRVO-414 %x,%x DRAM failure is detected. for more information.
-Selected DCS tool frame number is not
DCS Invalid tool (G%d) defined. -Verify I/O of DCS tool frame is
SRVO-415 %x,%x not set in the selected DCS tool frame Check DCS TCP setting.
DCS Tool All Verify I/O of DCS tool frame are OFF
SRVO-416 mismatch(G%d) %x,%x or two or more Verify I/O are ON for Check Verifiy I/O status.
DCS APSP_C Invalid DCS approach speed check Check DCS approach
SRVO-417 alarm(G%d) %x,%x parameter for Cartesian position check. speed check parameter
DCS APSP_J Invalid DCS approach speed check Check DCS approach
SRVO-418 alarm(G%d,A%d)
PROFIsafe comm.%x,%x parameterSafety
error PROFINET for Joint position check.
communication error speed check
Check PROFINETparameter
Safety
SRVO-419 %x,%x
Safety FL-net comm. occurs.
Safety function by FL-net connection.
Check Safety function by
SRVO-420 error %x,%x communication error occurs. FL-net connection
$DMR_GRP.$MASTER_DONE is not When you enter the
ready to be set to TRUE because mastering data via direct
Jnt phs not Universal Joint phase calibration data is entry, enter Universal
SRVO-421 calibrated(G%d) not set. Joint phase calibration
Equalization was infeasible at this robot If possible, try to change
EQZ Bad robot posture. This message tells you the last the configuration (U/D,
SRVO-429 posture(G:%d) EQ was done with Ghost Run mode. T/B) of the robot
EQZ Not supported Cannot start equalization because this Document the events that
SRVO-430 (G:%s) robot does not. support equalization. led to the error, and
Cannot start equalization for some Document the events that
SRVO-431 EQZ Failed to start (%d) reason. led to the error, and
Equalization is no longer
effective in this motion. If
Equalization was aborted for some you need to try the
SRVO-432 is aborted
EQZ Dir (%d)
not selected reason, HOLD,
Equalization E-STOP
Soft etc. is not
Direction Equalization
Select motion via
Soft Direction
SRVO-433 (G:%d) selected the setup screen.
Equalization is infeasible at this robot
posture. Equalization requires that at If possible, try to change
EQZ Bad robot least one axis among J1, J2 or J3 is the configuration (U/D,
SRVO-434 posture(G:%d) sensitive to the reaction force from the T/B) of the robot.
This alarm indicates an
overrun of the robot
Motion with equalization exceeded the motion. -Check if the
SRVO-435 EQZ Move Limit (G:%d) Robot Move Limit. workpiece exists. - If this
EQZ Stroke Limit Robot reached to its stroke range limit If possible, try to change
SRVO-436 (G:%d,A:%d) during Equalization motion. the configuration (F/N,
Robot wrist axis is near the singular If possible, try to change
SRVO-437 EQZ Singular (G:%d) point. In other words, J5 is near 0. the configuration (U/D,
An instantaneous high speed motion If possible, try to change
EQZ Speed Excess was detected. One possible cause is the configuration (U/D,
SRVO-438 (G:%d) that robot posture is bad (near SRVO- Correct
T/B) of the
therobot.
arguments in
SRVO-440 EQZ Invalid argument
GunMntTyp not Some arguments in KAREL are invalid. the KAREL program
Select Gun Mount Type
SRVO-441 selected
EQZ FUP time out Gun Mount
Robot Type is not
kept moving whenselected. via theifsetup
Equlization is Check screen.
the part is firmly
SRVO-442 (G:%d) about to end. fixed.
1. Check if EQTCHPOS is
Because EQTCHPOS was not called or called before EQ start. If
not successfully processed, destination not called, add call
SRVO-443 EQZ Pos not calculated position of EQ motion is not calculated. EQTCHPOS before EQ
(1): Failed to get destination angle of (1): Document the events
last motion segment before EQ. (2): that led to the error, and
Failed to calculate EQ position by contact your FANUC
SRVO-444 error (%s)
EQZ Can't use with forward
Both kinematics,
Equalization andprobably
Softfloatbecause technical
become Don't use representative.
Equalization
SRVO-445 softfloat (G:%d) enabled. and Softfloat at the same
In Auxiliary axis servo off (Local stop)
function, the safe I/O assigned to the
fence input is OFF when the auxiliary
axis is not servo off condition. The
value displayed in the message shows Set the safe I/O assigned
the No. of local stop that the alarm to the fence input to ON,
DCS LS Fence open occurs. The value is hexadecimal, and or set the auxiliary axis
SRVO-446 %x,%x each bit is corresponded to each item servo to off.
In Auxiliary axis servo off (Local stop) 1: Check the setting of
function, mismatch of STO-OUT and DCS local stop menu. 2:
STO-FB is detected. The value displayed Check the connection
in the message shows the No. of local between emergency stop
stop that the alarm occurs. The value is board and auxiliary axis
DCS LS STO-FB alarm hexadecimal, and each bit is servo amplifier. 3: Replace
SRVO-447 %x,%x corresponded to each item in DCS local the cable between
The monitored signal of safety output is 1. Check the cabling of
not OFF even though OFF pulse is safety output circuit. 2. In
DCS PLSCHK alarm output. The signal name that the case of B-cabinet, replace
SRVO-448 (SFDO%d) trouble is detected is displayed after the optional safety I/O
The monitored signal of safety ouput is 1. Check the cabling of
DCS DOMON alarm different from the output command. safety output circuit. 2. In
SRVO-449 (SFDO%d) The signal name that the trouble is case of B-cabinet, replace
Drvoff circuit fail(G:%d The two drive off inputs are not in the 1. Check the line of the
SRVO-450 A:%d) same status. two drive off inputs. 2.
Internal S-BUS fail(G:%d An error is found in the serial bus Replace the servo
SRVO-451 A:%d) communication in the servo amplifier. amplifier.
ROM data failure(G:%d An error is found in the ROM data in Replace the servo
SRVO-452 A:%d) the servo amplifier. amplifier.
Low volt driver(G:%d Driver supply voltage in the servo Replace the servo
SRVO-453 A:%d)
CPU BUS failure(G:%d amplifier is low.
An error was found in CPU bus data in amplifier.
Replace the servo
SRVO-454 A:%d)watch dog(G:%d
CPU theerror
An amplifier.
occurred in CPU operation in amplifier.the servo
Replace
SRVO-455 A:%d) the amplifier. amplifier.
Ground fault (G:%d An error is found in the motor current Replace the servo
SRVO-456 A:%d) detection data in the servo amplifier. amplifier.
1. Check the ground fault
Ground fault(PS) (G:%d Ground fault occurs in the motor of the motor and the
SRVO-457 A:%d) power line.
The root-mean-square current value motor power
1. Check cable.
whether the2.duty
which is calculated internally by the and applied load exceed
Power Supply (alpha iPS) exceeds the the rating. If so, reduce
maximum permissible value. This alarm the duty or applied load.
is issued to protect the Power Supply 2. Check whether the
(alpha iPS) from damage of thermal robot is pushed or pulled
destruction. Probable cause: 1. by external force. If so,
Overload 2. External force to the robot remove the external force
3. Disconnection of the brake cable 4. to the robot or modify the
Insufficient torque by low voltage of taught point. 3. Check
power supply 5. Brake failure (includes whether the brake
mis-setting of brake number for cable/connector are
auxiliary axis) 6. Auxiliary brake unit connected correctly. 4.
failure for auxiliary axis 7. The Power Measure the supplied
Soft thermal(PS) (G:%d Supply (alpha iPS) failure 8. The servo voltage. Then, check
SRVO-458 A:%d) amplifier failure whether the voltage is
Excess regeneration2%s An error is found in the discharge Replace the 6-axis
SRVO-459 (G:%d A:%d) circuit in the 6-axis amplifier. amplifier.
Illegal parameter%s An error is found in the setting of the 1. Replace the Power
SRVO-460 (G:%d A:%d) parameters in the Power Supply (alpha Supply (alpha iPS). 2.
Hardware error%s An error is found in the circuit in the 1. Replace the Power
SRVO-461 (G:%d A:%d) Power Supply (alpha iPS) or servo Supply (alpha iPS).
This alarm occurs at start-
up and for user to pay
TmpDetachedNode Temporary detached node exists in attention, so this alarm is
SRVO-468 exists in FLSF Safety function by FL-net. defeasible by reset.
Waiting until space gets Special checking space is not clear.
SSPC-001 WARN clear dead lock
PAUSE. Occer Wait for the special checking space to N/A
SSPC-002 G condition The priority of space is invalid Set the priority valid
PAUSE. Space Check function is not compatible Not use AccuPath or
SSPC-003 G AccuPath not allowed with AccuPath. AccuPath is not disable space check
Space Check function is not compatible Remove CTV option or
PAUSE. with Continuous Turn CTV option. The disable space check
SSPC-004 G
PAUSE. CTV option not allowed CTV motion option is not allowed. function
SSPC-005 G Disabled while waiting The space is disabled while waiting. None.
SSPC-006 (G:%d) Space is cleared Space is cleared. Continues to move.
SSPC-007 SYSTE (G:%d) Miss Space NUM Commom space is 0. Select a common space.
SSPC-011 M APDT error
Invalid %x (%s:%d
element
SSPC-012 SERVO %d)
Invalid hand num (G:%d
SSPC-013 SERVO UT:%d)
Common frame setting
SSPC-014 SERVO (G:%d)
SSPC-015 SERVO Not calibrated
Invalid (G:%d)
comb type (C:%d
SSPC-016 SERVO %s)
Invalid comb index
SSPC-017 SERVO (C:%d
APDT is%s)
not supported
SSPC-018 SERVO (G:%d)
SSPC-019 SERVO (G:%d) is closeobj
Invalid fixture to target
SSPC-020 SERVO (F:%d)
SSPC-021 SERVO Too many settings
You can reset the alarm
with SHIFT+RESET and can
jog the robot to the out of
SSPC-101 SERVO (G:%d) is close to target Interaction is detected. the interacted area. This
PAUSE. (G:%d) is close to jog the robot to the out of
SSPC-102 G target(qstop) Interaction is detected. the interacted area. This
PAUSE. jog the robot to the out of
SSPC-103 G
SYSTE (G:%d) is near to target Interaction is detected. the interacted
Please area. This
call customer
SSPC-104 M APDT error %x Internal error. service. And report %x.
Reduce the number of
SSPC-105 SERVO Too many settings APDT setting is too many. interaction element or
Failed to get dist Reduce the number of
SSPC-106 SERVO (%d,C:%d)
Invalid comb type Faied
The model type in combination setting interaction
to get distance Confirm theelement or in
model type
SSPC-111 SERVO (ST,C:%d,%s) screen is invalid. the combination setting.
Invalid comb The index number in combination Confirm the index number
SSPC-112 SERVO index(ST,C:%d,%s) setting screen is invalid. in the combination
APDT isn't supported The group number specified in Confirm the index number
SSPC-113 SERVO (ST,G:%d)
Not calibrated combination setting is invalid. in the combination
Perform the calibration
SSPC-114 SERVO (ST,G:%d)
Invalid utool number The group is not calibrated. for the group.
Confirm current tool
SSPC-115 SERVO (ST,G:%d) Invalid tool number number
Invalid hand The hand number related to the Confirm the hand
SSPC-116 SERVO num(ST,G:%d,UT:%d) current tool number is invalid. number.
Common frame setting There is no calibration data for the Perform the calibration
SSPC-117 SERVO (ST,G:%d) group. between the group and
Invalid element Check the link type and
SSPC-118 SERVO (ST,%s:%d,%d) There is an invalid model elemnt. link number of the model
Can't get elem Check the link type and
SSPC-119 SERVO pos(ST,G:%d,%d) Failed to get element position link number of the model
Invalid fixture obj The taught group number of the fixture Confirm the taught gourp
SSPC-120 SERVO
PAUSE. (ST,F:%d)
Invalid comb type elements
The modelistype
invalid. number of
in combination setting Confirm thethe fixture
model type in
SSPC-131 G (WT,C:%d,%s) screen is invalid. the combination setting.
PAUSE. Invalid comb The index number in combination Confirm the index number
SSPC-132 G index(WT,C:%d,%s) setting screen is invalid. in the combination
PAUSE. APDT isn't supported The group number specified in Confirm the index number
SSPC-133 G
PAUSE. (WT,G:%d)
Not calibrated combination setting is invalid. in the combination
Perform the calibration
SSPC-134 G
PAUSE. (WT,G:%d)
Invalid utool number The group is not calibrated. for the group.
Confirm current tool
SSPC-135 G (WT,G:%d) Invalid tool number number
PAUSE. Invalid hand The hand number related to the Confirm the hand
SSPC-136 G num(WT,G:%d,UT:%d) current tool number is invalid. number.
PAUSE. Common frame setting There is no calibration data for the Perform the calibration
SSPC-137 G (WT,G:%d) group. between the group and
PAUSE. Invalid element Check the link type and
SSPC-138 G (WT,%s:%d,%d) There is an invalid model elemnt. link number of the model
PAUSE. Can't get elem Check the link type and
SSPC-139 G pos(WT,G:%d,%d) Failed to get element position link number of the model
PAUSE. Invalid fixture obj The taught group number of the fixture Confirm the taught gourp
SSPC-140 G (WT,F:%d) elements is invalid. number of the fixture
App_STOP (ST,C:%d) is This combination is originally disabled If you want to use this
SSPC-151 WARN disabled on setup screen. one,enable this
App_STOP (ST,C:%d) is This combination is originally disabled Enable this combination
SSPC-152 WARN disabled on setup screen. on setup screen.
PAUSE. (WT,C:%d) is enabled by This combination is already enabled by Disable this combination
SSPC-153 G other another program. first.
PAUSE. (ST,C:%d) is disabled by another program disabled this Enable this combination
SSPC-154 G
PAUSE. other
Invalid host name condition.
Specified condition has invalid host by the program that use
SSPC-155 G
PAUSE. (ST,C:%d)
Invalid host name name. condition has invalid host
Specified Input correct host name.
SSPC-156 G
PAUSE. (WT,C:%d)
Intrupt signal name.
Approach Input correct
wait intruput signal is turned
Please turn offhost name.
intruput
SSPC-157 G (WT,C:%d)
PAUSE. App_WAIT timeout to ON signal.
Restart again if opponent
SSPC-158 G (WT,C:%d) Approach wait limit has passed. is far away enough.
Approach wait cannot be used with: Don't use approach wait
PAUSE. App_WAIT can't be Tracking motion of slave of with these types of
SSPC-159 G used(WT,G:%d) simultaneous robot link Continuous motion.
App_STOP is If you want to enable this
SSPC-160 WARN TMP_DISed(ST,C:%d) IASTOP[*] = TMP_DIS is executed. combination, please
App_STOP is enabled Resume from different line when a If you want to disable this
SSPC-161 WARN (ST,C:%d) program is paused. combination, enable it by
App_WAIT is enabled If you don't want to use
SSPC-162 WARN (WT,C:%d) IAWAIT[*] = ENABLE is executed. this condition, please
App_WAIT is disabled Resume from different line when a If you want to use this
SSPC-163 WARN (WT,C:%d) program is paused. condition, enable it by
(%s,%d) TMP_disabled Resume from different line when a If you want to use this
SSPC-164 WARN (ST,C:%d) program is paused. condition, enable it by
(%s,%d) enabled Resume from different line when a If you want to use this
SSPC-165 WARN (ST,C:%d) program is paused. condition, enable it by
(%s,%d) enabled Resume from different line when a If you want to use this
(%s,%d) disabled Resume from different line when a If you want to use this
PAUSE. (%s,%d) invalid group The rate value specified to Specify the correct rate
SSPC-168 G
PAUSE. number
(%s,%d) invalid rate Approach_RATE[] instruction is invalid. value.
Confirm hostname, IP
SSPC-169 G value Comm init error address hostname, IP
Confirm
SSPC-181 WARN Comm init error %d %s Comm init error address
Confirm hostname, IP
SSPC-182 SERVO Invalid hostname (%s) Invalid hostname address hostname and IP
Confirm
SSPC-183 SERVO Number
Invalid address
of host(%s)
exceed Invalid IP address address
SSPC-184 SERVO limit
Number of element Specified host is too many Reduce target host
SSPC-185 SERVO Invalid
exceed element
limit Enabled element is too many Reduce enabled element
SSPC-186 SERVO (%s,%d,%d)
Receive invalid data %d Invalid element element
Confirm target contents
host's
SSPC-187 WARN %s Receive invalid data setup
Confirm own element
SSPC-188 SERVO Timeout
Invalid data for send %d
element Invalid data exists to send setup
Confirm target host is
SSPC-189 SERVO
PAUSE. (%s,%d,%d) Target element is too old information working
Check target host and
SSPC-190 G No communication
Target elem not (%s) Target is OFF or comm stopped communication
Confirm lineand
own setup
SSPC-191 SERVO Target
PAUSE. exist(ST,C:%d,%s)
elem not Specified element does not exist target setup
Confirm own setup and
SSPC-192 G exist(PA,C:%d,%s)
IAL detect overload Specified element does not exist target setup
SSPC-193 WARN (%d)
IASV Buffer Overrun APDT task is overload Increase ITP
SSPC-194 (%d)
Interference Internal error Report to FANUC
SSPC-201 WARN Detected(G:%d)
PAUSE. Obstacle Abort the program and
SSPC-202 G Detected(G:%d)
Check combination type Collision Detected for the group jog awaycheck
Change
SSPC-203 SERVO mismatch Check combination type mismatch combination type
Two points not form a Two points not form a line Remed:
SSPC-204 SERVO line Move the two points apart N/A
Three points not form a Three points not form a plane Remed:
SSPC-205 SERVO plane Move the three points apart N/A
Four points not form a Four points not form a box Remed:
SSPC-206 SERVO box Move the four points apart N/A
Check combination not Check combination not supported
SSPC-207 SERVO supported
Unit vector formation Remed: Check
Unit vector the check
formation combinations
error Remed: N/A
SSPC-208 WARN error Internal error N/A
Robot goes into obstacle for more than
SSPC-209 SERVO Robot
Comb check I/O Setting 3 ITPs before resulting the priority issue
in too far(G:%d) N/A
SSPC-210 SERVO invalid Collision Detected for the group jog away
Obstacle A collision has been detected for the Abort the program and
SSPC-211 STOP Detected(G:%d^2)
Invalid Comb Pair group. jog thea robot
Enter away from
valid Combination
SSPC-212 Num(%d) Invalid Combination Pair number. Pair number.
Invalid Critical Zone Enter a valid Critical Zone
SSPC-213 #(%d) Invalid Critical Zone number. number. A valid Critical
Invalid Position Register number, or Enter a valid Position
Invalid Position invalid Position Register content. OnlyRegister number, and a
SSPC-214 Register(%d)
Invalid AutoZone Sched XYZWPR
An invalidtype in PR isSchedule
AutoZone supported, Joint
valid
EnterPosition
number Register
a valid AutoZone
SSPC-215 #(%d) was specified. Schedule id.
Too many AutoZone Too many autozone buffers between Reduce the number of
SSPC-216 buffers AutoZone Start and AutoZone End. motion lines between
Disable the combination
(G:%d) Outside Virtual Robot is outside the boundary of the pair temporarily, jog the
SSPC-217 Sphere sphere virtual fence. robot back inside the
(G:%d) Outside Vir Robot is outside the boundary of the pair temporarily, jog the
SSPC-218 Cylinder cylinder virtual fence. robot back inside the
(G:%d) Outside Vir Inf Robot is outside the boundary of the pair temporarily, jog the
SSPC-219 Plane infinite plane virtual fence. robot back inside the
(G:%d) Outside Vir Fin Robot is outside the boundary of the pair temporarily, jog the
SSPC-220 Plane finite plane virtual fence. robot back inside the
(G:%d) Outside Virtual Robot is outside the boundary of the pair temporarily, jog the
SSPC-221 Box box virtual fence. robot back inside the box
The device id provided for Interference Confirm that both my
SSPC-223 Invalid ICMA Dev Id(%d) Check Karel built-in routine is invalid. device id and other device
SSPC-224 (G:%d) is close to :%s Interaction is detected. jog the robot out of the
Only one robot is allowed
(G:%d) Both robots are to stay inside the zone,
SSPC-225 inside Both robots are inside the critical zone. move another robot to
The robot is configured to be bypassed This is a warning message.
SSPC-226 %s %d robot bypassed in MASH setup menu. No action is required if
No IIC DSP is available. Dedicated DSP is
SSPC-240 DSP not available required for IIC. Add a DSP
Record to and
error support IIC.
report
SVGN-001 WARN
PAUSE. Serious Internal error Internal Servo Gun error to hotline.
SVGN-002 G No sysvar pointer This is an internal system error. to hotline.
PAUSE. Record error and report
SVGN-003 G No global variables This is an internal system error. to hotline.
Check amount of memory
PAUSE. Unable to Allocate A failure occured while allocating being used by the system.
SVGN-004 G Memory memory. Perform a cold start on
PAUSE. This SPOT instruction format is not Reteach this instruction
SVGN-005 G Wrong TPP inst. format correct. This SPOT instruction is not with current
PAUSE. Another TASK used this Another TPP specified this equipment
SVGN-006 G equip. and now executing or paused. Force abort another TPP.
error and continue the
program. If this error
continues to occur,
Pre-execution has some trouble and perform a cold start by
PAUSE. system pauses the program execution turning off the robot, then
SVGN-007 G Pre execution failed for safety. while pressing SHIFT and
PAUSE. Instruction syntax error. This Reteach the instruction.
SVGN-008 G Syntax error instruction is for air gun spot. Reteach servo gun SPOT
PAUSE. Motion Group config. Different motion group assigned Check the motion group
SVGN-009 G mismatch motion group to robot TCP side tip and of this program or robot
PAUSE. Check the servo gun
SVGN-010 G Invalid SG group config. Invalid servo gun group number. group motion of servo
Incremental, offset or tool offset Reteach this SPOT
PAUSE. Can not execute instructions can not execute with servo instruction to another line
SVGN-011 G instruction(s). gun SPOT instruction at the same stand alone.
PAUSE. The index value is invalid. The register
SVGN-012 G
PAUSE. Invalid value for index index value is invalid. Check the index value.
SVGN-013 G
PAUSE. Pressure exceeds limit Specified pressure is too high. Lower
Recordpressure.
error and report
SVGN-014 G
PAUSE. Associate
Setup TID not found
Configuration This is servo
Some an internal system error.data are Check
gun configulation to hotline.
servo gun
SVGN-015 G error invalid. configulation data.
PAUSE. Specified pressure too Specified pressure value is too low. Higher pressure. Lower
SVGN-016 G
PAUSE. low pressure
Invalid Pressure coefficient-B value is bigger Pressurepressure
Change coefficient-B.
SVGN-017 G coefficient Invalid pressure coefficient-A value. coefficient-A value from
Check the max motor
PAUSE. torque in servo gun setup
SVGN-018 G Illegal torque limit value Illegal torque limit value is specified. menu. the
Check Check the of
status specified
tip
SVGN-019 WARN
PAUSE. Pressure shortage Acutal pressure is shortage. contack.
Check the status of tip
SVGN-020 G
PAUSE. Pressure shortage
Uninitialized BU Acutal pressure is shortage.
Servo gun condition BU is not contack.
Add a servo gun condition
SVGN-021 G condition initialized. instruction.
PAUSE. Uninitialized Pres. Pressure condition is not initialized. Add a servo gun condition
SVGN-022 G
PAUSE. condition
Incomplete Pressure Pressure condition value is invalid. instruction.
Please calibrate pressure
SVGN-023 G
PAUSE. calibration Wear Down
Incomplete Incomplete pressure calibration. in Pressure
Please Calibration
calibrate in Wear
SVGN-024 G
PAUSE. calibration
Illegal BU condition Incomplete
Invalid Wear Down
BU condition calibration.
number is Down Calibration
Specify existing BUmenu.
SVGN-025 G
PAUSE. number
Illegal P condition specified. condition number.
Specify existing P
SVGN-026 G
PAUSE. number element
Untaught Invalid P condition number is specified. condition number.
SVGN-027 G
PAUSE. encountered This instruction is not taught completly. Teach
Changethis instruction.
position type to
SVGN-028 G Pos. type is JOINT Position type is JOINT. XYZWPR.
PAUSE. Over max motor torque The convert value from specified Check the specied
SVGN-029 G value pressure value to torque limit value pressure value. Check the
PAUSE. Check the specied
SVGN-030 G Tip Stick detection Tip stick detection DI is ON pressure value. Check the
PAUSE. When tear off function is executing, Restart program after tear
SVGN-031 G Tear Off is executing program cannot be started. off function finished.
PAUSE. Tip increased The tip wear down value of gun side Some chips may stick to
SVGN-032 G error(Gun) exceeds the increased error. the gun side tip. Please
PAUSE. Tip increased The tip wear down value of robot side Some chips may stick to
SVGN-033 G
PAUSE. error(Robot)
Excessive robot tip exceeds the increased error. the
Checkrobot
the side tip.ofPlease
status tip
SVGN-034 G difference. Acutal pressure is over. contack.
PAUSE. Pressure enable time Pressure enable signal has not input Check the reason of
SVGN-035 G out after time out. pressure enable signal off.
Check the reason of comp
PAUSE. Comp confirmation Comp confiramation signal has not confirmation signal off. Or
SVGN-036 G
PAUSE. time out
Illegal pressure enable input after time out. Fix thepressure
Setup value of enable
time
SVGN-037 G
PAUSE. signal
Illegal comp Pressure enable signal
Comp confirmation number
signal is illegal.
number is signal in SPOT I/O.
Setup comp confirmation
SVGN-038 G confirmation signal illegal. signal in SPOT I/O.
Thickness out of The measured thickness deviates more Check the part or re-enter
SVGN-039 WARN tolerance than the specified tolerance. the part thickness.
PAUSE. Thickness out of The measured thickness deviates more Check the part or re-enter
SVGN-040 G tolerance than the specified tolerance. the part thickness.
No more available The number of $SGGUN is less than the Please increase
SVGN-041 WARN memory(PERM) total axis number of servo gun group. $SGSYSCFG.$M_GUN_NU
The number of $SGGUN is less than the Increase
SVGN-042 WARN Lack of $SGGUN total axis number of the servo gun $SGSYSCFG.$M_GUN_NU
None. This is a notice to
SVGN-043 WARN AutoTune
AutoTuning Started.
Successfully Servotuning
Auto Gun autotuning has been started.
has been completed log thecontroller
Cycle event. power in
SVGN-044 WARN Complete successfully. order to use servo gun.
Restart Auto tuning on
SVGN-045 WARN AutoTuning Failed. Auto Tuning Could not be completed. the tuning
Clear menu, and try
ALL FAULTS
SVGN-046 WARN FAULTS must
Step mode be reset.
must be A FAULT exists. start
Disable STEPagain.
tuning mode, and
SVGN-047 WARN disabled. STEP mode is enabled. start tuning again.
Machine lock must be Disable Machine lock from
SVGN-048 WARN disabled. Machine Lock is enabled for servo gun. the
ClearTEST
the CYCLE
HOLD,Menu,
and start
SVGN-049 WARN Hold must be cleared. Hold is active. tuning again.
Autuning: Re-power Re-power is required to make some Cycle power before
SVGN-050 required parameter changes effective. proceeding.
Backup stroke is not Backup stroke index for manual Set the stroke in the
SVGN-051 WARN selected. operation is not selected. backup stroke setup
The motion group number of the user Change the motion group
Motion group program for manual pressure or number of the program to
SVGN-052 WARN mismatch. manaul backup is not matched to the match the Servo Gun
Backup stroke is not Specified backup stroke index is not set Set the valid backup
SVGN-053 WARN
PAUSE. set.
$EQNUM is invalid the valid stroke value. stroke
Set theto theequipment
valid specified
SVGN-054 G number. $EQNUM is not use in the system. number to $EQNUM.
PAUSE. $EQNUM is not Servo The equipment specified by $EQNUM is Set the equipment
SVGN-055 G Gun. not assigned to the Servo Gun number which is assigned
PAUSE. $GUNNUN is invalid Specified number is not valid for $GUNNUM can be set
SVGN-056 G
PAUSE. number.
Tip $GUNNUM.
Wear Down Cal. is The Tip Wear Down Calibration is not only 1 or
Please 2 which
perform is Tip
the
SVGN-057 G INCOMP. completed. Wear Down Calibraiton.
PAUSE. The tool frame number or user frame Change the frame number
SVGN-058 G UT or UF is different. number is different from the standard to same number of
PAUSE. Cannot read specified System cannot read the position Check the number of
SVGN-059 G PR[]. register which is specified by $PRINDEX. $PRINDEX.
Pressure program is not The pressure program name is not set Set correct program name
SVGN-060 WARN set. correctly. in manual operation setup
Backup program is not The backup program name is not set Set correct program name
SVGN-061 WARN set. correctly. in manual operation setup
Pressure data is not Pressure data index for manual Set the pressure data in
SVGN-062 WARN selected. operation is not selected. the pressure data setup
Specified pressure data index is not set Set the valid pressure data
SVGN-063 WARN Pressure data is not
Manual Weld Verif. set. the validWeld
Manual pressure data. feature was
Verification to
Justthe specified pressure
a notification, no
SVGN-064 Enabled Weld Verif.
Manual enabled.Weld Verification feature was
Manual action
Just necessary. no
a notification,
SVGN-065 Disabled disabled. action necessary.
Manual Weld Verif. Manual Weld Verification feature was Just a notification, to let
SVGN-066 Activated activated. user know he is in this
Manual Weld Verif. De- Manual Weld Verification feature was Just a notification, to let
SVGN-067 Activated activated. user know he is in this
Resume the program to re-
Could not load program The teach pendant program could not attempt the load. If the
SVGN-068 WARN %s be loaded. See cause code for reason. load is successful, then
Check the master position
The actual position of the gun during and close stroke limit for
pressuring (SPOT or PRESS_MOTN) is the gun. If these values
approaching the gun's close limit: the are incorrect, then update
distance between the gun tip (position) them. If these values are
Pressure position is and the close limit < correct, then install new
SVGN-069 near close limit. $SGSYSCFG.$CLSLMWRNTOL. tips OR, reduce the value
PAUSE. Gun Change is This equipment is set to Air Gun. Or the Set the equipment type to
SVGN-070 L DISABLED. gun change setup is disabled. Servo Gun in initial setup
PAUSE. Machine lock is Machine lock for robot axes is enabled
SVGN-071 L
PAUSE. ENABLE.
Illegal assignment of at gun attach instruction. Release machine
Confirm Gun numberlock.
SVGN-072 L gun axis. Gun number assignment are wrong . assignment.
PAUSE. Gun not detatched Gun is not detached. Some AXISORDER GUN ATTACH instruction
SVGN-073 L (AXISORDER). are not 0. can be executed only
PAUSE. Gun is not detached. Gun attach input GUN ATTACH instruction
SVGN-074 L Gun not detatched. signal is OFF. can be executed only
PAUSE. Gun is not attached. Gun attach input GUN DETACH instruction
SVGN-075 L Gun not attached. signal is ON. can be executed only
Another program is executing GUN Wait until another
PAUSE. Another process is ATTACH or GUN DETACH instruction. program end GUN
SVGN-076 L
PAUSE. executing.
Gun identify signal is $CHG_PHASE is not 0 at executing the Confirm
ATTACH/DETACH
the setting for
SVGN-077 L
PAUSE. OFF. Gun identify signal is OFF. Gun identify
Confirm signal. for
the setting
SVGN-078 L Gun set signal is OFF. Gun set signal is OFF. Gun set signal.
PAUSE. GUN ATTACH or GUN DETACH Do COLD START the
SVGN-079 L Gun change canceled. instruction is canceled while executing system.
PAUSE. GUN ATTACH or GUN DETACH Do COLD START the
SVGN-080 L Gun change timeout. instruction become timeout while system.
SYSTE Gun mastering data is Mastering data of the gun is lost by a Do COLD START the
SVGN-081 M
PAUSE. lost. pause while mastering.
Gun mastering is failed by a pause system.
ContinueThen master the
to retry
SVGN-082 L
PAUSE. Gun mastering is failed. GUN
whileATTACH
mastering.
instruction failed. Please mastering.
SVGN-083 L
PAUSE. GUN ATTACH is failed. GUNsee cause code.
DETACH instruction failed. Please Please see cause code.
SVGN-084 L GUN DETACH is failed. see cause code. Please see cause code.
PAUSE. Robot not The mastering of servo gun axis has not Please perform the
SVGN-085 L mastered(Gun axis). been performed yet. System variable mastering of the servo
PAUSE. Robot not The calibration of servo gun axis has Please calibrate the servo
SVGN-086 L calibrated(Gun axis). not been performed yet. System gun axis.
PAUSE. Ref pos not set(Gun Reference position has not been set Quick mastering may not
SVGN-087 L axis). when quick mastering. be possible. Fixture or
PAUSE. Another gun is The another gun which is different from Verify the gun number of
SVGN-088 L attached. the gun number specified by GUN GUN DETACH instruciton.
PAUSE. Calibrate motion is While the calibrate motion, the detect Verify the detect
SVGN-089 L failed. condition was not triggered. condition in the gun
PAUSE. The PR[] index for the calibrate motion Please set PR[] index for
SVGN-090 L PR[] index is not set. is not set. the calibrate motion in
PAUSE. The Touch torque for the calibrate Please set Touch torque
SVGN-091 L Touch torque is not set. motion is not set. for the calibrate motion in
PAUSE. The Detect signal for the calibrate Please set Detect signal
SVGN-092 L Detect signal is not set. motion is not set. for the calibrate motion in
PAUSE. At the Gun Zero Master[] instruction, After servo gun axis stops,
SVGN-093 L Gun does not stop. Servo gun axis does not stop. execute the Gun Zero
PAUSE. At the Gun exhange[] instruction, the Make sure that the each
SVGN-094 L
PAUSE.GUNtype
Gun EXCHANGE
is not failed Opposable
new gun could gun not
typebeis activated.
required for servogun
Set hasas
gun type valid
SVGN-095 LPAUSE.
opposable. target gun.
Cannot do this operation while Gun opposable, if appropriate.
SVGN-096 L Gun closedown
Tip wear is disabled. AClose is disabled.
misdetection occurred during tip Enable Gun
Remove theClose.
cause and
SVGN-097 PAUSEmisdetection. wear measurement. measure the tip again.
Invalid inform Inform signal of maximum wear down Set WHAT TO? a valid
SVGN-098 PAUSE signal(Gun). for movable tip is invalid. PLEASE number to Inform
Invalid inform The inform signal of the maximum wear Set a valid number to
SVGN-099 PAUSE signal(Robot). down for the fixed
The specified tip number
register is invalid.is out of Inform Signal(Robot).
Set a register index > 0
SVGN-100 PAUSE Invalid position
register number.
reg range.
The specified position register number anda<valid
Set max position
register
SVGN-101 PAUSE number. is out of range. register number.
The increased error limit for the Specify a value > 0.0 (5.0
Increased err. not movable tip is not set is a typical setting) for mis-
SVGN-102 WARN set(Gun). correctly(0.0mm). A value of 0.0 means detect tolerance, on the
Increased err. not The increased error limit for the fixed Set the increased error to
SVGN-103 WARN set(Robot). tip is not set. a value that is greater
Excessive load An excessive load has been detected.
SVGN-104 PAUSE detected.
Failed to reset pulse The gun axis mastering might be Master
Reset thethepulse
gun.coder
SVGN-105 PAUSE coder. The pulse coder alarm was not reset. alarm again.
Execute tw_setup, or the
appropriate user program
that calls twkinit. Please
SVGN-106 PAUSE Tip wear no
uninitialized.
load Tip wear
The measurement
load threshold is uninitialized.
for tip wear referato
Run theprogram
user Servo Gun
SVGN-107 PAUSE threshold. measurement is not set. calling TW0THOLD.
Tip wear no standard Standard pulse is not measured for tip Run a user program
SVGN-108 PAUSE pulse. wear measurement. calling TW1MTCLB.
Tip wear no standard The standard gun opening was not Run a user program
SVGN-109 PAUSE opening. measured for tip wear measurement. calling TW1MTFIX.
Tip wear no detect DI The digital input (DI) index for Set the correct digital
SVGN-110 PAUSE index. detecting the movable tip is not set. inptu (DI) index.
The gun failed to touch the fixture for Confirm gun master
SVGN-111 PAUSE Failed to touch fixture. measurement by the movable tip. position and fixture.
Incomplete Servo Execute autotuning,
SVGN-112 PAUSE tuning. Servo tuning is incomplete. either by using one of the
Tip wear measurement was started Confirm the gun
SVGN-113 PAUSE Gun must be open. from a gun closed position. mastering was done
Tip wear Misdetection occurred during tip wear Remove the cause, and
SVGN-114 PAUSE misdetection.(FIX). measurement. perform tip wear
SVGN-115 PAUSE MP detection failed. The Magnetic Phase detection failed. led to the error, and
Magnetic Phase detection is Change the calibrating
MP detection unavailable with the current calibration motion type (to 7 or 8) on
SVGN-116 PAUSE unavailable. motion type. the Gun change SETUP
Ref pos auto-setup The Gun closing motion to set the Confirm that the Touch
SVGN-117 PAUSE failed. reference position failed. torque(%) on the Gun
Max wear exceeeded The maximum tip wear amount has Replace the gun tip or re-
SVGN-118 WARN (Gun Tip). been exceeded on the gun tip. run tip wear setup.
Max wear exceeded The maximum tip wear amount has Replace the robot tip or re-
SVGN-119 WARN (Rbt Tip). been exceeded on the robot tip. run tip wear setup.
See the cause code to
Skipped over-torque The overtorque limit was not updated identify the reason for the
SVGN-120 WARN limit update: Gun%d. due to an invalid parameter. update failure. Correct the
Adjust the torque limit
and/or sensitivity. The
torque limit
Illegal disturbance The specified threshold was < minimum ($sggun#.$cd.$prs_lim_tr
SVGN-121 WARN threshold. torque or > max available torque. q) is adjusted via the
The specified force cannot be used Re-perform force
SVGN-122 STOP Force is not invertible. because it does not lie on the calibration or reduce the
This is a warning to notify
Gun ovrtrq protection Overtorque protection has been the operator that
SVGN-123 WARN disabled. disabled. overtorque protection is
Over-torque limit must The overtorque limit is less than gun Increase the torque limit
SVGN-124 WARN be > floor. friction (2*sbr[].$param[183]) OR by increasing the pressure
Over-torque limit must The overtorque limit is greater than Decrease the torque limit
SVGN-125 WARN be < ceil. 7282 or $sbr[].$param[27]. by decreasing the
Overtorque protection is enabled, but Disable then re-enable
one or more of the parameters overtorque protection in
Servo parameters responsible for limiting torque exceed order to re-write servo
SVGN-126 STOP exceed overtorq limit. the overtorque limit. parameters. Alternatively,
A timeout has occurred while waiting Check communication
for an acknowlegement of new between the servo and
DSP overtorque update overtorque parameters. The DSP the host. Toggle the
SVGN-127 STOP timeout. update could not be confirmed. overtorque protect enable
Invalid thickness value A string parameter or a value < 0.0 was Re-enter a parameter
SVGN-128 STOP specified. specified for the THK_VAL (thickness value >= 0.0 into the
Invalid thickness A string parameter or a value < 0.0 was Re-enter a parameter
SVGN-129 STOP tolerance specified. specified for the THK_TOL (thickness value >= 0.0 into the
Invalid thickness A string parameter or a value other Re-enter a parameter
SVGN-130 STOP severity specified. than 1 or 2 was specified for the value of 1 or 2 into the
A string parameter or a value other This parameter is optional
Invalid gun index than 1, 2, or 3 was specified for gun but if it is specified, set it
SVGN-131 STOP specified. index in a THK_ macro. as follows: 1: Gun.A only
An encoder scale value of 0.0 was Re-enter the gear ratio on
SVGN-133 STOP Encoder scale is NULL. detected. the NOBOT Maintenance
Deflection calibration was never Go to the servogun tune
Deflection calibration is performed or did not complete screen and re-execute
SVGN-134 STOP incomplete. successfully. deflection calibration OR,
Torque% for a calibration point is either Go to the servogun tune
Invalid deflection cal less than 0.0 or smaller than a previous screen and re-execute
SVGN-135 STOP torque point. torque% (decreasing). deflection calibration OR
The deflection distance for a calibration Go to the servogun tune
point is either less than 0.0, or smaller screen and re-execute
Invalid deflection cal than a previous deflection distance deflection calibration. If
SVGN-136 STOP deflect point. (decreasing). the error still occurs, re-
Display the system
variable screen and type a
value of 2, 3, or 4 into
Invalid number of The number of deflection calibration $sgthkset#.$num_cal_pts,
SVGN-137 STOP deflection cal pts. points is less than 2 or greater than 4. where # is the gun
The tipwear value < 0.0 or > 1.0. This odify the teach pendant
SVGN-138 STOP Invalid tipwear ratio. error only applies to fixtureless wear program so that a wear
Could not read tip stick Tip stick detect input could not be read, Check the I/O
SVGN-139 STOP detect input. due to an I/O error. mapping/configuration
Uninitialized start The specified start distance number is Specify a start distance
SVGN-140 STOP distance number. not valid. number >= 1 and <=
Uninitialized end The specified end distance number is Specify an end distance
SVGN-141 STOP distance number. not valid. number >= 1 and <=
The decel rate option setting is
incompatible with the speed calibration
specification. $sgsyscfg.$change_spd
indicates that the robot should Reset the bit
decelerate by a % during move to the corresponding to 0x8 in
SVGN-142 STOP Illegal decel option. pressure position. However, absolute $sgsyscfg.$change_spd.
The Minimum speed Re-perform force
($sggun#.$setup.$prs_spd_min) cannot calibration to update
Min press speed > max be larger than the maximum speed $sggun#.$setup.$prs_spd
SVGN-143 STOP press speed. ($sggun#.$setup.$prs_spd_max). _min automatically
Re-perform force
calibration to update
Min press speed < The Minimum speed must be greater $sggun#.$setup.$prs_spd
SVGN-144 STOP 1mm/sec. than 1mm/sec. _min automatically
Joint velocity limit must be >= 1, for Go to the maintenance
Joint velocity limit too mm/sec pressure calibration speed menu and set the speed
SVGN-146 STOP low. specification. or manually set
Internal start position is more open
Sync/speed min than the user-specified start distance. Increase the start
SVGN-147 WARN distance =%s. This means that the sync position and distance.
The routine name corresponding to the
Can't identify routine standalone instruction cannot be See remedy for cause
SVGN-148 WARN name. identified. Refer to the cause code for error.
CP mode is not enabled, but Enable CP mode
synchronize move to pressure position ($cpcfg.$cp_enable=TRUE
is enabled AND/OR linear distance is ) OR disable synchronize
SVGN-149 STOP CP enable is required. enabled. move to pressure position
Linear distance function is enabled, but Enable synchronize move
Synchronization enable synchronize move to pressure is not to pressure
SVGN-150 STOP is required. enabled. position($sgsyscfg.$sync_
Cannot add file to The Servogun sysvar file(s) could not be Document the events that
SVGN-151 WARN backup/restore list. added to the backup/restore list. led to the error and call
Check the present value
of
The Digital Output assigned to notify of $sggun#.$setup.$tipincioi
Invalid increase increased error on the Gun Tip is dx (on the system variable
SVGN-152 signal(Gun). invalid. screen). Change this value
Check the present value
of
The Digital Output assigned to notify of $sggun#.$setup.$rbtincioi
Invalid increase increased error on the Robot Tip is dx (on the system variable
SVGN-153 signal(Robot). invalid. screen). Change this value
Tipwear update Tip wear update did not complete, due Correct the condition
SVGN-154 cancelled. to cancel or gun close error. Refer to identified in the cause
Pressure shortage occurred during zero Correct the issue that
Cancel or ffr was calibration and “Cancel tip wear update caused the pressure
SVGN-155 selected. and exit” or “Initiate fast fault shortage, then run tip
Gun close reference position was NOT
Gun close NOT recorded (for tip wear gun close check). Run tip wear update
SVGN-156 detected. PRESS_MOTN[]
Zero calibrationinstruction did not
was not performed again.
1. If gun position is
because gun is not closed (gun is too changing after
far from close position). Note1: the PRESS_MOTN[] (inverted
condition for SVGN-157 detection is: |a- gun that drops/drifts for
b| > c, where: a = Gun position after example) then correct this
PRESS_MOTN[] instruction executes in condition so zero
zero calibration program (TWZRCLB2). calibration is accurate. 2.
b = Gun position when Gun Zero Increase gcls_err_tol, if
Master[] instruction executes in zero gcls_err_tol is too small.
calibration program(TWZRCLB2). c = 3. Perform tip wear
Gun close error tolerance (default: update again. 4. Disable
2.0mm). Note2: Items a-b and c are gun close error check by
karel variables in program: TWKINIT. a- setting
Gun not closed at zero b: Posdiff is stored in [TWKINIT]gcls_err_enb =
SVGN-157 cal process end. [TWKINIT]gcls_posdif[ eq# ] c: Close FALSE.
Pressure margin Pressure margin conversion for Refer to cause code's
SVGN-159 conversion error. touchup process failed. See cause code remedy.
A torque calibration point is non-
Invalid calibration increasing or > torque_max. Note: this Perform the force
SVGN-160 STOP point: bad torque. error only appplies to piece-wise force calibration again.
Invalid calibration A speed calibration point is <= 0.0% or Perform the force
SVGN-161 STOP point: bad speed. > 100%. Note: this error only appplies calibration again.
A pressure (force) calibration point is
Invalid calibration <= 0.0 or non-increasing. Note: this Perform the force
SVGN-162 STOP point: bad pressure error only appplies to piece-wise force calibration again.
Change the setting to one
of the following settings,
The calibration model specification reperform calibration if
Invalid calibration ($sgsyscfg.$cal_model) is not necessary: 3: Single linear
SVGN-163 STOP model setting. supported. segment force and speed
Change setting to one of
the following settings, and
reperform calibration if
necessary:
$sgsyscfg.$cal_model = 3
and
Force to speed conversion specification $sgsyscfg.$frc2spd_cnv =
Invalid force/speed ($sgsyscfg.$frc2spd_cnv) is not 0: Single linear segment,
SVGN-164 STOP convert setting. supported. JNT%.
The open distance condition for Go to the Spot Equipment
equalization pressure trigger was not SETUP screen, and
met before start of motion to pressure decrease the open
Gun opened < equalizer position, for the next spot. Note that distance after the
SVGN-165 WARN trigger distance. the equalization trigger state for the equalization pressure
The specified equalization pressure
trigger type is not supported. The Go to the Spot Equipment
Invalid equalizer trigger following settings are supported: SETUP screen, and select a
SVGN-166 STOP type. $spoteqsetup[].$epb4_trgtyp = 1(time), valid trigger type.
Invalid equalizer trigger The specified equalization pressure Go to the Spot Equipment
SVGN-167 STOP event. trigger event is undefined. SETUP screen, and select a
The pushing depth specified in the Update one or more of
pressure schedule or the minimum the parameters used to
pushing depth, exceed the strokelimit. specify pushing depth:
Push depth %s[mm] The contact speed might be slightly $sgsch#[].$push_depth
SVGN-168 exceeds strokelimit lower than specified as a result of this and
Decrease
$sggun#.$setup.$push_m
The minimum push depth (internally argin, or increase the
calculated distance) required to close stroke limit.
decelerate from the contact speed Although this alarm has a
exceeds the maximum possible pushing warn severity, this
depth: part thickness + close stroke condition should be
limit. The value of the minimum corrected since the
pushing depth (specified in the alarm minimum push depth has
PushDepth%s[mm]clam message) was clamped to the been clamped to a value
SVGN-169 pd, speed affected maximum possible pushing depth. that is small enough to
If you want to use the
The instruction format instruction format
PRESS_MOTN[SD=,P=,SEL=(,)] cannot PRESS_MOTN[SD=,P=,SEL
be used with the setting =(,)] then set
$SGSYSDG.$UGA_IDX4GB=FALSE. GunB $SGSYSDG.$UGA_IDX4GB
Incompatible must use GunA data, for this =TRUE. If you do not want
SVGN-170 PRESS_MOTN format. instruction. to use the instruction
The Pressure[]kgf or Pressure level Gun Perform autotuning or
Requested torque > instruction was executed, and the disable overtorque
SVGN-171 max gun torque. requested torque > max gun torque protection.
A SPOT[] or PRESS_MOTN[] instruction Adjust the trigger timing
Can not move gun was performed during an interrupt of interrupt routine. Also,
SVGN-172 during interrupt routine (Ex. TB,TA,DB,program monitor wait until the interrupt
A timeout occurred during power-up Check alarm log for servo
Gun-attach sequence. Possible causes errors and and correct the
are: 1. A servo problem interrupted the issue if one is found. For
servo startup sequence, and caused the example: SRVO-058 FSSB
attach sequence to fail. For example, %d init error (%d) If no
Timeout G%d A%d %x fuse FS1 on servo amp is blown. 2. The servo problem is found,
SVGN-173 %d servo gun is NOT connected correctly. then check cable
The Servo Gun softpart could not be Document the events that
SPCALL error fcod:%x, notified of the event. Refer to the led to the error, and call
SVGN-174 stat:%x function code(fcod) and status(stat). your FANUC America
GunTouchup(F3) or AutoTouchup(F4) See SVGN-176. NOTE:
was requested but touchup did not SVGN-175 is an optional
occur. This alarm (SVGN-175) only alarm (enabled by
indicates that touchup failure has default). Set
SVGN-175 Position not recorded occurred, SVGN-176 identifies cause of $SGSYSTCH.$PTNOTRECAL
Refer to remedy for
SVGN-176 %s Refer to message in string. message in string.
Incorrect thickness or/and
gun close limit would
cause a pressure shortage
If thikness or/and gun
close limit is incorrect,
gun tip can not go correct
push depth for setpoint
pressure The Thk is value
which is specifiied in
Thk%smm,CloseLim%s This is information at pressure pressure schedule. Check
SVGN-177 mm,StdLim%smm shortage. if thikness value in
Gun storke limit is
compensated by tip wear
down. The standard value
is stroke limit when
TW_SETUP or WR_SETUP
This is information of standard stroke is performed an original
SVGN-178 Open/CloseLim=%s limit. value. This shorter
The servogun option
supports a maximum of 2
groups due to complex
The program attempted the servogun synchronization. Use a
SVGN-179 More than two groups command with more than 2 groups. program with less than 3
Pressure could not be
persisted during BWD or
Pressure persist is Persisted pressure after HOLD is ABORT So Persisted
SVGN-180 canceled canceled pressure is canceled This
The Measured part thickness is less
than the under-thickness limit(mm).
The part may be out-of-tolerance.
Nominal thickness:%s NOTE: This message displays the
SVGN-181 MinAllowable:%s nominal (expected/programmed) See SVGN-040.
The Measured part thickness is greater
than the over-thickness limit(mm). The
part may be out-of-tolerance. NOTE:
Nominal thickness:%s This message displays the nominal
SVGN-182 MaxAllowable:%s (expected/programmed) thickness and See SVGN-040.
The 4 parameters in SVGN-
183 p1/p2/p3/ p4 provide
details about the modified
point. p3: Corrected value
Gun touchup function has modified is the difference between
position of spot point. This message is new recorded position
provided for informational purposes and old recorded position.
only, it is not a fault/problem. Note: Note: robot close
SVGN-183 is not posted during program direction is positive
SVGN-183 %s/%s/%s/%s touchup. polarity, so if new position
Spot point touchup was cancelled, Execute point touchup
Point touchup because shift key was released and again, and don't exit
SVGN-184 cancelled. program edit screen was de-selected editor screen.
Data collected during search process Reduce unpress time by
exceeded storage buffer. Note: SVGN- increasing speed
Gun monitor buffer 185 only occurs during unpress (a ($SGGUN#.$TEACH.$LWD
SVGN-185 overflow process that is no longer used), so it is T_CLOSPD) or decreasing
This indicates information for tip Please see remedy for
increased error. The left value indicates SVGN-32 and/or SVGN-33.
the last wear down. The right value Note: If current measured
indicates current measured wear down. wear down is nearly 0,
Wdn,Old:%smm- Since the current measured wear down update program might be
SVGN-186 >New:%smm is incorrect, so increased alarm is performed without new
Tip wear setup was performed, without Perform gun zero
performing gun zero mastering first. mastering in gun zero
Do gun zero mastering This condition can lead to incorrect mastering screen with
SVGN-187 with new tip mastering for tip wear reference new tip.
Restart info An internal error has occurred. Document the events that
SVGN-188 incomplete:%d/%d/%d Execution restart information is led to the error and call
Tipwear had been setup, but a BZAL Go to gun master screen
alarm occurred and tipwear zero and execute recalibrate or
reference (pls0) is not up to date. Pls0 master. Either action
Tipwear overstroke must be updated after BZAL to updates pls0, and turns
SVGN-189 protection is off maintain proper stroke limit overstroke protection on.
Open (search start) distance for upper
panel detection exceeded gun stroke If point touchup is being
limit, so open distance was clamped to performed, close gun (jog)
gun open limit. Note: Gun open to reduce open distance.
distance for upper panel search If program touchup is
depends on touchup type: if point being performed, reduce
touchup: open distance = initial pos + one or more of the
search prep dist if prog touchup: open following parameters:
distance = upper panel detect
Backup position not thk.nom+thk.err.max+pos.err.max+sear distance, max thickness
SVGN-190 reachable. chprep dist SVGN-190 does not cause error, max pos error.
Thickness Check Calibration was
Thickness Check Calib successful - parameters were updated.
SVGN-191 Updated. Note: This alarm is merely status None.
Thickness Check Calibration parameter Please see cause code or
is not updated Thickness Check other relative alarm on
Thickness Check Calib Calibration could not finished correctly alarm screen Remove
SVGN-192 Not Updated. Note: If thickness Check Calibration had cause that makes pausing
Automaster operation was successful, No remedy needed - this
Automastered:%.1fmm and mm distance between old and new alarm is for information
SVGN-193 from old masterpos. master position is provided for purposes only.
Automaster operation failed. Refer to Formulate remedy based
SVGN-194 Automaster failed. cause code for reason. on cause code.
Masterct(old:%d,new:% Automaster operation was successful, No remedy needed - this
SVGN-195 d). and master count values - old and new - alarm is for information
TW Auto wear calibrate operation was No remedy needed - this
recalibrated:%.1fmm successful, and mm distance between alarm is for information
SVGN-196 from old pulse0. old and new pulse0 value is provided purposes only.
Auto wear calibrate operation failed. No remedy needed - this
SVGN-197 TW recalibrate failed. Refer to cause code for reason. alarm is for information
Auto wear calibrate operation was
Pulse0ct(old:%d,new:% successful, and master count values - Refer to cause code for
SVGN-198 d). old and new - are provided for specific information.
Status information about automaster Refer to cause code for
SVGN-199 Automaster message. operation is being posted. specific information.
FCTRL must be off for Automaster was requested while gun Press fault reset and
SVGN-200 automaster. was still in force control. Automaster execute automaster again.
The posted error occurred on GunA Correct the error on the
SVGN-201 Gun index 1 (gun index 1) of the dual gun. gun number
The posted error occurred on GunB Correct the error on the
SVGN-202 Gun index 2 (gun index 2) of the dual gun. gun number
Speed for move to pressure position is Check pressure calibration
GunA, GunB contact different for GunA and GunB. Equal data and/or pressure
SVGN-203 PAUSE speed is different speed is required, for synchronized schedule data.
Pushing depth is different for GunA and Set $sgsch#[].$pushing
GunA, GunB pushing GunB. Equal pushing depth is required, depth, and
SVGN-204 PAUSE depth is different for synchronized move to pressure $sggun#.$setup.$push_m
Creep distance is different for GunA Set
GunA, GunB creep and GunB. Equal creep distance is $sggun#.$setup.$creep_di
SVGN-205 PAUSE distance is different required, for synchronized move to st to same value, for both
The Part Thickness used in this Pressure
GunA, GunB part Schedule is different for GunA and Set the part thickness to
SVGN-206 thickness is different GunB. Equal thickness is required to same value, for both guns.
Gun sag values are different for GunA
GunA, GunB sag and GunB. Gun Sag value must be Set gun sag compensation
SVGN-207 settings are different equal, for synchronized move to values the same.
GunA, GunB linear Specify the same linear
SVGN-208 distance is different Linear distance values are different. distance value for GunA
Use the Gun Setup Utility
to set the Maximum
Joint velocity limits are different for Speed (i.e. joint velocity
gunA and gunB. Joint velocity limit limit) of both Gun A and B
GunA, GunB joint must be equal to achieve synchronized to the same value. - Go to
SVGN-209 velocity limits differ. contact with the part. UTILITIES - GUN SETUP -
Use the Gun Setup Utility
Acceleration Times are different for to set the Acceleration
gunA and gunB. The acceleration times Times of both Gun A and
GunA, GunB accel times must be equal to achieve synchronized B to the same value. - Go
SVGN-210 differ contact with the part. to UTILITIES - GUN SETUP -
Incomp weight calc in Weight calculation in the autotuning is Complete weight
SVGN-211 ATUN not completed. Therefore, pressure calculation of the
Incomp weight calc for Weight calculation for X gun is not Complete weight
SVGN-212 X gun completed. Therefore, pressure was calculation by executing
The setting of the tool
coordinate system is
wrong. It is necessary to
Can't detect pressure set the tool coordinate
SVGN-213 posture Can't detect pressurizing posture. system to the servo gun
Servo gun type is not Servo gun type is not set. Therefore, Confirm the weight
SVGN-214 set pressure was not able to be compensation gun type of
Incomplete manual weight Go to the Servo Gun
Incomp manual wt compensation setup was performed. General Setup screen,
SVGN-215 comp setup Therefore, pressure was not able to be select Manual weight
Illegal wt compens val: The weight compensation value is too Confirm the contents of
SVGN-216 Gun%d,P%d large. Therefore, pressure was not able the setup of the weight
There is mistake in the setting of Confirm the weight
Do press calib over weight compensation function at compensation gun type of
SVGN-217 again pressure calibration. the Servo Gun General
Because this command pressure was Confirm the value of WT
lower than the value of WT compn press low lim of
This press can't be compensation press low lim of Servo the Servo Gun General
SVGN-218 compensated Gun General Setup screen, this Setup screen.
The interval between
angle and angle at
SVGN-219 Angle is wrong A set value of the angle is wrong. pressure calibration
The interval between
angle and angle at
pressure calibration
A set value is wrong. The calculated should be away by 70
SVGN-220 Set value is wrong weight has become negative. degrees or more. Confirm
Incomplete semi-auto weight Go to the Servo Gun
Incomp semi-auto wt compensation setup has occurred. General Setup screen, and
SVGN-221 comp setup Therefore, the pressure was not able to select the Semi-auto
UT correct ang is out of The UT correct angle is out of range. Go to the Servo Gun
SVGN-222 range
Max disturbance excess Therefore, the position
Max disturbance torqueofexceeds
the gunthe
was General
Check theSetup screen. Set
pressure
SVGN-223 G%d
Average disturbance tolerance.
Average disturbance torque exceeds calibration.
Check the pressure
SVGN-224 excess
Min G%d
disturbance the tolerance.
excess Min disturbance torque exceeds the calibration.
Check the pressure
SVGN-225 G%d
Servogun Diagnosis is tolerance. calibration
SVGN-226 failed. Servogun diagnosis is failed. Remedy internal error.
A mistake is found in the setting of the Go to the Servo Gun
Manual weight setup manual weight compensation. General Setup screen,
SVGN-230 err: Gun%d,P%d Therefore, pressure was not able to be select Manual weight
The setting of the tool
coordinate system is
wrong. It is necessary to
Can't detect pressure Pressurizing posture cannot be set the tool coordinate
SVGN-231 posture
This gun cannot use detected.
This gun cannot use the auto weight system
Set the to
gunthe
to servo gun
another
SVGN-232 AUTO
This gun cannot use compensation
This gun cannottype.
use the auto weight weight
Set the compensation
gun to another
SVGN-233 AUTO compensation type. weight compensation
This message is posted if user presses Set
F2(rec) fkey when prompt "Is tip on $SGSYSTCH.$LOG_FLAG=F
SVGN-234 Recorded touchup log. panel" is presented. SVGN-234 is ALSE and/or
User notification that touchup log
Already recorded already exists. This message is posted if Press F2(rec) fkey only
SVGN-235 touchup log F2(rec) fkey is pressed more than once, once.
Program execution paused because
position and/or thickness is out of Set Det/Thk/Pos error
tolerance. This pause occurs when pause Sev in the gun
DET/THK/POS error pause severity is teach setup screen to
set to warn or alarm, and one more of DISABLE if you do not
[PauseMod]Det/Thk/Po the following conditions exist: upper want robot to pause when
SVGN-236 s Err :Eq%d panel mis-detect: SVGN-240, thickness the alarms above occur.
Increase maximum
allowable position error
or decrease min allowable
position error, on gun
teach setup screen. If
problem persists, take the
following actions:
1.Confirm the position
error offset in the spot
program touchup setup
screen. This alarm might
be generated immediately
after the position error
offset is changed. 2.
Measured position error is greater than Confirm the parameter to
Excessive Position maximum allowable position error or correct position for Xgun
SVGN-237 error:(Eq:%s) less than min allowable position error. in the spot program
Program execution paused because If you do not want the
TCHDSB is attached to spot instruction, robot to pause, either: a.
[PauseMod]SpotProgTo and SpotprogTouch_DSB pause severity set SpotProgTouch_Dsb
SVGN-238 uchDsb:Eq%d = warn or alarm. pause Sev in the gun
Measured thickness is out of tolerance. Confirm that: 1. actual
Note: SVGN-242 Act thick:x.x, Nom panel thickness is correct.
Thickness thick: y.y is posted as cause code for 2. nominal thickness in
SVGN-239 error:(Eq:%d,Ln:%d) SVGN-239. the pressure schedule is
Upper panel detection distance is Confirm that: 1. no
larger (gun more open) than max obstruction exists
detect distance. where: max detect between guntip and
distance = pos.err.max + thk.nom + panel. 2. actual panel
Up Panel Mis- thk.err.max This alarm occurs only thickness is correct 3.
SVGN-240 detect:(Eq:%d,Ln:%d) during program touchup (not point nominal thickness in
Position error exceeds Max allowable
ActPosErr:%smm pos error. SVGN-241 supplies the actual
SVGN-241 MaxPosErr:%smm position error and maximum allowable See SVGN-237.
Thickness error exceeds OverThickness
Act thick:%smm Nom tolerance or UnderThickness tolerance.
SVGN-242 thick:%smm SVGN-242 supplies the actual thickness See SVGN-239.
Detect distance (observed) exceeds
ActDetDis:%smm Max Detect distance. SVGN-243
SVGN-243 MaxDetDis:%smm supplies the actual detection distance See SVGN-240.
Retry Thickness Check Thickness check calibration (0kgf)is Execute thickness check
SVGN-244 calibration incomplete. Thickness check calibration calibration on gun setup
Position register (PR) that stores
undeflect (relax) position for gun/robot
could not be set. Note that undeflect Correct problem identified
Gun not open to pos is starting point for thickness check, in cause code, and retry
SVGN-245 undeflect pos it removes deflection at lower panel touchup.
Panel simulation is enabled, but Disable panel
machinelock is disabled on robot group simulation($SGSYSTCH.$SI
Machinelock required or gun group. Machinelock must be M_PNL_ENB=FALSE) or
SVGN-246 for PNLSIM. ENABLED on both robot group and gun ENABLE machinelock on
Touchup is already in progress on an Wait for touchup
Concurrent multiarm arm and touchup is being requested on operation that is already
SVGN-247 touchup unsupported. another arm (at the same time). in progress to complete,
Upper or lower panel search ended, 1. ensure that panel is
but panel was not detected. I.E. gun present. 2. increase
speed never fell below speed threshold, $sggun#.$teach.$pnldflctd
during search. The following conditions st. 3. decrease pressure
SVGN-248 Panel not detected. can cause this problem: 1. missing margin. If problem
Panel was not detected during second
Spot program touchup part of upper panel search. Internal
SVGN-249 enabled ! condition for search termination was Retry touchup.
If verify (not touchup)
mode is desired, change
A tp program started (or resumed) and execution mode via
spot program touchup function is Touchup setup screen: a.
enabled with execution mode = if tp is disabled, set
TOUCHUP. Touchup mode means that Execution mode for AUTO
Spot program touchup points will be evaluated AND positions = VERIFY mode, b. if tp is
SVGN-250 enabled ! will be modified. enabled, set Execution
Position error (change between
observed position and recorded
position) is less than MinPosError. This
message is posted to display magnitude
of observed position error and If position error is
minimum pos error, when SVGN-237 acceptable, decrease min
occurs. Note that min pos error is used pos error and execute
in conjunction with max pos error to touchup again. Set min
control when points are touched up. pos error = 0.0, to disable
ActPosErr:%smm < Points are only touched up if position min pos error check
SVGN-251 MinPosErr:%smm error is greater than or equal to min completely.
Upper panel detection failed. The Confirm that: 1. no
integer parameter ()identifies the obstruction exists
failure type: type1: gun tip did not between guntip and
contact panel during search motion panel. 2. actual panel
Panel Detection was (internal condition to terminate search thickness is correct 3.
SVGN-252 failed.(%d) was not met). type2: exact position of nominal thickness in
Pause mode in the program touch-up Please set pause mode in
Pause mode start by function started. Pause mode starts by the gun teach setup
SVGN-253 alarm:Eq%d alarm when the following warning are screen to DISABLE when
Confirm that: 1. no
Low Panel Mis- Measured thickness was too large at obstruction exists
SVGN-254 detect:(Eq:%d,Ln:%d) lower panel detection. between panel and either
Register specified for SPTCH_OFS or Set a valid parameter for
SPTCH_RSD is invalid. Note: SPTCH_OFS the instruction: 1.
is attached to spot instruction to SPTCH_OFS: Greater than -
Invalid parameter in specify offset/adjustment value that is 2.0mm and less than
SVGN-256 SPTCH_XXX added to final offset for point 2.0mm 2. SPTCH_RSD:
Specify a valid register
number in SPTCH_OFS or
Register specified for SPTCH_OFS or SPTCH_RSD instruction:
SVGN-257 Invalid register number.
Retry number > Max SPTCH_RSD is invalid.
Initial touchup attempt and retries min:
Examine1 max:
log posreg
and max
SVGN-259 retry number failed. determine reason for
Upper panel detection failed. Robot
Search motion is motion stopped before gun tip touched
SVGN-260 unsuccess. panel. Data for the detection is invalid. Retry search motion.
Examine the servo gun.
Disturbance of gun is Gun torque command is erratic. This Confirm that there is no
SVGN-261 abnormal. gun may have mechanical issues. actuator damage or
Disturbance of gun is Gun torque command is erratic. This Confirm that there is no
SVGN-262 abnormal. gun may have mechanical issues. actuator damage or
Variation in disturbance Gun torque command is erratic. This Confirm that there is no
SVGN-263 is too much. gun may have mechanical issues. actuator damage or
Variation in disturbance
Gun torque command is erratic. This Confirm that there is no
SVGN-264 is too much. gun may have mechanical issues. actuator damage or
Mech Comp Calib. Mechanical calibration for This is a status message
SVGN-265 succeeded point/program touchup function for informational
This message shows the compensation
value for point/program touchup Remedy: This is a status
function. Value in () means Num of message for informational
SVGN-266 Comp Dist: %s mm (%s) Successful calibration / Specified Num purposes.
Mech Comp Calib. Mechanical calibration for Refer to SVGN-268 for
SVGN-267 failed point/program touchup function failed. cause.
This message identifies cause of gun Invalid gun number.
mechanical compensation (calibration) Correct gun number
failure. It is posted, along with SVGN- between 1 and
267. input data is invalid - parameter $SGSYSCFG.$GUN_NUM
specified in SGKTCHCL() is invalid. The Invalid thickness: Corrct
remedy depends on the parameter (p1- thickness value greater
p5) that is identified: Invalid gun than or equal to 1.0
number. Specify Gun number between Invalid Gun Open
1 and $SGSYSCFG.$GUN_NUM Invalid Distance: Correct gun tip
thickness: Specify thickness value open distance. Invalid
greater than or equal to 1.0 Invalid Gun Robot Open Distance:
Open Distance: Specified gun tip open Correct robot tip open
distance is not invalid. Invalid Robot distance. Invalid Num of
Open Distance: Specified robot tip Calib: Correct calibration
open distance is not invalid. Invalid iterations (number) Check
Num of Calib: Calibration iterations system status:Calibration
(number) is invalid. Minimum=1 Check cannot proceed due to
system status:Calibration cannot system error or illegal
SVGN-268 %s proceed due to system error or illegal condition. - Rest nny
Spot program touchup This indicates spot program touchup is Enable spot program
SVGN-269 disabled disabled. touchup via TEST CYCLE or
Confirm that distance of
gun panel contact is not
larger than search start
distance. Retry spot
program touchup. If gun
Gun tip contacted upper panel surface tip contacts upper panel
before search motion started. Torque surface before search
Too large torque limit became unexpectedly-large during start distance, increase
SVGN-270 limit.(Upper) upper panel detection step1. start distance(SD) for gun
Confirm that distance of
panel contact is not larger
than search start distance.
Retry spot program
touchup. If robot tip
contacts lower panel
surface before search
start distance, increase
start distance(SD) for
Robot tip contacted lower panel robot tip and/or lower
surface before search motion started. panel detection distance.
Too large torque Torque limit became unexpectedly- Refer to Chapter "20.6
SVGN-271 limit.(Lower) large during lower panel detection. LOWER
ConfirmPANEL DETECTION
that robot tip has
enough clearance from
panel surface at start
position. If distance
between robot tip and
panel is too short,
increase start distance(SD)
for robot tip an/or lower
panel detection distance.
Refer to Chapter "20.6
Open distance of a gun axis was too LOWER PANEL DETECTION
Lower Det start pos was short at start position of lower panel DISTANCE CLAMP" or
SVGN-272 wrong. detection. "20.13 SPTCH_RSD
R:1 means that error
occurred during upper
panel detection. Confirm
that gun tip has enough
clearance from upper
position.If distance
between the tip and the
panel is too short,
for gun tip. R:3 means
that error occurred during
lower panel detection.
Confirm that robot tip has
enough clearance from
position and that there is
no obstacle between the
panel and the robot tip at
start position. If distance
between the tip and the
panel is too short,
for robot tip and/or lower
Refer to Chapter “20.6
A gun tip was contacted an upper panel LOWER PANEL DETECTION
Det was irregular surface on a free running section DISTANCE CLAMP” or
SVGN-273 stop.R:%d P:%d before search motion. “20.13 SPTCH_RSD
If gun tip contacted panel
surface at start position,
for gun tip. If robot tip
contacted lower panel
surface at start position,
for robot tip and/or lower
Refer to Chapter "20.6
LOWER PANEL DETECTION
Speed threshold is too Threshold to detect panel contact DISTANCE CLAMP" or
SVGN-274 low became unexpectedly-low. "20.13 SPTCH_RSD
Search start distance was clamped due
to gun open limit. SVGN-275 is posted
Search starts@:%smm as cause code for SVGN-190. Actual
SVGN-275 (%s desired). search start distance is displayed, along See SVGN-190.
Search mode was not Search mode was not selected. Set
SVGN-276 selected. Therefore, position detection was not $SGSYSTCH.$ACCUDET_E
Gun open deistance required for Initiate normalization
OpenLim too normalization search is larger than process with smaller gun
SVGN-277 small:%.1fmm required. open limit. Normalization process open distance or increase
Averaging speed is Axis speed will be varied during search If the gun has no
SVGN-278 enabled. motion. So counter-measure is turned abnormality, there is no
Axis speed will be varied during search If the gun has no
Averaging speed is motion. So counter-measure is used abnormality, there is no
SVGN-279 used. automatically. remedy. Turn Use
Wear down amount of gun side is
exceeded to max compensation
tolerance. Cap tip may be worn out Change tip to new tip. If
and/or shank may be shorter than shank is shorter than
Excessive Wear down original length. Gun axis will run over original length, change to
SVGN-280 Comp (Gun). away mechanical stroke limit and gun new shank
Wear down amount of robot side is
exceeded to max compensation
tolerance. Cap tip may be worn out Change tip to new tip. If
and/or shank may be shorter than shank is shorter than
Excessive Wear down original length. Gun axis will run over original length, change to
SVGN-281 Comp (Rbt). away mechanical stroke limit. And gun new shank.
Wear ratio updated:%s- Wear ratio was updated. Displayed This is just information.
SVGN-282 >%s value means old wear ratio -> new There is no remedy.
Wear ratio was updated. (However
wear down was updated ) System can
not calcarate when tips are not
WORN.DOWN( = cap tip is increased ). Turn on new tip when tip
There are some causes - Cap has been is replaced in next time.
Wear ratio(%s) Not replaced. But new tip flag is OFF - Cap Also Perform 2step after
SVGN-283 updated wear has been hardly changing. Wear tip dressing several times
This indicates wear down changing: The
last 2step wear down -> Current 2step Turn on new tip when tip
wear down If The last 2step wear down is replaced in next time.
is larger than current 2step wear down, Also Perform 2step after
SVGN-284 Gun:%s,Rbt:%s tip would be replaced If cap wear has tip dressing several times.
This indicates calculated wear down is Turn on new tip when tip
exceeded user's tolerance - Cap has is replaced in next time.
Wear ratio Out of been replaced. But new tip flag is OFF - Also Perform 2 step after
SVGN-285 Tolerance Cap wear has been hardly changing. tip dressing several times.
This indicates calcurated wear down
SVGN-286 Wear ratio:%s > Max:%s and user's tolerance(Max) See SVGN-286
This indicates calcurated wear down
SVGN-287 Wear ratio:%s < Min:%s and user's tolerance(Max) See SVGN-286
1step performed with new tip flag. Do
New tip !! Use 2step not perform 1step with new tip falg Perform 2step with new
SVGN-288 TWD when auto update
Wear ratio has not wear
been ratio is enable.
updated tip falg agin.
for
SVGN-289 Update
Do pressWear
calib ratio
over long time.
There is mistake in the setting at Please update
Execute wear ratio.
pressure
SVGN-290 again:G%d pressure calibration calibration again
Illegal temperature Temperature compensation value is too Confirm the content of
SVGN-291 compens
Invalid val:G%d
AI,GI conversion large. Therefore,
Invalid pressure
AI,GI conversion was setting
factor not ableis
the setupthe
Confirm of AI,GI
temperature
SVGN-292 factor:G%d not correct. conversion factor setting.
Temp info from motor Temperature information cannot be Examine the figure
SVGN-293 isn't obtained:G%d obtained from this pulse corder. number for the pulse
Temp exceed abnormal Temperature exceeded abnormal Confirm the temperature
SVGN-294 up lim:G%d motor temperature upper limit value. sensor is not out of order.
Temp below abnormal Temperature fell below abnormal Confirm the temperature
SVGN-295 low lim:G%d
Invalid temperature motor temperature
Temperature lowersetting
coefficient limit value.
sensor
Confirmisthe
is not nottemperature
out of order.
SVGN-296 coefficient:G%d
Temp info from AI isn't correct.
Temperature information cannot be coefficient setting.
SVGN-297 obtained:G%d
Temp info from GI isn't obtained frominformation
Temperature AI cannot be Confirm the AI setting.
SVGN-298 obtained:G%d obtained from GI Confirm the GI setting.
Instruction for which invalid thickness Confirm the thickness in
SVGN-299 Invalid thickness: t=** was specified was executed. the instruction.
This is just warning
Program is paused when gun is closing massage. Early welding is
Early welding OFF at with early welding. Early welding is disabled for the only
SVGN-300 resuming disabled for resumed gun closing. resumed gun closing. In
Early weld calibration Early weld calibration is incomplete. Execute early weld
SVGN-301 INCOMP Early welding can not be enabled. calibration on gun setup
Welding in pressure When pressure did not reach target Please refer to remedy of
SVGN-302 stortage pressure, weld init would asserted in SVGN-020 Also, Execute
in pressure of dual gun, either gun
Gun%d: Disabled early disable early welding. Weld init will Enable/Disable early
SVGN-303 welding assert when pressure of gun that welding for both gun.
Invalid early welding Invalid early welding time was Correct early welding
SVGN-304 time specified. Early welding time is too time. Early welding time
OVR < 100%%,Early General override is not 100%. Early
SVGN-305 Welding Disabled
Thickness Check Calib welding time can work correctly with Set override
This 100%. It's
is just a message.
SVGN-306 Retrying... Thickness check calibration is retrying. no remedy.
DT of current NORMFIND search differs -Increase max rotation
too much from DT of initial NORMFIND error. Max rotation error
search. DT should be the same during should be set for worst
FINDNORM searches, because case rotation error in
operating conditions (speed, program. Note that max
orientation, etc) are the same during rotation error increases
Excessive DT change these searches. Refer to cause code for FINDNORM time because
SVGN-312 from srch1. magnitude of DT change. There are 2 motion to search point in
DT of current search and DT of search1
value (that caused SVGN-279) are
reported in this alarm, for reference.
SVGN-313 Srch%d:%d, Srch1:%d. SVGN-280 is posted as cause (info) for Refer to SVGN-279.
Thickness could not be read because Perform deflection
deflection calibration is incomplete. calibration or disable
Thickness%d not read, Number after thickness refers to type thickness read
SVGN-314 deflect cal incomp of thickness that could not be read ($RDTHK_ENB=TRUE).
Torque value for current pressure is not1. Go to pressure
in deflection calibration table - calibration screen and add
deflection value is obtained via present pressure to
Torque value not in interpolation. Accuracy of deflection pressure calibration table
SVGN-315 deflect cal table. estimate may improve if deflection is (if it is not there already).
Refer to cause and
remedy of thickness error.
Thickness1 error Thickness error has occurred and Note that this alarm is
SVGN-320 requires reset. operator attention is required. posted AFTER gun has
Thickness after weld Expected change in thickness Execute SPOT[] again, if
SVGN-321 NOT ok (%.1f). (decrease) was NOT observed. possible.
Decrease=%.1f (Min Observed thickness decrease and None. This alarm is for
SVGN-322 decrs=%.1f)mm minimum thickness decrease are informational purposes
Decrease=%.1f (Max Observed thickness decrease and None. This alarm is for
SVGN-323 decrs=%.1f)mm maximum thickness decrease are informational purposes
Thickness after weld ok Thickness measured (#.#) after weld None. This alarm is for
SVGN-324 (%.1f). was within tolerance. informational purposes
Thickness change from before weld to None. This alarm is for
after weld (#.#) is provided. Note: informational purposes
SVGN-325 Decrease=%.1fmm. Thickness decrease is displayed as a only.
Refer to cause and
remedy of thickness error.
Thickness2 error Thickness error has occurred and Note that this alarm is
SVGN-326 requires reset. operator attention is required. posted AFTER gun has
Thickness:%.1fmm in Measured thickness is within tolerance Disable thickness ok
SVGN-327 tolerance (ok). This warning is posted for message to suppress this
Measured thickness before weld was 1. Confirm that panel is
smaller than nominal thickness + under ok, and that robot is at
thickness limit. Note that this alarm is correct location on panel.
posted as cause code for SVGN-193. 2. Confirm that nominal
SVGN-328 Thickness1 undertol. SVGN-193 and SVGN-270 are posted thickness is correct. 3.
Measured thickness before weld was 1. Confirm that panel is
larger than nominal thickness + over ok, and that robot is at
thickness limit. Note that this alarm is correct location on panel.
posted as cause code for SVGN-193. 2. Confirm that nominal
SVGN-329 Thickness1 overtol. SVGN-193 and SVGN-271 are posted thickness is correct. 3.
Difference between thickness
measured before and after weld was
smaller than Setdown tolerance 1. Confirm that weld
min(mm). I.E. thickness decrease was settings are ok. 2. Confirm
smaller than expected. Note that this that Setdown tolerance
SVGN-330 Setdown undertol. alarm is posted as cause code for SVGN- min(mm) is not too large.
Difference between thickness
measured before and after weld was
larger larger than Setdown tolerance 1. Confirm that weld
max(mm). I.E. thickness decrease was settings are ok. 2. Confirm
larger than expected. Note that this that Setdown tolerance
SVGN-331 Setdown overtol. alarm is posted as cause code for SVGN- max(mm) is not too small.
This alarm is posted if None. This alarm is posted
trqcmd:%d, ClsThrsh: [sgprscfg]sho_thr_inf = TRUE. The to provide feedback on
SVGN-333 %d alarm provides torque command gun control parameters,
[sgprscfg]sho_pos_inf = TRUE. The to provide feedback on
alarm provides feedback on gun open gun control parameters,
distance, for following events: a. force during close stroke. Set
Pos(fctl%s,thk%s,fcenb control command status($fctrl) changes [sgprscfg]sho_pos_inf =
SVGN-334 %s)mm from false to TRUE b. thickness FALSE, to disable this
[sgprscfg]sho_pos_inf = TRUE. The to provide feedback on
alarm provides feedback on gun gun control parameters,
disturbance torque, for following during close stroke. Set
DT(fctl%d,thk%d,fcenb events: a. force control command [sgprscfg]sho_pos_inf =
SVGN-335 %d)trqct status($fctrl) changes from false to FALSE, to disable this
ClsThrshLo(obs:%d,cur: [sgprscfg]sho_thr_lo = TRUE AND to provide feedback on
SVGN-336 %d,std:%d) [sgprscfg]wt4cls2thk==TRUE AND gun control parameters,
$sggun#.$setup.tc_okmsg=TRUE to provide feedback on
Nom:%.1fmm,Min:%.1f (thickness check ok). The alarm gun control parameters,
SVGN-337 mm,Max:%.1fmm provides feedback on thickness during close stroke. Set
Specify thickness in Specify thickness value in
SVGN-338 instruction Macro THK_KVAL is obsolete. SPOT (or PRESS_MOTN)
Prog:%s is write- Spot program touchup function could
SVGN-340 protected. not modify program position, because Disable write protection.
Spot program touchup has been Note: purpose of this
enabled with execution mode = warning is operator
TOUCHUP mode during spot instruction notification, this is not a
execution, so spot program touchup fault condition. In order to
will not start until next spot. Conditions execute program touchup
leading to this message: 1. Start immediately, either
Spot program touchup program with spot program touchup execute shift backward (to
SVGN-341 pending. disabled 2. Pause program during restart spot) or abort
If touchup (not verify)
A tp program started (or resumed) and execution mode via
spot program touchup function is Touchup setup screen: a.
enabled with execution mode = VERIFY. if tp is disabled, set
Verify mode means that points will be Execution mode for AUTO
Spot program evaluated but positions will NOT be = TOUCHUP mode, b. if tp
SVGN-342 verification enabled ! modified. is enabled, set Execution
enabled in VERIFY mode during spot warning is operator
instruction execution, so spot program notification, this is not a
touchup will not start until next spot. fault condition. In order to
Conditions leading to this case are: 1. execute program touchup
Spot program Start program with spot program immediately, either
SVGN-343 verification pending. touchup disabled 2. Pause program execute shift backward (to
Touchup was requested with torque Complete touchup torque
Torque calibration control type 2, but torque calibration is calibration or change
SVGN-344 incomplete. incomplete. $sggun#.$tchup.$updt_tq
Prog(%s): Read group Group mask could not read from Lookup error code for
SVGN-345 msk failed. specified program(). Refer to cause SVGN-347 and take
Prog(%s): Write group Group mask could not be written to Lookup error code for
SVGN-346 msk failed. specified program(). Refer to cause SVGN-347 and take
SVGN application alarm has occurred.
This message merely reports the status Lookup error code and
SVGN-347 status:%s. (error) number that caused this take appropriate action.
considered to be detection failure
(missing panel). However, in case of
very soft gun and thin panel, gun
position may be past point of closure Set panel deflect distance
(0). Increase to 0, if panel and or gun
Panel deflect distance > $sggun#.$teach.$pnldflctdst for this are rigid. note: defauult
SVGN-348 0.
Thickness not case. However, if panel is not thin/soft
settingtoofthe
Refer $pnldflctdst is 0.
error cause
SVGN-349 measured. Thickness is not measured. code.
Pressure release Fault occurred or shift key was released
Correct reason for fault
SVGN-350 aborted. while pressure release progress was and/or do not release
Map norm search input to
a valid input index via
SVGN-351 Nrm srch input error. Norm search input DIN is invalid. $SGNRMCFG[].$PNLDETDI
Torque limit control is NOT equal to Goto torque limit control
static type2, which provides best in teach setup screen.
Static tqlim ctrl performance for normalization Select Static torque
SVGN-352 recommended. function. This message is merely a control type 2, and
Gun open distance should be identical Confirm that detection
for vx.midpt and vy.midpt. Present result is correct. Redo
Vx.mid-Vy.mid:%.2f difference exceeds tolerance, so one or tqlimit calibration if
SVGN-353 overtol. more of the testpoints may be misdetection occurred.
Gun open distance @vx.midpt should Confirm that detection
be same as pt0. Present difference result is correct. Redo
Vx.mid-TstPt0:%.2f exceeds tolerance, so one or more of tqlimit calibration if
SVGN-354 overtol. the testpoints may be incorrect. Refer misdetection occurred.
Present difference exceeds tolerance, Confirm that detection
Vy.mid-TstPt0:%.2f so one or more of the testpoints may result is correct. Redo
SVGN-355 overtol. be incorrect. Refer to manual for tqlimit calibration if
Panel detection occurred sooner than
expected (see orange block in search Confirm that detection
segment drawing in manual). This result is correct. Redo
Max rot err too small means that max rotation error is too tqlimit calibration if
SVGN-356 (tstpt:%d).
w:%03.1f->%03.1f, small for change:
Rotation the rotation error to
org angle that misdetection
Status messageoccurred.
- no
SVGN-357 p:%03.1f->%03.1f normalized angle.
x+=%03.1f, y+=%03.1f, X,Y coordinate change: org pos to corrective action
Status message - no required.
SVGN-358 z+=%03.1f normalized pos. corrective action required.
Invalid before nrm user B4nrmprgenb = TRUE and Set B4nrmprgenb = TRUE
SVGN-359 prog. B4NRMPRGNM does not exist or is or create valid program
Invalid after nrm user AFnrmprgenb = TRUE and Set AFnrmprgenb = TRUE
SVGN-360 prog. AFNRMPRGNM does not exist or is or create valid program
Popup template files could not be
found, and/or could not be displayed,
Popup windows so norm popup feature was disabled.
SVGN-361 disabled. Note that this message is posted at Refer to cause code.
Normalize process Normalization process did not not Take appropriate action
SVGN-362 failed. complete. Refer to cause code for for this cause code.
Invalid rbt close Robot close is not set to x,y or z. I.E. it
set robot clos direction to
SVGN-363 direction. is set to fix or an invalid direction. appropriate direction: +/-
Invalid gun out Gun is not set to x,y or z OR it is set to
set gun out direction to
SVGN-364 direction.
Number of iterations is the same direction as robot close appropriate
Set direction: +/-
SVGN-365 invalid. Number of iterations < 1. $SGNRMCFG[].$NUM_ITE
Set
$SGNRMCFG.$SPD_STRTV
SVGN-366 Speed range is invalid. Specified speed range is invalid. AL>0, and set
Set
$SGNRMCFG.$RAD_STRTV
SVGN-367 Radiusincrement
Speed range is invalid.
is Specified radius range is invalid. AL>0, and set
Set
SVGN-368 invalid.
Radius increment is Specified speed increment is invalid. $SGNRMCFG.$SPD_INC_V
Set
SVGN-369 invalid. Specified radius increment is invalid. $SGNRMCFG.$RAD_INC_V
Gun tip contacted panel sooner than -If thickness is incorrect,
expected - either settings are incorrect set proper thickness value
or wrong panel is present. If correct in spot/pres_motn
Invalid Gun Close (G:%d panel is present, then confirm that instruction. -If gun zero
SVGN-370 A:%d) Pressure Gain
Invalid following items are correct: -Thickness Record
master is incorrect,
error go to
and report
SVGN-371 Tuning Internal Servo Gun error. to hotline.
Use measure thickness
Uninitialized thickness: This value has not been specified in tp value to measure and
SVGN-372 t=** instruction. enter thickness value
Gun open required for Gun is pressuring (closed past 0). Auto Jog gun open, to release
SVGN-373 autotuning. tune can not start because pressure pressure, then restart
To update wear ratio, 2
step measurement must
be performed with new
1 step measurement was performed tip. This locking is released
Wear ratio update with new tip. Wear ratio updating is by 2 step measurment.
SVGN-374 Locked. loacked. SVGN-288 is posted as
Next 2step TWD 2 step measurement was performed
SVGN-375 updates wear ratio. after 1 step measurement has been No remedy.
Repower, go to control
start, and then back to
Internal TPP error cold start. This action re-
SVGN-376 LBL:%d Internal servogun program error. generates the internal
Repower required for Repower required for auto continue Repower, go to control
SVGN-377 autocont fn function start, and then back to
Thickness measurement process Identify specific cause of
Thickness measurement started, but did not complete. measurement failure,
SVGN-378 cancelled. Completion may be due to a correct it, and execute
Thickness table is Shift hardkey was pressed (to change Set one (or more) values
SVGN-379 empty. manual pressure) but all values in into the thickness table.
Shift+Gun hardkey was pressed (to Set one (or more) values
Thickness table execute manual pressure operation) into the thickness table
SVGN-380 value/index is invalid. but thickness index and/or thickness and select a valid
This message is posted because
thickness measurement was
performed, and
$SGCFG[].$THKMESCFG.$ALM4MESINF
O = TRUE. This message merely
provides a record of thickness Set
measurment in the alarm log. It is not a $SGCFG[].$THKMESCFG.$
Thk:%.1fmm, fault/abnormal condition. Note: SVGN- ALM4MESINFO = FALSE to
SVGN-381 Press:%d%s,%.1fmm 176 is provided as cause code for this disable this message.
Panel contact speed specified in Confirm gun open
pressure calibration table was not met. distance, before pressure.
A slight amount of pressure error can Also, confirm fixed tip
occur because of this contact speed location, gun mastering,
error. Root cause of contact speed and thickness. Note: this
error is insufficient gun open distance warning can be ignored if
Tip could not contact before pressure. The specific conditions panel does not vibrate,
SVGN-382 with specified speed that can cause this error are: -Overly and weld quality is ok.
When extra groups are used in a
robot+servogun program, motion of an
SVGN-383 Extra group motion extra group was detected during SPOT None.
Normalization supports Normalization is NOT supported for UF Change frame type to UT
SVGN-384 UT frame type only. (pedestal) gun type. if possible.
Spot program touchup mode had Make the spot program
SVGN-385 Prg tch mode swich err become ENABLE immediately before touchup mode ENABLE
Robot bkup Requested robot backup distance 1. Increase gun open limit
clamped:%.1fmm(%.1fd cannot be provided, due to gun open if possible. 2. Reduce
SVGN-386 esired) limit. Actual robot backup provided is robot backup distance.
Tune log and/or press log are enabled,
Increase sglogarr size to but sglogarr size <= 1. Tune log and
SVGN-387 log data. press log data files are created only if Set sglogarr size >1.
Variation in speed during observation
period (before detection), is larger than
speed variation observed during
calibration. Number at end of message
indicates phase. 1=Upper panel
detection, 2=Lower panel detection. 1. Redo calibration. 2. if
Root causes are: 1. Gun mechanical problem persists, increase
Speed noise characteristics have changed or value of
hi:%.1fmm/sec(nom%.1 calibration is not up to date. 2. Current $SGSYSTCH.$P0SPDALMM
SVGN-388 f):%d orientation is different than orientation GN.
Torque required for current search is
larger than torque limit that was
required to close gun during panel
detection calibration. Number at end of
message indicates phase: 1=Upper
panel detection, 2=Lower panel 1. Redo calibration. 2. if
detection. Root causes are: 1. Gun problem persists, increase
mechanical characteristics have value of
Search torq changed or calibration is not up to $SGSYSTCH.$P0TRQALMM
SVGN-389 hi:%.1fkgf(nom%.1f):%d date. 2. Current orientation is different GN.
Gun mode change Stroke/No Stroke mode might have To prevent spot welding
SVGN-390 detected while welding been changed while executing spot point being skipped, the
Torque CF cannot be Torque conversion factor cannot be Confirm the gear ratio of
SVGN-391 calculated. calculated because divide-by-zero is servo gun.
This TW**.TP is not This TWD program is for R-J3iB. R-30iB Replace TW***.TP to
SVGN-392 supported. does not supported this. TWK***.PC like the
Panel detection calibration has started. This message is provided
Note that detection calibration occurs for informational
Panel detection calib during autotuning, and also when user purposes only, it is not a
SVGN-393 started. invokes it on detection calibration problem.
Panel detection calib This message is provided
SVGN-394 ended. Panel detection calibration has ended. for informational
Automatic zero calibration has started. This message is provided
Note that detection calibration occurs for informational
SVGN-395 Auto-zero calib started. during autotuning, and also when user purposes only, it is not a
Automatic zero calibration process has This message is provided
SVGN-396 Auto-zero calib ended. ended. for informational
Thickness check calibration has started. This message is provided
Thickness check calib Note that thickness check calibration for informational
SVGN-397 started. occurs during autotuning, and also purposes only, it is not a
Thickness check calib Thickness check calibration process has This message is provided
SVGN-398 ended. ended. for informational
This alarm merely provides additional
information for SVGN-274 alarm. Min
Speed(mm/sec) speed and max speed specify speed
SVGN-399 min:%.1f, max:%.1f range observed during panel detection Refer to SVGN-274
execution mode via
A tp program started (or resumed) and Touchup setup screen: a.
spot program touchup function is if tp is disabled, set
enabled with execution mode = TCHUP Execution mode for AUTO
Spot touchup+weld + WELD. This means that points will be = TOUCHUP mode, b. if tp
SVGN-400 enabled ! touched up, and then spot will execute. is enabled, set Execution
enabled in TCHUP + WELD mode during warning is operator
spot instruction execution, so touchup notification, this is not a
process will not begin until next spot. fault condition. In order to
Conditions leading to this case are: 1. execute touchup
Start program with spot program immediately, either
Spot touchup+weld touchup disabled 2. Pause program execute shift backward (to
SVGN-401 pending. during execution of spot instruction 3. restart spot) or abort
Power-up attach occurred, gun This alarm is not a
connnect input and/or gunidentify problem. However, set
input is mapped, and $SHC_CFG.$ATIO_WT_AL
Attach io wait time: $SHC_CFG.$ATIO_WT_ALM = TRUE. M = FALSE, if you wish to
SVGN-402 %.1f(sec) This message is posted to report time disable this alarm.
execution mode via
A tp program started (or resumed) and Touchup setup screen: a.
spot program touchup function is if tp is disabled, set
enabled with execution mode = VERIF + Execution mode for AUTO
Spot verify+weld WELD. This means that points will be = TOUCHUP mode, b. if tp
SVGN-403 enabled ! touched up, and then spot will execute. is enabled, set Execution
enabled in VERIF + WELD mode during warning is operator
spot instruction execution, so touchup notification, this is not a
process will not begin until next spot. fault condition. In order to
Conditions leading to this case are: 1. execute touchup
Spot verify+weld touchup disabled 2. Pause program execute shift backward (to
SVGN-404 pending. during execution of spot instruction 3. restart spot) or abort
Program touchup executed with This is merely a warning
execution mode set to TCHUP+WELD or for
WeldComp: Prg=%s, VERIFY+WELD. This message indicates feedback/confirmation.
SVGN-405 Ln=%d that weld operation completed, after Set
Specified TP program was opened No action is needed. This
successfully. Note that this message is alarm is merely a message
SVGN-406 Opened:%s successfully. only posted after a program open to inform you that a
This program should
already exist in memory,
so open failure is
unexpected. If open
Specified TP program could not be failure occurs, system
opened - program may have been reloads program from
SVGN-407 Open:%s failed. cleared. Refer to cause code for reason. FRS, and no action is
Specified TP program was loaded. Note No action is needed. This
SVGN-408 Loaded:%s successfully that this message is only posted after a alarm is merely a message
Specified TP program could NOT be This program should
loaded - program may have been always on FRS, so load
SVGN-409 Load:%s failed. deleted. Refer to cause code for failure is unexpected.
Specified TP program could NOT be Contact your FANUC
SVGN-410 Close:%s failed. closed. Refer to cause code for reason. America Corporation
TP Line data could not be read, for Re-execute current
specified program at line. TP program process again: program
may be corrupt, so it was automatically will reload and line data
SVGN-411 Get line failed(%s). cleared. See cause code for more will be read again. Contact
TP Line data could not be set, for Re-execute current
specified program at line. TP program process again: program
may be corrupt, so it was automatically will reload and line data
SVGN-412 Set line failed(%s).
Pressure Check Init cleared. See cause code for more will be set again. Contact
SVGN-413 Start
Pressure Check Init Pressure Check Init Start No remedy.
SVGN-414 CompleteCheck
Pressure Pressure Check Init Complete No remedy. Confirm Gun
SVGN-415 Tolerance Exceed
Pressure Adjustment Pressure Check Tolerance Exceed Condition.
No remedy. Confirm Gun
SVGN-416 Tol Exceed Pressure Adjustment Tolerance Exceed Condition.
Select Non-Adaptive2 Search motion is done, but upper For precision stabilization,
SVGN-417 GUN:%d detect condition is not set Non- it is better that Non-
A tp program started (or resumed) and If touchup (not measure
Det offset for Simple spot program touchup function is offset) mode is desired,
SVGN-418 search enabled ! enabled with execution mode = MEAS change execution mode
enabled in MEAS OFS mode during spot warning is operator
instruction execution, so spot program notification, this is not a
touchup will not start until next spot. fault condition. In order to
Conditions leading to this case are: 1. execute program touchup
Det offset for Simple touchup disabled 2. Pause program execute shift backward (to
SVGN-419 search pending. during execution of spot instruction 3. restart spot) or abort
A tp program started (or resumed) and If touchup (not pass
TOUCHUP Pass check spot program touchup function is check) mode is desired,
SVGN-420 mode enabled ! enabled with execution mode = PASS change execution mode
enabled in PASS CHECK mode during warning is operator
spot instruction execution, so spot notification, this is not a
program touchup will not start until fault condition. In order to
next spot. Conditions leading to this execute program touchup
case are: 1. Start program with spot immediately, either
TOUCHUP Pass check program touchup disabled 2. Pause execute shift backward (to
SVGN-421 mode pending. program during execution of spot restart spot) or abort
SVGN-422 Incorrect Override
Fixed tip capwear:%s Incorrect
Cap wear Override
value exceeds value specified Set correct
Replace capoverride
or increase
SVGN-423 over limit.tip
Movable in $TWGUN.
Cap wear value exceeds value specified value in $TWGUN.
Replace cap or increase
SVGN-424 capwear:%s over limit. in $TWGUN. value in $TWGUN.
Fixed tip wear rate:%s Rate of wear exceeds tolerance Confirm that wear value is
SVGN-425 overtol. specified in $TWGUN. not excessive, for this
Movable tip wear Rate of wear exceeds tolerance Confirm that wear value is
SVGN-426 rate:%s overtol. specified in $TWGUN. not excessive, for this
Fixed tip wear%%:%s Wear percentage exceeds tolerance Confirm that spot process
SVGN-427 overtol. specified in $TWGUN. is operating correctly.
Movable tip Wear percentage exceeds tolerance Confirm that spot process
SVGN-428 wear%%:%s overtol. specified in $TWGUN. is operating correctly.
Gun tip compression (non-capwear
change) exceeds tolerance specified in
Fixed tip $TWGUN. Ideally, gun tip compression
compression:%s should be 0. However, compression can Replace electrode / tip
SVGN-429 overtol. become greater than 0 over time, holder.
Gun tip compression (non-capwear
change) exceeds tolerance specified in
Movable tip $TWGUN. Ideally, gun tip compression
compression:%s should be 0. However, compression can Replace electrode / tip
SVGN-430 overtol. become greater than 0 over time, holder.
Close stroke limit is less than max wear Increase stroke limit, if
Max wear not value. Gun tip compression is too large possible (if new limit does
SVGN-431 reachable(clslim=%s) and/or close limit is too small. not exceed extension of
Nominal:%s, Cause message posted with alarms 425- None - SVGN-432 is
SVGN-432 Tolerance:%s 430 for additional info. merely supplemental info
Insufficient memory for $TWGUN#V#[] could not be created Increase memory or
SVGN-433 TWDIAG due to lack of memory. reduce
Cause message posted with alarm 431 Replace caps if wear is too
SVGN-434 Wear(%s) Compress(%s) for additional info. large. Replace shank/cap
Open robot tip with
following ways and retry.
Open robot tip & search Direction of Lower panel search motion In Spot point touchup,
SVGN-435 again. was wrong. open robot tip by jog. In
Calibration point 2 torque value ≤=
Deflection cal pt2 ≤= $minimum_trq. Therefore, torque Increase torque value for
SVGN-436 minimum_trq. value for calpt2 = calpt1. Torque values calibration point2.
Thickness check calibration opens gun
to original position after calibration,
but original (current) position is 1. Jog gun in close
Gun position exceeds unreachable, because it is past open direction, until open limit
SVGN-437 openlimit.
Axis number does not stroke limit. Thickness check calibration is not exceeded.
Make sure axis number is
SVTL-001 exist Axis number doesn't exist. right.
This should only happen
Update trq_lim Time out while Updating servo in desktop unit or virtual
SVTL-002 timeout(g:%s) parameters. robot. Otherwise, please
Other Servo Tool Servo Tool is active when TP program is Abort the original TP
SVTL-003 running executed. program which activates
Torque Limit too small Torque limit used in Servo Tool Set torque limit in Servo
SVTL-004 (ID:%s) schedule ID is less than 0.1%. Tool schedule ID to more
Group number Group number in Servo Tool schedule Use group number 0 in
SVTL-005 mismatch (ID:%s) ID does not match with current TP Servo Tool schedule or
No contact or dest. The destination position has been Make sure part is present
SVTL-006 reaches
Paused while detecting reached before contact detected. or
Notincrease torque limit.
pause program while
SVTL-007 part
Continue paused is paused while
Program continues detecting
after pause part. Not
while part pause
detecting.
program while
SVTL-008 detection detecting. part detecting.
Zero group mask program is running
SVTL-009 Servo Tool is active when Servo Tool is active. This is warning only
Time out occured while detecting part Make sure part present,
SVTL-010 Detecting timeout and coasting to the destination increase torque limit, or
Axis Limit (G:%d A:%d Software axis limit occurred while axis This is a warning to
SVTL-011 U:%d) is under low torque for G: group, A: remind the axis may be
forward kinemtics failed or unknown Change offset value from
SVTL-012 Cannot update position position type of taught points menu
HOLD button is being You attempted an operation while the Clear the hold button
SYST-001 WARN pressed hold button (input) is pressed. (input), and try the same
Meaning: The condition that the robot
is being held is locked by the program,
and it could not be cleared. If a HOLD
statement is executed in a Karel Wait until the UNHOLD
program, the held condition can only statement is executed by
PAUSE. HOLD is locked by be cleared by the same program using the karel program, or
SYST-002 G program the UNHOLD statement/action, or by abort the karel program.
The attempted operation could not be Disable the teach
SYST-003 WARN TP is enabled done because the teach pendant is pendant, and try the same
The attempted operation could not be Turn the REMOTE switch
SYST-004 WARN SOP is enabled done because the System Operator on the SOP to REMOTE
Turn the REMOTE switch
to local (if the operation is
The attempted operation could not be attempted from the SOP),
UOP is the master done because the User Operator Panel or set the $RMT_MASTER
SYST-005 WARN device is enabled. system variable correctly.
attempted from the SOP),
The attempted operation could not be or set the $RMT_MASTER
SYST-006 WARN KCL is the master device done because KCL is the master device. system variable correctly.
The attempted operation could not be attempted from the SOP),
NETWORK is the master done because the NETWORK command or set the $RMT_MASTER
SYST-007 WARN device processor is the master device. system variable correctly.
The system variable $RMT_MASTER is attempted from the SOP),
Nothing is the master set to disable all devices. Therefore, no or set the $RMT_MASTER
SYST-008 WARN device remote device can issue motion. system variable correctly.
The attempted operation could not be Close the safety fence,
SYST-009 WARN Safety Fence open done becauseofthe
The number tasksafety fence is the
has reached open. and tryone
Abort theofsame
the running
SYST-010 WARN Max num task reached maximum. task.
The system has failed to run the Refer to the error cause
SYST-011 WARN Failed to run task program. code.the
Turn Useremote
MENU switch
to
SYST-012 WARN Not in remote Remote condition is not satisfied. on.
Invalid program The specified PNS number is not in the Specify correct program
SYST-013 WARN number range of 1 to 9999. number.
PNS operation has failed by some Refer to the error cause
SYST-014 WARN Program select failed reason. code. Use MENU to
Robot Service Request RSR operation has failed by some Refer to the error cause
SYST-015 WARN failed reason. code. Use MENU to
SYST-016 WARN ENBL signal is off
Single step operation ENBL signal in UOP is off Set ENBL signal ON
SYST-017 WARN effective Single step operation is effective Disable single step switch
Continuing from Attempt to continue program from Respond YES or NO in the
SYST-018 WARN different line different line from paused line prompt box on at the
Select a program from the
SYST-019 WARN Program not selected Program has not been selected program select menu on
Program not verified by Program specified by PNS is different Select a correct program
SYST-020 WARN System
PNS not ready, press from
An current
error selected
has been program.
detected This
by the from the
Press program
RESET select
to clear error
SYST-021 WARN reset system condition
PNS not zero, cannot Paused program cannot be continued if Set all PNS input ports to
SYST-022 WARN continue PNS input ports are not zero This error OFF
SYSTE Teach Pendant Check the teach pendant
SYST-023 M communication error A communication cable is broken. cable. Replace the cable if
PNSTROBE is OFF. Because PNSTROBE is off, prod_start Set PNSTROBE input to
SYST-024 WARN Cannot start exec could not be processed ON
Teach Pendant is The type of teach pendant being Connect the same type of
SYST-025 WARN different type connected, is different from the one teach pendant as
System normal power System has executed normal power This is just a notification.
SYST-026 WARN up startup You do not have to do
HOT start has failed for one of the
following reasons: 1. Power failed
PAUSE. HOT start failed during system start up. 2. Flash ROM COLD start is selected
SYST-027 G (Error:%d) module was changed. 3. A run-time automatically.
$PWR_HOT,$PWR_SEMI program has Decrease program size so
SYST-028 WARN (%s) Program timed out been aborted by the system due to that it can be executed
PAUSE. Robot was connected The connect/isolate key was turn to the This is just a notification.
SYST-029 G (Group:%d) connect side You do not have to do
PAUSE. Robot was isolated The connect/isolate key was turn to the This is just a notification.
SYST-030 G (Group:%d) isolate side You do not have to do
SYSTE RESET keys. 3. While still
SYST-031 M F-ROM parity
ENBL signal from UOP is An error has occurred accessing F-ROM pressing
Determine theand
SHIFT and the
correct
SYST-032 WARN lost signal from UOP
SFSPD ENBL input signal from UOP is lost cause of loss
Determine andof correct
this signal.
the
SYST-033 WARN is lost signal from
HOLD SFSPD input signal from UOP is lost cause of loss
Determine andof correct
this signal.
the
SYST-034 WARN SOP/UOP is lost HOLD input signal from SOP/UOP is lost cause of loss of this signal.
Low or No Battery Replace the Old Battery
SYST-035 WARN Power on MAIN Battery in PSU board is low in power. with a new battery of
Semi power failure This is just a notification.
SYST-036 WARN recovery System did semi-hot start You do not have to do
ABORT. Please fix the CE Sign key
SYST-037 G Key switch broken Improper input from Key switch switch
PAUSE. Operation mode T1 This is just a notification.
SYST-038 G Selected Operation mode T1 Selected You do not have to do
PAUSE. Operation mode T2 This is just a notification.
SYST-039 G Selected Operation mode T2 Selected You do not have to do
PAUSE. Operation mode AUTO This is just a notification.
SYST-040 G
PAUSE. Selected
Ovrd Select could not Operation mode AUTO Selected You do not have to do
SYST-041 G ENABLED DI index is invalid Please set valid DI index
The mode switch was changed from T1
or T2 mode to AUTO mode and the
PAUSE. DEADMAN was already pressed. The Release the DEADMAN
SYST-042 G DEADMAN defeated DEADMAN must be released when and press RESET.
PAUSE. TP disabled in T1/T2 The mode selector is in T1 or T2 and Turn the TP ON/OFF
SYST-043 G mode the TP ON/OFF switch is in the OFF switch to ON. Press RESET.
The mode selector is in T1 or T2 and
SYSTE (Abnormal) TP disabled the TP ON/OFF switch is in the OFF Call your FANUC Robotics
SYST-044 M in T1/T2 mode position and SVON is ON. This is an technical representative.
PAUSE. TP enabled in AUTO The mode selector is in AUTO and the Turn the TP ON/OFF
SYST-045 G mode TP ON/OFF switch is in the ON position switch to OFF. Press
Either 1.Control Reliable or CE Mark If the Control Reliable/CE
hardware exists but the CR or CE Mark Mark option has not been
option has not been loaded,or 2.The loaded, load the Control
Control Reliable/CE Mark option has Reliable/ CE Mark option.
SYSTE Control Reliable/CE been loaded but the hardware is not If it has been loaded then
SYST-046 M Mark config mismatch available. this is a system without
Continuing from distant Attempt to continue program from Respond ABORT or
SYST-047 WARN
ABORT. position
NECALC couldn't get distant position
OS couldn't give from stopped
NECALC position.
soft part CONTINUE in the prompt
Please increase
SYST-048 G
ABORT. work memory
SFCALC couldn't get enough
OS memory
couldn't give SFCALC soft part Controller's
Please memory
increase
SYST-049 G work memory
Invalid time in trigger enough memory Controller's
Time must bememory
less than
SYST-050 WARN request Invalid time used in TG request 6,000,000 us
Excessive time iin trigger routines First Event or scan routine
number indicates event routine (1) or need to be made more
scan routine (2). Second number efficient, scan rate
indicates individual overrrun (1) or reduced, or system
excessive cumative CPU use (2). Third variable values increased
PAUSE. SYTG overrun: %d %d number: event number(hexadecimal) to permit more CPU
SYST-051 G %x %d %d
Trigger slot already or scan routine address Fourth number: usage.
Use cancel request to
SYST-052 WARN used: %d Specified entry already used delete old entry
SYST-053 WARN Invalid
Event-IDfast_DIN
alreadyno: %d
used: Specified Fast-DIN number is invalid Use Valid
uniqueFast-DIN
event ID or
SYST-054 WARN %d Specified event ID is already in use in
not presently cencel previous request
SYST-055 WARN Event-ID not found: %d use Check event ID
A call to syscnrtn was made when the Either cancel scan
scan list was full. A maximum of 10 routines that are no
SYST-056 WARN Scan routine list full scan routines, including the standard longer needed or combine
The interval parameter in a call to Use a value in the range 1-
SYST-057 WARN Illegal interval syscnrtn was greater than 1000000 (1 1000000
syscnrtn was called specifying a routine Don't request the same
SYST-058 WARN Duplicate scan routine and data_p that is already being rtn/data_p twice
syclclsc was called with a routine and Don't cancel a non-
SYST-059 WARN Scan routine not active data_p that that does not match any existent scan
Duplicate cond/act syaddtbl called with pointer to table
SYST-060 WARN table that is already in the scan list Add table only once
syaddtbl called when all 10 Cancel tables that are no
SYST-061 WARN Scan table list full condition/action table slots are already longer needed or combine
sycncltb called with cond/act table that Check for duplicate
SYST-062 WARN Scan table not active is not active. sycncltb call or wrong
Scan time record seq System error: consecutive time interval Contact Fanuc Robotcs
SYST-063 WARN error start calls wth information on
System error: Invalid data in scan table
The following can result in this error: Contact Fanuc Robotcs
Too many cond/action sets (max = 10) wth information on
SYST-064 WARN Bad scan table data Invalid condition code Invalid action events leading up to error
ABORT. SFCALC task can't get enough MPU Please reduce some
SYST-065 G SFCALC overrun power. software options or
Too much communication
PAUSE. Teach Pendant Communication with the advanced may have caused the
SYST-066 G
SYSTE communication error Teach HSSB
Panel Pendant was interrupted.
communication is interrupt.
Check panelCheck
HSSBthe teach
SYST-067 M Panel HSSB disconnect disconnected. hardware connection.
Program number out of The selected style number is zero or Select a valid style
SYST-069 WARN range greater than the size of the style table. number, or adjust the size
No program name in There is no program name in the style Put a valid program name
SYST-070 WARN table table. in the proper place in the
The selected style program does not Create a program for the
SYST-071 WARN Program not found exist on the controller.
The selected style program is not style,
Set theorVALID
put a field
valid to YES
SYST-072 WARN Program not enabled enabled. in the style table.
Manual selection The style input does not match the The PLC must send a style
SYST-073 WARN mismatch manually selected style.
Communications with the Karel shell code that matches the
SYST-074 WARN Karel shell failed extension failed. Cold start the controller.
The shell was unable to start due to
SYST-075 WARN Shell init failure resource allocation failures. Cold start the controller.
Shell condition setup The shell could not set up its required
SYST-076 WARN Entered
failure INTERLOCK condition
The handlers.
controller is interlocked with the Cold isstart
This the controller.
an informational
SYST-077 WARN mode PLC
The controller is isolated from PLC message. There is no
This is an informational
SYST-078 WARN Entered ISOLATE mode control. message. There is no error
One or more of the pre-startup system Look for a previous
SYST-079 WARN Startup check failed checks failed. message
Reset thethat faultindicates
before
SYST-080 WARN Fault must be reset The system is in a faulted state. trying the operation
The program can not start because the Move the robot to the
SYST-081 WARN Not at home position robot is not at the defined home home position.
The program can not be resumed
Not within resume because the robot has been moved Jog the robot back to the
SYST-082 WARN tolerance from the position on the path where it Unsimulate
correct position.
all I/O before
SYST-083 WARN I/O is simulated One or more I/O points are simulated.
The system has forced all I/O to be trying to start the
This is an informational
SYST-084 WARN I/O forced unsimulated unsimulated. message.
SYST-085 WARN Gen override not 100% The general speed override is not 100% Set the override to 100%.
Gen override forced to The system has forced the general This is an informational
SYST-086 WARN 100% speed override to 100% message.
SYST-087 WARN Prog override not 100% The program override is not 100%. Set the override to 100%.
Prog override forced to The system has forced the program This is an informational
SYST-088 WARN 100% speed
The override
machine to is
lock 100%.
on, motion can not message.
SYST-089 WARN Machine lock on occur.
The system has forced machine lock to Turn This isoff
anthe machine lock.
informational
SYST-090 WARN Machine lock forced off the off state. message.
Take the system out of
SYST-091 WARN Single step active programhas
The system is in single-step
forced mode.
single-stepping single-step
This mode.
is an informational
SYST-092 WARN Single step forced off to be off. message.
The program can not start because the Make the process
SYST-093 WARN Process not ready process is not ready. equipment ready for
The system has forced the process This is an informational
SYST-094 WARN Process forced
ABORT.
Remote diagnose ready equipment
Internal to in
Error theRemote
ready state.
Diagnose message.
SYST-095 G internal error
ABORT.
Designated task is not function.
Internal Error in Remote Diagnose Internal error
SYST-096 G valid function.
SYST-097 WARN Fail toModem
Card initialize
is Modem function.
SYST-098 WARN removed
Card Modem is not function.
SYST-099 WARN responded function.
SYST-100 WARN DSR in Modem OFF function.
SYST-101 WARN Connection is stopped
ABORT. function.
SYST-102 G HDI not recorded function.
User bypassed not-home condition at Internal
None error - warning
needed
SYST-103 WARN Not-home ignored program startup. only.
Resume tolerance User bypassed TCP position tolerance None needed - warning
SYST-104 WARN ignored at program
User bypassedresume.
I/O simulated at only. needed - warning
None
SYST-105 WARN Simulated I/O ignored program startup. only.
User bypassed general override < 100% None needed - warning
SYST-106 WARN Gen override ignored at program startup. only.
User bypassed program override < None needed - warning
SYST-107 WARN Prog override ignored 100% at program
User bypassed startup.
machine lock at only.
None needed - warning
SYST-108 WARN Machine lock ignored program startup. only.
User bypassed single-step condition at None needed - warning
SYST-109 WARN Single step ignored program startup.
User bypassed process not ready at only.
None needed - warning
SYST-110 WARN Process ready ignored program startup. only.
Enable at least one
No home position defined for motion reference position for
SYST-111 WARN No home pos defined group 1. group 1 as a home
The production start input, which is Set up a production start
No production start required with the current program input in the Cell Input I/O
SYST-112 WARN input defined selection options, has not been menu and restart the
The style number input group, which is Set up a style number
No style input group required with the current program input group in the Cell
SYST-113 WARN defined selection options, has not been Input I/O and Group I/O
One or more RSR inputs, which are Set up the RSR inputs in
required with the current program the Cell Input I/O menu
SYST-114 WARN No RSR input defined selection options, have not been and restart the robot.
One or more PNS selection inputs, Set up the PNS selection
No PNS select input which are required with the current inputs in the Cell Input I/O
SYST-115 WARN defined program selection options, have not and Group I/O menus and
One or more RSR echo outputs, which Set up the RSR echo
No RSR echo output are required with the current program outputs in the Cell Output
SYST-116 WARN defined selection options, have not been I/O menu and restart the
The PNS echo outputs, which are Set up the PNS echo
No PNS echo output required with the current program outputs in the Cell Output
SYST-117 WARN defined selection options, have not been I/O and Group I/O menus
No PNS strobe input The PNS strobe input, which is required Set up a PNS strobe input
SYST-118 WARN defined with the current program selection in the Cell Input I/O menu
The acknowledgement strobe output, Set up an
No echo strobe output which is required with the current acknowledgement strobe
SYST-119 WARN defined program selection options, has not output in the Cell Output
One or more style option inputs, which Set up the style option
No style option input are required with the current program inputs in the Cell Input I/O
SYST-120 WARN defined selection options, have not been menu and restart the
The decision code input group, which is
Set up a decision code
No decision input group required with the current program input group in the Cell
SYST-121 WARN defined selection options, has not been Input I/O and Group I/O
The echo/manual style output group, Set up a style output
No style output group which is required with the current group in the Cell Output
SYST-122 WARN defined program selection options, has not I/O and Group I/O menus
One or more style option outputs, Set up the style option
No option output which are required with the current outputs in the Cell Output
SYST-123 WARN defined program selection options, have not I/O menu and restart the
The decision code output group, which Set up a decision code
No decision output is required with the current program output group in the Cell
SYST-124 WARN group defined selection options, has not been Output I/O and Group I/O
No in-cycle output The in-cycle output, which is requiredSet up an in-cycle output
SYST-125 WARN defined with the current program selection in the Cell Output I/O
No task-OK output The task_OK output, which is required Set up a task-OK output in
SYST-126 WARN defined with the current program selection the Cell Output I/O menu
The isolate mode output, which is Set up an isolate mode
No isolate output required with the current program output in the Cell Output
SYST-127 WARN defined selection options, has not been I/O menu and restart the
The interlock mode output, which is Set up an interlock mode
No interlock output required with the current program output in the Cell Output
SYST-128 WARN defined selection options, has not been I/O menu and restart the
The manual style request output, whichSet up a manual style
No manual style output is required with the current program request output in the Cell
SYST-129 WARN defined selection options, has not been Output I/O menu and
The shell is already running an activeFinish or abort the current
SYST-130 WARN Program still running program. program before
Invalid manual style The manual style request cannot be Examine the secondary
SYST-131 WARN request done. There is also a secondary error error message.
Manual request timed The specified manual style was not Determine why the PLC
SYST-132 WARN out requested by the PLC within the did not respond to the
System trigger request A request for a system trigger functionDefer any of these
SYST-133 WARN early (scan routine, etc) was made before the
requestsoruntil
Reduce late in the
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
A frequency input connected to one of (1000 Hz) and the system
the HDI inputs momentarily or for an variable
extended time had a frequency $FQINT_SETUP[n].$FREQ_
exceeding the setting for the maximum. MAX_AL to 1020. If the
Max. freq. exceeded The channel or input number is frequency dip switch
SYST-134 WARN ch.: %d indicated in the alarm text. setting on the HDI Pulse
Invalid Clock, Please The system clock has an invalid time. Reset the system Clock
SYST-135 WARN Reset The clock may not have been set. using the SYSTEM Clock TP
The system clock was reset by either an Check the system Clock
SYST-136 WARN System Time was reset Operator or by the SNTP protocol (if using the SYSTEM Clock
The requested device is not installed on Request only valid
SYST-137 WARN Motherboard
Device not found
not the motherboard.
The specified motherboard is not devices.only installed
Specify
SYST-138 WARN Invalid
installed
motherboard installed.
The specified motherboard index is not motherboards.
This is a programming
SYST-139 WARN request a valid value. error. Specify only index 0
An invalid interrupt number was Specify an IRQ from 3
SYST-140 WARN Invalid IRQ specified specified by the device driver. through 7 only.
BMON was automatically updated
SYST-141 WARN BMON was updated because of a newer version. Check BMON version.
ABS time in sytmrev in The time specified for a timed event Specify a later time for the
SYST-142 WARN past has already passed
pkt_data_size The event
parameter in will event
Use size <=
SYST-143 WARN pkt_data_size too big syinpev_gen call is too big. MAX_PKT_DATA in
Invalid or unassigned DOUT number Set the sysem variable to
specified in the indicated system zero (no port used) or to a
SYST-144 WARN Bad DO specfied by %s variable. valid port number and
DO specfied by %s DOUT specified in the indicated system Set the device to which
SYST-145 WARN OFFLINE variable is Off-line. the DOUT is assigned On-
n_pkts_parameter in syinpev_gen call Use value in the range of
SYST-146 WARN n_pkts invalid is invalid. 1 to 20, or zero if
PAUSE. Dynamic Brake is Dynamic Brake is disabled by dynamic If you would like to turn
SYST-148 G Disabled brake release request signal on servo, please turn off
Dynamic Brake is Dynamic Brake is enabled because
SYST-149 WARN Enabled dynamic brake release request is It is message only.
The program is started except from the Respond YES or NO in the
SYST-150 WARN Cursor is not on line 1 1st line. prompt box on at the
After the program is started except Start the same program
SYST-151 WARN Start again (%s, %d) from the 1st line, respond YES in the again.
Cannot force DO's in Attempt to force output signal while Exit AUTO mode before
SYST-152 WARN AUTO mode controller is in AUTO mode doing this operation
Cannot SIM/UNSIM Attempt to force output signal while Exit AUTO mode before
SYST-153 WARN DO's in AUTO mode controller is in AUTO mode doing this operation
No start in Production start received when Put controller into AUTO
SYST-154 WARN ISOLATE/BYPASS mode controller is in ISOLATE or BYPASS or INTERLOCK mode
Reduce some software
ARM Bending Control function cannot options or disable some
SYST-155 SERVO ABC overrun
SYSTE get enough MPU power. motion groups which had
SYST-156 M
SYSTE CE/RIA software does CE/RIA software does not exist in this Mount
Unknown hard ware This PCB is not used on this controller. the correct
Install CE/RIA optionPCB.
to
SYST-157 M not exist controller. this controller.
PAUSE. Robot cannot move in The mode selector is in T2. Robot Change the mode switch
SYST-158 G T2 mode cannot move in T2 mode. to T1 or AUTO mode.
GO %d for Error Output GO dedicated for the Error Output Configure GO dediocated
SYST-159 WARN not configured feature is not configured. for the Error Output
PAUSE. Value output to GO %d Value to be outputted to GO with Error Configure GO using more
SYST-160 G out of limit Output feature is out of limit for this digital outputs.
Cannot start Remote Remote diagnostics are not started Turn off the servo then
SYST-161 WARN diagnostic
Servo On during because
The servo is turned on during remote retry
the servo status is on. thethe
Turn off remote
servo before
SYST-162 WARN Remote diagnostic diagnostics. attempting remote
Cannot operate IO An attempt was made to operate I/O Do not operate I/O during
SYST-163 WARN during Remote during remote diagnostics. remote diagnostics.
Too much communication
Teach Pendant Communication with the teach may have caused the
SYST-164 WARN communication error pendant was interrupted. interrupt. Check that the
Intermittent errors occurred during Check to determine if
TP intermittent communication with the teach there is any source of
SYST-165 PAUSE communication error pendant. electrical noise. Check
Perform the following: 1.
Intermittent errors occurred during Check to determine if
TP intermittent communication with the teach there is any source of
SYST-166 WARN communication error pendant.
An attempt was made to operate an electrical
Do noise. an
not operate 2. Check
SYST-168 Robot(G:%d) is isolated isolated Robot. isolated Robot.
S/W Registration is in effect. This alarm Display the S/W
S/W Registration is is posted when there are more than 28 Registration screen: 1.
SYST-169 WARN temporary days until registration expires. Press MENUS. 2. Select
S/W Reg. expires in %d is posted when there are between 14 Registration screen: 1.
SYST-170 WARN days and 28 days until registration expires. Press MENUS. 2. Select
S/W Reg. expires in %d is posted when there are between 1 Registration screen: 1.
SYST-171 PAUSE days and 14 days until registration expires. Press MENUS. 2. Select
S/W Registration has is posted when registration has Registration screen: 1.
SYST-172 PAUSE expired expired. The robot cannot be operated Press MENUS. 2. Select
S/W Registration is in effect. Display to Display the S/W
See S/W Reg Screen the S/W Registration screen for more Registration screen: 1.
SYST-173 WARN (STATUS) details. Press MENUS. 2. Select
SYSTE S/W Reg. active, option Software Registration is in effect but Load the Software
SYST-174 M missing the Software Registration option is not Registration Option.
S/W Registration is in effect. The The System was updated.
System was updated. This message is This message is for
SYST-175 WARN System was updated for reference only. No action is reference only. No action
The system software is updated by the
SYST-176 WARN Software was updated Auto Software update function. None.
The attempted operation could not beMake sure that the
RobotLink master is the done because the robot is under Remote/Local Setup item
SYST-177 WARN master control of the RobotLink Master robot.
in the System
book(%d) was not The book of operation logbook was not
Reduce the number of
SYST-188 created created. books or $LOG_BUFF[
SYST-189 There is no book There is no book of operation logbook.
None.
HMI Mode - key iPendant HMI Mode is enabled and this
Enable the key in the
SYST-190 unavailable specific key is disabled. iPendant Setup screen.
TP (on Rob#%d) More than one teach pendant is Disable the teach pendant
SYST-195 PAUSE enabled in T2 mode enabled while in T2 mode within the which is not being used
The desired operation could not be Disable the teach
SYST-196 WARN Enabled TP exists (H%x) performed because teach pendants pendants which are not
The master robot did not receive a Check and repair any
Multi-arm Watchdog heartbeat message from the slave broken network
SYST-197 PAUSE alarm robots within the time specified by the
connections.
All slave robots have
Auto/T1/T2 switch to be
AUTO. $RMT_MASTER
system variable must be 4
(Robot Link). Refer to the
Some slave robots are not ready to run FANUC Robotics Software
SYST-198 WARN Slave Robot Not Ready a program. Reference Manual,
The selected robot program could not If you are selecting the
Def Prog NOT change be changed because the robot has program using a teach
SYST-199 WARN (TP disbl) been defined as a slave to a master pendant, enable the teach
Only the teach pendant on the master Use the teach pendant on
Only Master TP may robot can perform the SHIFT- the master robot to
SYST-200 WARN FWD/BWD FWD/BWD operation for multi-arm perform the SHIFT-
The master robot number does not Verify the master robot
SYST-201 WARN Master mismatch match with the one specified in the number in the slave
One or more of the specified slave Verify that the system
Incorrect $rmt_master robots does not accept the command variable $RMT_MASTER is
SYST-202 WARN on Slave robot from the master robot because of set to 4 on all slave
Robot #%d has become This is a notification that a robot has
SYST-203 WARN online been successfully added to the robot None.
Multi Program start in The program run sequence is still in Wait until the previous
SYST-204 WARN progress progress. request is taken care of
The teach pendant FWD or BWD key Press the SHIFT key in
SYST-205 WARN NO
Operation canceled by was
action specified pressed without
The operation also pressing
was canceled the
by pressing addition to pressing the
SYST-206 WARN RESET key the RESET key. None.
Display the error history
Message posted at An error message has been posted on screen of the robot where
SYST-207 PAUSE robot #%d another robot. the error was posted, and
The attempted operation is not Be sure to perform only
SYST-208 PAUSE Feature NOT supported supported. For example, you tried to the supported operations.
The process synchronization condition 1. Check the program
Process Sync Time-out was not satisfied within the specified logic (for a seq_id
SYST-210 PAUSE error time-out limit. inconsistency, for
The communications processor did not and then turn it on again.
SYSTE Comm processor Time- respond within the specified timeout If the alarm persists
SYST-211 M out error limit. document the events that
Need to apply to DCS Mastering data or robot parameters Press F3(APPLY) in the
SYST-212 PAUSE param are
A changed,
user cycled but they
power are the
from not function
applied DCS menu.
SYST-213 PAUSE User power cycle menu. None
A DCS ESTOP occurred. This occurs only Set
SYST-214 PAUSE DCS ESTOP when $DCS_CFG.$TEST_PARAM1 bit 0 $DCS_CFG.$TEST_PARAM
A DCS ESTOP occurred. This occurs only Set
SYST-215 PAUSE DCS CSTOP when $DCS_CFG.$TEST_PARAM1 bit 0 $DCS_CFG.$TEST_PARAM
A DCS DCSALM occurred. This occurs Set
SYST-216 PAUSE DCS DCSALM only when $DCS_CFG.$TEST_PARAM1 $DCS_CFG.$TEST_PARAM
The DCS position/speed process setting Set the DCS
DCS pos./speed is not is set to ENABLE, when the hardware is position/speed process to
SYST-217 available not DCS type or the DCS option is not DISABLE, or load the DCS
The Dual Check Safety Position/Speed Delete the Dual Check
Check Function option is loaded, but Safety Position/Speed
DCS Unavailable robot this robot model is not supported. 'i' is check function option.
SYST-218 model G:%x Hex a hexadecimal value and each bit This alarm can be cleared
When 'Position/Speed process' is
enabled, backup files are loaded and
DCS parameter is changed. The
meaning of 'i' is the following. - 1 :
Image backup is loaded. - 2 :
SYSVARS.SV is loaded and DCS Check the setting in DCS
parameter is changed. - 4 : SYSVARS.SV menu, and do the VERIFY
Need to verify DCS is loaded and DCS parameter for robot operation in the DCS top
SYST-219 param (%d) setting is changed. - 8 : SYSMAST.SV is menu.
The process synchronization condition 1. Check the program
SYST-220 PAUSE Sync Time-out error was not satisfied within the specified logic (seq_id
1. Make sure same
Sync Schedule The sync schedule does not match schedule number is used
SYST-221 PAUSE mismatch
Image backup between robots. in the program between
SYST-222 succeeded Image backup was successful. None.
RCRON: Action This notification can be
SYST-230 WARN successful RCRON command was executed. disabled by setting the
RCRON command could not be
executed. This is caused by either an
incorrect crontab file or by the Check md:crontab.dg for
SYST-231 WARN RCRON: Action failed corresponding module not being errors.
RCRON was prevented from running on Too many RCRON jobs
SYST-232 WARN RCRON: Tick missed time. might be executing. Check
RCRON: No response A job on the MAIN processor was not Too many RCRON jobs
SYST-233 WARN from MAIN completed on time. might be executing on
Auto Software Update Restore backup in
SYST-239 failed Last software
The RPS code update failed.
is an invalid BCD in BCD MC:00TEMP and of
Check the status retry the
RPS1,
SYST-242 Invalid RPS code mode. RPS2, ... RPS128.
The program selection by RPS has Refer the cause code.
SYST-243 RPS failed(%s) failed. Typically,
Change the the program
mode switch
SYST-244 Auto mode is required This operation requires Auto mode. to Auto.the mode to
Change
SYST-245 Local mode is required This operation requires Local mode. Local. the mode switch
Change
SYST-246 Teach mode is required This operation requires Teach mode.
a Master ON to Teachthat
Ensure mode.
the Master
SYST-247 Master ON is required situation.
This operation requires no alarm ON situation exists.
SYST-248 Alarm condition situation.
This operation requires the System Clear the
Check thealarm
statussituation.
of the
SYST-249 No system ready input Ready input. requires the Robot
This operation System Ready input.
SYST-250 No robot ready input Ready
This input. requires the Teach Plug
operation Robot the
Check Ready input.
status of the
SYST-251 No teach plug ON input ON input.
This operation requires no Teach Plug Teach Plug ON input.
SYST-252 Teach plug ON input ON input.
This operation requires the Safe Stop Teach Plug
Check ON input.
the status of the
SYST-253 No safe stop input input.
This operation requires no Safe Stop Safe Stop
Check theinput.
status of the
SYST-254 Safe stop input input.
This operation requires the Teach OK Safe Stop input.
SYST-255 No Teach OK input input.
This operation requires the Servo OFF Teach OK
Check theinput.
status of the
SYST-256 Servo
No Ext.OFF
Holdinput
Relase input.
This operation requires the External Servo OFF
Check input. of the
the status
SYST-257 input Hold Release input. External Hold Release
This operation requires that the Check the status of the
SYST-258 Operator panel hold HOLD/RUN switch on the Panel is set to HOLD/RUN switch on the
This operation requires that UI signals Check the setting of
SYST-259 UI signals are disabled are enabled. 'Enable UI signals' in the
SYST-266 Please cycle
System power
is being Robot controller power must be cycled. Cycleapower
Wait moment manually.
for
SYST-267 initialized System initialization is not finished. system to be initialized.
- Do not input the
The program cannot be selected by PNSTROBE pulse signal
Resume program(%s) PNSTROBE pulse signal while resume while resume program is
SYST-268 execution program is being executed. being executed. ( - Input
- Do not input the
PNSTROBE pulse signal
The program cannot be selected by the while fast fault recovery
FFR sequence(%s) PNSTROBE pulse signal while fast fault sequence is being
SYST-269 execution recovery sequence is being executed. executed. - Input the
Ref. Position maximum Reference Positions were enabled Do not exceed maximum
SYST-270 exceeded beyond the maximum number. enabled Reference
Lack of enough space in MC for saving Keep enough space in MC
SYST-271 Lack of MC for saving diagnostic log data. to save data.
Lack of enough space in USB for saving Keep enough space in USB
SYST-272 Lack of USB for saving diagnostic log data. to save data.
Refer to the error cause
code in the Alarm history
An automatic update of BMON failed for a specific reason.
SYST-277 BMON update failed for power
By some reason.
failure, safety parameter file Manually
Please update
apply, BMON
verify and
SYST-278 DCS File is lost is lost. cycle power
Operating panel is This error happens only when using M- When using M-TP, set
SYST-280 Teach mode[P] TP(J897). Operating panel is Teaching operation panel to Auto
Teaching mode input is This error happens only when using M- When changing to Auto
SYST-281 ON[P] TP(J897). When changing to Auto mode, set Teaching mode
Auto mode input is This error happens only when using M- When changing to
SYST-282 ON[P] TP(J897). When changing to Teach Teaching mode, set Auto
$SCR.$MAXNUMUFRAM
and
$SCR.$MAXNUMUTOOL
There is not enough memory to have been reset to the
Not enough memory to support the number of requested number of frames that
SYST-287 increase frames
Write of safety frames. were
Wait aable to be and try
moment
SYST-288 parameter
Request to failed(0x%x)
DCS Write of safety parameter failed againa moment and try
Wait
SYST-289 failed(0x%x) Request to DCS failed again
Cycle power to use new “Apply” and “Verify” of safety
SYST-290 DCS parameter
unknown error parameter completed Cycle power is Please cycle power
TAST-000 WARN (TAST00) Internal system error Cold start controller
The Through Arc Seam Tracking (TAST) Perform a controlled start
TAST-001 WARN TAST global vars failure An
PAUSE. variables are not
IO memory loaded error has
allocation to initialize
Perform motion
a cold start of
TAST-002 G
PAUSE. error
TAST IO IO allocation An
initialization occurred
analog port number error has controller
Check a connection of
TAST-003 G
PAUSE. failed occured process
PerformIO board
a cold start of
TAST-004 G TAST IO start failed IOSETRTN error has occurred controller
Change the value of
weaving frequency to be
TAST-005 WARN
PAUSE. TAST time tick dispose
memory missing Time tick missing in TAST IO memory
An IO memory disposition error has lower
Perform or athe value
cold startofof
TAST-006 G failure occurred controller
Check RPM softparts was
PAUSE. loaded correctly If same
TAST-007 G TAST RPM
PAUSE. saving
incorrect failure
schedule RPM
An invalid TAST schedule number was position
data saving error has occurred Change the IDs schedule
are used at
TAST-008 G num weave freq is too
PAUSE.
TAST specified
An invalid weaving frequency was number the
Change to be in range (1 -
frequency
TAST-009 G low
PAUSE.
TAST software error specified for TAST value to be
Perform higher
a cold start of
TAST-010 G (SRIF)
PAUSE.
TAST software error Internal system error (SRIF) controller
Perform a cold start of
TAST-011 G (PMPT)
PAUSE.
TAST software error Internal system error (PMPT) controller
TAST-012 G (INTP)
PAUSE. Internal system error (INTP) controller
TAST-013 G
PAUSE. software
TAST weave error
freq is too Internal system error controller
Change the value of
TAST-014 G high
Force Beyond High Weaving frequency is too high for TAST check
weaving thefrequency
system orto be
TAST-015 Limit Measured force is beyond its limit change the
check the systemup limit
or
TAST-016 Force Below Low Limit Measured force is below its low limit change the low limit
TAST-017 Sensor is not calibrated Sensor is not calibrated Calibrate the sensor
Exceed lateral tracking Re-teach the welding
TAST-018 limit vertical tracking
Exceed Exceed TAST/AVC lateral tracking limit Re-teach
path, or adjust L_tracking
the welding
TAST-019 limit Exceed TAST/AVC vertical tracking limit path, or adjust V_tracking
TCPP-000 WARN Unknown (TC00) System internal error. Notify FANUC Robotics.
TCP Speed Prediction global variables Perform a controlled start
TCPP-001 WARN No global variables are not loaded. and initialize
Perform a cold motion
start on
TCPP-002 WARN No mmr pointer This is an internal system error. the controller.
TCPP-003 WARN No mir pointer This is an internal system error. the controller.
TCPP-004 WARN No sysvar pointer This is an internal system error. the controller.
Perform a controlled start
TCPP-005 WARN No tcppir
Error pointer
allocating This
A is anoccured
failure internal while
system error.
allocating and initialize
Check amountthe of motion
memory
TCPP-006 WARN memory
Error making TCPP memory. being used by system.
TCPP-007 WARN mailbox
Error making TCPP This is an internal system error. the controller.
TCPP-008 WARN spmktsk This is an internal system error. the controller.
The program positions prior to this line The positions being
are too close together to allow proper executed prior to the one
Pnts too close before speed prediction to be performed. It is specified should be
TCPP-009 WARN line:%d^5
Error writing PLAN also most likely that the robot can not moved further
Perform a cold apart,
start onor
TCPP-010 WARN mailbox This is an internal system error. the controller.
The first motion segment time (time Extend time of first
Pred time skips first between first two taught points) is motion segment (increase
TCPP-011 WARN motion shorter than the prediction equipment distance or decrease
The motion was commanded using an Check program setup to
TCPP-012 WARN Invalid TCPP filter type invalid motion filter type. ensure
Check theproper program
values for the
TCPP-013 WARN Invalid TCPP start pos The start position is not valid.
destination currentthe
Check and previous
values for the
TCPP-014 WARN pos The destination position is not valid. current and previous
Invalid time into The time computed for the current Check the value for the
TCPP-015 WARN segment segment exceeds the segment length. current position data.
TCPP-016 WARN No cfseg data The Cartesian Filter data is not valid. the Cartesian Filter option
Modone computation The internal Motion Done computation No action is necessary,
TCPP-017 WARN error generated an error. but the TCP Speed value
The program positions beginning with Check the error log to find
this line have caused an error condition speed limit errors which
which makes further speed prediction may be causing this TCPP
invalid. The speed prediction task has error to occur. Check the
therefore entered an error handling program beginning with
mode within which it discontinues this line to determine if
speed prediction but provides the the robot can not function
actual robot speed as an output as programmed. Modify
Begin Error Mode at reference with an affective equipment the program to avoid all
TCPP-018 WARN line:%d^5 delay time of 0. (That is, with such speed limit errors. In
A speed override occured beginning Normal prediction will
with this line causing an error condition resume automatically
which makes further speed prediction once the speed override
invalid. The speed prediction task has has propagated through
therefore entered an error handling the system. No further
Speed Ovrd Mode at mode within which it discontinues action is required. The
TCPP-019 WARN line:%d^5 speed prediction but provides the user should avoid this
TCPP internal cartseg Internal error when searching cart No action is necessary,
TCPP-020 WARN error segment. but the TCP Speed value
Allocate TCPP/VC Internal error when allocating memory Check amount of memory
TCPP-021 WARN memory error to TCPP AccuPath segment. being used by system.
PAUSE. Invalid delay time Internal error specified delay time for System problem. Need to
TCPP-022 G specified TCP extention is too big fix the problem by
Speed output failed A failure occured while writing I/O or a Check the program to
TCPP-070 STOP (T_S[%d]) >=
Min.speed register.
The minimum speed is not less than determine whether both
TCPP-071 STOP Max.speed (T_S[%d]) maximum speed.
The specified index of TCP_SPD[] is Correct the speed values.
TCPP-072 STOP Invalid index (T_S[%d]) invalid. Correct the index.
TCPP-073 STOP Unknown target type The specified target type is invalid. Correct the target type.
TG-000 WARN unknown error (TG00) Internal system error Cold start controller
PAUSE. Check memroy
TG-001 G Error allocating data Not enough memory configuration to see if it
TG-002 WARN Illegal I/O Port Illegal IO Port Reassign IO port
TG-003 WARN Illegal I/O Port Type Illegal IO Port Type Reassign IO port type
Motion trigger has been told to set a A digital port must always
TG-004 WARN Bad Command Value I/O port to a value which that port be set to 1 or 0. You must
Motion trigger has been told to set a A digital port must always
TG-005 WARN Bad Alternate Value I/O port to a value which that port be setbefore
Time to 1 ormust
0. You
bemust
TG-006 WARN Bad Time Before Illegal Time Before greater than -0.1
Reassign to a valid seconds
TG-007 WARN Bad Schedule Number schedule number out of range schedule
An I/O port was not triggered when it You must adjust your path
was supposed to. This is usually caused so that it does not try to
by too many I/O events being set up to fire so many I/O events
TG-008 WARN Could not trigger I/O fire within too short a time frame. within a such a short time.
This is a warning to indicate that the
Adjust Trig Sch:%d^2 trigger time for the specified TG event
TG-009 WARN Ev:%d^3 L:%d^5 was miscalculated, so the event was None.
This is a warning indicating that two Modify the position of the
Pts Too Close %s^4 taught points containing triggering node (line number and
L:%d^5 Sch:%d^2 events were too close to each other, program number)
TG-010 Ev:%d^3 such that the second point trigger time indicated so that it is
led to the error, including
Cannot Allocate An internal error occurred while an All File Backup from
TG-011 Memory attempting to allocate memory. the time of the error if
A trigger schedule (system variable Generally this alarm
$TGSCHED[num], where “num”is the occurs when a process
Bad Num ISDT in Sch schedule indicated in the alarm text) axis related option is
TG-012 %d^2 Ev%d^3 has an event defined with an invalid loaded, but the process
Change
$TGSCHED[Sch].$PORT_TY
In the trigger schedule number PE[Ev] to a valid port type.
$TGSCHED[num] indicated by the alarm Note that Robot Digital
Invalid IO Port in text, the indicated event number has Input and Group Input are
TG-013 Sch%d^2 Ev%d^3 an invalid port type specified. not allowed. If you have
Examine the TP programs
running at the time of the
The number of outstanding trigger error for a very large
events exceeds the maximum. This number of motion lines
indicates either an excessive number of that have instructions
very short segments in a TP program with trigger events and
with trigger instructions, or an internal that are very close
TG-014 Gun Queue is Full error. together or the same
If this alarm appears,
obtain a controller backup
TG-015 Trigger Overrun This alarm is not used. (image at least) and
The time before (or
anticipator) value cannot
The indicate trigger schedule event in be less than (i.e. more
Bad Time Before in $TGSCHED[Sch] has an invalid value for negative than) -100 msec.
TG-016 Sch%d^2 Ev%d^3 time before. Check all anticipator
Obtain a controller
Invalid Schedule An internal error occurred during backup and easy debug (if
TG-017 Number %d^2 processing of a TP instruction. available) and contact
Examine the TP programs
There are too many outstanding trigger executing at the time of
events that have not yet been fired. the error to confirm that
This indicates either an excessive there are not a large
number of short motion segments with number of short or zero
trigger instructions, or else an internal length motion segments
TG-018 Trigger Buffer is Full error. back-to-back with
If this alarm appears,
Internal Timing Data obtain an image backup
TG-019 Error This alarm is currently not used. and contact your FANUC
This indicates an error occurred in the Examine the alarm log for
Error planning app planning of an application TP the other TG-XXX alarm
TG-020 instruction instruction and is always accompanied that was posted at the
Trying to execute a touch sensing Please check the touch
instruction out of sequence. For sensing instruction
PAUSE. Illegal instruction example, a Search Start instruction sequence, or abort the
THSR-001 G sequence follows a Offset start instruction current program and start
PAUSE. The input schedule number is beyond Choose a schedule
THSR-002 G Illegal schedule number the allowable range. number from 1 to 32.
PAUSE. Illegal work frame The input work frame number is Choose a work frame
THSR-003 G number beyond the allowable range number from 1 to 32.
PAUSE. Illegal output PR The input position register number is Choose an approperiate
THSR-004 G number beyond the allowable range. position register number.
PAUSE. Illegal search PR The specified position register for Choose an approperiate
THSR-005 G
PAUSE. numberwithout search search result is beyond the allowable
Search position
Add register
search start number.
THSR-006 G start Search instruction without search start. instruction.
PAUSE. Invalid touch I/O Please check touch I/O
THSR-007 G assignment The touch I/O assignment is incorrect. setup screen under the
PAUSE. Please disable arc welding
THSR-008 G Arc
Teachenable detected
pendant not The arc weld circuitry is enable. circuitry before enabling
THSR-009 WARN
PAUSE. enabled The Teach pendant is disable. Enable
Hit the the
resetteach
buttonpendant.
to
THSR-010 G Illegal motion state The motion system is in error state. reset the controller.
PAUSE. Illegal sensor port The specified search port is beyond the Change the port type and
THSR-011 G
PAUSE. number allowable
The range.
specified search pattern is not port number
Change in thepattern
the search touch
THSR-012 G Illegal search pattern recognizable. in the touch sensor
PAUSE. Number of searches is not coincident Change the search pattern
THSR-013 G Illegal number of search with the search. pattern. or add/delete search
This is a warning message. The Change the search speed
specified search distance is beyond the in the touch sensor
THSR-014 WARN Illegal search distance allowable range. A default speed is schedule.
The specified search speed is beyond Change the search speed
THSR-015 WARN Illegal search speed the allowable range. in the touch sensor
The specified return speed is beyond Change the retunr speed
THSR-016 WARN Illegal return speed
PAUSE. the allowable
The range. Anodefault
search produces contactspeed
with is in the
Use touch sensor
touchup to teach a
THSR-017 G
PAUSE. No contact with part the part
Too many searches for the specified new search
Delete start position.
unnecessary
THSR-018 G Too many searches search pattern. search instructions
PAUSE. NONE search type can not be mixed Delete all searches with
THSR-019 G Mixing search types with directional search within one NONE type or delete
PAUSE. Geometic computing The searches do not generate a Check the search pattern
THSR-020 G
PAUSE. error satisfactory
The touchedoffset
positions are too close to and search
Teach instructions
new search start in
THSR-021 G
PAUSE. Points are too close each other.
Search instructions have no master positions
THSR-022 G Part is not mastered data.
The search instruction does not have a Mastering
Add searchthe part
start first
before
THSR-023 WARN No search start search start. search
The offset end instruction does not Add offset start
THSR-024 WARN No offset start have an associated offset start instruction
PAUSE. The search start instruction is nested Add a search_end
THSR-025 G Nested search start inside another search start instruction. instruction in appropriate
PAUSE. The offset start instruction is nested Add a offset_end
THSR-026 G Nested offset start inside another offset start instruction. instruction in appropriate
PAUSE. It is normal to issue an
THSR-027 G
PAUSE. Preplannumber
Group is not allowed The
No preplan motion has
search motion inside search
to be start.1. Use
in group stopgroup
error when preplan is
1 to record
THSR-028 G mismatch motion.
The search produces no contact with search
Use motions.
touchup to teach a
THSR-029 WARN No contact warning the part new search start position.
PAUSE. Wire makes contact with part before Check part and wire, or
THSR-030 G Contact before search search motion starts teach a new search start
The input register number is illegal, and
THSR-031 WARN Illegal register number it is reset by the software to the Check the input data.
PAUSE. The position type in the position Change the position
THSR-032 G Position type mismatch register should be XYZWPR type. Joint representation to XYZWPR
PAUSE. Touch sensing system does not have
THSR-033 G Not enough points enough points to compute the Record more points
PAUSE. No bwd on search Touch sensing does not allow backward Do not Shift-BWD on
THSR-034 G
PAUSE. motion execution on search motion search unneeded loaded
Remove
THSR-035 G Error Allocating
PAUSE. Coord pair is not Data Not enough memory
Coord motion is not installed or not variables andmotion
Install coord programs
and
THSR-036 G
PAUSE. available calibrated
Simple search must have schd_ref_grp calibrate cd pair
THSR-037 G Illegal motion ref. grp. = 1 Modify reference grp
PAUSE. Not matches to leader Touch frame or schedule reference grp
THSR-038 G grp. mismatches leader grp Modify reference grp
PAUSE. Reference grp None simple search requires frame
THSR-039 G
PAUSE. mismatch Reference grp equal
Search distance to schedule
in touch schedule is Modify
Increasereference grp
search distance
THSR-040 G Search Distance Short too short in touch schedule
Check group mask in T.P.
PAUSE. Invalid touch group Invalid touch sensing group mask in program header, each
THSR-041 G mask program detail. program can support only
Disable the Maintenance
Program in the Error
Recovery menu, or use
Maint Program not Touch Sensing does not support a Resume Program in teach
THSR-042 STOP allowed Maintenance Program. pendant program for
Create an analog input
calibration file called
th_calib.dt. The
Calibration File not The touch sensing analog input calibration file needs to
THSR-043 WARN found calibration file was not found. be stored in frs: via the
Correct the data format in
the analog input
calibration file, including
configuration data and
Invalid TH Calibration The analog input calibration file has an lookup table. Refer to the
THSR-044 WARN Data invalid data format. "Analog Input Calibration
Create an analog input
calibration file with the
correct data format. Refer
Analog Input Not Analog input support has not been to the Laser Analog Input
THSR-045 STOP Calibrated calibrated. Calibration Data section in
Analog input data needs
to be within a valid range.
Invalid Analog Input The valid range of analog
THSR-046 STOP Data The analog input data is not valid. input value is defined by
Check the OD/ID search
Can Not Construct A The searches do not generate a pattern and search
THSR-047 Circle satisfactory circle. instructions in the
Check the 1D/1D+R search
Illegal Num of 1D An illegal number of 1D/1D+R search pattern and search
THSR-048 Search Dir directions exists. instructions in the
THSR-049 Search Dir directions exist. instructions in the
THSR-050 Search Dir directions exists. instructions in the
Check search instructions
with the first search
direction. The first search
direction is specified in
Err Compute Along 1st An error occurred computing the offset the first search instruction
THSR-051 Srch Dir along the first search direction. in the corresponding
Check the search
instructions with the 2nd
search direction. The 2nd
search direction is the first
Err Compute Along 2nd Error computing the offset along the new search direction
THSR-052 Srch Dir 2nd search direction. other than the 1st search
Check search instructions
with the 3rd search
direction. The 3rd search
direction is the first new
search direction other
Err Compute Along 3rd An error occurred computing the offset than the 1st and the 2nd
THSR-053 Srch Dir along the 3rd search direction. search directions in the
Invalid Tracking Jog An attempt was made to jog multiple Set $track_mode to the
TJOG-001 WARN Mode arms at an invalid jog mode. correct value.
Multiple Arm Hardware An attempt was made to start the Start the tracking jog
TJOG-002 WARN required tracking jog feature on a single arm feature on a controller
TJOG disabled in An attempt was made to start the Enable $track_jog.$enable
TJOG-003 WARN $track_jog tracking jog feature when TJOG is before starting the
G%d is not a robot arm Trying to start the tracking jog feature Change to a robot motion
TJOG-004 WARN group
Integer number out of on a non-robot motion group. group before starting the
TKSP-001 WARN valid number
Real range. Illegal
out of
TKSP-002 WARN valid range.
Current Illegal
string is tooreal:
TKSP-003 WARN long. String: %s
Quoted string not
TKSP-004 WARN terminatednot
Character before
validend
TKSP-005 WARN without Id following.
Invalid constant value:
TKSP-006 WARN %s
New line must follow
TKSP-007 WARN "&" unexpected
%% (cancel new or line)
TKSP-008 WARN directive not
Character foundvalid.
is
TKSP-009 WARN unexpected. Character:
Id exceeds %d
TKSP-010 WARN characters.
Not enoughId: %s
memory to
TKSP-011 WARN allocateerror
Syntax %d number of
TKSP-012 WARN encountered.
Too many syntax errors
TKSP-013 WARN encountered.
Internal error. Parser
TKSP-014 WARN stackaccess
File underflow.
failed - file
TKSP-015 WARN not opened. File:of%s
Too many levels
TKSP-016 WARN nested %INCLUDE's.
TorchMate has found that the offset of Determine if the Torch
the torch from the original TCP is needs to be replaced at
TMAT-000 WARN Offset is out of range beyond the offset limits in the SETUP this time. Replace it if
The wire is in contact with the touch REMEDY1: Shorten the
plate or is grounded prior to executing wire stickout before
the touch move; CAUSE 1: The wire TorchMate execution by
stickout is too long; CAUSE 2: The retracting the wire or
starting position for the touch move is clipping the wire; REMEDY
to close to the touch plate; CAUSE 3: 2: Increase the value of
Sensor is ON before The weld equipment touch circuit or the Start Search position
TMAT-001 WARN search user provided external touch circuit has in the TorchMate SETUP
Cause1:The TorchMate sensor circuit Remedy1: Decrease the
indicates the wire is in contact with the stickout, increase the
touch plate before the search move search start distance, or
(too much stickout-the search start replace the bent torch.
Sensor failed during distance is too small.) Cause 2: An Remedy 2: Contact the
TMAT-002 WARN search electrical short exists in the touch supplier of your weld
This error indicates that Z
compensation was disabled while Disable Z compensation in
mastering and enabled during the TorchMate SETUP
TMAT-003 WARN Z offset is not mastered TorchMate adjustment. TorchMate screen.
Program paused while Mastering was stopped by releasing the Select the MASTER
TMAT-004 WARN mastering SHIFT key. softkey to execute
Reassign the TorchMate
output signal to the
WO[1] is not available The TorchMate output signal has been welder's touch sense
TMAT-005 WARN for output assigned to the Weld Start output. circuit, or to an external
Override must be 100 The speed override must be 100% Set the override to 100%,
TMAT-006 WARN %% during bothdoes
TorchMate mastering and TorchMate
not function if DRY and execute
Display mastering
the Test Cycle or
TMAT-007 WARN Dry run is not allowed RUN is turned on. menu, and turn DRY RUN
CAUSE1: TorchMate Adjustment was
attempted before mastering. CAUSE 2:
TorchMate Ajustment has Z offset
enabled, but the mastering was done Calibrate the TCP correctly
TorchMate is not with Z offset disabled. CAUSE 3: before using TorchMate
TMAT-008 WARN mastered TorchMate Ajustment has Z offset Adjustment.
The automatic setup of macros during The Macro teach pendant
installation cannot find an unused program will be loaded on
Macro number. No macro table entry the controller. Remove an
No unassigned MACRO will be automatically assigned to unused Macro from the
TMAT-009 WARN is available TM_ADJST, TM_ADJ2, TM_ADJ3. Macro table, and assign
An attempt was made to run
TorchMate adjust or mastering in T1 On the affected
mode on a CE or Control reliable controllers, change the
controller. This error applies to Teach mode to T2 and
Cannot run TorchMate TorchMate and TorchMateII on R-J, R- rerun mastering or
TMAT-010 WARN in T1 Mode J2, and early software releases on R-J3 TorchMate adjustment.
Multiple equipment is TorchMate mastering or TorchMate Set up multiple
TMAT-011 WARN not defined adjustment has been attempted on an equipment prior to
System Utool is not The UTOOL that you are trying to Set up your UTOOL using
TMAT-012 WARN defined adjust or master is not defined. the six-point method.
On the ATFLASH release
media for your robot,
locate the the programs
PRODUCT\TORCHMAT\T
MTMPLT.TP and
%s is corrupt or does The UTOOL that you are trying to PRODUCT\TORCHMAT\T
TMAT-013 WARN not exist adjust or master is not defined. MTPSET1.TP. Copy these
During TorchMate mastering, the Abort the PAUSED or
MOVETO operation in the TorchMate RUNNING program prior
Abort program using SETUP screen, or TorchMate to executing any of these
TMAT-014 WARN G:%s adjustment was attempted
TorchMate mastering on a motion functions.
or TorchMate
adjustment was used on a motion
group that is not associated with the
robot(s) in your system. CAUSE 1: At
mastering, the group is determined by
the currently selected jog motion group
as shown in the TP status line. You have REMEDY1: Select for
selected for jogging a motion group jogging a motion group
associated to a positioner, nobot, or that is associated with the
index device. CAUSE 2: TorchMate robot(s) in your system.
G:%s does not support adjustment has macros for each robot REMEDY 2: Correct the
TMAT-015 WARN TorchMate group installed on your system. The programming error.
This indicates that the TorchMate This is cleared by pressing
Touchup Monitor has been turned on the ENTER key. It is
(Touchup monitor value is > 0.0 Hrs.), recommended that you
Run TorchMate before that the program contains a robot execute TorchMate adjust
TMAT-016 WARN edit motion group(s), and that a TorchMate for the motion group(s) in
This indicates that the TorchMate This alarm causes a
collision monitor has been turned on prompt box to be
Collision! Run and that it has detected that a collision displayed. Press the
TMAT-017 WARN TorchMate detect alarm, a disturbance excess ENTER key to clear the
Do not peform TorchMate
DCS tool frame is not TorchMate cannot use for DCS tool for DCS tool frame. If you
TMAT-018 allowed frame. want to use TorchMate
When tool change was disabled on the Perform a Controlled
Tool Change is servo tool initial setup screen, an start, open the servo tool
TOOL-001 WARN DISABLED. attempt was made to execute a tool initial setup screen, then
1) A machine lock is applied to the
robot axis when the TOOL ATTACH
instruction or the TOOL DETATCH Release the machine lock
PAUSE. Machine lock is instruction is executed. 2) A machine applied to the robot axis
TOOL-002 LPAUSE. ENABLED.
Illegal assignment of lock is applied to the servo tool
The tool number assignments are axis or the servo
Confirm the tool number
axis.
TOOL-003 L Tool axis. wrong. assignment.
An attempt was made to execute the If any tool is attached, the
PAUSE. Tool not detached TOOL ATTACH instruction when a servo TOOL ATTACH instruction
TOOL-004 L (AXISORDER). tool was not detached. System variable cannot be executed.
An attempt was made to execute the If any tool is attached, the
PAUSE. TOOL ATTACH instruction when a servo TOOL ATTACH instruction
TOOL-005 L Tool not detached. tool was not detached. The servo tool cannot be executed.
While no servo tool was attached, an Unless a tool is attached,
PAUSE. attempt was made to execute the TOOL the TOOL DETACH
TOOL-006 L Tool not attached. DETACH instruction. The servo tool instruction cannot be
After the TOOL ATTACH or
PAUSE. Another process is Another program is executing a TOOL TOOL DETACH instruction
TOOL-007 L executing. ATTACH or TOOL DETACH instruction. being executed by the
Check whether the tool
PAUSE. Tool identify signal is The servo tool identification signal is number taught in the
TOOL-008 L OFF. OFF. instruction and the actual
PAUSE. Check whether the tool is
TOOL-009 L Tool set signal is OFF. The servo tool mount signal is OFF. mounted correctly. Check
The TOOL ATTACH or TOOL DETACH and hold the SHIFT and
PAUSE. instruction is canceled while executing RESET keys. 3. While still
TOOL-010 L Tool Change canceled. the instruction. pressing the SHIFT and
The TOOL ATTACH or TOOL DETACH and hold the SHIFT and
PAUSE. instruction times out while executing RESET keys. 3. While still
TOOL-011 L Tool Change timeout. the instruction. pressing the SHIFT and
1. The tool pulse values
and mastering data are
lost. So, first move the
Mastering data of a servo tool was lost tool by manual feed to
SYSTE Tool mastering data is because of an unexpected stop during cancel the "SRVO-075
TOOL-012 M
PAUSE. lost. mastering of the tool. Pulse not to
Continue established"
retry
TOOL-013 L Tool mastering is failed. Tool mastering failed. mastering.
PAUSE. The TOOL ATTACH instruction failed. Refer to the cause code
TOOL-014 L TOOL ATTACH is failed. Refer to the cause code for details. for details.
PAUSE. The TOOL DETACH instruction failed.
TOOL-015 L TOOL DETACH is failed. Refer to the cause code. Refer to the cause code.
PAUSE. Robot not Mastering of the servo tool axis has not Perform mastering of the
TOOL-016 L
PAUSE. mastered(Tool
Robot not axis). beenservo
The performed.
tool axis has not been servo toolthe
Calibrate axis.
servo tool
TOOL-017 L calibrated(Tool axis). calibrated. axis.
PAUSE. Ref pos not set(Tool A reference position required for quick
TOOL-018 L axis). mastering is not set. Set the reference position.
PAUSE. Another tool is The attached tool is not the tool Check the tool number
TOOL-019 L attached. specified in the TOOL ATTACH specified in the TOOL
Check the detection
condition on the Tool
Change SETUP screen.
REMEDY 1 1. The tool
pulse values and
mastering data are lost.
So, move the tool by
manual feed to cancel the
"SRVO-075 Pulse not
established" alarm. 2.
Carry out tool 0 position
mastering and calibration
manually. The tool 0
position may be an
approximate position. 3.
Execute the detach
instruction to temporarily
The detection condition (touch torque detach the tool. Also,
PAUSE. Calibrate motion is or the detection signal) was not physically detach the tool
TOOL-020 L failed. satisfied during calibration. from the robot.
PAUSE. For the calibration motion type 3 to 6, Set the position register
TOOL-021 L PR[] index is not set. no position register number is set. number on the Tool
PAUSE. For the calibration motion type 3 or 4, Set touch torque on the
TOOL-022 L Touch torque is not set. no touch torque is set. Tool Change SETUP
PAUSE. For the calibration motion type 5 or 6, Set the detection signal
TOOL-023 L
PAUSE. Detect signal is not set. At
no the
detection signalmotion,
calibration is set. Servo tool on theservo
After Tool tool
Change
axisSETUP
stops,
TOOL-024 L Tool does not stop. axis does not stop. execute calibration
$SCR_GRP[].$AXISORDER[] of the tool Set
TOOL-025 Illegal AXISORDER. was battery
The set to antype
illegal value.
of the $SCR_GRP[].$AXISORDER[
multi-axis tool Set the battery type of the
TOOL-026 Battery type OFF. was set to OFF. multi-axis tool to ON.
Timeout G%d A%d %x A timeout occurred during Tool-attach led to the error, and call
TOOL-027 %d or -detach at the start. your FANUC America
TOOL-028 Internal error System internal error your FANUC America
Mnemonic editor error RESET keys. 3. While still
TPIF-001 WARN (%s^1) Illegal case occured on software. pressing the SHIFT and
Operating system error RESET keys. 3. While still
Window I/O error RESET keys. 3. While still
TPIF-004 WARN Memory write error Illegal case occured on software. pressing the SHIFT and
The program was not selected yet, Select a program in the
TPIF-005 WARN Program is not selected when the program was displayed at the SELECT screen.
This taught statement needed the Teach the SELECT
TPIF-006 WARN SELECT is not taught SELECT
The statement
robot beforecalibrated
has not been the current statementthe
Calibrate before
robotthe
TPIF-007 WARN Memory
Robot is not calibrated properly.
protect properly..
Release protection of the
TPIF-008 WARN violation The program is write protected. program on the SELECT
Cancel delete by Release protection of the
TPIF-009 WARN Cancel
application
enter by Program is protected program
Try on the
edit after SELECT
release
TPIF-010 WARN application Program is protected protection by application
Try another item or close
TPIF-011 WARN Item is not found Item is not found below this line search function
Kinematics solution is Check the configuration of
TPIF-012 WARN invalid Cannot translate position data robot and
Other program is You cannot select a program when Select a program after
TPIF-013 WARN running another program is running or paused. aborting the program
Teach pendant is You cannot edit a program when the First enable the teach
TPIF-014 WARN Bad
disabled
position register teach pendant
Specified is disabled.
aa invalid index of position pendant,
Check thethen
indexedit
of the
TPIF-015 WARN index register position register
Memory access failed RESET keys. 3. While still
TPIF-017 WARN Memory read failed Illegal case occured on software. pressing
Check the SHIFT
specified and
index
TPIF-018 WARN Unspecified index
This item cannot be value Specified index value is invalid. value.
Try another item or close
TPIF-019 WARN replaced This item cannot be replaced replace function
TPIF-020 WARN Mnaction search error Illegal case occured on software. pressing the SHIFT and
TPIF-021 WARN Mnteach software error Illegal case occured in software. pressing the SHIFT and
TPIF-022 WARN WJNT and RTCP are not Remove Wjnt or RTCP
TPIF-023 WARN compatible Wjnt and RTCP are not compatible. before
Set addingprogram
a proper the other.
TPIF-030 WARN Program name is NULL Program name is not set properly. name
Remove num from start Remove numeric value
TPIF-031 WARN of Program name Start of program name is numeric. from beginning of
Remove space from Remove space from
TPIF-032 WARN Program name from
Remove comma Space is included in program name. program name. from
Remove comma
TPIF-033 WARN Program dot
Remove namefrom Comma is included in program name. programdot
Remove name.
from
TPIF-034 WARN Program name
Remove minus from Dot is included in program name. program name.
Remove minus from
TPIF-035 WARN Program name Minus is included in program name. program name.
TPIF-036 WARN Not enough memory There is not enough memory available. Delete unused program.
Program must be Only the Teach Pendant default Select the program on the
TPIF-037 WARN selectedchar
Invalid by TP
in program program can be edited on the CRT Teach Pendant
Remove invalid before
character
TPIF-038 WARN name Invalid character in program name from program
Change namelabel
to different
TPIF-040 WARN Label already exists
MNUTOOLNUM Same label
Specified No. already exists
MNUTOOLNUM number is No.
Check system variable
TPIF-041 WARN number is invalid
MNUFRAMENUM invalid
Specified MNUFRAMNUM number is $MNUTOOLNUM
Check system variable
TPIF-042 WARN number is invalid invalid $MNUFRAMNUM
You cannot change the robot (group), Set system variable
TPIF-043 WARN External change is valid because the function that select robot $MULTI_ROBO.CHANGE_S
Program is unsuitable The group mask of program differs Check selected robot
TPIF-044 WARN for robot from selected robot (group) (group) or check program
Pallet number is over Cannot teach more than 16 Palletizing
TPIF-045 WARN Motion
max option is over instructions
Too in oneoptions
many motion program, Teach another
for default
Decrease program.
motion options
TPIF-046 WARN max
Invalid program is motion for default motion
TPIF-047 WARN selected Program type is wrong Select TPE program
Running program is not There is currently no program running
Run program before
TPIF-048 WARN found that can be monitored. attempting to monitor.
TPIF-049 WARN Port number is invalid Port
A is not set
program forassigned
is not outside deviceSet porta for
to this macro
Assign outside
program to device
this
TPIF-050 WARN Macro does not exist command macro command
Program has been When a program has been selected byTurn off the PNSTROBE
TPIF-051 WARN selected by PNS PNS, you cannot select program fromsignal.
When the Disabled FWD function has Select the Disabled FWD
TPIF-052 WARN FWD/BWD is disabled been selected, you cannot execute the
in the function menu,
Not editing background The program has not been selected by
Select the BACKGROUND
TPIF-053 WARN program BACKGROUND editing program in the SELECT
1. There is not enough memory. 2. The
1. Delete unnecessary
TPIF-054 WARN Could not end editing background program is invalid. programs. 2. Confirm the
Failed recovering original program End editing by the
Could not recovery which has been selected by the END_EDIT of [EDCMD]
TPIF-055 WARN original program BACKGROUND again before executing
This program is used by The program of BACKGROUND cannot End editing by the
TPIF-056 WARN the CRT be selected by the CRT and TP at the
END_EDIT of [EDCMD] at
This program is used by The program of BACKGROUND cannot End editing by the
TPIF-057 WARN the TP be selected by the CRT and TP at the
END_EDIT of [EDCMD] at
Can't record on You can record this
TPIF-060 WARN cartesian (G:%d) This current position is in singularity position on joint type only
This position data has not been Check this recorded
Group[%s] has not changed to displayed groups because position again before
TPIF-061 WARN recorded you selected the function key which did excution
You cannot mix AND and
AND operator was All AND operators on this line were OR operator on a the
TPIF-062 WARN replaced to OR replaced with OR operators. same line. Verify that all
All OR operator on this line were Verify all logical operators
OR operator was replaced by AND operators. You cannot on this line before
TPIF-063 WARN replaced
Too manytoAND/OR
AND mix
Too AND
manyOR operaotr
AND/OR on a the(Max.4
operators same execution
Teach the logical
TPIF-064 WARN operator(Max.4) on a single line) operation on another line
Arithmetic operator on this line was Verify all arithmetic
Arithmetic operator changed to +- or */. Cannot mix operators on this line
TPIF-065 WARN was unified to +- or */ arithmatic + and - operators with * and before execution
Too many arithmetic Too many arithmetic operators (Max.5 Teach the arithmetic
TPIF-066 WARN operator(Max.5) on a single line) operation on another line
Too many arguments Too many arguments (Max.10 for a Check arguments of the
TPIF-067 WARN (Max.10) program or a macro) program/macro
This instruction contains too many
items. You can add only a limited
number of items to a line. It is limited Split this long complex
by the fact that a single line can be only line into several simpler
TPIF-068 WARN Too many items 255 bytes long. The number of items lines.
You cannot foreground edit a program Select the BACKGROUND
from the CRT or from the Internet. You program in the SELECT
TPIF-069 WARN Use background
Cannot teach theedit can only edit using a background screen.the sub type of the
Check
TPIF-070 WARN instruction Cannot teach the instruction. program.
Check sub type of the
TPIF-071 WARN Cannot change sub type Cannot change sub type
motion program
Check sub type of the
TPIF-072 WARN group Cannot change motion group program
This program has The program specified in $PWR_HOT, Set * to all motion group
TPIF-090 WARN motion group $PWR_SEMI
An and $PWR_NORMAL
error occurred when accessing must
a in program
Refer to thedetail
error screen
cause
TPIF-091 WARN PREG access error position register. code on the ALARM log
The value_array that was passed to a Make sure the
built-in was incorrectly specified. The value_array specifies the
error line shows the index into correct names for the
TPIF-092 WARN Value %d expected %s value_array where the error occurred variables and that the
A KAREL program called a user Use
interface built-in which required the FORCE_SPMENU(tp_panel
USER menu must be USER menu to be displayed on the , SPI_TPUSER, 1) before
TPIF-093 WARN selected teach pendant or CRT. calling the user interface
A KAREL program called a user Use
interface built-in which required the FORCE_SPMENU(tp_panel
USER2 menu must be USER2 menu to be displayed on the , SPI_TPUSER2, 1) before
TPIF-094 WARN selected teach pendant or CRT. calling the user interface
Execution history table Perform a controlled start
TPIF-095 WARN error
Execution history Software internal error (it isn't necessary to re-set
TPIF-096 WARN doesn't exist
Can't display running The execution history of the executing Use this screen when the
TPIF-097 WARN task's history program cannot be displayed program is paused or
The program of $PWR_HOT, Refer to the error cause
TPIF-098 WARN %s was not run $PWR_SEMI or $PWR_NORMAL is not code. Use the Alarm Log
The program specified in $PWR_HOT,
This program is being $PWR_SEMI and $PWR_NORMAL is not
TPIF-099 WARN edited executed, when the program is in Select the other program
TPIF-100 WARN No vacant table space Illegal case occured on software. pressing the SHIFT and
TPIF-101 WARN No such menu Illegal case occured
FWD execution on software.
is selected while, pressing
Turn the the SHIFT
E.STOP off.and
Then
TPIF-102 WARN E.STOP is asserted E.STOP is asserted. select FWD execution
FWD execution is selected while, Press and hold down the
TPIF-103 WARN Dead man is released DEADMAN switch is released. DEADMAN, then select
Teach Pendant is FWD execution is selected while, TP is Enable the teach pendant.
TPIF-104 WARN disabled disabled. Then select FWD
FWD execution is requested without Select a proram for
TPIF-105 WARN Program is not selected selection of program. execution Then select
Program is already FWD execution is requested when Abort the running
TPIF-106 WARN running program is running. program before
When the Disabled FWD function has Select the Disabled FWD
TPIF-107 WARN FWD/BWD is disabled been selected, you cannot execute the in the function menu,
Form error, line %d, The Form Manager detected an error Refer to the cause code
TPIF-108 WARN item %d on the specified line with the specified on the ALARM log screen
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
%v not specified The Form Manager detected an error contains the display
TPIF-109 WARN correctly when displaying a %v item. values. For example:
The screen you are attempting to use
on the TP is currently displayed on CRT
Screen used by other or the screen you are attempting to use Exit from the screen on
TPIF-110 WARN device
op_global does not on the CRT is currently displayed on TP the other device
TPIF-111 WARN exist
TPIF-112 WARN op_sel does not
Illegal param exist
in op
TPIF-113 WARN menu
TPIF-114 WARN Illegal data in op menu
TPIF-115 WARN Data
Systemis full
variable error: Check the spelling and
TPIF-116 WARN %s
Cannot backup to System
The variable
default name
device is invalid
is not valid for formataofvalid
Select the device
name. and
TPIF-117 WARN device: %s backup try again
TPIF-118 WARN File error for %s File error pressing the SHIFT and
TPIF-119 WARN File compression failed Failed creating compressed file backupand
Check device device
try
TPIF-120 WARN Device failure Device failure again
Invalid copy. Use MOVE Cannot COPY a file on a Memory device Use the MOVE key and try
TPIF-121 WARN key.
Specified softpart ID is to the same Memory device. again
TPIF-122 WARN illegal
TPIF-123 WARN No activeapplication
Current applications
is
TPIF-124 WARN nothing
Specified softpart ID is
TPIF-125 WARN nothing
TPIF-126 WARN THKY ASLOAD is failed
TPIF-127 WARN TOPK ASLOAD is failed
The reverse motion copy function does Check the above motion
not support the following motion option instruction. And
Verify logic of pasted option instruction. 1. Application modify the copied
TPIF-128 WARN line(s) command 2. Skip, Quick Skip 3. statement correctly.
The group motion instruction is Check the group motion
Group motion inst. is copyied. The reverse motion copy instruction. And modify
TPIF-129 WARN pasted function does not supported group the copied statement
Specified application
TPIF-130 WARN has no EQ
Please set application Please set the application
TPIF-131 WARN mask data This program has no application mask mask in the program
Can't recover this Because the data for UNDO can not be Check the cause code. If
TPIF-132 WARN operation saved, this operation can not recover the memory is full, please
Can't recover this Palletizing command and Compliance Check the cause code. If
TPIF-133 WARN command control command can not be recovered the memory is full, please
This error is posted
PAUSE. because CTRL Upgrade
TPIF-134 G CTRL Upgrade is Armed CTRL Upgrade is Armed cannot be done while
This error is posted
SYSTE because CTRL Upgrade is
TPIF-135 M CTRL Upgrade is Started CTRL Upgrade has Started underway. Allow the
Restore ERR, see See FRD:REST_LOG.LS for
TPIF-136 WARN FRD:REST_LOG.LS CTRL Upgrade Restore Failed a listing of files and status
A user has logged into the teach This is for information
TPIF-137 WARN TP: %s interactive login pendant menuing system. only. No action is
A user has logged into the teach This is for information
TPIF-138 WARN TP: %s diagnostic login pendant diagnostic monitoring system. only. No action is
A user has logged off of the teach This is for information
TPIF-139 WARN TP: %s logged out pendant menuing system. only. No action is
An attempt to log into the teach The system variable
pendant menuing system from an $UI_CONFIG.$NUM_CON
external web browser has failed NECT controls the number
Connection limit because the connection limit has been of external connections
TPIF-140 WARN exceeded reached. allowed. The maximum
A user has failed to log into the teach Add RAM memory to your
pendant menuing system because not system. You can also
enough RAM memory is available to lower the memory limit
No memory for make the connection. The system required for login by
TPIF-141 WARN connection might still be usable because the changing the system
Too many user interface menus are Eliminate some active
active. The iPendant requires three browser windows or
menus which are always available for it increase the number of
to use. External browser onnections menus in
require one menu for each window in $UI_CONFIG.$NUM_MEN
TPIF-142 WARN Menu limit exceeded use. Therefore, a browser connection US. The total maximum
An external connection to the teach Restart the controller, and
TPIF-143 WARN Connection error pendant menus has failed. try again.
A change to the iPendant window When this error occurs,
configuration has taken longer than the display might not be
expected. This can occur on startup or what is expected. In this
after you make a basic system case, change back to
Configuration change configuration change. It might also Single mode, and try the
TPIF-145 WARN time out occur in the presence of significant operation again.
The firmware version on your iPendant You will need to update
is incompatible with the system the firmware to execute
software loaded on your controller. In all available iPendant
some cases this will cause the iPendant functionality. Refer to the
TP firmware version is to execute in ?legacy? mode. In this FANUC Robotics SYSTEM R-
TPIF-146 WARN too new mode it only provides the functionality J3iB Software Installation
The firmware version on your iPendant You will need to update
is too old to provide all functionality for
firmware to have all
your system software release. In some functionality available.
cases this will cause the iPendant to Refer to the FANUC
TP firmware version is execute in ?legacy? mode. In this mode Robotics SYSTEM R-J3iB
TPIF-147 WARN too old it only provides the functionality that is
Software Installation
You cannot change the focus of the Finish the current
Must complete iPendant in the middle of an entry operation by pressing
TPIF-149 WARN operation first operation. The entry operation must be ENTER, or abort the
Select a valid pane for an
No editing is permitted on the device edit operation. You can
Look mode only, use TP you are using to access a teach pendant only edit teach pendant
TPIF-150 WARN to edit program. programs on the iPendant
A popup menu was requested for the
pane that does not have focus. This
error only occurs in Double, Triple, or
Status/Single Display Modes. For Press the DISP key to
instance, if you connect to the iPendant change the focus to the
menus from Internet Explorer, bring up correct pane before
Pane does not have a web page that has the ComboBox requesting the popup
TPIF-151 WARN focus Control, switch focus to another pane, menu.
The keystroke that was just entered Make the change from the
was not accepted by the system iPendant instead. Your
Read Only Mode because the system does not allow access to make changes
TPIF-152 WARN Enabled edits. Typically remote operations will will depend on your
You are trying to edit a field that is
write protected. This happens if you Perform this operation
Edit operation not are editing from an external from the teach pendant,
TPIF-153 allowed connection, or if your password or log in.
The iPendant firmware consists of
Teach Pendant Core Firmware and
Browser Plugins. The Browser Plugins,
also referred to as application code, Update the whole
can be updated independently of the firmware for the
Teach Pendant Core Firmware. iPendant. Refer to the
However, the major versions must FANUC Robotics SYSTEM R-
match. For example, Teach Pendant J3iB Controller Software
Core Firmware V6.22xx cannot be used Installation Manual for
TP firmware with Browser Plugins V6.31xx. When details on updating the
TPIF-154 WARN Core/Plugins mismatch this happens, the iPendant will detect iPendant firmware.
The [TYPE] pullup menu cannot find
any other menus to display. The Press MENUS to select
TPIF-156 WARN No type menus current menu might be the only menu another menu catagory.
Another menu will be
displayed instead and you
The controller attempted to display a can ignore this warning. If
Menu cannot be menu that can only be displayed by the you want to display the
TPIF-157 WARN displayed iPendant. menu and you have a
To log in to a robot
remotely with the
iPendant, you must
You are attempting to connect a teach configure an iPendant
pendant to a robot that already has a ring. Press MENUS to
TPIF-158 WARN TP is already connected teach pendant connected. reconnect to the local
You attempted to log in to a robot Install the version of the
remotely with Internet Explorer and iPendant Controls that
the iPendant Controls installed on your match the robot version.
iPendant Controls too PC are not compatible with the robot's Refer to the application-
TPIF-159 WARN new version. specific Setup and
You attempted to log in to a robot Install the version of the
remotely with Internet Explorer and iPendant Controls that
the iPendant Controls installed on your match the robot version.
iPendant Controls too PC are not compatible with the robot's Refer to the application-
TPIF-160 WARN old version. specific Setup and
Cannot change position The position ID cannot be changed by Set the system variable
TPIF-161 WARN ID setting the system variable. $POS_EDIT.$LOCK_POSNU
The Edit screen cannot enter the
Can't enter P-SPS in daughter program while the program is Abort the program to
TPIF-162 WARN PAUSED paused outside of the daughter enter the P-SPS.
The Edit screen cannot exit the
Can't exit P-SPS in daughter program and enter the parent Abort the program to exit
TPIF-163 WARN PAUSED program while the program is paused the daughter program.
This program has no This program has no motion group Change the MOTION
TPIF-164 WARN motion group defined. The MOTION instruction instruction or set up the
An attempt is being made to resume Use BWD to return to the
TPIF-165 WARN Can't resume in P-SPS the daughter program while the parent parent program, and then
When the focus is in the right hand Press DISP to change the
FWD/BWD in left window of the teach pendant, you focus to the left hand
TPIF-166 WARN window only cannot execute the program. window. Use DISPLAY
Program already in The program you selected is already Select End_edit in the
TPIF-167 WARN background edit being edited in the background in other window's
To connect an iPendant to
a remote robot, you must
configure an iPendant
You are attempting to connect an ring. Press MENUS to
Cannot connect iPendant to a remote robot that will reconnect to the local
TPIF-168 WARN iPendant not accept your IP address. robot. If you are
You are attempting to connect an Disable the remote
iPendant to a remote robot that robot's teach pendant.
TPIF-169 WARN TP is enabled already has a teach pendant connected Press MENUS to
This program cannot be started Select the correct
TPIF-170 WARN Can't start this program because the program name is not an program, and start the
The operation cannot be performed Wait until the iPendant is
iPendant is not ready because the iPendant system is not initialized to do this
TPIF-171 WARN yet initialized. operation. Typically, this is
Only available from The operation you selected is only Perform this operation
TPIF-172 WARN pendant available from the teach pendant. from the attached teach
The pos. can't be The position data is wrong. Refer to the Change the position data
TPIF-173 WARN handled part repr. cause code for details. correctly, and press F5
New pos. can't be The new position data is wrong. Refer Type the correct position
TPIF-174 WARN handled part repr. to the cause code for details data.
Group was The shift key and the figure key were
TPIF-175 changed(Old:%d,Now:% pushed at the same time when TP was None.
The situation unexpected by the Turn off controller power
Illegal state(D1:%d, software occured. The index value and turn it on again. If the
TPIF-176 D2:%d) indicates the reason. problem persists,
You cannot record motion line using Move the cursor to the
TPIF-201 Next line exist. the record button if the next line exists. end of the program, and
Format does not match Record status(TUI default motion) is Select TUIDFMTN.to and
TPIF-203 to unified
There is notspecification
specified not written in TUI motion format. teach J P[ ] R[101]% FINE
TPIF-204 sourceisprogram
There not specified The input value is not correct. Confirm the input value.
TPIF-205 source
The numbernumber.
step of steps of The input value is not correct. Confirm the input value.
TPIF-206 sourceisprogram
There doesn't
not specified The input value is not correct. Confirm the input value.
TPIF-207 destination program
There is not specified The input value is not correct. Confirm the input value.
TPIF-208 destination
Because step
destination The input value is not correct. Confirm
Stop the the input value.
destination
TPIF-209 program
The numberis executing,
of steps to The destination program is executing. program.
TPIF-210 transfer is 0. The number of steps to transfer is 0. Confirm the input value.
TPIF-211 Specify
The the copy
number range.
of steps in The copy range is not specified. Specify the copy range.
TPIF-212 the destination
Check GO/BACKexceeds
from The input
You cannotvalue is not
Check correct.
GO/Back from logic Confirm
Move the input
cursor value.
to motion
TPIF-213 logic instruction
Run/continue from instruction.
You cannot run or continue from a logic instruction
Move the cursor toagain.
and try a
TPIF-214 logic instruction instruction. motion
If you are trying to log intry
instruction and
from a PC, set Internet
Explorer to prevent
Windows from blocking
communication with the
robot controller: - The PC
must have Microsoft™
Internet Explorer 5.5 or
greater installed. - The PC
must have the iPendant
Controls installed. - If you
have a firewall, unblock
port 60005. - If you are
iPendant login An error occurred trying to log in as an using a proxy server,
TPIF-215 unsuccessful iPendant connection. make sure that your
The operation falied because program
to be edited/executed does not
displayed group. If you press insert,
Program does not have overwrite, record, or touchup on the Use a program with the
TPIF-216 group %d TUI TP, the program displayed by line proper group mask.
FN code of TUI FN instruction is Use the correct function
unknown. If this is posted by the code. If the loaded
TPIF-217 Unknown FN code loaded program, the option might not program or break of
Usually this error is
TPIF-218 %s failed to load The indicated program failed to load. posted when a program is
Finish edit in full editor Edit in TUI full editor is not finished yet. Please go to TUI full editor
TPIF-219 for check GO/BACK To do Check GO/BACK, edit must be and complete edit of
This line is not motion line selected or to be modified is not Confirm contents of the
TPIF-220 statement motion statement of unified line
Don't copy P-SPS to P-SPS.
TPIF-221 Copy P-SPS to P-SPS line including P-SPS is copied to P-SPS Please select lines to copy
This feature requires This feature does not work on the
TPIF-222 the iPendant monochrome teach pendant. Please use an iPendant.
Special error for production support Continue production
TPIF-223 Save SLAVEDATA to MC Saving SLAVEDATA is successful examination
Special error for production support Continue production
TPIF-224 Load SLAVEDATA G%d Loading SLAVEDATA is sucessful examination
Not MC for save/load Special error for production support Change MC to MC that
TPIF-225 SLAVEDATA MC is not regard for save/load MC has directory SLAVE
MC for save/load Special error for production support Change MC to MC that
TPIF-226 SLAVEDATA MC is regard for save/load MC does not have directory
Cannot jump to called Editor can not jump to called program Please select the program
TPIF-227 program anymore
Jog override has been anymore. Number of programs to in select
Active screen.moved to
Override
TPIF-228 enabled
Prog override has been Program Override was active Jog Override
Active Override moved to
TPIF-229 enabled Jog Override was active Program Override
Menu Favorites editing Editing Menu Favorites has been Contact the engineer
TPIF-230 disabled disabled. responsible for robot
User Views editing Contact the engineer
TPIF-231 disabled Editing User Views has been disabled. responsible for robot
Contact the engineer
Coordinate Systems Editing Coordinate Systems has been responsible for robot
TPIF-232 editing disabled disabled. configuration to re-enable
3D Graphics Initialize Update your video card
TPIF-233 Failed Offline PC must support OpenGL 2.0. drivers to the latest
Operator has changed the This is a warning that the
Offset may be applied representation of a Position Register PR[] may be modified by a
to PR[%d], grp #%d, PR[] = Position Register number grp = different UF or UT then it
TPIF-234 uf#%d, ut#%d Group number uf = User Frame number was recorded with. Make
Cannot change editor Editor can not jump to called program Please stop running the
TPIF-235 while running while any programs is running or program.
Override step setting is invalid In case Sort
$OVRD_SETUP.$OVERRIDE[]'s values or $OVRD_SETUP.$OVERRID
Override step setting is $OVRD_SETUP.$OVERRIDE_S[]'s values E[1-n] or
TPIF-236 invalid
The iPendant available are invalid, Override key is pressed $OVRD_SETUP.$OVERRID
Please cycle power on the
TPIF-237 internal memory is low. The iPendant memory is low. controller.
The iPendant detected and turn it on again. If the
an unhandled The iPendant detected an unhandle error still exists,
TPIF-238 exception. exception. document the events that
No more SHADOW available Program Delete some programs or
TPIF-239 %s loaded
This documentto CMOS
is loaded to CMOS
Password instead
protected documents cannot allocate more
Remove DRAM
password
TPIF-240 password protected. be viewed. protection from the
Not enough memory to There is not enough memory available Try loading the document
TPIF-241 view document. to load the document. from the UT1: device or
This document is not a The document is of an unknown type Save the document in a
TPIF-242 known format.
iPendant firmware was or is corrupted. supported format or
TPIF-243 updated The iPendant firmware was updated. No action is required.
iPendant update The iPendant firmware was updated Please cycle power on the
TPIF-244 requires power cycle and a power cycle is required. controller.
iPendant firmware The iPendant firmware update failed Check that the media is
TPIF-245 update failed because required files could not be correct
C1(FTP) has not been This alarm is for production in FANUC This alarm is for
TPIF-246 mounted. factory. Customers must not encounter production in FANUC
TRAK-000 WARN
PAUSE. Unknown error
Track jnt move not (TO00) System internal error Cycle start controller
TRAK-001 G
PAUSE. allowed
Track error allocating Illegal joint move error Change to linear move
TRAK-002 G
PAUSE. data global variable
Track System internal error Increase RAM size
TRAK-003 G
PAUSE. failure
Track illegal schedule System internal error Increase RAM size
TRAK-004 G
PAUSE. number Track
G:%d^2 Schdule out of range error Use legal schedule
TRAK-005 G destination
G:%d^2 Track gone error Destination out of window error Move conveyor back
TRAK-006 WARN destination gone
Unsupported function Destination out of window error reteach destination
TRAK-007 WARN codesupport semi hot
Not System
Semi hotinternal
start iserror
not supported for this No action required
TRAK-008 WARN start function error No action required
PAUSE. Track cart move not
TRAK-009 G
PAUSE. allowed
Track no line track Illegal
The Linecartesian
Trackingmove errorpointers do
function Change to joint
Reload the move
tracking
TRAK-010 G functn ptr not exist. error softparts.
PAUSE. Track no CIRC Wrist Wrist-joint motion is not supported for Change motion type to
TRAK-011 G Joint CIRCULAR motions during Line non-wrist-joint motion.
Track no Maintenance The maintenance program is not Disable the Maintenance
TRAK-012 Program supported for Tracking. Program in Error Recovery
The TCP (Line Tracking) or Extended Adjust the Entry Limit or
Extreme entry position Axis (Rail Tracking) has been change the Tracking
TRAK-013 violation commanded beyond the Entry Limit Boundary to be inside of
The TCP (Line Tracking) or Extended Adjust the Exit Limit or
Extreme exit position Axis (Rail Tracking) has been change the Tracking
TRAK-014 violation commanded beyond the Exit Limit Boundary to be inside of
The robot is already out of the
Skip outbound motion boundary before its attempt to move Program at faster speed
TRAK-015 WARN LN:%d to the programmed location. Skip this or extend the boundary.
Fail to record Stop The offset used by stop_pos recording This error is the side effect
TRAK-016 Position was not initialized. of previous error in the
TRAN-000 WARN Undefined
Successful Translation.
parse syntax
TRAN-001 WARN error.
TRAN-002 WARN "ROUTINE" expected.
TRAN-003 WARN Number,
Quoted string
Id, orexpected.
quoted
TRAN-004 WARN string expected.
TRAN-005 WARN Number or Id expected.
TRAN-006 WARN Parameter
Type or Id expected.
type
TRAN-007 WARN expected.
Integer, Id, or "*"
TRAN-009 WARN "*" expected.
TRAN-010 WARN Integer or Id expected.
TRAN-011 WARN Invalid
Id expected.
statement. ";" or
TRAN-012 WARN new line expected.or
Invalid statement
TRAN-013 WARN "FILE"
"ENDxxx" or "UNTIL"
or "HAND"
WHEN clause expected
TRAN-015 WARN in a condition handler
Invalid or missing
TRAN-016 WARN condition
"EVENT" orwithin a
TRAN-017 WARN Local
"SEMAPHORE"
condition handler
TRAN-018 WARN expected in a MOVE
"CASE" expected within
TRAN-019 WARN a SELECT statement.
TO, ALONG, NEAR, AXIS,
TRAN-020 WARN AWAY, RELATIVE,
Id or quoted stringor
TRAN-022 WARN Invalid read item.
TRAN-023 WARN Variable
Id or systemexpected.
Id
Invalid or missing
TRAN-025 WARN expression.
"AFTER" or "BEFORE"
TRAN-026 WARN "DOWNTO"
expected in aorlocal"TO"
TRAN-027 WARN expected in the FOR
TRAN-028 WARN System Id expected.
TRAN-029 WARN Number expected.
TRAN-030 WARN "PROGRAM" expected.
TRAN-031 WARN "=" expected.
TRAN-032 WARN "." expected.
TRAN-033 WARN ":" expected.
TRAN-034 WARN "[" expected.
TRAN-035 WARN "[" or "OF" expected.
TRAN-036 WARN "]" expected.
TRAN-037 WARN "," or "]" expected.
TRAN-038 WARN "," or ")" expected.
TRAN-039 WARN "(" expected.
TRAN-040 WARN ")" expected.
TRAN-041 WARN ","
";" or ":"
newexpected.
line
";", new line, or ")"
TRAN-044 WARN "BEGIN" expected.
TRAN-045 WARN "BY" expected.
TRAN-046 WARN "CONDITION" expected.
TRAN-047 WARN "DO" expected.
"ENDSTRUCTURE"
TRAN-049 WARN "EVENT" expected.
TRAN-050 WARN "FOR" expected.
TRAN-051 WARN "GROUP" expected.
TRAN-052 WARN "HAND" expected.
TRAN-053 WARN "NODE" expected.
TRAN-054 WARN "OF" expected.
TRAN-055 WARN "THEN" expected.
TRAN-056 WARN "TIMER" expected.
TRAN-057 WARN "TO" expected.
TRAN-058 WARN "," expected.
"ERROR", "COMMAND",
TRAN-059 WARN or "TPENABLE"
"CMOS" or "DRAM"
Value cannot be
TRAN-063 WARN negative.
Id is already defined in
TRAN-064 WARN themust
Id current
be defined
TRAN-065 WARN before this use. Id: %s
Label used in GO TO
TRAN-066 WARN statement is never
Parameters for routine
TRAN-067 WARN not needed since
Number of nested
TRAN-068 WARN routines or structures
Symbol definition table
TRAN-069 WARN size exceeded. Reduce
Id name on PROGRAM
TRAN-070 WARN END statement does
Code size exceeded
TRAN-071 WARN maximum. Break
TRAN-072 WARN P-code file device full.
TRAN-073 WARN be defined before use
Invalid class for Id,
TRAN-074 WARN CONSTant expected. Id:
be definedclassbefore
for Id,use
TYPE
Number of arrayId: %s
TRAN-077 WARN dimensions exceeded
Id name on ROUTINE
TRAN-078 WARN END statement does
Program name may not
TRAN-079 WARN be
Arraythedimensions
same as anymust
TRAN-080 WARN Group
be specified
number foristhis
notId.
in
TRAN-081 WARN PATH
valid range.
data type is not
TRAN-082 WARN allowed.
PATH, FILE, and vision
TRAN-083 WARN File
datacannot
types are not
be opened
TRAN-084 WARN Number
or created. File: %s
of groups
TRAN-085 WARN exceeded maximum.
Data type of Id must be
TRAN-086 WARN Operator
FILE. Id: %s not defined
TRAN-087 WARN No
on VECTORS.
valid operation for
TRAN-088 WARN this
BOOLEANdata type
data type
Statement ROUTINEs
TRAN-090 WARN don't have return
ROUTINE called has less
TRAN-091 WARN arguments than
Routine calls invalid
within CONDITION
class for Id, and
TRAN-093 WARN VARiable expected.are
PATH assignments Id:
TRAN-094 WARN invalid.
Operator expected
TRAN-095 WARN INTEGER
POSITIONdata datatype
type for
Id is not user accessible
TRAN-097 WARN or not a valid system Id.
Id type is not an ARRAY
TRAN-098 WARN or indexing
Id type is notexceeded
a
TRAN-099 WARN Id
STRUCTURE.
type is notId: %s in a
a field
TRAN-100 WARN Indexing
STRUCTURE. Id: %s
invalid of Id.
TRAN-101 WARN Id: %s
Id type is not a
TRAN-102 WARN ROUTINE. Id: %s
ROUTINE has a return
TRAN-103 WARN value, statement
ROUTINE called has
TRAN-104 WARN more arguments than
Must enclose this
TRAN-105 WARN "write protected" Id in
Invalid class for Id;
TRAN-106 WARN VARiable, ROUTINE,
ROUTINE argument
TRAN-107 WARN data
STRING type does
data not
type
TRAN-108 WARN Data
expected.
type of Id cannot
TRAN-109 WARN Data
be loaded
type ofbyId value.
cannotId:
TRAN-110 WARN be loaded by
Types may only be value.
TRAN-111 WARN declared at the
FROM, IN CMOS, or IN
TRAN-112 WARN DRAMdata
REAL is only
type valid at
VECTOR data type
POSITION data type
This system Id is not
TRAN-116 WARN valid in the MOVE
Only one group may be
TRAN-117 WARN specified
PATH dataintype this type of
"WITH" group mask
TRAN-119 WARN does
InvalidnotId,match
static VAR of
TRAN-120 WARN type INTEGER
Label name was expected.
TRAN-121 WARN previously
Invalid classused in other
for Id,
TRAN-122 WARN PORT expected.
Id is invalid for PULSE,Id: %s
TRAN-123 WARN only valid Id is DOUT.
This system Id is not
TRAN-124 WARN valid in the CONDITION
Both operands in
TRAN-125 WARN condition
Port arrayshandler
must be
TRAN-126 WARN indexed. Port: %s
BOOLEAN, INTEGER, or
TRAN-127 WARN REAL scalar static VAR
In cond expressions,
TRAN-128 WARN either a "NOT" or a
"NOT" is invalid before
TRAN-129 WARN the
"AND"Id inand
a relation
"OR" cannot
TRAN-130 WARN both be specified
RETURN value expectedin a
TRAN-131 WARN in this
FOR ROUTINE.loop
statement
TRAN-132 WARN index Id must be an
RETURN statement
TRAN-133 WARN cannot have a return
Expression ROUTINE
TRAN-134 WARN return type
Expected Id does
to benot an
TRAN-135 WARN INTEGER CONSTant.
Cannot READ into port Id:
TRAN-136 WARN values of any type. Port:
Cannot load
TRAN-137 WARN environment
Not enough memory file, to
TRAN-138 WARN allocate
Data type%dofnumber
Id is notof
TRAN-139 WARN valid in this context. Id:
RETURN statement
TRAN-140 WARN invalid within
This system Id is "write
TRAN-141 WARN protected" from KAREL
Data type of Id is
TRAN-142 WARN incompatible
Data cannot be with right
stored
TRAN-143 WARN into input ports.
Cannot convert VAX Port:
TRAN-144 WARN real number to
READ/WRITE is IEEE
invalid
TRAN-145 WARN for this data
Operation type.for
invalid
TRAN-146 WARN this data type.
Operator not defined
TRAN-147 WARN on INTEGERS.
TRAN-148 WARN on REALS.not defined
Operator
TRAN-149 WARN on BOOLEANS.
TRAN-150 WARN on STRINGS.
TRAN-151 WARN on POSITIONS.
PATH data type is not
TRAN-152 WARN allowed; create a user-
Please move
TRAN-153 WARN %%DEFGROUP
BYNAME before
is invalid.
TRAN-154 WARN Argument expected.
Must enclose this
TRAN-155 WARN variable in parenthesis
Group number of Id
TRAN-156 WARN does not
Invalid match
port typegroup
for this
TRAN-157 WARN operation.
Label Port:defined
is already %s
TRAN-158 WARN in the PROGRAM.
More than one group Label:
in
TRAN-159 WARN move statement
POSITION or VECTOR
TRAN-160 WARN data type expected.
Scalar or indexed array
TRAN-161 WARN expected, this Id must
Cannot load
TRAN-162 WARN environment file,
PATH, FILE, and vision
TRAN-163 WARN data types may only be
"NODE" group mask
TRAN-164 WARN does not match
Invalid class for Id,
TRAN-165 WARN VARiable or CONSTant
Routine name was
TRAN-166 WARN previously
String used
size is in other
greater
TRAN-167 WARN than 128 or less
Path does not have thana 1.
TRAN-168 WARN position
Path does node. Id: %sa
not have
TRAN-169 WARN header. Id: %s
Cannot load
TRAN-170 WARN environment file,
Cannot load
TRAN-171 WARN environment
Path does notfile, have any
TRAN-172 WARN node data defined.
TRAN-173 WARN Translation cancelled.
TRAN-174 WARN Unknown
%cr - Create option '%c'.
routine
TRAN-175 WARN stack file (.RS) for local
Label used in GO TO
TRAN-176 WARN statement is not
Supersedes previous
TRAN-177 WARN value of
Id is already defined in
TRAN-178 WARN another environment
Argument will be
TRAN-179 WARN passed by
Internal value.
error. Id: %s
Parser
TRAN-180 WARN stack underflow.
Internal error. cannot
TRAN-181 WARN be extracted.
Internal error. Handle =
TRAN-182 WARN %d, offset = %d
Internal error.
TRAN-183 WARN Production not
Internal error.
TRAN-184 WARN Unimplemented p-code
Internal error. Invalid Id
TRAN-185 WARN class to generate
Internal error. Cannot
TRAN-186 WARN find routine
Internal in Value
error. symbolof
TRAN-187 WARN Id exceeded range. Id:
TRAN-190 WARN All Rights
Press any Reserved.
key to
TRAN-191 WARN continue...
TRAN-192 WARN %32s
An error has occured trying to read
VARS-001 WARN Corrupt variable file specifed file. This file is corrupt or the
Try a different file.
The variable file does not exist on the
Place correct media in
VARS-002 WARN Open Error on File device, director or media. drive or select the proper
A variable being loaded from a variable
%s array length file exists in memory. The array length
You do not have to do
VARS-003 WARN updated reflects what was in the variable file.
anything for this warning
%s memory not A variable being loaded from a variable
Clear the program and
VARS-004 WARN updated file exists in memory. The variable file
load the variables first
A variable being loaded from a variable
%s PC array length file exists in memory. The array length
You do not have to do
VARS-005 WARN Unknown
ignored Variable reflects what was in the variable file.
anything
Load foror
PC file this
VRwarning
file to
VARS-006 WARN Name Referenced variable does not exist create the variable
Load PC file or VR file to
VARS-007 WARN Unknown Type Code Referenced type code does not exist createPCthe
Load filetype
or VR file to
VARS-008 WARN Type Name not found Referenced type name does not exist create the named type
SV Load at CTRL Start A variable load has been requested Create an error condition
VARS-009 WARN Only while controller is capable of motion
such as E-stop and load of
This variable is not to be
Variable/field write- The variable or field you are trying to changed by customer for
VARS-010 WARN protected
No data defined for access is write protected
Referenced program name does not safety
Load PC orfile
other reasons
or VR file toIf
VARS-011 WARN program have variables create the named
VARS-012 WARN Create var - %s failed Named variable could not be created. code. Use the Alarm Log
Referenced variable already exist in This is just a notification.
VARS-013 WARN Variable Already Exists memory You do not have to do
VARS-014 WARN Create type - %s failed Named type could not be create code. Use the Alarm Log
Too many The limit of variables types, programs You must delete some
VARS-015 WARN vars/nodes/programs or nodes has been reached programs or reorganize
Axis configuration The variables you are trying to load are These variable cannot be
VARS-016 WARN mismatch were created on a controller with a used on this controller
Sysvar version The system variable file you are You must use the default
VARS-017 WARN mismatch attempting to load is not compatible system variable file
Compatible Type Referenced type already exists in This is just a notification.
VARS-018 WARN Already Exists memory You do not have to do
You are attempting to rename a Use a different program
VARS-019 WARN Rename target exists program
Referenced variable is not found in the name
to a program which already Load PCor file
delete
or VRthefile to
VARS-020 WARN [%s]%s not fnd system create the variable
Memory allocation There is no more permanent memory You must delete
VARS-021 WARN failure available in the system unneeded programs,
Variable that is being created already Delete existing variable
Duplicate creation TYPE exists but is of a different type than before creating it as a
VARS-022 WARN mismatch what you are attempting to load/create different type
Variable that is being created already Delete existing variable
Array len creation exists but has different dimensions before creating it with
VARS-023 WARN mismatch than what you are attempting to conflicting dimensions
Bad variable or register You are attempting to use an invalid
VARS-024 WARN index index into an array or path Use a valid index
Do not have vision hardware on this Load these variables on an
VARS-025 WARN Vision reference error system so cannot load vision variables appropriate system
The file which has been loaded is: A. Try a different file or
Not a variable file B. A file on bad convert the current file to
VARS-026 WARN File sequence
Variable used error
by other media C. A file not compatible with an updated
Delete otherversion.
program
VARS-027 WARN program Variable is used by another program which references these
Consult your SYSTEM RJ-2
Value that you entered is not a valid Controller Software
VARS-028 WARN Value out of range value. It is either too big or too small reference Manual for valid
Requires PROGRAM The operation that you are attempting You must go to the
VARS-029 WARN password is password protected. password setup screen
Requires SETUP The operation that you are attempting You must go to the
Requires INSTALL The operation that you are attempting You must go to the
The variable you are loading is larger Make the array size
than 65,535 bytes or has an array smaller or use a path data
VARS-032 WARN Maximum
Variable size toolength
path big element larger than 32,767 bytes typemust
You for large
breakarrayed
up the
VARS-033 WARN exceeded A path can only contain 2,007 nodes. large path into smaller
The CMOS variable that you attempted Delete the variable in the
to delete was created This could also same start mode that the
be because a KAREL program, Network variable was created. For
or KCL was adding deleteing or doing a example if a CMOS
Variable cannot be node operation when access was variable was created at
VARS-034 WARN accessed
CMOS memory is attempted CONTROLLED
Controller start
initial it must
start
VARS-036 WARN Position
corrupt register is CMOS memory
Position registerhas been destroyed
is locked by program must until
Wait be performed
program is
VARS-037 WARN locked operation finished
Cannot change An existing variable is being created in Delete the variable or
VARS-038 WARN CMOS/DRAM type a different memory area (CMOS vs change the memory type
Permanent memory was successfully This is just a notification.
VARS-039 WARN Data set created allocated. You do not have to do
Cannot load at Variables may not be properly created Load variables at COLD
VARS-040 WARN CONTROL START 2 if loaded at this time. start or at CONTROLLED
Path insertion or delete of a node Perform operation with a
VARS-041 WARN Invalid Node Number occured with node number which valid node number.
The type definition for the variable The program with the
TEMP type invalid for being created is in temporary DRAM type definition for the
VARS-042 WARN CMOS create memory. This means variable cannot be variable you are creating
The memory pool for this variable does Put the old board in back
Variable memory pool not exists on the controller. An auxiliary into the controller. If this
VARS-043 WARN is invalid board has probably been removed or board is not not available
Group number The variable file has different number You must configure the
VARS-044 WARN mismatch on load of groups defined than controller. groups from controlled
The robot type referenced in the Setup the controller for
Mismatch SV - %s loaded SV file is different than the type the proper robot type and
VARS-045 WARN System %s that the controller is setup for. load system variables
When transferring a variable to a Allocate a larger buffer for
VARS-046 WARN Buffer size mismatch different computer the memory buffer the transfer
Incompatible var file The variable file that you specified does This file is not useful. You
VARS-047 WARN version not contain
The variablekey information
name it isthe
specified in needmust
You to get the the
change
VARS-048 WARN Bad
Name is too big
Element in a request is too long. variable name to make it
VARS-049 WARN Structure The ASCII value specified is invalid. Specify a valid ASCII value.
The version of the saved PC image and
PC Revision mismatch saved VR image are different. This is
VARS-050 WARN %s probably because power was removed Load the PC file again.
The requested operation is not You must do this
VARS-051 WARN Illegal operation supported on this processor operation in a different
A system variable file created on an
earlier version has been loaded. The
specified variable changed since that
VARS-052 WARN Variable %s converted early release so it has been converted. This is informational.
Input data pointer The variable data pointer specified is This is an error in the
VARS-053 WARN invalid incorrect Or an invalid pointer was sent application Check all
A system variable file created on an
VARS-054 WARN Sysvars - %s loaded earlier version has been loaded. This is informational.
Another program exists with the same
Program name is not program name in first eight Characters. Change the name of the
VARS-055 WARN unique Program name must be unique in the program
You cannot load any
additional options on this
SYSTE No more system types All available system types are already controller. If you need a
VARS-056 M available being used on this controller. different set of options
There are too many user types defined When you load this file
to be saved in one file. Each file can you must load all of the
hold up to 255 types. If more than 255 individual files created.
types are referenced, then it will use During loading, the file
VARS-057 WARN Using %s for save additonal files. This error should only names will have an index
Remote version is not You attempted to access a controller Update the target
VARS-058 WARN compatible that is using an incompatible software controller to the same
Program name syntax is Make sure you use UNC
VARS-059 WARN bad The program name syntax is invalid. compatible naming to
Variable type is not Make sure you use UNC
VARS-060 WARN compatible The program name syntax is bad. compatible naming
You cannot load any
additional programs on
this controller. You can
No more user types All available user types are already delete programs and
VARS-061 WARN available being used on this
No variable or program No name supplied for controller. variables
Make suretoyou freesupply
up types.
a
VARS-062 name program/variable. name
The named variable will
The CMOS memory for the named be set to "Uninitialized" in
variable was corrupted. This named the process and might
[%s]%s CMOS variable was reallocated as a result of need to be set back to a
VARS-063 WARN lost/reallocated the corruption. valid initial value. In
The alarm will occur when you attempt
to do a GET_VAR or SET_VAR but the Be sure that the array
array indices do not match. For indices line up with the
example, the variable type is a one variable that you are
VARS-107 WARN Illegal array
BD_INFO operation dimensional array but you specify two attempting to access.
is FANUC
VARS-121 WARN V5.11
Allocate a larger buffer
VARS-122 WARN for the transfer
VARS-123 WARN different file
VARS-124 WARN to makeaitvalid
Specify shorter.
ASCII
VARS-125 WARN value.
You must do this
VARS-126 WARN operation in aset
with the new different
of
VARS-127 WARN options System variable data has been Cycle Start the controller
VARS-200 corrupted
[%s]%s 0x%x bad end corrupted.
System variable data has been and try
Cycle the the
Start operation
controller
VARS-201 tag corrupted. and try the operation
[%s]%s (%d) Shadow An unexpected internal error has led to the error and
VARS-202 error occurred contact your FANUC
[%s] (%d) Interrupted Power cycle interrupted the variable The system has attempted
VARS-203 WARN Power
file saveoff incomplete file backup. tothe
If recover. Cycle
problem power to
persists,
VARS-204 WARN %d Power off processing did not complete. replace the hardware.
Move some variables to
VARS-205 WARN Shadow memory full SHADOW memory is full. DRAM or mark variables
The variable must be reallocated at
VARS-206 %s will load at startup system initialization. None.
A file that deferred loading until startup
VARS-207 %s loaded at startup has succesfully loaded. None.
A file that deferred loading until startup Correct the problem in
VARS-208 %s loaded failed has failed to load. See the cause code. the file and try the
[%s]%s Shadow A path node of a shadowed path has Save the PRV file via the
VARS-209 Disabled
%s only one shadow been
A shadowed path already exists in this SAVE_DRAM
modified but shadow is disabled. Move the shadow built-in to to
path
VARS-210 path per program program. its own program.
%s Shadow paths A shadowed path and some other Move the shadow path to
VARS-211 exclude other shadow shadow variable cannot exist in the its own program name.
The program is protected and cannot Unprotect the program
VARS-212 Program is protected be cleared or reloaded. from the
Check theapplication.
console log for
VDIG-000 unknown error Internal system error details
Setup can only be run in one pane at a Dismiss setup Cold start
from the
VDIG-001 Setup is aleady active time other pane
Inv state num. Indicator A state number in vdscreens.xml for The state information is
VDIG-002 %s this indicator is invalid ignored. Fix it in the setup
This error is raised if the
The Custom Logic Program takes too program takes over 1
VDIG-003 CLP %s takes too long. long to run second to run. It should
The hardware diagnostics executed by Replace the V-400i board
VISN-001 WARN Vision diagnostics failed the V-400i system powerup failed. set, if possible, or call your
Use the vision training
OBJ_OFFSET cannot determine the menus to determine why
offset because one or more of the the object was not found,
PAUSE. Offset unknown-feature location tools in the vision process and retrain the location
VISN-002 G missing failed to find the feature in the image. tools if necessary. Add
Use the vision training
FOUND_ENDPTS cannot cannot menus to determine why
determine the line end-points because the feature was not
Feature not found in the location tool in the vision process found, and retrain the
VISN-003 WARN the image failed to find the feature in the image. location tool if necessary.
FOUND_CIRCLE cannot cannot Use the vision training
determine the circle parameters menus to determine why
because the location tool in the vision the circle was not found,
Circle not found in the process failed to find the circle in the and retrain the location
VISN-004 WARN image image. tool if necessary. Add
FOUND_LINE or FOUND_PLANE cannot Use the vision training
cannot determine the geometric menus to determine why
parameters because the location tool in the line was not found,
Line not found in the the vision process failed to find the line and retrain the location
VISN-005 WARN image in the image. tool if necessary. Add
FOUND_ELLIPS cannot cannot Use the vision training
determine the ellipse parameters menus to determine why
because the location tool in the vision the ellipse was not found,
Ellipse not found in the process failed to find the ellipse in the and retrain the location
FOUND_BRDATA cannot cannot Use the vision training
determine the connectivity parameters menus to determine why
because the location tool in the vision the region was not found,
Region not found in the process failed to find the region in the and retrain the location
An edge with the specified name does Make sure the edge name
Edge not found in the not exist in the model in the call to and the model are
VISN-008 WARN model INIT_FF_VSPR, MATCH_LINE, or correct.
Vertex not found in the A vertex with the specified name does Make sure the vertex
VISN-009 WARN model not exist in the model in the call to name and the model are
Circle not found in the A circle with the specified name does Make sure the circle name
VISN-010 WARN model not exist in the model in the call to and the model are
Model edge is not a The specified model feature is not a Make sure the circle name
VISN-011 WARN circle circle in the call to MATCH_CIRCLE or and the model are
The specified model feature is not a Make sure the line name
VISN-012 WARN Model edge is not a line line in the call to MATCH_LINE, or and the model are
The array you passed to a routine has Check the built-in
PAUSE. Bad input array length an invalid length (number of elements). description for restrictions
VISN-013 G %d The value of "&new_linexxx" indicates on the parameters.
One of the options you passed to
OPTIONS_CS in the integer or real
arrays is out of range. The number
PAUSE. Bad cam_setup option indicates which array element was bad. Change the value of the
VISN-014 G # %d The integer array elements are bad array element.
OPTIONS_OF in the integer or real
PAUSE. Bad object find option # indicates which array element was bad. Change the value of the
VISN-015 G %d The integer array elements are bad array element.
OPTIONS_FF in the integer or real
arrays for the scanning algorithm is out
PAUSE. Bad scanning option # of range. The number indicates which Change the value of the
VISN-016 G %d array element was bad. The integer bad array element.
arrays for the shape match algorithm is
PAUSE. Bad shape match out of range. The number indicates Change the value of the
VISN-017 G option # %d which array element was bad. The bad array element.
arrays for the edge tracing algorithm is
PAUSE. Bad edge trace option # out of range. The number indicates Change the value of the
VISN-018 G %d which array element was bad. The bad array element.
OPTIONS_BR in the integer or real
PAUSE. Bad connectivity option indicates which array element was bad. Change the value of the
VISN-019 G # %d The integer array elements are bad array element.
One or more of the elements in the Make sure all of the mask
Convolution coeffs. convolution mask array you passed to array elements are in
VISN-020 WARN truncated CONVOLVE was greater than 31 range.
The point passed to or returned from Change the location of the
Point not located within FOUND_LINE3D, FOUND_POINT, point so that it within the
VISN-021 WARN image PIXREAD, PIXWRITE, PLOT_POINT, or field of view.
The window that was to be used for the Resize the window so that
Window boundaries attempted operation has boundaries its boundaries are within
VISN-022 WARN not in image that extend outside of the range of the the range of the screen.
The window that was to be used for the Change the values of the
Invalid window attempted operation has invalid high and/or low rows
VISN-023 WARN boundaries boundaries, most likely, the high row (columns).
Integer value %d out of The integer value you specified is not Check the parameter
VISN-024 WARN range within the valid range for that variable. values to find the valid
You supplied an illegal dimension, an Refer to the
Invalid convolution invalid length array, or an invalid kernel MAKE_KERNEL built-in
VISN-025 WARN parameters type when calling MAKE_KERNEL. description for restrictions
PAUSE. You supplied an invalid direction code Refer to the PROFILE built-
VISN-026 G Invalid direction value when calling PROFILE. in description for
You passed a three dimensional line Make sure the line is
variable to the routine L3_PL_INTER or normalized.
PAUSE. Invalid 3-D line LINE3D_INTER that is not in the Mathematically, this
VISN-027 G parameters normalized form. means that the direction
You passed a plane variable to the Make sure the plane is
PAUSE. Invalid plane routine L3_PL_INTER or PLANE_INTER normalized.
VISN-028 G parameters that is not in the normalized form. Mathematically, this
Vision process is not The VIS_PROCESS parameter which was Make sure to train the
VISN-029 WARN trained
Illegal vision global passed to a built-in routine has not VIS_PROCESS variable
VISN-030 WARN variable This error message is not used. N/A
There are two possible causes of this
error: 1. PROFILE was called with one of
the diagonal directions (3 or 4), which Do not attempt to use
are not supported in this version of the these unsupported
VISN-031 WARN Vision Driver: %d %d software. 2. IMG_MOMENTS or features.
The built-in routine EXTRACT_FF, Make sure the vision
OPTIONS_FF, TRAIN_FF, TRAIN_OF, or process is set up correctly
WIN_SET_FF was called with a vision by first calling
VISN-032 WARN Feature-find not setup process which has not been set up. INIT_FF_VSPR for feature
You called a built-in routine with Check the built-in
VIS_PROCESS that uses an algorithm description for restrictions
which is not appropriate for that built- on the parameters. Make
Invalid algorithm type in. For example, you cannot call sure that the
VISN-033 WARN %d FOUND_MODEL with a VIS_PROCESS VIS_PROCESS parameter
You called INIT_FF_VSPR with a feature Check the built-in
Feature and alg. do not type and algorithm type that do not description for restrictions
VISN-034 WARN match match. For example, you cannot find a on the parameters.
The built-in routine CAM_CALIB, Train the CAM_SETUP
Must supply initialized OPTIONS_CS, or TBL_SET_CS was called variable before calling one
VISN-035 WARN cam_setup
Vis_Process not an with a CAM_SETUP variable which has of these built-in routines.
VISN-036 WARN Acquire This error message is not used. N/A
Do not call WIN_GET_FF
with this type of
You called the built-in routine VIS_PROCESS. The value
Vis_Proc. not Feature WIN_GET_FF with a VIS_PROCESS of "&new_linexxx"
VISN-037 WARN Find %d which is not trained as a location tool. indicates the type of
The built-in routine INIT_CS was called make sure that the
VISN-038 WARN Invalid camera number with a camera number which is out of camera number is within
The built-in routine INIT_CS was called
with an invalid calibration method, or Check the built-in
Invalid calibration else the built-in routine CAM_CALIB description for restrictions
VISN-039 WARN method %d was called with a calibration method on the parameters.
The built-in routine OPTIONS_CS was If you want to change the
Cam_setup changed to called with integer array element 5 set CAM_SETUP parameters
VISN-040 WARN NOT TRAINED to 0. and force it to still be
Vision array length The array you passed to a built-in has Check the built-in
VISN-041 WARN mismatch the wrong number of elements. description for the correct
You passed a parameter to a built-in Check the built-in
Vision parameter value that is incompatible with the function description for restrictions
VISN-042 WARN bad or with other parameters. on the parameters.
You called a built-in routine with Check the built-in
VIS_PROCESS that is trained to find a description for restrictions
feature which is not appropriate for on the parameters. The
that built-in. For example, you cannot value of "&new_linexxx"
VISN-043 WARN Invalid feature type %d call FOUND_LINE with a VIS_PROCESS indicates the type of
Invalid array index or The array or array index that you Check the built-in
VISN-044 WARN length passed to a built-in is invalid. description for restrictions
Cam_setup successfully Informational message displayed by the
VISN-045 WARN TRAINED built-in routine CAM_CALIB. None is required.
Changed $WINDOW The search window used by the built-in None necessary. Values
VISN-046 WARN boundaries routine is invalid or extends beyond the are automatically
The built-in routine MEAS_MUL_DIS, The image type is
MEASURE_ALL, MEASURE_DIST, or specified in the first
TRAIN_GAUGE was called with an element of the gauge
VISN-047 WARN Invalid image type invalid image type. parameters, which are
The built-in routine MEAS_MUL_DIS, Modify the gauge
Gauge not totally in MEASURE_ALL, or MEASURE_DIST was endpoints to be within the
VISN-048 WARN image called with a gauge that was not totally screen boundaries.
The built-in routine MEAS_MUL_DIS, Modify the width. It must
MEASURE_ALL, MEASURE_DIST, or be within the range 1 to 3.
PAUSE. TRAIN_GAUGE was called with an The width is specified in
VISN-049 G Invalid gauge width invalid gauge width. the third element of the
Element "xxx" in the configuration Check the built-in
PAUSE. Invalid Profile array, which is an input parameter to description for restrictions
VISN-050 G configuration %d the built-in routines PROFILE_FIND and on the parameters.
Vision variable training was attempted Exit training from the
Teach Pendant training from the CRT menus or from a KAREL teach pendant before
VISN-051 WARN active program, but training is already active attempting training from
Vision variable training was attempted Exit training from the CRT
from the teach pendant menus or from menus before attempting
VISN-052 WARN CRT training active a KAREL program, but training is training from the teach
Vision variable training was attempted Exit training from the
Karel program training from the teach pendant menus or from KAREL program before
VISN-053 WARN active the CRT menus, but training is already attempting training from
VISN-054 WARN Cannot plot this type This error message is not used. N/A
Cam_setup is not The CAM_SETUP parameter which was Make sure to train the
VISN-055 WARN trained passed to a built-in routine has not CAM_SETUP variable
The variable file you tried to LOAD
Incompatible vision contains vision variables that are The variables must be
VISN-056 WARN variables incompatible with the current software retrained.
The vision program cannot be run Load the other program
Cannot run due to because it contains vision variables containing the required
VISN-057 WARN reference which refer to vision variables in variables before
Cannot delete due to The vision variable cannot be deleted Delete the other vision
VISN-058 WARN reference because it is referred to by another variable first.
A file open error occurred while trying Make sure that the file
VISN-059 WARN Error opening file to read or write a model file or an device is ready and try
A file close error occurred while trying Make sure that the file
VISN-060 WARN Error closing file to read
An errororoccurred
write a model file orto
while trying anread devicesure
Make is ready
that and
the try
file
VISN-061 WARN Error reading file an image file. device is ready and try
An error occurred while trying to write Make sure that the file
VISN-062 WARN Error writing file a model file or an image file. device is ready and try
Vision training was attempted from the Select the correct
No vision variables in teach pendant or CRT menus, but the program before trying
VISN-063 WARN program currently selected program does not vision training.
A built-in routine has been called with a
vision process which has been trained
for a multiple camera view location, Do not try to use this built-
PAUSE. Multiple views not but the built-in does not support this in with this type of vision
VISN-064 G allowed type of vision process. Usually, this is process
A built-in routine has been called with a
vision process which has been trained
with a location tool list, but the built-in Do not try to use this built-
PAUSE. Location tool list not does not support this type of vision in with this type of vision
VISN-065 G allowed process. Usually, this is because it is process
PAUSE. The built-in routine INIT_VP_VIEW has Train the MODEL before
VISN-066 G Model is not trained been called with a MODEL parameter calling INIT_VP_VIEW.
PAUSE. View config. %d out of The built-in routine INIT_VP has been Check the built-in
VISN-067 G range called with an invalid viewing description for restrictions
PAUSE. Location type %d out of The built-in routine INIT_VP_VIEW has Check the built-in
VISN-068 G range been called with an invalid location description for restrictions
PAUSE. Output array is too The output array passed to the routine Increase the output array
VISN-069 G short %d MEAS_RESULTS or VP_TOOL_LIST is not length and try again.
The built-in routine INIT_VP_VIEW has Correct the requested
PAUSE. View number %d out of been called with a view number larger view number and try
VISN-070 G
ABORT. range Bad Input
3DGP than the number of views which were again.
VISN-071 G Parameter Internal error in Host Simulator menu. Contact FANUC Robotics.
ABORT. 3DGP Corrupt Vision Camera, target, or part data in memory Check camera, target, or
VISN-072 G
ABORT. Data Vision Code Not A
3DGP has been corrupted.
required KAREL routine was not part variables
Make sure theusing TP is
software
VISN-073 G Loaded loaded. loaded properly.
ABORT. The task IGP_TASK could not be run in Make sure the software is
VISN-074 G 3DGP Task Not Active the routine IGP_START in the module loaded properly.
No vision boards installed. The Make sure that the vision
operator attempted to set the Use boards are installed and
ABORT. 3DGP No Vision Internal Hardware flag or the idle active the V-400i software is
VISN-075 G Hardware Installed flag from the Host Simulator menu, but loaded.
The task IGP_TASK is not running, but
the task IGP_TRN3 is. IGP_TASK should
ABORT. 3DGP Package Not never abort, and is automatically Find out how IGP_TASK
VISN-076 G
ABORT. Running started every time the operator selects was aborted or paused.
VISN-077 G
ABORT. Nest Error
3DGP Library Locking This error message is not used. N/A
VISN-078 G Error This error message is not used. N/A
One of the routines IGP_NEW_PART, Do not attempt these
ABORT. 3DGP Illegal Broadcast IGP_NEW_TARG, or IGP_FND_TARG operations while in
VISN-079 G Mode was called with the broadcast mode Broadcast mode and not
During the loading process, the Check the spelling of the
ABORT. 3DGP No Work Cell by specified work cell name could not be work cell name in the
VISN-080 G that Name found in the bubble memory. autoload file. Also make
During the load process, the specified Check the spelling of the
ABORT. 3DGP No Part by that part name could not be found in the part name in the autoload
VISN-081 G Name bubble memory. file. Also make sure that
ABORT. 3DGP No Target by that target name could not be found in the target name in the
VISN-082 G Name bubble memory. autoload file. Also make
ABORT. 3DGP No Camera by camera name could not be found in the camera name in the
VISN-083 G
ABORT. that
3DGPName
Not Valid Vision bubble memory. autoload file. Also make
VISN-084 G Data This error message is not used. N/A
ABORT. 3DGP Library Request Timeout occurred while waiting for Check hardware and
VISN-085 G Time Out response from other robot. cables. Make sure
ABORT. An error occurred while attempting to Check hardware and
VISN-086 G 3DGP Process Time Out route a message to another robot. cables. Make sure
ABORT. 3DGP Not Control of A vision request was received by a Check vision hardware.
VISN-087 G Hardware robot which has the Use Internal Make sure Use Internal
You tried to select a work cell from the You must load the work
ABORT. 3DGP Work Cell Not on-screen list in the Utilities Menu, or cell files into RAM before
VISN-088 G Trained the Autoload Menu, when there are they appear in the on-
ABORT. You have attempted to find a part by You must train a part
VISN-089 G 3DGP Part Not Trained using the F10, FIND function key, in the completely before using
ABORT. 3DGP Target Not You have tried to use a target before it
VISN-090 G Trained has been trained completely. Train the target first.
The camera must be calibrated before
ABORT. 3DGP Camera Not it can be specified for use by a target, a
VISN-091 G Trained part, a work cell, or the V-400i vision
Calibrate the camera.
ABORT. The part could not be found due to one
Check the status display
VISN-092 G 3DGP Part Not Found or more targets not being found or due
to determine why the part
Use the target training
ABORT. The target was not found by the vision menus to determine why
VISN-093 G 3DGP Target Not Found system. the target was not found.
The part offset computed by the vision Check the part location to
ABORT. system is larger than the offset see whether it is within
VISN-094 G 3DGP Offset Tolerance tolerance. the specification. Check
The found target positions are not Use the Part Editor Menu
ABORT. 3DGP Target Fit consistent with the trained target to find and check each of
VISN-095 G Tolerance positions. the targets. Make sure
Check all of the cameras
ABORT. A mathematical error occurred while to make sure that the
VISN-096 G 3DGP Solution Error trying to find the part position. calibration frames are.
The fit error exceeded the target fit Check the status display
tolerance when all of the targets were to determine which
3DGP Not All Targets used. One or more bad targets were targets were declared bad
VISN-097 WARN Used
ABORT. deleted,
A severe and a position
internal wasoccurred
error has calculated
in and omitted from the
VISN-098 G 3DGP General Fault the software. Call FANUC Robotics.
An error has occurred while attempting
ABORT.
3DGP Serial to communicate with another robot Check the
VISN-099 G Communications Fault using the serial communications lines. communications cables.
VISN-100 WARN Nom. pos. set (%s)
VISN-101 WARN Set Variable
Variable Name
names arefirst
the
VISN-102 WARN same
VISN-103 WARN Variable
Vision type is pool
memory wrong
VISN-104 WARN empty
PAUSE.
Nominal position is not The nominal data required for this Carry out nominal
VISN-105 G set vision mnemonic has not been set. execution and set nominal
Location tool is not The LOCATION TOOL parameter which Make sure to train the
VISN-106 WARN trained was passed to the vision mnemonic has LOCATION TOOL variable
Meas. tool is not The MEASUREMENT TOOL parameter Make sure to train the
VISN-107 WARN trained which was passed to the vision MEASUREMENT TOOL
You executed the vision mnemonic Specify a vision variable
VISN-108 WARN Vis_Proc. not a Loc. tool with a vision variable which is not which is trained as a
Vis_Proc. not a Meas. You executed the vision mnemonic Specify a vision variable
VISN-109 WARN tool with a vision variable which is not which is trained as a
You executed the vision mnemonic Specify a vision variable
Vis_Proc. not a Master with a vision variable which is not which is trained as a
VISN-110 WARN VP trained as a master vision process. master vision process.
Same register number Same register number is used as Specify another register
VISN-111 WARN is usedposition
Robot arguments in one vision instruction. number.
VISN-112 WARN uninitialized
Bad pointer set to
VISN-113 WARN NULL, data loss
Image buf. is write Cannot save the image into the Try save the image after
VISN-114 WARN protected specified image buffer by write protect. release write-protection
The images of the image buffer #7 and
#8 on the vision engine PCB were
erased by turning power of controller
Image #%d erased by off. If image buffer #7 or #8 is saved,
VISN-115 WARN power down and the power is turned off, this error None.
VISN-116 WARN No image
Cam Setupfile
Image not The images file is not existed. None.
VISN-117 WARN LINEAR
The vision process find was
unsuccessful. The light-meter window
Adjusting gains and option is enabled, so the gains will be
VISN-118 WARN retrying
No tracking schedule adjusted
The for any
tracking lighting
schedule change
data is notand None.
VISN-119 WARN data existed. INstall the tracking option.
The setting data for pulse encoder is Check the setting data in
VISN-120 WARN Invalid encoder setting invalid, so the system can not read encorder setting screen
Only one location tool may be used in a Remove extra location
Invalid Find Next find next operation. Or the first vision type vision tools or ensure
VISN-121 WARN operation tool is not a location tool. the first vision tool is not a
Invalid vision tool One of the vision tools references a Unreference the vision
VISN-122 WARN referenced vision tool that follows its location. tool and retry the
Invalid offset tool One of the vision tools referenced by Unreference the vision
VISN-123 WARN referenced find/window offset tool is not valid for tool and retry the
PAUSE. Tracking queue is full, so vision can not Clear unnecessary queueu
VISN-124 G Tracking queue is full push vision result into tracking queue. or expand the number of
No tracking queue to be Can not pop vision result from tracking Pop tracking queue after
VISN-125 WARN popped queue because tracking queue is vision process is executed.
VISN-126 WARN Tracking queue error Can not handle tracking queue.
Image buf. #%d not for When visual tracking function uses the Change the usage of the
VISN-127 WARN system image buffer #7 or #8, the usage of the image buffer from USER
Reference tool not A window can not be placed because
VISN-128 WARN found the tool it references cannot be found.
Reference tool not A window can not be placed because Retrain the tool that is
VISN-129 WARN trained the tool it references is not trained. referenced.
Reference tool not Attempt to use multi gauges without a A reference tool must be
VISN-130 WARN defined proper reference tool. selected before multi
A multi gauge Attempt to delete a reference tool that Set multi gauge Use
VISN-131 WARN references tool is referenced by a multi gauge. Rotation Ghost and Use
Reference tool not Attempt to use multi gauges without a A reference tool must be
VISN-132 WARN Connectivity proper Connectivity reference tool. selected before multi
Tool Referenced by Calc Attempt to disable multi gauges The gauge name must be
VISN-133 WARN Offset tool without remiving its reference in calc removed from the calc
Tool Referenced by Attempt to remove a connectivity tool The multi gauge tool must
VISN-134 WARN Vision
Gauge Variable
tool in that is referenced by a multi gauge. be removed
Call before
your FANUC the
Robotics
VISN-135 WARN Temp_Pool
3DGP Vision Offset Design problem.
The vision system is reattempting to service.
None required. This is
VISN-136 WARN Retry Attempt find the part. status information only.
Press
The communication port setup is MENUS=>SETUP=>TYPE=>
3DGP Configure Port %s incorrect. A port configured for use by PORT INIT and set the
VISN-137 WARN to No Use 3DGP is in use by another device. communications port in
The vision system failed to initialize a If posted with VISN-137,
3DGP Failed to open communication port. May be posted use the remedy for VISN-
VISN-138 WARN Port %s with VISN-137. 137. Otherwise,
Consult check the
your system
VISN-139 WARN 3DGP %s Site specific alarm. documentation.
Robot RUN WITHOUT OFFSETS input is Check the RUN WITHOUT
3DGP Run Without on. This robot will NOT request a OFFSETS input from the
VISN-140 WARN Offsets VISION FIND, and the job will be PLC, it should be OFF.
Retry the find part
3DGP Required Target The vision system was unable to find a process. If this fails, you
VISN-141 WARN Not Found target with a 'MUST FIND' attribute. may need to touch-up the
the VISION OFFSET DATA
SOURCEs have been set
3DGP Vision Master Not This robot could not find a valid vision up in the P_XXXXXX part
VISN-142 WARN Found master to send a message to. file. Check that the port
The find part attempt failed with a 'Fit This is a warning and no
Tolerance' error. The part file has been action is necessary unless
3DGP Vision Degrade set up to retry vision by asking for this function is not
VISN-143 WARN
PAUSE. Part Retry another set of offsets, most likely using desired. To disable this
VISN-401 G
PAUSE. dummy
VISN-501 G
PAUSE. $IVCFG not got
VISN-502 G
PAUSE. $IVCLBJIG not got
VISN-503 G
PAUSE. $IVSCHD not got
VISN-504 G
PAUSE. $IVSENS not got
VISN-505 G $DEBUG not read
PAUSE. This sensor function and the previous
VISN-506 G
PAUSE. Function mismatch one are mismatch. When PS > 1, they Match them.
VISN-507 G $DTCT_TYPE not wrote
PAUSE. Bad measurement When PS > 1, it must be just one larger
VISN-508 G
PAUSE. position num than the PS number of the previous Correct the PS number.
VISN-509 G
PAUSE. $PS_NUM not wrote
VISN-510 G
PAUSE. $TEMP_VEC not read
VISN-511 G
PAUSE. $TEMP_VEC not wrote
VISN-512 G
PAUSE. $MN_COMP not read
VISN-513 G
PAUSE. $MN_COMP not wrote
VISN-514 G
PAUSE. $MN_STAT not wrote Correct the group in the
VISN-515 G Bad robot group The robot group must be from 1 to 5. sensor schedule screen.
PAUSE. Bad sensor data The sensor data number must be from Correct the sensor data
VISN-516 G number 1 to 5 number in the sensor
PAUSE. Bad status output The status output number is not set Correct the status output
VISN-517 G
PAUSE. number rightly. numberthe
Correct in the sensor
offset type in
VISN-518 G Bad offset type The offset type is not set rightly. the sensor schedule
PAUSE. Bad offset output The offset output number is not set Correct the offset output
VISN-519 G number rightly. number in the sensor
PAUSE. Correct the offset limit
VISN-520 G Bad offset limit XYZ The offset limit XYZ must be plus. XYZ in the sensor schedule
PAUSE. Correct the offset limit
VISN-521 G Bad offset limit angle The offset limit angle must be plus. angle in the sensor
Correct the offset limit in
Offset position not The offset position exceed the offset the sensor schedule
VISN-522 WARN
PAUSE. calculated limit or the sensor function failed. screen. Or move the robot
VISN-523 G
PAUSE. Bad offsetposition
Nominal positionnot
VISN-524 G
PAUSE. read
Nominal position not
VISN-525 G wrote
PAUSE. Correct the nominal
VISN-526 G Bad nominal
Actual position
position not The nominal position is not set rightly. position in the
Execute the sensorfrom
function
VISN-527 WARN
PAUSE. calculated
Actual position not The sensor function failed. the beginning.
Execute the function from
VISN-528 G normalized The sensor function failed. the beginning.
VISN-529 WARN
PAUSE. Actual position not set The actual position of the work is not Detect the actual position
VISN-530 G
PAUSE. position
Bad actual correction set rightly. again.
VISN-531 G
PAUSE. XYZ
Bad actual correction
VISN-532 G NOA
PAUSE. The sensor function is different from
VISN-533 G Bad function that in the sensor schedule screen. Match them.
PAUSE. Bad laser intensity The laser intensity threshold must be Correct the laser intensity
VISN-534 G
PAUSE. threshold
Laser int. threshold not from 0 to 255. threshold in the sensor
VISN-535 G
PAUSE. set
VISN-536 G Laser power not set
PAUSE. Correct the scanning
VISN-537 G Bad scanning center The scanning center is not set rightly. center in the sensor
VISN-538 G
PAUSE. Bad scanning
Scanning range
range not The scanning range is not set rightly. range in the sensor
VISN-539 G made
PAUSE. The scanning direction must be +X, -X, Correct the scanning
VISN-540 G Bad scanning direction +Y or -Y. direction in the sensor
VISN-541 G
PAUSE. Bad scanning width The scanning width must be plus. width inthe
Correct thespot
sensor
pitch in
VISN-542 G
PAUSE. spot pitch
Bad number of spot pitch
The number ofmust be plus.
scanning lines is too the sensor
Correct schedule
scanning line
VISN-543 G
PAUSE. scanning lines many or 0. interval or scanning
Correct spot pitch or
VISN-544 G Bad number of spots The number of spots is too many or 0. scanning range.
PAUSE. Correct the sensing MAX Z
VISN-545 G Bad sensing MAX Z The sensing MAX Z is not set rightly. in the sensor schedule
PAUSE. The sensing MIN Z must be smaller Correct the sensing MIN Z
VISN-546 G Bad sensing MIN Z than the sensing MAX Z. or the sensing MAX Z in
PAUSE. Bad dispersion of The dispersion of measurement is not Correct the dispersion of
VISN-547 G
PAUSE. measurement set rightly. measurement
VISN-548 G Bad $SEG_MIN_NUM
PAUSE. Bad edge judgement The edge judgement direction must be Correct the edge
VISN-549 G direction +X, -X, +Y, -Y, +Z or -Z. judgement direction in
PAUSE. The diameter must be larger than twice Correct the diameter or
VISN-550 G Bad diameter the spot pitch. the spot pitch in the
PAUSE. The cylindar length must be larger than Correct the cylindar
VISN-551 G Bad cylindar length twice the cylindar diameter. length or the cylindar
PAUSE. The cylinder direction must be +X, -X, Correct the cylinder
VISN-552 G
PAUSE. Bad cylindar direction The
+Y, -Y, +Z or -Z. number must be
verification directionthe
Correct in number
the sensorin the
VISN-553 G
PAUSE. Bad verification number positive. sensor schedule
Correct the sensor screen.
VISN-554 G
PAUSE. Bad sensor location The sensor location is not set rightly. locationthe
Correct in the sensor
sensor data
frame
VISN-555 G Bad sensor frame The sensor frame is not set rightly. in the sensor data screen.
This schedule number and that of the
PAUSE. Schedule number previous sensor function are mismatch.
VISN-556 G
PAUSE. mismatch When PS > 1, they must be the same. Match them.
VISN-557 G $SC_NUM not wrote
Check the schedule and
VISN-558 WARN Fail to calculate circle
PAUSE. The sensor function failed. execute the function from
VISN-559 G
PAUSE. Osnewmem fail
VISN-560 G Osdspmem fail
The sensor function failed. Because No the beginning. If this error
VISN-561 WARN Edges not got edge points was got. often occurs,
Execute Set the from
the function
VISN-562 WARN
PAUSE. Fail to calculate line The sensor function failed. the beginning.
VISN-563 G
PAUSE. Iccurpos fail
VISN-564 G
PAUSE. SetSpot fail
Scanning measurement
VISN-565 G fail
Set the sensor schedule or
VISN-566 WARN No detected point There is no detected point. teach the robot again so
Set the sensor schedule or
VISN-567 WARN No valid
Fail detected
to find quasi- point There is no valid point. teach thethe
Execute robot againfrom
function so
VISN-568 WARN highest The sensor function failed. the beginning.
VISN-569 WARN Fail to find crowd
cylindar The sensor function failed. the beginning.
VISN-570 WARN
PAUSE. head The sensor function failed. the beginning.
VISN-571 G
PAUSE. Scanning fail
VISN-572 G $MN_STAT not read An alarm occurred in the previous Execute the function from
VISN-573 WARN Previous
No function
valid point failed
within function. the beginning.
VISN-574 WARN
PAUSE. range The sensor function failed. the beginning.
VISN-575 G
PAUSE. Calibration
Bad check
calibration fail
check calibration
The nominal of check fail.
the calibration check is the beginning.
Correct the nominal in the
VISN-576 G nominal not set rightly. sensor schedule screen.
PAUSE.
VISN-577 G Bad $PNT_NUM
PAUSE.
Bad calib check corner The scanner positions of corner points Correct the scanner
VISN-578 G pos
PAUSE. must be from 0 to 16383. positions in the sensor
VISN-579 G Bad $XNP or $YNP
PAUSE.
VISN-580 G Bad $POWER
Fail to calculate Check the schedule and
VISN-581 WARN doughnut The sensor function failed. execute the function from
Check the schedule and
VISN-582 WARN Fail to calculate plane The sensor function failed. execute the function from
PAUSE. The diameter margin must be larger Correct the diameter or
VISN-583 G Bad diameter margin than the spot pitch. the spot pitch in the
VISN-800 WARN Vision diagnostics failed
VISN-801 WARN Firmware errr %d
VISN-802 WARN Cameracamera
Invalid not connected
VISN-803 WARN maximum
Invalid encoder
VISN-804 WARN parameter
VISN-805 WARN Trigger waiting timeout
VISN-810 WARN File already exists
VISN-811 WARN File does not exist
VISN-812 WARN Memory is empty
VISN-813 WARN File system error
VISN-814 WARN Set Variable Name first
VISN-815 WARN BMP file was loaded
VISN-816 WARN BMP file was saved
VISN-817 WARN BMP file not loaded
VISN-818 WARN BMP file not saved
VISN-900 WARN Too few feature to train
VISN-901 WARN Feature not found
VISN-902 WARN Invalid model file
VISN-903 WARN Invalid model version
VISN-904 WARN Invalid param file
VISN-905 WARN Invalid param vesion
VISN-906 WARN Model not
Invalid datatrained
type to
VISN-907 WARN load
VISN-908 WARN Invalid version to load
VISN-909 WARN Calib not trained
VISN-910 WARN Invalid camera type
VISN-911 WARN Computation
Too error
few calibration
VISN-912 WARN points
VISN-913 WARN Same calibration point
VISN-914 WARN Invalid camera type
VISN-915 WARN Loc. tool error %d
WEAV-000 WARN unknown
Weave errorvariable
global (WV00) Internal system error Cold start controller
Controlled start, initialize
WEAV-001 WARN
PAUSE. failure
Weave motion data Weave variables not loaded motion softparts
WEAV-002 G
PAUSE. missing
Weave error allocating Internal system error Cold startunneeded
Remove controllerloaded
WEAV-003 G
PAUSE. data
Weave system variable Not enough
Weave memory
system variables not loaded or variables and
Controlled programs
start, init
WEAV-004 G
PAUSE. failure
Weave pattern does initialized motion softparts
WEAV-005 G
PAUSE. not
Weaveexistillegal schedule Internal system error Delete
ChangeProgram line
weave schedule to
WEAV-006 G number Invalid weave schedule number be in limits
PAUSE. Weave illegal frequency Change frequency to be
WEAV-007 G
PAUSE. value
Weave illegal amplitudeFrequency value invalid within
Changelimits
amplitude to be
WEAV-008 G
PAUSE. value illegal dwell
Weave Weave amplitude value invalid within limits
Change dwell to be within
WEAV-009 G value
Weave too many pre- Weave
Several dwell
weavevalue invalid pre-
statements limits
WEAV-010 WARN exec WS
Unsupported function executed Warning only
WEAV-011 WARN code Internal system error Cold start controller
Stop dwell is specified but the program
Multi-group stop dwell has multiple groups. Stop dwell is not Change Weave setup to
WEAV-012 WARN invalid supported for multiple groups. Moving use Moving Dwell
PAUSE. Incorrect weaving Weaving vector can not be calcurated Change path direction or
WEAV-013 G vectors because direction of weaving vector is setting of UTOOL to plan
PAUSE. Change wrist
WEAV-014 G
PAUSE. Joint 5Limit
Wrist axes closes to Wrist axes reaches to its limit configuration
Change wrist to allow
WEAV-015 G zero
PAUSE. Unknown wrist Joint 5 is too close to zero configuration
Change wrist to avoid
WEAV-016 G configuration error Unknown wrist configuration error configuration
PAUSE. Run_ang exceeds The angles of Weaving direction away Change torch angle or
WEAV-017 G
PAUSE. tol_ang from its best direction is larger than increase the value of
WEAV-018 G Invalid UTool The current utool has null value Usethe
Set a valid utool
value of total of
WEAV-019 WARN Component
Total of phaseof is
all0 The total of phase is 0 phase
Set the value of
WEAV-020 WARN vectors
Weave illegal elevation The component of all unit vectors is 0.
are 0 component correctly.
Change elevation to be
WEAV-021 WARN Weave
value illegal azimuth ELevation value invalid within limits
Change azimuth to be
WEAV-022 WARN Weave
value illegal center Azimuth value invalid within limits
Change center rise to be
WEAV-023 WARN rise value
Weave illegal radius Center rise value invalid within limits
Change radius to be
WEAV-024 WARN value Radius value invalid within limits
WEAV-025 WARN
WEAV-026 WARN
WEAV-027 WARN
WEAV-028 WARN
WEAV-029 WARN
WMAP-000 WARN unknown error (WM00) An internal system error has occurred. Cold start the controller.
WMAP-001 STOP Error allocating data Not enough memory
WMAP-002 STOP HSDI system call error Internal system error led to the error, and call
WMAP-003 WARN Invalid $wmcfg setting: Internal system error
Invalid screen name Format of screen name in DEF_SCREEN, Screen names must be 1-4
WNDW-001 WARN format ACT_SCREEN, or ATT_WINDOW_S call is alpla- characters Supply a
Format of window name in Window names must be 1-
Invalid window name ATT_WINDOW_D, ATT_WINDOW_S, or 4 alpla- characters Supply
WNDW-002 WARN format DET_WINDOW call or an OPEN a valid window name
Invalid keybd. name Invalid display device name in Use TP for teach pendand
WNDW-003 WARN format DEF_SCREEN or ATT_WINDOW_D call screen or CRT for KCL
Invalid disp dev name Invalid format of display device name in Device names must be 1-4
WNDW-004 WARN format DEF_SCREEN or ATT_WINDOW_D call alpla- characters
n_rows Supply
value must a
be 1 to
WNDW-005 WARN Bad number of rows Invalid n_rows in DEF_WINDOW call 50 Correct the value
n_cols value must be 1 to
WNDW-006 WARN Bad number of cols Invalid n_cols in DEF_WINDOW call 132 Correct the value
For ATWINDOW_S or
Invalid value of row parameter in AT_WINDOW_D calls, row
ATT_WINDOW_S, AT_WINDOW_D, or must be in the range 1-
WNDW-007 WARN Bad row number SET_CURSOR call (display_device_size-
For ATWINDOW_S or
Invalid value of col parameter in AT_WINDOW_D calls, col
ATT_WINDOW_S, AT_WINDOW_D, or must be in the range 1-
WNDW-008 WARN Bad col number SET_CURSOR call (display_device_size-
Unknown display device name in Use TP for teach pendand
WNDW-011 WARN Unk. disp dev name DEF_SCREEN or ATT_WINDOW_D call screen or CRT for KCL
Keyboard device specified in a Use 'TP' for teach pendant
WNDW-012 WARN Unk k/b dev name PUSH_KEY_RD or POP_KEY_RD call or keys or 'CRT' for KCL
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.
Screen name specified in DEF_SCREEN Otherwise, it may be
WNDW-013 WARN Duplicate screen name call is already defined necessary to cold-start the
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
Duplicate window Window name specified in being changed, this may
WNDW-014 WARN name DEF_WINDOW call is already defined not be a problem.
The screen name specified in a Use the name of a defined
WNDW-015 WARN Unknown screen name ATT_WINDOW_S, DET_WINDOW, or screen
The window name specified in a
Unknown window ATT_WINDOW_S, ATT_WINDOW_D, or Use the name of a defined
WNDW-016 WARN name DET_WINDOW call or an OPEN window
The window name specified in a If the present attach is
Window already attchd ATT_WINDOW_S, ATT_WINDOW_D is acceptable, this may not
WNDW-017 WARN to scrn ready attached to the specified screen be a problem. Otherwise
The following forms are
The file name in an OPEN statement valid: WD:wnam KB:knam
begins WD: or KB: but is not a valid WD:wnam/knam
WNDW-018 WARN Invalid file name string format. KB:knam/wnam where
Write to file w/o A write was issued to a file opened to a Either change the OPEN to
WNDW-019 WARN window keyboard (KB:knam), but not a window specify a window or do
Specify a value in the
The buffer_size parameter in a range 10-128 for
Bad buffer length on INI_DYN_DISI INI_DYN_DISR, INI_DYN_DISx calls; for
WNDW-020 WARN read INI_DYN_DISS or READ_KB call is invalid READ_KB calls, specify a
The time_out value in a READ_KB call is The value must be less
WNDW-021 WARN Invalid timeout value Invalid than 65535000. Use a
Zero term char mask in The terminate character mask in a Use a non-zero value for
WNDW-022 WARN read keyboard read is zero. the terminate character
The init_data value is longer than the Either increase the value
WNDW-023 WARN Initial data too long buffer size parameter of buffer_size or specify a
A READ_KB call or READ statement was Either modify the OPEN
Attempt to read with executed on a file that was OPENed to FILE statement to specify
WNDW-024 WARN no kb a window but not a keyboard a keyboard or do not use
A READ_KB call was executed where This may be a normal
the specified file is opened to a window result if the user intended
that is not attached to the active screen READ_KB requests to fail
Echo window for read and the terminate mask included the if the required window is
WNDW-025 WARN not act no_window bit not displayed. Otherwise,
A READ_KB call was executed where This may be a normal
the the keyboard for the specified file result if the user intended
currently has another READ_KB call or READ_KB requests to fail
Read for same keys/kbd READ statement that accepts some of if the Keyboard is in use.
WNDW-026 WARN active the same classes of keys and the Otherwise, modify the
The maximum depth of key read PUSH Check for situations in
WNDW-027 WARN Too many pushes active operations has been exceeded. which a PUSH_KEY may be
Check the logic in use of
This indicates that the pop_index PUSH_KEY_RD and
specified in a POP_KEY_RD call is not POP_KEY_RD to ensure
Mis-match on push/pop the expected value, indicating that call that the pop_index values
WNDW-028 WARN seq are being made out of order. are being suplied in the
The interval parameter in a This must be in the range
WNDW-030 WARN Invalid time INI_DYN_DISI, INI_DYN_DISR, or 1-32767 (ms)
There is no currently active dynamic Check the variable and
No match on var disp display for variable and window window names. Also
WNDW-032 WARN cncl specified in a CNC_DYN_DISI, check logic to see that
The field_width parameter in a call to Value must be in the
WNDW-033 WARN
SYSTE Field width invalid
unexpected packet one of the INI_DYN_DIS builtin routines range of 0-255
WNDW-051 M returned
WNDW-052 WARN no memory for packet
WNDW-053 WARN postreply
no request failedfrom
received
WNDW-054 WARN WIOM
WNDW-055 WARN packet delete failed
WNDW-056 WARN bad keyboard
duplicate disp type
dev code
WNDW-057 WARN name
WNDW-058 WARN disp port name in use
WNDW-059 WARN dup. k/b dev name
WNDW-060 WARN
SYSTE k/bmemory
no port in use
for
WNDW-061 M
SYSTE allocation
WNDW-062 M invalid request code
initialization
WNDW-063 WARN level
no screen active on
WNDW-064 WARN device
window not attached to The window specified in a This is only a warning. It
WNDW-065 WARN
SYSTE screen
no update task id's DET_WINDOW call is not attached to can be ignored or avoided
WNDW-066 M available
invalid number of recall
WNDW-067 WARN bfrs
WNDW-068 WARN
SYSTE channel
error not open
disposing recall
WNDW-069 M
SYSTE bfr
WNDW-070 M error disposing
invalid port name CDBin
WNDW-071 WARN dfdd
WNDW-072 WARN invalid mode
WNDW-073 WARN
SYSTE invalidmessenger
make char size call
WNDW-074 M failed
WNDW-075 WARN second init request
WNDW-076 WARN init request not rcvd
timeout waiting for wrt
WNDW-077 WARN pkt
DDB_p not found in
WNDW-078 WARN delete
WNDW-079 WARN Bad display type code
WNDW-080 WARN Invalid device
specified dev islun
already
WNDW-081 WARN disc
WNDW-082 WARN specified dev is not disc The XML tag limit is a
XMLF-001 WARN Tag too long The XML tag string is too long. maximum of 32
Limit the length of the
attribute data to 64
characters. If a very long
attribute string is required
use it as the body of the
XML for example: This is a
string longer than 64
characters. In fact it could
XMLF-002 WARN Attribute too long The attribute data is too long. be many pages of text
Invalid use of / In general the \ character cannot be Do not use \ in tag (or
XMLF-003 WARN character used in a tag name. This is a special attribute) names. For
Tag names cannot contain special Do not use special
XMLF-004 WARN Invalid character in tag characters such as &<>\ or ". characters in tag names.
There is no value string for an attribute. Make sure all attributes
This error occurs if the attribute is not are of the form name =
XMLF-005 WARN No value for attribute like the follwing example: name = "value".
End tag with no An end tag was found with no matching Start tags and end tags
XMLF-006 WARN matching start start tag. must alway balance. That
Invalid character in An attribute contains an invalid Change the attribute. For
XMLF-007 WARN attribute character. Attributes cannot contain example, is valid.
Make sure the file you are
XMLF-008 WARN Cannot find file The specified file does not exist. trying to access exists on
The nesting of tags is limited to 32 Reformulate your XML file
Tag nesting level too levels deep. This error indicates that to reduce the complexity.
XMLF-009 WARN deep you have more than 32 tags within Make sure that the file
The XML source has a badly formed Follow the rules for XML
XMLF-010 WARN Error in comment comment. comment delimeters. This
Unknown character The & is used to denote special If the character is not
XMLF-011 WARN &xxx; characters. Only &, , and " are supported as a special
This is returned by the remove tag Register the tags before
XMLF-012 WARN Tag not found builtin xml_remtag in the case that the you remove them.
The XML file ended before the starting Make sure that the last
XMLF-013 WARN Unexpected end of file tag was closed. tag in the file closes the
The KAREL builtin xml_scan returned Recall the builtin xml_scan
XMLF-014 WARN Scan limit exceeded becuase it had scanned as many lines to scan more lines.
This is returned by the KAREL builtin This indicates that the
XMLF-015 WARN Function code return xml_scan when a registered tag has builtin should process the
The iPendant detected a problem with Correct the XML content,
XMLF-016 WARN Tag %s %s an XML tag. Most likely an unknown or and retry the operation.
The iPendant detected a problem with Correct the XML content,
XMLF-017 WARN Attr %s %s an ATTRIBUTE
The / VALUE apair
iPendant detected in the
syntax XMLin
error and retry
Correct the
the operation.
XML content,
XMLF-018 WARN User func %s the XML content. and retry the operation.
There are too many ATTRIBUTE/VALUE Reduce the number of
XMLF-019 Too many attributes pairs with the XML tag. ATTRIBUTE/VALUE pairs in

infoPLC Net ErrorCodes 2015-02-05 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

infoPLC Net ErrorCodes 2015-02-05 PDF

Uploaded by

Copyright:

Available Formats

infoPLC.

You might also like