Sheet1ClassIDSeverityError MessageCauseRemedyARC1PAUSE.LIllegal
arc equipment configAn attempt was made to add or usemore equipment
than permitted.To Be DeterminedARC2PAUSE.LIllegal arc schedule
number (%s^4,%d^5)An arc instruction containedan illegal schedule
number.Change the schedule number toone shown in the weld data
screen.ARC3PAUSE.LNo gas flow (%s^4,%d^5)No gas flow was detected
duringan arc start.Check the gas supply.ARC4WARNGas flow after weld
(%s^4,%d^5)The gas fault input was not ONafter the gas output was
set to OFF.Check the gas valve and the gas
flowswitch.ARC5PAUSE.LGas fault (%s^4,%d^5)A gas fault input was
detectedduring welding.Check the gas supply.ARC6PAUSE.LWire fault
(%s^4,%d^5)A wire fault input was detectedduring welding.Check the
wire supply.ARC7PAUSE.LWater fault (%s^4,%d^5)A water fault input
was detectedduring welding.Check the water supply.ARC8PAUSE.LPower
supply fault (%s^4,%d^5)A power fault input was detectedduring
welding.Check the power supply.ARC10PAUSE.LWire stick detected
(%s^4,%d^5)A wire stick has occured.Secure the robot and
equipment.Cut the wire.ARC11PAUSE.LWire stick, not reset
(%s^4,%d^5)A wirestick was detected andwirestick reset was not
performed.Wirestick reset may be disabled.Wirestick reset is not
doneduring TIG welding or if welding is stoppedby turning weld
enable off.Secure the robot and equipment.Cut the
wire.ARC12PAUSE.LWire stick reset(s) failed (%s^4,%d^5)A wirestick
was detected andthe automatic wirestick resetfailed to break the
wirestick.Secure the robot and equipment.Cut the
wire.ARC13PAUSE.LArc Start failed (%s^4,%d^5)The arc detect input
did notstabilize during an arc start.Check the wire and weld
equipment.Adjust the weld scheduleand/or adjust the arc detecttime
in the Weld Equipment SETUP screen.ARC14WARNTeach pendant is
disabledThe weld enable or a wire inchhardkey was pressed with
theteach pendant enable switch OFF.Enable the teach
pendant.ARC15WARNPress shift with this keyThe weld enable or a wire
inchhardkey was pressed withoutholding the shift key.Try again
while holdingthe shift key.ARC16PAUSE.LWeld by Shift FWD is
disabledA program executing from the teachpendant attempted an Arc
Start withwelding from the teach pendant disabled.Disable the arc
for testing fromthe teach pendant or change the WeldSystem SETUP to
permit welding duringteach pendant execution.ARC17WARNArc Start was
disabled (%s^4,%d^5)An Arc Start instruction wasexecuted with
welding disabled.Welding can be enabledusing the teach pendantarc
enable key or theremote arc enable input.Also check the machinelock
and dry runsettings in the Test Cycle screen.ARC18PAUSE.LLost arc
detect (%s^4,%d^5)The arc detect signalwas lost during a weld.Check
the wire feeder.Check the welding schedule,speed or arc loss
time.ARC19PAUSE.LCan't read arc detect input (%s^4,%d^5)The arc
detect inputcould not be read.Check the process I/Oboard
connection.ARC20PAUSE.LNo plan data area availableInsufficient
memory exists toplan an arc instruction.Try reducing the number
ofprograms.ARC21ABORT.LProgram aborted while welding (%s^4,%d^5)A
program was abortedwhile welding.Check if the program endswithout
an Arc End instruction.ARC22WARNWeld AO scaling limit used
(%s^4,%d^5)The programmed analog output isbeyond the equipment
limits.Modify the weld parametersused in the arc instructionto be
within the equipment limits.ARC23PAUSE.LIllegal arc schedule type
(%s^4,%d^5)The arc instruction registeris not an integer type.Use a
register thatis an integer type.ARC24WARNInvalid equipment rangeThe
equipment min to maxrange is too small.Enter new min or max values
forthe equipment.ARC25WARNInvalid A/D or D/A rangeThe binary range
data forthe A/D or D/A is too small.Modify the correct
systemvariable fields within$AWEPRR.ARC26WARNCannot scale AIO while
weldingAn analog scaling limitwas modified while welding.The
scaling was not changed.Turn off the controllerand turn it on
again.ARC30WARNWire stick is still detected (%s^4,%d^5)A wire stick
is still detectedafter a system RESET.Secure the robot and
equipment.Cut the wire.ARC31PAUSE.LNo motion while welding
(%s^4,%d^5)Motion has stopped longerthan $arc_los_tim
whilewelding.If no motion is neededduring welding, increase thearc
loss time in the Weld EquipmentSETUP screen or disable arc
lossdetection in the Weld SystemSETUP screen.ARC32PAUSE.LWeld
stopped by single step (%s^4,%d^5)Welding was stopped byentering
single step modeafter welding began.To continue welding youmust
exit single step mode.ARC33PAUSE.LOverride must be 100%% to weld
(%s^4,%d^5)The speed override is lessthan 100%.Set the speed
override to100% to weld or disable weldingto continue at a low
speed.ARC34PAUSE.LTask does not control welding (%s^4,%d^5)A task
which does not have weld controlattempted to execute an Arc Start
or anArc End instruction. Only one task ispermitted to have weld
control.Allow the task which has weld control toend or abort before
attempting to weld withanother task.ARC35PAUSE.LEquipment number
isn't set (%s^4,%d^5)The arc instruction does not havethe equipment
numberPlease set the equipment number tothe program attribute data
orthe arc instructionARC36PAUSE.LSuch equipment mask isn't
supported (%s^4,%d^5)This equipment mask is not supported nowPlease
change the equipment maskARC37WARNAnother equipment is inching
nowAnother equipment is wire inching now.Please stop wire inching
for another equipmentby releasing the shift key or user
keyARC38PAUSE.LAlready held another equipment (%s^4,%d^5)This
program( task ) has already held the another equipmentA task can
only use a equipment.Please control the equipment by the another
taskARC39PAUSE.L%s^1 AO[%d^2] is not scaled (%s^4,%d^5)The named
weld analog outputsignal is not scaled properly.Adjust the weld
analog outputscaling in the Weld I/O screenusing the CONFIG
function key.ARC40PAUSE.LMissing I/O: %s^1 (%s^4,%d^5)The named
weld I/O signal is notdetected or configured properly.Verify the
I/O hardware is connectedand the signal is assigned aport number in
the Weld I/O screen.Use the CONFIG function key if the signal is
unassigned.ARC41PAUSE.LWeld EQ needs DeviceNet optionThe weld
equipment has been configured to use DeviceNet by settingthe fields
$VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the systemvariable $AWEPRR
to non-zero values.However, the DeviceNet option is not
installed.Add the DeviceNet option or choose a weld equipmentmodel
which does not require DeviceNet.If the weld equipment model is
correct and does not requireDeviceNet then set the $AWEPRR fields
mentioned above to zeroand cycle power.ARC42PAUSE.LWeld EQ needs
Expl Msg optionThe weld equipment has been configured to use
DeviceNet by settingthe fields $VENDOR_ID, $DEV_TYPE, and
$PROD_CODE in the systemvariable $AWEPRR to non-zero
values.However, the Explicit Messaging option is not installed.Add
the Explicit Messaging option or choose a weld equipmentmodel which
does not require DeviceNet.If the weld equipment model is correct
and does not requireDeviceNet then set the $AWEPRR fields mentioned
above to zeroand cycle power.ARC43PAUSE.LWeld EQ needs DeviceNet
boardThe weld equipment has been configured to use DeviceNet by
settingthe fields $VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the
systemvariable $AWEPRR to non-zero values.However, DeviceNet
hardware was not detected.Add DeviceNet hardware or choose a weld
equipmentmodel which does not require DeviceNet.If the weld
equipment model is correct and does not requireDeviceNet then set
the $AWEPRR fields mentioned above to zeroand cycle
power.ARC44PAUSE.LWeld EQ needs DeviceNet defn.The weld equipment
has been configured to use DeviceNet by settingthe fields
$VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the systemvariable $AWEPRR
to non-zero values.A DeviceNet device definition could not be found
for that product.You can add a DeviceNet definition for this
product or if theweld equipment you are using does not support
DeviceNet you can setthe $AWEPRR fields mentioned above to zero and
cycle power.ARC45WARNWeld EQ Device is OFFLINEArcTool attempted to
communicate with the Welding Equipmentusing the DeviceNet network,
but could not because the linkwas not properly established.Verify
the Weld Equipment is ON.Verify the DeviceNet cable is
connected.Check the DeviceNet I/O screen board status and device
status.ARC46WARNWeld EQ communication errorThere was a
communication error detected between ArcTool andthe Weld
Equipment.Verify the Weld Equipment is ON.Verify the DeviceNet
cable is connected.Check the DeviceNet I/O screen board status and
device status.ARC47WARNNot allowed during a weldAn operation was
attempted which is not permittedwhile a weld is executing or
paused.Try the operation after the program ends or is
aborted.ARC48WARNAuto AI/O setup is unsupportedAuto AI/O setup for
the mounted I/Omodule is not supported.So parameters are not set
automatically.Verify mounted I/O moduleand set system variables of
$AWEPRR[]in system variable screen manuallyif need.ARC49WARNProcess
%d switch to %d failedArcTool failed to switch weld processes.The
weld power supply may be OFF, unconnected,or data in the second
process may be incorrect.ARC50WARNProcess %d NOT foundArcTool
failed to find this processon the weld power supply.Enter a
different number or use theSEARCH parameters and function
key.ARC51WARNWeld EQ ONLINE: %sArcTool is communicating with
theweld power supply. The versionnumber of the power supply is
shown.This message is for notification andinformation. It does not
indicate a problem.ARC52WARNBad %s %s Prc %dThe indicated parameter
is out of range.Enter a number within range.ARC53WARNNo ramp at
process switch (%s^4,%d^5)Ramping is not allowed when switchingweld
processes.Complete the process switch first, thenramp with another
arc start instruction.ARC54PAUSE.GNo motion while arc weldingMotion
has stopped longerthan the time specified in weld schedulleand weld
setup while welding.If no motion is neededduring welding, increase
theabove time in the system variable screen.ARC72PAUSE.LIllegal AMR
packetInternal error.Sometimes this error requirescycling the
controller power.ARC84ABORT.LApplication process is changed during
weldingApplication is changed during welding.Please change the
program.ARC85PAUSE.LIncomplete of conversion factor setupImcomplete
the analog signal conversion factor.Please set
it.ARC86PAUSE.LInvalid of binary data in conversion factorThe
binary data($AWEPRR.$io_min/max_bin) is invalid.The difference is
zero.Please set correct value.ARC87PAUSE.LInvalid conversion factor
dataThe conversion factor data is invalid.It must be filled more
than 2 tables at least.But the value of the second table is
zero.Please set conversion factor more than 2
tablesARC88PAUSE.LOver selected AO factor No.The selected number of
AO conversion factor datais over the number of the actual data
arrayPlease select the correct number of AO conversion factor
dataARC90WARNWeld disable by reason[%d]In this situation, the
welding is disalbled by the following reason1: In Single step
mode2: In Machine lock mode3: In Dry run mode4: No I/O board
exist5: No I/O assignment for welding6: In Flush AMR status7: In
Application disabled mode8: In Arc disabled status9: In Skip
welding status10: In disable status mode by AWDBGPlease remove the
specified reason to perform the welding.ARC100PAUSE.LSVT:
Unsupported Wire materialThe selected wire material is notsupported
for Servo Torch.Please select the correct wire
materal.ARC101PAUSE.LSVT: Unsupported Wire sizeThe selected wire
size is notsupported for Servo Torch.Please select the correct wire
size.ARC102WARNSVT: Unsupported speed unitThe selected unit of
inching speed is notsupported for Servo Torch.Please select the
correct unit of inching speedARC103PAUSE.LSVT: WFS conversion
failedFailed to convert weld schedule towire feed speed command for
Servo Torch.If another alarm is also occured atthe same time,
please check it andremove the cause of the alarm.If no other alarm
is occured, someinternal error is occured.ARC104PAUSE.LSVT: Invalid
sequence modeInternal error.Invalid sequence mode command issent to
Servo Torch.Internal error.Cycle power to
recover.ARC105PAUSE.LCannot read WSTK input signalCannot received
WSTK signal fromserial communication power supply.Confirm which
type of weld equipis used.Confirm the connection with
serialcommunication power supply.Confirm the setting of serial
port.ARC106WARNConfig of Roboweld is invalidConfiguration of
Roboweld was invalid.So data for Robowelds were
setinappropriately.Remove all Robowelds by selecting otherequip in
weld equip select screen.Then select and setup Roboweld again,if
you want to use Roboweld.ARC107PAUSE.LRoboweld internal
Error(%d)RoboWeld internal error.Cycle power to
recover.ARC120WARNEnable/Disable Sim mode failedNecessary signals
for Simulation modecannot be detected.Verify that AI/O and WDI/O
signalsare assigned appropriately.ARC121WARNWeld not performed(Sim
mode)Simulation mode is enabled.So actual welding is not
performed.This is not an error.There is no need to do
anything.ARC122WARNCannot SIM/UNSIM(%s,Id:%d)I/O signals were not
set to sim/unsimappropriately when Simulation mode
is.enabled/disabled.Verify that AI/O and WDI/O signalsare assigned
appropriately.ARC123SYSTEMMemory size is too smallMemory size is
too small to get memoryarea for necessary data.Change memory module
into the one which hasappropriate size and do INIT
start.ARC150PAUSE.GInvalid op. in weld(0x%X)(E:%d)Detect invalid
signal operation in welding.Reset and try again after Arc
OFF.ARC151PAUSE.GInvalid wire size(E:%d)Detect invalid wire
size.Set proper wire size.ARC152PAUSE.GInvalid weld
process(E:%d)Detect invalid welding process.Set proper welding
process.ARC153PAUSE.GInvalid wire material(E:%d)Detect invalid wire
material.Set proper wire material.ARC154PAUSE.GInvalid Arc Loss
Time(E:%d)Arc loss time is invalid range.Set proper arc loss
time.ARC155PAUSE.GComm. Timeout(E:%d)Communication with RoboWeld
power source is timeout.Confirm port setup and connection
cable.ARC156SYSTEMRoboWeld Error(0x%X, %d)RoboWeld internal
error.Please call FANUC service.ARC157PAUSE.GReceive
error(0x%X)(E:%d)Receive invalid data from Power Source.Confirm
noise environment and cable.ARC158PAUSE.G1st currency (E:%d)Detect
1st currency abnormal.Check currency.ARC159PAUSE.G2nd currency
(E:%d)Detect 2nd currency abnormal.Check
currency.ARC160PAUSE.GTemperature alaram(E:%d)Detect temperature
abnormal.Check overload.ARC161PAUSE.GHigh voltage(E:%d)Detect high
voltage.Check voltage.ARC162PAUSE.GLow voltage(E:%d)Detect low
voltage.Check voltage.ARC163PAUSE.GStart signal error(E:%d)Detect
start signal abnormal.Check start signal.ARC164PAUSE.GPower source
error(E:%d)Detect 3-phase power source abnormal.Check 3-phase power
source.ARC165PAUSE.GEQ is detached(E:%d)RoboWeld is
detached.Confirm port setup.ARC166PAUSE.GComm. stopped in
weld(E:%d)Communication with RoboWeld power source stopped in
welding.Confirm another error message and port, cable
setup.ARC167SYSTEMI/O asginment overlap(%d)(E:%d)I/O space for
RoboWeld is already in use.Confirm another I/O device and $IO_START
in $RBWLD.ARC168SYSTEMI/O error(%d)(%d, E:%d)I/O initialization
error.Confirm another I/O device and $IO_START in
$RBWLD.ARC169PAUSE.GInvalid wire op.(E:%d)Detect invalid wire
FWD/BWD operation.Confirm wire control sequence.ARC170PAUSE.GDetect
Arc OFF(E:%d)Detect ARC off.Confirm welding device and workpiece
status.ARC171PAUSE.GUnified data RCV error(%d,0x%X)(E:%d)Failed to
receive unified data.Confirm port setup, noise environment, cable
status.ARC172WARNWarning, Rcv(0x%X)(E:%d)Receive invalid command
from power source.Confirm noise environment, cable
setting.ARC173WARNWarning, Retry(0x%X)(E:%d)Retry to send the
command to power source.Confirm noise environment, cable
setting.ARC174WARNWarning, NAK for(0x%X)(E:%d)Receive NAK from
power source.Confirm noise environment, cable
setting.ARC175PAUSE.GSignal change is ignored(E:%d)Communication
with power source is stopped.Confirm welding setup, cable
connection, then reset.ARC176WARNNo sysvar $RBWLD for E:%dSysvar
$RBWLD is not setup for new EQ number.Confirm $RBWLD and $RBWLD_CFG
setup.ARC177WARNRoboWeld(E:%d) reset completeRoboWeld reset
sequence is complete.Arc welding is now available.ARC178PAUSE.GArc
short alarm(E:%d)ARC179PAUSE.GPower supply com alarm(E:%d)Power
supply communication errorConfirm RS-422 communication line.After
check try again. If the same alarm occurs,inform of the
service.ARC180PAUSE.GGabana alarm(E:%d)Wire feeder motor speed is
over the limited speed.Check the wire feeder motor.After check try
again. If the same alarm occurs,inform of the
service.ARC181PAUSE.GEncoder alarm(E:%d)Wire feeder motor sensor
line was connected off orwire feeder motor did not rotate
correctly.Check the wire feeder motor sensor line.After check try
again. If the same alarm occurs,inform of the
service.ARC182PAUSE.GMotor alarm(E:%d)While the motor should stop,
the motor rotation was detected.If the motor was rotated actually,
the control board in wire feedcontroller may be
broken.ARC183PAUSE.G2nd High voltage(E:%d)ARC184PAUSE.GRun signal
alarm(E:%d)ARC185PAUSE.GCT offset alarm(E:%d)ARC186PAUSE.GVT offset
alarm(E:%d)ARC187PAUSE.GWater circuit
alarm(E:%d)ARC188PAUSE.GExternal emergency input(E:%d)ESTOP signal
was input from the external.Turn off the power and remove the
reason then power on.ARC189PAUSE.GExternal input1(E:%d)Exernal1
hold signal was input from the external.Remove the
reason.ARC190PAUSE.GExternal input2(E:%d)Exernal1 hold signal was
input from the external.Remove the reason.ARC191PAUSE.GMemory
alarm(E:%d)Power supply control memory errorTurn off the power then
try again.If the same alarm occurs again, inform of the
service.ARC192PAUSE.GCPU alarm(E:%d)Weld power supply CPU errorTurn
off the power then try again.If the same alarm occurs again, inform
of the service.ARC193PAUSE.GArc start alarm(E:%d)Torch switch was
turned ON but the arc could not startedwithin
4sec.0ARC194PAUSE.GGas low pressure(E:%d)ARC195PAUSE.GNot support
weld type(E:%d)The specified weld type has not been supported for
this powersupply.Check the setup of process type, wire size, wire
materialin weld equipment setup screen and pulse mode in weld
schedule.Then change them.ARC196WARNChanging weld type
...(E:%d)Changing weld type data now. Please wait for a
moment.ARC197WARNComplete weld type change(E:%d)Complete to change
weld type data. So you can do arc welding.ARC200WARNArclink ch%d
heartbeat timeoutThe Arclink bus master did not respondto a
heartbeat request within the maximumtime period. The channel has
been reset.Check the Arclink connections and theweld controller
devices that are on.the Arclink network.ARC201WARNArclink ch%d obj
#%d no respA device on the Arclink did not respond toa request
within the maximum time period.The channel has been reset.Check the
Arclink connections and theweld controller devices that are on
theArclink network.ARC202WARNArclink ch%d obj #%d error respA
device on the Arclink sent and unexpectederror response to a
request message. Thechannel has been reset.Check the Arclink
connections and theweld controller devices that are on theArclink
network.ARC203WARNArclink ch%d reset by masterThe Arclink bus
master has detected an erroror other condition that requires the
Arclinknetwork to be reset. This may be a normalevent if a new
device has been plugged intothe network.If this is unexpected, then
check the connectionsand other devices on the Arclink
network.ARC204WARNArclink ch%d availableThe Arclink reset and
initialization sequenceis complete.The Arclink network is ready for
welding.ARC205WARNArclink ch%d h/s event lostThe high speed event
message expected during weldingfailed to arrive in time.The Arclink
network is automatically reset. If thiserror persists, it indicates
a problem with thecommunications network or welding
equipment.ARC206WARNArclink ch%d too many errorsThe Arclink
interface detected too many errorson the CANbus network. This is
usually caused bynoise or bad connections.Check Arclink network
connections and shielding.ARC207WARNArclink ch%d no bus powerThe
Arclink interface detected too many errorson the CANbus network.
This is usually caused bynoise or bad connections.Check Arclink
network connections and shielding.ARC208WARNArclink ch%d no nodes
on busThe Arclink interface is not detecting any otherdevices on
the CANbus network.Check the Arclink cable connections and make
surethat the welding equipment is also connected andpowered
on.ARC209WARNArclink ch%d bus errorsThe Arclink interface is
detecting a high numberof errors on the network. This is not fatal
rightnow, but indicates potential problems on the network.Check the
Arclink cable connections and noisesources.ARC210WARNArclink ch%d
network floodedThe Arclink interface is unable to send messagesdue
to too much traffic on the network.Cycle power on the robot
controller and weldcontroller.ARC211WARNArclink ch%d comm error
%dThe Arclink interface has detected a fatal errorcondition and has
reset the communications network.If this problem persists, contact
tech support.CD1WARNNo global variablesCoordinated Motion global
variables are not loaded.Perform a controlled start and initialize
motion softparts.CD2WARNUnable to allocate memoryA failure occurred
while allocating memory.Check amount of memory being used by the
system.CD3PAUSE.GFollower recv invalid segmentLeader segment MMR
number does not match that of the followerCall FANUC
Robotics.CD4PAUSE.GIllegal leader INTR point dataIllegal Leader
Interpolated Point Data is detected whentrying to convert it to a
transformCall FANUC Robotics.CD5PAUSE.GNon-coordinated group
detectedCoordinated Motion is used for a group whichhas not been
SETUP for coordinated motion.Check motion statement.Perform
Coordinated Motion SETUPand perform a COLD START.CD6PAUSE.GIllegal
follower joint motionJOINT MOTYPE was used for a follower
duringcoordinated motion.Use LINEAR or CIRCULAR MOTYPE
insteadCD7PAUSE.GCircular motype not supportedCIRCULAR MOTYPE Not
Implemented YetUse LINEAR MOTYPE insteadCD8PAUSE.GNo leaderThere is
no leader in the coordinated motionCheck motion statement.Perform
Coordinated Motion SETUPand then perform a COLD
START.CD9PAUSE.GMore than one leaderThere is more than one leader
in the coordinated motionCheck motion statement.Perform Coordinated
Motion SETUPand then perform a COLD START.CD10PAUSE.GInvalid angle
in point dataInvalid Angle detected in Point DataInternal Error,
call FANUC Robotics.CD11PAUSE.GError in flushing CD mailboxError in
reporting mailbox statusCOLD START.CD12PAUSE.GIllegal leader
motionLeader single group motion aftercoordinated motion not
allowedIssue non-coordinated motioninvolving the follower
groupCD13WARNJog group is not a leaderAttempt to perform
coordinatedjog with a non-leader groupSelect leader group
forcoordinated jogCD14WARNJog group has multi followerAttempt to
perform coordinatedjog with a leader group whichhas multiple
followersSelect only one leader/followerpairCD15PAUSE.GWrist joint
is not supportedWRIST JOINT Motion is not supportedwith coordinated
motionDelete Wjnt motion instructionCD16PAUSE.GINC motion is not
supportedINCREMENTAL motion is not supportedwith coordinated
motionDelete INC instructionCD17PAUSE.GINDEP motn is not
supportedIndependent motion is not supportedwith coordinated
motionChange Independent motion toSimultaneous motionCD18PAUSE.GNo
calibration for CDCalibration for coordinatedmotion is not
doneExecute calibration of coordinatedmotion in SETUP
screenCD19PAUSE.GIllegal follower settingNumber of follower is
zeroor two or greater on thismotionSet number of followercorrectly
or set groupmask correctlyCD20WARNNot reach relative speedFollower
can not reachrelative speed in programTeach follower and leader
positionagain to reach relative speedCD21PAUSE.GNo kinematics in CD
groupAttempt to perform coordinatedmotion with
non-kinematicsrobotInitialize robot library
correctlyCD22PAUSE.GPrev term type is not FINETerm type before
coordinated motionis not Fine or CNT0Change term type before
coordinatedmotion to FINE or CNT0or JOINT motionCD23PAUSE.GIllegal
CD settingSetting of coordinated motionis not correctCheck setting
of coordinated motionin SETUP screenAnd set
correctlyCD24WARNCalibration was inaccurateTeaching points is
incorrect orLeader's mechanics is inaccurateCheck the mechanics and
reteachthe pointsCD25PAUSE.GCan't convert positionSystem can't
convert position properlyCall FANUC Robotics.CD26PAUSE.GIllegal
transition:nonCDCDIllegal transition (nonCD->CD or CD->nonCD)
happens.Add or remove motion option COORD.CD27PAUSE.GIllegal
follower transitionTransition from one CD pair to another
happens.But same follower group is used in both CD pair.Insert non
coordinated motion betweencoordinated motion of different
pair.CD28PAUSE.GT1 speed limit(G:%d^2)Speed of TCP or Face Plate
exceeded T1 speed limit.Specify slower speed or change to AUTO
mode.CMND1WARNDirectory not foundThe specified directory cannot be
found.Check the device and path thatyou entered. If none
entered,check the system default devicefrom the FILE Menu or from
theKCL command, CHDIR.CMND2WARNFile not foundThe specified file
could not be found.Check to make sure the file has beenspelled
correctly and that itexists. Also verify the deviceand path name
are correct.CMND3WARNFile already existsThe file already exists and
couldnot be overwritten.Make sure the overwrite optionhas been
specified.CMND6WARNSelf copy not allowedA file cannot be copied to
itself.Change the name of thedestination file so it isdifferent
from the sourcefile.CMND10WARNSource type code is invalidThe source
variable was not a positiontype when converting between aCartesian
and joint position.The valid postion types are POSITION,JOINTPOS,
XYZWPR, and XYZWPREXT.CMND11WARNDestination type code is invalidThe
destination variable was not aposition type when converting
betweena Cartesian and joint position.The valid postion types are
POSITION,JOINTPOS, XYZWPR, and XYZWPREXT.CMND12WARNType codes do
not matchThe requested type code doesn't matchthe passed variable
type.Internal error. Insure that the typecode matches the variable
type.CMND13WARNRepresentation mismatchAn attempt was made to
compare twopositions that are not the same type.Both positions must
be the same type.Convert one before comparing.CMND14WARNPositions
are not the sameTwo positions were compared and foundnot to be
equal.The two positions were not equal withinthe specified
tolerance. This could bea normal occurence. This warning isthe
logical opposite of SUCCESS.CMND15WARNBoth arguments are zeroBoth
arguments to ATAN2 were zero or aninternal error occurred when
attemptingto convert a POSITION to XYZWPR.If calling ATAN2, insure
that botharguments are not zero. If convertinga POSITION, then it
is not converableto an XYZWPR.CMND16WARNDivision by zeroAn attempt
was made to divide by zero.This is an internal error. Insure
thatthe divisor is not equal or close tozero.CMND17WARNAngle is out
of rangeThe rotational angle is to great.Make sure that the
rotational angle is nogreater than 100 times PI, or
about314.15926...CMND18WARNInvalid device or pathAn invalid device
or pathhas been specified.Check the device and path thatyou
entered. If none entered,check the system default devicefrom the
FILE Menu or from theKCL command, CHDIR.CMND19WARNOperation
cancelledThe operation was cancelled because CTRL-C or CTRL-Ywas
pressed.Repeat the operation.CMND20WARNEnd of directoryThe
directory listing is finished.This is a notification. You do not
have to do anythingfor this warning message.CMND21WARNCannot rename
fileThe destination file name contained bothalphanumeric characters
and theglobal character '*'.Use only alphanumeric charactersor a
single global character whenrenaming a file.CMND22PAUSE.GTime
motion with dist beforeA time-based motion was specifiedalong with
distance before.Do not use these options incombination.CNTR1WARNNo
global variablesContinuous Turn global variables are not
loaded.Perform a controlled start and initialize motion
softparts.CNTR2WARNNo MIR pointerThis is an internal system
error.Perform a cold start on the controller.CNTR3WARNNo sysvar
pointerThis is an internal system error.Perform a cold start on the
controller.CNTR4WARNNo cnir pointerThis is an internal system
error.Perform a controlled start and initialize the motion
softparts.CNTR5WARNWrong CN Axis/N1 or N2(G:%d^2)The continuous
turn axis that was selectedis not a valid cont. turn axis,or
cn_gear_n1 or cn_gear_n2 have a zero valueCheck Continuous turn
axis, cn_gear_n1, and cn_gear_n2Select different continuous turn
axis and/or set correctgear ratio for continuous turn
axis.CNTR6WARNUnable to Allocate MemoryA failure occured while
allocating memory.Check amount of memory being used by the
system.CNTR7PAUSE.GSerious Internal error (G:%d^2)Internal
Continuous Turn errorRecord error and report to
hotlineCNTR8PAUSE.GInvalid dest. angle, (G:%d^2)Invalid destination
angle during linear motion.Incompatibility with Continuous Turn and
other options.Check compatibility of motion options.Remove other
options.CNTR9WARNWarn-Cont Vel too high(G:%d^2)Continuous turn axis
velocity is too high.cn_turn_no will not be valid because of high
rotational speed.Lower contaxisvel. This warning may be ignored
ifcn_turn_no is not used.CNTR10PAUSE.GInd.EV option not
allowed.Continuous turn is not compatible with independent extended
axesThe Ind.EV motion option is not allowed.Remove Ind.EV option or
disable continuous turn on the groupCNTR11PAUSE.GAxis speed exceeds
lim(G:%d^2)Programmed motion exceeds the speed limits on
thecontinuous turn axis. Speed limit is 180 degrees per ITP
timeLower the speed either through KAREL or Teach
PendantCNTR12PAUSE.GEnding Cont Rot on Rel MotionAttempted to end
Continuous Rotation with a Relative MotionContinuous Rotation must
be ended with an absolution motionUse an absolution motion to end
continuous rotationCOMP0SYSTEMUnknown errorCOMP1PAUSE.GRetry count
overCOMP2PAUSE.GRetry count over(Hardware)COMP3PAUSE.GRetry count
over(Undefind TCC)COMP4PAUSE.GRetry count
over(Parity)COMP5PAUSE.GRetry count over(Interval)COMP6PAUSE.GDSR
off when transmissionCOMP7PAUSE.GInvalid data
formatCOMP8PAUSE.GResponse time overCOND1WARNCondition does not
existSpecified condition does not existCheck for condition
statementsto verify if the specified condition hasreally been
created or not.COND2WARNCondition handler supersededThe specified
condition number alreadyexists in the system, and has
beensuperseded by the new condition.This is just a notification,
and youdo not have to do anything for thiswarning
message.COND3WARNAlready enabled, no changeThe specified condition
is alreadyenabled. No change has been made.This is just a
notification, and youdo not have to do anything for thiswarning
message.COND4WARNAlready disabled, no changeThe specified condition
is alreadydisabled. No change has been made.This is just a
notification, and youdo not have to do anything for thiswarning
message.COND5WARNNo more conditions definedNo more conditions are
definedfor the specified task.No action is required.COND9WARNBreak
point encounteredBreak point has been encountered.No action is
requiredCOND10WARNCond exists, not supersededSpecified condition
already exists.Condition was not superseded.May indicate two
condition handlers forthe same task with thesame condition
handler.Either renumber the condition handler oravoid re-defining
the same condition handler.COND11WARNScan time took too longThere
are too many conditions defined.It took too long to scan them
all.Reduce the number of conditions defined.COPT1WARNSend_PC
errorThe system was not able to setup the messagepacket to send to
the PC.System probably out of memory. Cold start.COPT2WARNAdd PC
Uninit prog or var nameAn ADD PC buffer built-in was called with a
parameter thatis uninitialized.All parameters must have a value
when callingthe create a data buffer to PC built-ins.COPT3WARNAdd
PC Variable not foundThe variable requested in the ADD Byname or
Send SysVarroutines does not exist.Check program and variable name
spellings.Check variable data type. Only integer, realand string
data is supported.COPT4WARNAdd PC Var type not supportedThe
variable requested in the ADD Byname or Send SysVarroutines is of a
data type that is not supported.Check variable data type. Only
integer, realand string data is supported.Check program and
variable name spellings.COPT5WARNAdd PC illegal index into bufferAn
ADD PC buffer built-in was called with the indexparameter set too
big or too small.Set the index parameter correctly. Make surethe
data buffer is big enough for your data.COPT6WARNAdd PC buffer
overflow - parm %sThe data could not be copied to the data
bufferbecause the buffer is too small.Make sure the data buffer is
big enough for your data.If there is too much data to send, you
mighthave to use more than one event to send the data.COPT7WARNAdd
PC Un-initialized parameter %sAn ADD PC buffer built-in was called
with a parameter thatis uninitialized.All parameters must have a
value when callingthe create a data buffer to PC
built-ins.COPT8WARNSend_PC Un-initialized parameterA Send PC
built-in was called with a parameter thatis uninitialized.All
parameters must have a value when callingthe send PC
built-ins.COPT9WARNSend_PC Illegal event numberAn event number less
that 0 or greater than255 was used.Use an event number from 0 to
255.COPT10WARNSend_PC Illegal wait flagOnly wait flags of 0 or 1
are allowed.Use a legal wait flag.COPT11WARNSend_PC Buffer too big
for packetThe maximum data buffer size supported is 244 bytes.Use a
legal data buffer size.COPT20WARNSend_PC builtin failedA system
error occurred when trying to send the databuffer to the PC.Check
other alarms in alarm log for details.COPT21WARNSend_PC event parm
%s errorA Send to PC MACRO was called with a parameter thatis
illegal. The parameter is uninitialized or the wrong data
type.Check the MACRO call in the TP program.COPT22WARNStill waiting
for %sStatus message only. A controller task is waiting foran event
flag back from the PC.Check PC communications.COPT23WARNAbort wait
for %sA controller task waited too long for an event flagfrom the
PC. The controller task was aborted.Check PC
communications.COPT24WARNContinuing without %sStatus message only.
A controller task was waiting foran event flag back from the PC.
The PC is takingtoo long. The controller task has continued without
receiving the event flag.Check PC communications.COPT25WARNReceived
answer for %sStatus message only. The PC set the eventflag and the
controller task is contining.N/ACOPT26WARNWait timer cannot be setA
system timer cannot be created or set for thiscontroller task.Cold
startCOPT27WARNReg %s could not be setRegister operation failedThis
is just a debug messageCheck if the register is definedand if it
has the right value.Must ABORT ALL and retryN/ACOPT28WARNRegister
%s not definedCOPT29WARNMacro Table too small for send optionThe
MACRO table must have at least 60 elementsfor the SEND PC MACRO
option to be installedproperly.Increase the MACRO table
size.COPT30WARNParameter %s errorSend PC Macro data error.Check
other alarmlog errors for more details.COPT31WARNSend Macro - no
data to sendThe Send Data PC MACRO was not given any data to
send.Check MACRO parameters.COPT32WARNSend_n_wait - Illegal
actionThe wait action parameter must be 0 through 3.Check MACRO
parameters.COPT33WARNSend_n_wait - Uninit parm %sA send PC MACRO
was called with a parameter thatis uninitialized.All parameters
must have a value.COPT34WARN%s missingAn error occurred in the TP
program.A MACRO was called without a parameter thatmust be
entered.Check the MACRO call in the TP program.Check the TP
program.COPT35WARNAborting TP programCOPT36WARN%s Illegal typeA
MACRO was called with a parameter thatis illegal. The parameter has
the wrong data type.Check the MACRO call in the TP
program.DICT1WARNDictionary already loadedA dictionary cannot be
reloaded ifit was loaded into FROM.Load into a different language
and useKCL SET LANG to set the language.DICT2WARNNot enough memory
to load dictThere is no more permanent memoryavailable in the
system to loadanother dictionary.Clear all unnecessary
programs,dictionaries or variables.DICT3WARNNo dict found for
languageThere are no dictionaries loaded forthe specified
language.Use the DEFAULT language or a languagein which a
dictionary has been loaded.DICT4WARNDictionary not foundThe
specified dictionary was not found.Use KCL LOAD DICT to load the
dictionaryinto the DEFAULT language or the
currentlanguage.DICT5WARNDictionary element not foundThe dictionary
element was not found.Check the dictionary or element numberto be
sure it is specified correctly.DICT6WARNNested level too deepOnly
five levels of dictionary elementscan be nested.Fix the dictionary
text file to includefewer nested levels.DICT7WARNDictionary not
opened by taskThe dictionary was never opened.Remove the close
operation.DICT8WARNDictionary element truncatedThe dictionary
element was truncatedbecause the KAREL string array is notlarge
enough to hold all the data.Increase either the size of the
stringor the number of strings in the array.DICT9WARNEnd of
language listThe language list has completed.This is a
notification. You do not haveto do anything for this warning
message.DICT10WARNEnd of dictionary listThe dictionary list has
completed.This is a notification. You do not haveto do anything for
this warning message.DICT11WARNDict opened by too many tasksOnly
five dictionaries can be open by onetask at one time.Load the
dictionary to memory or closean unused dictionary.DICT12WARNNot
enough memory to load dictNot enough memory exists in TEMP poolon
the controller. The dictionary wasnot loaded.This is a notification
of insufficientmemory resources on the controller. Thehardware and
software configurationsneed to be verified.DICT13WARNCannot open
dictionary fileThe dictionary file does not exist on thespecified
device or in the specifieddirectory.Select the proper
device/directory andtry again.DICT14WARNExpecting $ in dictionary
fileThe dictionary text incorrectlyspecifies an element without a
$.Make sure all dictionary elements beginwith $.DICT15WARNReserved
word not recognizedA reserved word was not recognized inthe
dictionary text.Check for misspelling or look up thecorrect word in
the KAREL ReferenceManual.DICT16WARNEnding quote expectedThe
dictionary text incorrectlyspecifies an element without using
quotes.Make sure all dictionary text issurrounded by double quotes.
Use abackslash if you want an actual quoteto appear in the text.
For example,\"This is an example\" will produce"This is an
example"DICT17WARNExpecting element name or numA reference to
another element isexpected.Use the element number to reference
theelement.DICT18WARNInvalid cursor positionThe cursor position is
specifiedincorrectly or the values are outsidethe limits.Make sure
the cursor position is valid.For example, use @1,1 for the first
rowand col respectively.DICT19WARNASCII character code expectedA
series of digits are expected afterthe # to specify an ASCII
charactercode.Remove the # or look up the ASCIIcharacter code in
the KAREL ReferenceManual.DICT20WARNReserved word expectedAn
identifier is expected after the &to specify a reserved
word.Remove the & or look up the reserved wordin the KAREL
Reference Manual.DICT21WARNInvalid characterAn unexpected character
was found in thedictionary text file.Make sure all dictionary text
is correct.DICT22WARNDict already opened by taskThe dictionary is
already open by thetask.This is a notification. You do not haveto
do anything for this warning message.DICT23WARNDict does not need
to be openedDictionaries loaded to memory do notneed to be
opened.Do not try to open the dictionary file.DICT24WARNCannot
remove dictionary fileDictionaries loaded to FROM cannotbe removed
or a dictionary cannot beremoved if another task has it opened.Do
not try to remove a dictionary loadedto FROM. Remove the dictionary
from thesame task which loaded it.DICT28WARNNot enough memory to
load dictNot enough memory exists in TEMP poolon the controller.
The dictionary wasnot loaded.This is a notification of
insufficientmemory resources on the controller. Thehardware and
software configurationsneed to be verified.DICT29WARNHelp element
not foundThe help dictionary element was not found.Check the
dictionary to be sure thehelp dictionary element was
specifiedcorrectly. The help dictionary elementmust be specified
with a question mark (?)followed by the element
number.DICT30WARNFunction key element not foundThe function key
dictionary element wasnot found.Check the dictionary to be sure
thefunction key element was specifiedcorrectly. The function key
elementmust be specified with a caret (^)followed by the element
number.DICT31WARN%4s-%03d $%8lX, no message foundThe dictionary
containing the errormessage could not be found.Refer to the System
Reference Manual forthe error message.DICT32WARN%4s-%03d, see
posted errorThe error message was posted to the errorlog.See error
window or the Alarms menu forthe error message.DICT40WARNExpecting
element num after $The dictionary text incorrectlyspecifies an
element number.Make sure all dictionary elements beginwith $
followed by the element number.DICT41WARNExpecting element name
after ,The dictionary text incorrectlyspecifies an element
name.Make sure all dictionary elements arespecified as
",element_name" after theadd constant name.DICT42WARNExpecting add
constant nameThe dictionary text was specifiedincorrectly.Make sure
all dictionary elements arespecified as "+add_const_name" after
theelement number.DICT43WARNElement number out of sequenceThe
dictionary text was not specifiedin sequence.Make sure all
dictionary elementsare specified in sequential
order.DICT44WARNWarning - large hole in ele seqThe dictionary text
has a large gapbetween element numbers.Reduce the gap in the
element sequence.Each missing element uses up five bytesof
memory.DICT45WARN.LIT or .END mismatchThe dictionary text was
specifiedincorrectly.Verify that each .LIT is matched witha
.END.DICT46WARNCommand already encounteredThe dictionary text was
specifiedincorrectly.Remove the extra command.DICT47WARNFile
extension requiredThe dictionary compressor expects a
fileextension.Use the .etx file extension for errortext, the .utx
file extension foruncompressed text, or the .ftx fileextension for
form text.DICT48WARNInvalid file extensionThe dictionary compressor
did notrecognize the file extension.Use the .etx file extension for
errortext, the .utx file extension foruncompressed text, or the
.ftx fileextension for form text.DICT49WARNExpecting file nameThe
dictionary compressor expects a filename.Specify a file name after
the command.DICT50WARNExpecting facility numberThe dictionary
compressor expects afacility number in the .KL command.Specify the
facility number after thefile name.DICT51WARNSymbol invalid for
dictionary typeAn invalid command was specified forthis type of
dictionary file.Check the command and if a form is used,verify the
file extension is .ftx.DICT52WARNExpecting .ENDFORM symbolThe
dictionary text was specifiedincorrectly.Verify that each .FORM is
matched witha .ENDFORM.DICT53WARNCannot open include fileThe
include file could not be created.Make sure a valid file name has
beenspecified.DICT54WARNForm is being displayedThe form you are
trying to compress iscurrently being displayed.Abort the KAREL
program that isdisplaying the form.DNET1PAUSE.GNo system device
fileThe system device definition file is missing from the
system.INIT start and reload the DeviceNet Interface option.If the
error still exists, document the events that led to theerror and
call your FANUC Robotics technical representative.DNET2PAUSE.GNo
application device fileThe application device definition file is
missing from the system.INIT start and reload the DeviceNet
Interface option.If the error still exists, document the events
that led to theerror and call your FANUC Robotics technical
representative.DNET3PAUSE.GToo many DNet motherboardsThere are too
many DeviceNet motherboards connected to the robotcontroller.Turn
off controller power. Disconnect one of the DeviceNet
motherboards.Re-connect any DeviceNet cables to the other DeviceNet
motherboard. Poweron your controller.DNET4PAUSE.GBoard init failed:
Bd %dThe specified board has failed to initialize.Make sure the
board parameters are correct. Make sure the boardis properly
connected to the network and power is supplied.DNET5WARNUser dev
def Err, line:%dDNET6SYSTEMSystem error: %dA system error has
occurred.Document the events that led to theerror and call your
FANUC Robotics technical representative.DNET7WARNInvalid device
definitionDNET8WARNInvalid board indexAn invalid board index has
been specified.Specify a board index between 0 and
3.DNET9WARNInvalid MAC Id: Bd %d MAC %dAn invalid MAC Id has been
specified.Specify a MAC Id between 0 and 63
inclusive.DNET10WARNBoard already onlineThe specified board is
already on-line.Take the board off-line before attempting the
operation.DNET11WARNBoard not onlineThe specified board is not
on-line.Put the board on-line before attempting the
operation.DNET12WARNDevice already onlineThe specified device is
already on-line.Take the device off-line before attempting the
operation.DNET13WARNDevice not onlineThe specified device is not
on-line.Put the device on-line before attempting the
operation.DNET14WARNRequest timed outThe attempted DeviceNet
command request has timed out.Check all network connections. If all
connectionsappear to be in order, re-attempt the
command.DNET15WARNBoard not initializedThe specified board has not
been initialized.Initialize the board by attempting to put it
on-line, andthen cycle power. Then, re-attempt the
operation.DNET16SYSTEMSystem failedThe DeviceNet Interface system
has failed.Cold start the system. If the problem persists,INIT
start or reload the system. If the problem continuesto
persist,document the events that led to theerror and call your
FANUC Robotics technical representative.DNET17WARNBoard not
foundThe specified board was not found in the system.Make sure the
daughter boards are properly configuredand properly seated on the
motherboard.DNET19WARNCode file open failedThe code file required
to initialize the board cannot be accessed.Cold start the system.
If the problem persists,INIT start and reload the DeviceNet
Interface option.DNET20WARNCode file read failedThe code file
required to initialize the board cannot be read.Cold start the
system. If the problem persists,INIT start and reload the DeviceNet
Interface option.DNET21WARNCode file checksum errorThere is a
problem with the DeviceNet scanner code file.Cold start the system.
If the problem persists, INIT start andreload the DeviceNet
Interface option. If the problem continues topersist,document the
events that led to theerror and call your FANUC Robotics technical
representative.DNET22WARNBoard initialization timeoutThe board
initialization routine has timed out.Turn the controller off. Make
sure the motherboard is correctlyseated on the back plane. Cold
start the controller.If the problem persists,document the events
that led to theerror and call your FANUC Robotics technical
representative.DNET23WARNBoard initialization errorAn error has
occurred in the board initialization process.Cycle power to the
controller. If the problem persists, turn thecontroller off and
check the motherboard connection to the back plane.Cold start the
controller. If the problem persists,document the events that led to
theerror and call your FANUC Robotics technical
representative.DNET25WARNNo device assigned for Bd/MACA data
mismatch has occurred such that the system cannot find a
deviceassigned for the specified board number and MAC Id.Turn the
controller off and cold start the controller.If the problem
persists,delete the board from the Board List screen, reconfigure
the board,and re-add devices to the Device List. Cycle power. Also,
checkthe device MAC Id configurations.DNET26WARNNo match on dev
type look-upThe system cannot find the specified device type in its
list ofdefined device types.Check the selected device type on the
Device List. Next, check theDefined Device List and the Standard
Device Definition List for therequired device type. If it does not
appear, go to the DefinedDevice List and add the required device
definition, then select iton the Device List screen. When you have
finished, turn offthen turn on the controller.DNET27PAUSE.GDev
online err: Bd %d MAC %dThe device at the specified board number
and MAC Id cannot bebrought on-line.Make sure the device is
properly connected to the network.Check the device's MAC Id and
baud rate configuration. Check theboard's baud rate configuration
on the Board Detail screen.Check the board's network connection.
Cold Start the controller.DNET28PAUSE.GBoard online err: Bd %dThe
specified board cannot be brought on-line.Make sure the board is
properly connected to the network. Checkthat network power is being
supplied. Check that baud rates forthe board and devices are in
agreement. Cold Start the controller.DNET30PAUSE.GStd dev file fmt
err: Line %dThere is an error in the format of the specified device
definitionfile, on the specified line.Contact your FANUC Robotics
technical representative to obtaina correct device definition
file.DNET31PAUSE.GApp dev file fmt err: Line %dThere is an error in
the format of the specified device definitionfile, on the specified
line.Contact your FANUC Robotics technical representative to
obtaina correct device definition file.DNET33WARNUnknown keywordAn
unknown keyword has been found in the device definition
files.Contact your FANUC Robotics technical representative to
obtain thecorrect device definition files.DNET34WARNCycle power to
bring onlineThe user must turn power off and on to the controller
to bring onlinea newly-added device to a board's device list.Cycle
power to the controller. You will then be able to bring the
deviceonline.DNET35WARNBad format or out of rangeAn integer value
in the device definition files is incorrect.Contact your FANUC
Robotics technical representative to obtain thecorrect device
definition files.DNET36WARNI/O size/type not specifiedThe specified
line was not found in a device definition file.Contact your FANUC
Robotics technical representative to obtain thecorrect device
definition files.DNET37WARNNo PDTCODE lineThe specified line was
not found in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET38WARNNo MODULE lines with MULTIMODThe specified lines
were not found in a device definition file.Contact your FANUC
Robotics technical representative to obtain thecorrect device
definition files.DNET39WARNToo many MODULE linesThe specified lines
were incorrect in a device definition file.Contact your FANUC
Robotics technical representative to obtain thecorrect device
definition files.DNET40WARNMODULE specified w/o MULTIMODA
definition was incorrect in a device definition file.Contact your
FANUC Robotics technical representative to obtain thecorrect device
definition files.DNET41WARNRequired field missingA definition was
incorrect in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET42WARNDEVTYPE line absent/invalidThe specified line was
not found in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET43WARNVENDORID line absent/invalidThe specified line was
not found in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET44WARNPRODCODE line absent/invalidThe specified line was
not found in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET45WARNNo I/O mode line suppliedThe specified line was not
found in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET46WARNNo PDTCODE line suppliedThe specified line was not
found in a device definition file.Contact your FANUC Robotics
technical representative to obtain thecorrect device definition
files.DNET47PAUSE.GDeviceNet motherboard not foundThe DeviceNet
motherboard is not plugged into the back plane.Turn off the
controller and make sure the motherboard is properly seatedinto the
back plane of the controller. Cold start the
controller.DNET48WARNMultiple DEFAULT modes; ignoredThe device
definition file has too many I/O access modes designatedas DEFAULT.
Only one mode should be designated as DEFAULT.Remove the DEFAULT
designation from all I/O access modes exceptone.DNET49WARNDevice
Name not foundDNET50WARNBoard or network warning: Bd %dAn problem
has occurred with the specified daughter board or theDeviceNet
network connected to it. The problem is not severe enoughto disrupt
communications, but should be addressed as soon aspossible.Refer to
the next DNET alarm posted in the alarm log for specificalarm
recovery information.DNET51WARNNetwk comm errors: Bus warningThe
DeviceNet scanner has detected an abnormal number of
communicationserrors on the network. This message is a warning that
the scanner maygo offline if errors continue to occur at an
abnormal rate.Check your network topology to ensure conformance
with DeviceNetstandards. Check that your network terminators are in
place andproperly connected. Check that your network power supply
is ableto handle all of the devices on the network. Ensure that you
areusing properly shielded cables and connectors.DNET52WARNData
line too longThe specified line was incorrect in the device
definition file.Contact your FANUC Robotics technical
representative to obtain thecorrect device definition
files.DNET53WARNLine above DEVICE line ignoredAn extraneous line
was found in a device definition file.Check the Standard Device
Definition List to see if device typeshave been properly loaded. If
not, contact FANUC Robotics toobtain the correct device definition
files.DNET54WARNAll space in shared RAM usedThere is no space left
in the DeviceNet I/O buffer.Contact FANUC Robotics to report the
problem. Provideall details of the DeviceNet network, including
number and typeof devices, baud rates, MAC Ids, and network wiring
configuration.DNET55PAUSE.GBoard or network error: Bd %dAn error
has occurred with the specified daughter board or theDeviceNet
network connected to it.Refer to the Cause and Remedy of the cause
code (displayedimmediately below this error code on the teach
pendant).DNET56WARNNetwork power lostPower has been removed from
the DeviceNet network.Check the cable connecting the daughter board
to the DeviceNetnetwork. Also, check the connection to the power
source. Cyclepower to the controller.DNET57WARNNetwork
communications errorA network communications error has occurred on
the network connectedto the specified board.Check that the board's
baud rate corresponds to that of the devices.Check cable
connections to both the board and devices. Check thatthe proper
device definitions are selected for the devices on thenetwork and
that parameters are correct for user-defined devices.Turn off both
the controller and the DeviceNet network power, then coldstart the
controller.DNET58WARNMessage queue overrunThe board has received
more messages than it can handleat one time.The problem may be
momentary; attempt to bring the board on-lineagain. If the problem
persists, check that the board baud ratecorresponds to the baud
rate of the devices. Turn off then turn onthe
controller.DNET59WARNMessage lostThe board has missed a message
over the DeviceNet network.The problem might be momentary; attempt
to bring the board on-lineagain. If the problem persists, check
that the board baud ratecorresponds to the baud rate of the
devices. Turn off then turn onpower to the
controller.DNET60WARNXmit timeout: Network floodedThe traffic on
the DeviceNet network is too heavy for theboard to communicate with
the devices.Check that the board baud rate agrees with the baud
rate of thedevices. If no baud rate problem exists, turn off both
thecontroller and the DeviceNet network power, then turn on
both.DNET61WARNNo other nodes on networkAll of the devices expected
by the board to be on the network appearto be disconnected to the
network.Check cable connections to the board and to the devices. If
adevice has been disconnected, reconnect and press RESET on
theteach pendant. Check that the board baud rate is the same asbaud
rate of the devices.DNET62WARNBus off due to comm errorsThe board
is not communicating to the network because thereare too many
errors.Check that the baud rate of the board and of the devices
isthe same. Make sure that power is connected to the
DeviceNetnetwork. Press RESET on the teach pendant. If the
problempersists, begin removing devices from the network; after
eachdevice is removed, press RESET. When the board is
broughton-line, check the device configuration and the parameters
ofthe device definition.DNET63PAUSE.GDevice error: Bd %d MAC %dAn
error has occurred with the device at the specified boardnumber and
MAC Id.Refer to the Cause and Remedy for the cause code
(displayeddirectly beneath this error code on the teach
pendant).DNET64WARNConnection errorAn error has occurred when
attempting connection to thespecified device.Check that the baud
rate of the device agrees with the boardbaud rate. Check that the
device is properly connected tothe network; make sure the device is
receiving power fromthe network. Inspect the device definition to
see that theI/O type, access mode, and size of I/O are correct.
PressRESET on the teach pendant to re-attempt
connection.DNET65WARNIncorrect vendor IdThe vendor Id for the
device, as specified in the devicedefinition, is incorrect.Delete
the device from the Device List.Check the device documentation for
the correct vendor Id.Make corrections in the device definition and
add the deviceto the Device List.DNET66WARNIncorrect product
codeThe product code for the device, as specified in the
devicedefinition, is incorrect.Delete the device from the Device
List.Check the device documentation for the correct product
code.Make corrections in the device definition and add the deviceto
the Device List.DNET67WARNIncorrect device typeThe device type for
the device, as specified in the devicedefinition, is
incorrect.Delete the device from the Device List.Check the device
documentation for the correct device type.Make corrections in the
device definition and add the deviceto the Device
List.DNET68WARNDevice timeoutThe connection to the specified device
has timed out.Check the device's connection to the network. Make
sure thedevice baud rate agrees with the board baud rate. Attempt
tobring the device on-line by pressing RESET on the teach
pendant.DNET69PAUSE.GUnknown error code %dAn unknown error has
occurred with the specified device.Document the events that led to
theerror and call your FANUC Robotics technical representative.Make
sure the error code numberis noted and
reported.DNET70WARNConnection allocation errorAn error has occurred
when attempting connection to thespecified device.Check that the
baud rate of the device agrees with the boardbaud rate. Check that
the device is properly connected tothe network; make sure the
device is receiving power fromthe network. Inspect the device
definition to see that theI/O type, access mode, and size of I/O
are correct. PressRESET on the teach pendant to re-attempt
connection.DNET71PAUSE.GDup dbrd: Bd:%d Mbd:%sYou have two or more
DeviceNet daughter boards with the sameboard number
configuration.Re-configure the DIP switches on your daughter boards
so thatyou no longer have duplicates. DIP switch
configurationinformation is found in the User's Guide to the FANUC
RoboticsDeviceNet Interface.DNET72WARNFound dupl. DNet
daughterboardThis cause code is posted together with DNET-071
aboveto allow the user to easily identify the duplicatedaughter
board. Please see the Cause text for DNET-071for more
information.Please see the Remedy text for DNET-071 to fix
thisproblem.DNET73WARNNo match on mod type look-upThe system could
not find the module type corresponding to a moduleon the specified
device.View the module list for the device and delete or change
themodule in question. If this module was previously
functional,cold start the controller and attempt to use this module
typeagain. If the problem persists, perform an INIT start
andre-load the DeviceNet Interface option.DNET74PAUSE.GLoad only at
ctrl startAn I/O configuration file (.IO file) containing
DeviceNetconfiguration data was loaded at COLD START. The
DeviceNetconfiguration data in this file is ignored.Reload the .IO
file at controlled start.DNET76WARN$DN_DEV_DEFS array is fullThere
is no more room in the Defined Device List system variable.Delete
any unneeded device definitions from the DefinedDevice List before
adding a new one.DNET77WARNDNet I/O inactive at CTRL startAt
controlled start, I/O data assigned to DeviceNet devices isnot
active.This message is for informational purposes only. To make
DeviceNetI/O active, COLD start the controller.DNET78WARNNo room
for more devicesThe system variable for storage of devices is
full.If there are devices which are off-line, delete these
devicesunless they are required to be kept on the Device List.
Afterentries in the device list are freed, new devices can be
added.DNET79PAUSE.GUnknown dev type: Bd %d MAC %dThe device type
used by this device is currently unknown tothe system.This error
occurs during the I/O restore. Cold start the controller,add a new
device definition corresponding to the specifieddevice, then add
the device to the device list.DNET80PAUSE.GLoaded config too
largeThe previous I/O configuration contains too many
modules,devices, or device definitions to be loaded.Make sure you
have the same memory configuration as thesystem on which the I/O
configuration was saved.DNET82WARNPress RESET to reconnectThis
message appears when a board automatically restarts
communicationwith a DeviceNet network, but some or all devices are
not designated asautoreconnecting. Pressing RESET will attempt
reconnectionwith these devices.Pressing RESET will attempt
reconnection with the non-communicatingdevices and clear this
message.DNET83WARNBoard %d auto-restartedA board which was
previously in error state has automaticallyrestarted communications
with the DeviceNet network.This message is intended for user
notification only and does notindicate the presence of an error
situation.DNET84PAUSE.GBoard reset failed: Bd %dThe command to
reset the specified board has failed.Refer to the Cause and Remedy
for the cause code (displayeddirectly beneath this error code on
the teach pendant).DNET85PAUSE.GDev reset failed: Bd %d MAC %dThe
command to reset the specified device has failed.Refer to the Cause
and Remedy for the cause code (displayeddirectly beneath this error
code on the teach pendant).DNET86PAUSE.GStop scan cmd failed: Bd
%dThe specified board is unable to acknowledge the
stop-scanningcommand.Check DeviceNet connection to the board, as
well as DeviceNetpower to the network. If board is already in ERROR
state, thiserror can be disregarded.DNET87PAUSE.GBd offline cmd
failed: Bd %dThe board is not acknowledging the command to take it
off-line.Check DeviceNet connection to the board, as well as
DeviceNetpower to the network. If the board is already in the ERROR
state, thiserror can be disregarded.DNET88PAUSE.GIgnored: Bd %d MAC
%d Slot %dThe system does not recognize the module type of the
modulebeing loaded.Make sure the device definition data files are
the same betweenthe current system being loaded and the system on
which the I/Oconfiguration was saved. Contact FANUC Robotics for
the correctdefinition files.DNET89WARNCan't specify POLL and
STROBEThe data file contains lines which specify both POLL access
andSTROBE access for the same device.Contact FANUC Robotics to
obtain the correct devicedefinition files.DNET90WARNCan't STROBE w/
num outs > 0The device definition file specifies a
strobed-access device butthe number of outputs is not equal to
zero.Contact FANUC Robotics to obtain the correct devicedefinition
files.DNET91WARNInput size errorThe number of inputs specified in
the device definition forthis device does not match the number
expected by the scannerwhen it communicates with the device.Delete
the device, correct the device definition, then re-addthe device to
the device list.DNET92WARNOutput size errorThe number of outputs
specified in the device definition forthis device does not match
the number expected by the scannerwhen it communicates with the
device.Delete the device, correct the device definition, then
re-addthe device to the device list.DNET93WARNError reading vendor
IDThe scanner board encountered an error while trying to readthe
device's vendor ID.Check that the device baud rate matches the
board baud rate.Check also the device's connection to the
network.DNET94WARNError reading device typeThe scanner board
encountered an error while trying to readthe device's device
type.Check that the device baud rate matches the board baud
rate.Check also the device's connection to the
network.DNET95WARNError reading product codeThe scanner board
encountered an error while trying to readthe device's product
code.Check that the device baud rate matches the board baud
rate.Check also the device's connection to the
network.DNET96WARNError setting packet rateThe scanner board
encountered an error while trying to setthe communication packet
rate for this device.Check that the device baud rate matches the
board baud rate.Check also the device's connection to the network.
Resetthe device if possible.DNET97WARNConnection sync faultThe
board was unable to achieve synchronization in theconnection with
the specified device.Check that the device baud rate matches the
board baud rate.Check also the device's connection to the network.
Resetthe device if possible.DNET102WARNInvalid board MAC IdThe
board's MAC Id is not between 0 and 63.Check the Board Detail
screen to see if the board's MAC Idis between 0 - 63, inclusive. If
it is not, change the MAC Idto a valid value and press RESET on the
teach pendant. If theMAC Id appears valid, cold start the
controller. If the problempersists,document the events that led to
theerror and call your FANUC Robotics technical
representative.DNET103WARNInvalid board baud rateThe board's baud
rate is not one of: 125 KB, 250 KB, or 500 KB.Check the Board
Detail screen to see if the board's baud rateis one of the above
values. If it is not, change the baud rateto a valid value and
press RESET on the teach pendant. If thebaud rate appears valid,
cold start the controller. If the problempersists,document the
events that led to theerror and call your FANUC Robotics technical
representative.DNET104WARNDuplicate MAC Id errorThe specified
device has the same MAC Id as another device onthe network.Check
that no other devices have the same MAC Id, particularlythose
connected to a different master on the same network.Change the MAC
Id of the offending device at both the device andon the Device
List, and attempt to bring it on-line. If theproblem persists, cold
start the controller and try again.If the problem
continues,document the events that led to theerror and call your
FANUC Robotics technical representative.DNET105WARNDuplicate device
errorThere was an attempt to add a device to the board's device
listthat was a duplicate of a device already on the list.If the
desired device is already on the network and a secondone is not
being added, you may ignore the error. Otherwise,change the MAC Id
of one of the duplicate devices.DNET106WARNDevice not found errorA
device expected to be on the network was not found.Check that the
device is connected to the network. Check thatthe device baud rate
matches the board baud rate. Reset thedevice if possible. Cycle
power to the controller. If theproblem persists,document the events
that led to theerror and call your FANUC Robotics technical
representative.DNET107WARNBus offline errorThe board could not
perform an operation because thebus was off-line.Press RESET on the
teach pendant to attempt to bring the boardon-line. If the problem
persists, cycle power to thecontroller. If the problem continues to
persist, cycle power tothe DeviceNet network.DNET108WARNScanner
active errorThe board could not perform an operation because theit
is actively scanning the network.Take the board off-line and
re-attempt the operation.DNET109WARNBus not offline errorThe board
could not perform an operation because thebus is not off-line.Take
the board off-line and re-attempt the operation.DNET110WARNError:
board scanningThe board could not perform an operation because
theit is actively scanning the network.Take the board off-line and
re-attempt the operation.DNET111WARNError: board not scanningThe
board could not perform an operation because theit is not actively
scanning the network.Bring the board on-line and re-attempt the
operation.DNET112WARNBoard not ready; pls. waitAn attempt to bring
the board on-line was unsuccessful becausethe board was busy.Wait
ten seconds and re-attempt to bring the board on-line. Ifthe
problem persists, check board connection to the network,baud rate,
and network power.DNET114WARNBus fault error detectedThe board has
detected a fault on the DeviceNet network,and cannot communicate
with devices.Check that the baud rate of the board matches the baud
rateof all devices on the network. Also, check that power isbeing
supplied to the network. If the problem persists,cycle power to the
controller, and then to the network ifthe problem
continues.DNET115WARNInvalid I/O connection attemptA device does
not support the requested I/O connection(s).and cannot communicate
with devices.Check the device documentation to ensure that the
requestedI/O connection is supported.DNET119PAUSE.GDup. MAC Ack
FaultAck Fault-No acknowledge received during Duplicate MAC ID
sequence.Check it the Interface is not the only node on the
network.Check the baudrate of the interface and make sure it is
thenetwork baudrate. Check physical wiring of the
network.DNET120WARNDev online err: Bd %d MAC %dThe device at the
specified board number and MAC Id cannot bebrought on-line.Make
sure the device is properly connected to the network.Check the
device's MAC Id and baud rate configuration. Check theboard's baud
rate configuration on the Board Detail screen.Check the board's
network connection. Cold Start the controller.DNET121WARNDevice not
ready: Bd %d MAC %dWhen a device has been added to a scan list, it
cannot be brought onlinewithout cycling power to the
controller.Cycle power to the controller. You will then be able to
bring the deviceonline.DNET122WARNDevice error: Bd %d MAC %dAn
error has occurred with the device at the specified boardnumber and
MAC Id.Refer to the Cause and Remedy for the cause code
(displayeddirectly beneath this error code on the teach
pendant).DNET123WARNDev reset failed: Bd %d MAC %dThe command to
reset the specified device has failed.Refer to the Cause and Remedy
for the cause code (displayeddirectly beneath this error code on
the teach pendant).DNET124WARNDevice not autorec: Bd %d MAC %dThis
message appears when a board automatically restarts
communicationwith a DeviceNet network, but some or all devices are
not designated asautoreconnecting. Pressing RESET will attempt
reconnectionwith these devices.Pressing RESET will attempt
reconnection with the non-communicatingdevices and clear this
message.DNET125WARNSlave Conn. Idle: Bd %dThe slave connection of
the specified board is idleThe remote Master has not yet connected
to the slave connection.Make sure the remote Master is online and
configured properly.DNET130PAUSE.GInvalid parameterAn invalid
parameter has been specified for a DeviceNet KARELbuilt-in.Refer to
the cause code to determine which parameter is
invalid.DNET131WARNInvalid board numberThe specified board number
is invalid.Make sure the board number is an integer between 1 and
4, inclusive.DNET132WARNInvalid MAC IDThe specified MAC ID is
invalid.Make sure the MAC ID is an integer between 0 and 63,
inclusive.DNET133WARNI/O Size mismatchDNET134WARNMode
mismatchDNET135WARNAnalog size mismatchDNET136WARNName does not
matchDNET137WARNName and Analog do not matchDX0PAUSE.GUnknown error
(DX00)DX1PAUSE.GNo global variablesThe Delta Tool/Frame global
variables have NOT been properly loaded.Check the application
installation manual for the properinstallation procedure for Delta
Tool/Frame.DX2PAUSE.GError allocating data memoryDX3PAUSE.GNo
system variablesDelta Tool/Frame system variables (e.g.
$DXSCH[])not found.Check the application installation manual for
the properinstallation procedure for the Delta Tool/Frame
system.DX4PAUSE.GIllegal schedule numberInvalid Delta Tool/Frame
schedule number.Check all schedule numbers used within the
specified programto verify that they are within the allowablerange
specified for the $DXSCH[] system variable.DX5WARNSchedule already
enabledRequested Delta Tool/Frame schedule number has alreadybeen
enabled.Use END_OFFSET or abort program to disable
schedule.DX6WARNSchedule not enabledTry to disable a schedule which
has not been enabled.Check to see if the requested schedule has
been disabledbefore, or whether the requested schedule has not
beenenabled at all.DX7PAUSE.GSchedule not enabledTry to apply
offset to a schedule which has not been enabled.Check to see if the
requested schedule has been disabledbefore, or whether the
requested schedule has not beenenabled at all.DX8PAUSE.GInternal
errorInternal error: cannot find dxfndofs schedule.Notify FANUC
Robotics.DX9PAUSE.GInternal errorWrong packet was sent to INTP to
signal completion of updating$DXMOR deltatool or deltaframe
offset.Notify FANUC Robotics.DX10PAUSE.GDeltaJ DeltaT/F
incompatibleAttempt to enable deltajoint with deltatool
and/ordeltaframe in a schedule.Do not enable deltajoint with
deltatool and/or deltaframein a schedule.DX11PAUSE.GDeltaT DeltaF
incompatibleAttempt to enable deltatool withdeltaframe in a
schedule.Do not enable deltatool withdeltaframe in a
schedule.DX12PAUSE.GSpecified group already enabledThe specified
motion group has been already enabled by DX function.Abort the
enabled DX function before this start.DX13PAUSE.GInvalid robot link
group trackingDX14PAUSE.GInvalid offset orientationThe calculated
offset orientation of this time is out of rangespecified by
$DXRLINK.$ortmax.Decrease the speed of the Master robot or Check
the noize on theEthernet.DX15PAUSE.GInvalid offset distanceThe
calculated offset distance of this time is out of rangespecified by
$DXRLINK.$locmax.Decrease the speed of the Master robot or Check
the noize on theEthernet.DX16PAUSE.GUT is changedUT of master robot
is changed.Don't change UT of master during robot
link.ELOG0WARNELOG9WARNcall a service manA system error has
occurred.Perform a cold start: 1. Turn off the robot. 2. On the
teach pendant, press and hold the SHIFT and RESET keys. 3. While
still pressing the SHIFT and RESET keys, turn on the robot. If the
error is not cleared, document the events that let to the error and
call your FANUC Robotics technical representative.ELOG11WARNPower
off, if you want to recover.A system error has occurred.A system
error has occurred.Perform a cold start: 1. Turn off the robot. 2.
On the teach pendant, press and hold the SHIFT and RESET keys. 3.
While still pressing the SHIFT and RESET keys, turn on the robot.
If the error is not cleared, document the events that let to the
error and call your FANUC Robotics technical
representative.ELOG12WARNA system error has been occurred.A system
error has occurredA system error has occurred.Perform a cold start:
1. Turn off the robot. 2. On the teach pendant, press and hold the
SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET
keys, turn on the robot. If the error is not cleared, document the
events that let to the error and call your FANUC Robotics technical
representative.FIG0WARNUNUSED ERROR
CODE(FCT00)FIG10PAUSE.LParameter errorCase: Motion statment of
program has not parameterSet up parameterFIG11PAUSE.LL1,L2 is
differentCase:L1 and L2 is differL2 is longer than L1This figule
don't writeChange them like L1 is longer than
L2FIG12PAUSE.LLength,Width is differentCase:Length and Width is
differWidth is longer than lengthThis figule don't writeChange them
linke Length is longer than WidthFIG13PAUSE.LR is differentCase:R
is longer than WidthThis figule don't writeChange R and
L2FIG14PAUSE.LL1 is shortCase:L1 is too shortBRC is differThis
figule don't writeChange L1 or BRCFIG15PAUSE.LLength is
shortCase:Length is too shortBRC is differThis figule don't
writeChange Length or BRCFIG16PAUSE.LL1 is longCase:L1 is too
longBRC is differThis figule don't writeChange L1 or
BRCFIG17PAUSE.LLength is longCase:Length is too longBRC is
differThis figule don't writeChange Length or BRCFIG18PAUSE.LL2 is
shortCase:L2 is too shortBRC is differThis figule don't writeChange
L2 or BRCFIG19PAUSE.LWidth is shortCase:Width is too shortBRC is
differThis figule don't writeChange Width or BRCFIG20PAUSE.LL2 is
longCase:L2 is too longBRC is differThis figule don't writeChange
L2 or BRCFIG21PAUSE.LWidth is longCase:Width is too longBRC is
differThis figule don't writeChange Width or
BRCFIG22PAUSE.L$FCMIN_INTR is shortCase:$FCMIN_INTR is too
short$FCMIN_INTR is differChange $FCMIN_INTRFIG23PAUSE.L$FCMIN_INTR
is longCase:$FCMIN_INTR is too long$FCMIN_INTR is differChange
LofFIG24PAUSE.LBRC is shortCase:BRC is differChange
BRCFIG25PAUSE.LBRC is longCase:BRC is longBRC is differChange
BRCFIG26PAUSE.LMJ is differentCase:MJ is longer then circuitMJ is
differChange MJFIG27PAUSE.LMJ is shortCase:MJ is shortMJ is
differChange MJFIG28PAUSE.LFigure not writeCase:This figule don't
writeconfirm each parameterFIG29WARNDon't effective LofCase:Cutting
time turn out long, in the case Piercing offset is TRUEPiercing
offset don't executeFIG30PAUSE.LIndex value code is
differentCase:This data number don't set upFIG31PAUSE.LSpeed value
is differentCase:Change speed valueFIG32WARNGroup setup is
wrongCase:Group setup is wrongFIG33PAUSE.LSpeed unit is
differentCase:Speed unit don't set upSet up speed unit in data
menuFIG34PAUSE.LMJ is longCase:MJ is longMJ is differChang
MJFIG35PAUSE.LDiameter is longCase:Diameter is too longBRC is
differThis figule don't writeChange Diameter or BRCFILE1WARNDevice
not readySpecified file device is not ready.Check if the device is
mounted and readyto use.Check if the device name is
correct.FILE2WARNDevice is FullDevice is full. There is no more
spaceto store data on the device.Delete any unnecessary files or
changeto a new device.FILE3WARNDevice is protectedDevice is
protected. So, you cannotwrite to the device.Release the device
protection.FILE4WARNDevice not assignedDevice is not assigned.The
specified device is not recognizedby the system. If RD then
$FILE_MAXSECis set to 0If RD set $FILE_MAXSEC else sys
errFILE5WARNDevice not mountedDevice is not mounted. You should
mountthe device before using it.Mount the correct file
device.FILE6WARNDevice is already mountedYou tried to mount the
device which hadbeen already mounted.Mount device only
once.FILE8WARNIllegal device nameDevice name contains an
illegalcharacter.Check spelling and validity of
devicename.FILE9WARNIllegal logical unit numberIllegal LUN is
used.This is an internal error. Checkthe validity of the logical
unit number.FILE10WARNDirectory not foundSpecified directory does
not existCheck validity of directory name.FILE11WARNDirectory
fullDirectory is full.You tried to create a file in the
rootdirectory which execeeded the maximumnumber of files allowed on
the device.Delete unnecessary files in theroot
directory.FILE12WARNDirectory is protectedYou tried to write to a
writeprotected directory.Release the protection to the
directory.FILE13WARNIllegal directory nameDirectory name contains
an illegalcharacter.Check spelling of directory name.FILE14WARNFile
not foundThe specified file was not found.Check that the file
exists and thatthe file name was spelled correctly.FILE15WARNFile
is protectedYou tried to access a protected file.Release the
protection from file.FILE17WARNFile not openYou tried to access a
file which isnot open.Open the file before accessing.FILE18WARNFile
is already openedYou tried to create/delete/rename a file which is
already opened.Close file before such operations.FILE19WARNFile is
lockedYou tried to access a file which islocked.Release the
lock.FILE20WARNIllegal file sizeFile size is invalid.Change file
size to be correct.FILE21WARNEnd of fileEnd of file was
detected.This is a notification. You do not haveto do anything for
this warning message.FILE22WARNIllegal file nameFile name contains
an illegal character.Check spelling of file name.FILE23WARNIllegal
file numberFile number is illegal.Use a valid file number which is
theID returned from an open request.FILE24WARNIllegal file typeFile
type contains an illegal character.Check the spelling and validity
of thefile type.FILE25WARNIllegal protection codeFile protection
code is illegal.Check if the protection code is
correct.FILE26WARNIllegal access modeFile access mode is
illegal.Check if the access mode is correct.FILE27WARNIllegal
attributeFile attribute in the SET_ATTRIBUTErequest is
illegal.Check that attribute specified is valid.FILE28WARNIllegal
data blockData block is broken which is used inFIND_NEXT
request.You should keep the data block which isreturned from the
previous FIND_FIRSTor FIND_NEXT request.FILE29WARNCommand is not
supportedIllegal request command is specified.Check if the request
code is corect.FILE30WARNDevice lun table is fullDevice management
table is full.Dismount any unnecessary devices.FILE31WARNIllegal
path namePath name contains an illegal character.Check if the path
name is correct.FILE32WARNIllegal parameterIllegal parameter is
detected.Check that all parameters for the request are
valid.FILE33WARNSystem file buffer fullFile management buffer is
full.Close unnecessary files.FILE34WARNIllegal file positionIllegal
file position is specified.Check that the file position
parameterfrom SEEK request is positive and notbeyond the end of
file.FILE35WARNDevice not formattedYou tried to access a
unformatteddevice.Format the device before using it.FILE36WARNFile
already existYou tried to rename a file to analready existing file
name.Change the new file name to be uniqueor delete the existing
file.FILE37WARNDirectory not emptyYou tried to remove a
subdirectorywhich contains some files or directories.Remove all
files and directories in thesubdirectory before
removingsubdirectory.FILE38WARNFile locked by too many tasksThere
are too many lock requests to samefile.Unlock any unnecessary file
lock requests.FILE39WARNDirectory already existsYou tried to create
a sub-directory thatalready exists.Use a unique name for new
sub-directoryFILE40WARNIllegal file access modeYou tried to read
from a write onlyopened file or tried to write to aread only opened
file.Open a file with correct access mode.FILE41WARNFile not
lockedYou tried to unlock file which you hadnot locked.Don't unlock
a file that is not locked.You can only unlock files which YOU
havelocked.FILE45WARNneed to set $FILE_MAXSEC$FILE_MAXSEC has not
been set and must bebe set before device can be formatted.Set
variable $FILE_MAXSEC to valid value. 800 is a good default
value.FILE49WARNFile is not standard fileA file operation has been
attempted on afile which is not a standard fileUse a standard file
device (e.g., FR:or RD:FILE50WARNPChamp %s device NOT ready -
device FULLPChamp output device NOT ready or FULLCheck device OR
delete old files on deviceFILE51WARNNESTED kread issuedA call to
kread was made while aWOULDBLOCK read was pendingDo not call kread
again until the packetfrom the previous read has been
rcvdFILE52WARNKread re-call with different buf_pA call to kread was
made following aWOULDBLOCK read with a different buf_pCall kread
with the same buf_p as wasused in the original kread
callFILE53WARNMC InsertedMemory Card (MC) has been insertedand
properly detected by the systemStart MC access afterreceiving this
messageFILE54WARNMC RemovedMemory Card (MC) has been removedfrom
the systemReinstall Memory Card if you wishto continueFILE55WARNMC
not detectedEither the Memory Card (MC) is notproperly inserted or
the Card that isinserted is not a Memory Card type(SRAM or
Flashdisk)Either insert a MC or exchangeinserted card with a
MCFILE56WARNModem Card InsertedModem Card has been insertedand
properly detected by the systemStart Modem Card access
afterreceiving this messageFILE57WARNModem Card RemovedModem Card
has been removedfrom the systemReinstall Modem Card if you wishto
continueFILE58WARNIllegal Character in NameName contains an illegal
character.Remove any non alpha numeric characterwhich is not an
underscore.FILE59WARNNot enough TEMP memory for file operationThe
TEMP memory is too low to completethe file operation.Try one of the
following:1. Remove unnecessary files/programs from the system.2.
Remove unused options from the controller by reloading with fewer
options.3. Add more D-RAM to the system.FILE60WARNMax %d,Req %d,Ac
%dRequested Memory Size ($FILE_MAXSEC)exceeds Max Available.RD Left
at Actual SizeAdjust Requested Memory Size($FILE_MAXSEC) to less
than or equalto the Max AvailableFILE61WARNRequested RD Sz too
bigRequested RD Size (Req)exceeds Max Available (Max).RD Left at
Actual Size (Ac)Adjust $FILE_MAXSEC Memory Size(Req) to less than
or equalto the Max Available (Max)FILE62WARNBackup files are not
correctBackup file is not correct.Try again file backupoperation to
the other deviceor using the other media.FILE63PAUSE.G(%s) is not
loadedThe indicated file is not loaded, whenall files are restored
in AutomaticSoftware Update functionPlease check cause
codeFLPY1WARNEnd of directory reachedYour listing has reached the
end of thedirectory. You do not have to doanything for this warning
message.This is a notification. You do not haveto do anything for
this warning message.FLPY2WARNFile already existsThe file name you
are trying to createalready exists on this device.Delete the file
of this name or choosea different file name.FLPY3WARNFile does not
existThe file you are trying to open does notexist on this
device.Open a file that does exist on
thedevice.FLPY4WARNUnsupported commandOperation is not supported on
floppydisk.Use only operations supported on
floppydisk.FLPY5WARNDisk is fullThe disk file capacity has been
reached.Delete some unneeded files or use adisk with sufficient
free space.FLPY6WARNEnd of file reachedThe end of the file was
reached whilereading.Do not attempt to read beyond the end ofa
file.FLPY8WARNOnly one file may be openedAn attempt was made to
open more thanone file.Do not attempt to open more than onefile at
a time.FLPY9WARNCommunications errorThe protocol format was
invalid.Retry the operation.FLPY15WARNWrite protection violationThe
disk has write protection enabled.Remove write protection from the
disk oruse a disk that is not write protected.FLPY100WARNDirectory
read errorThe directory information iscorrupted and unreadable.Try
another disk or reformat the disk.FLPY101WARNBlock check errorThe
checksum data is bad.Data is corrupted on disk and can notbe
read.Try another disk, or reformat the diskFLPY103WARNSeek
errorThere is a bad sector or track on thedisk.Clean the disk
drive, try another disk,or reformat the disk.FLPY104WARNDisk
timeoutThe drive did not respond to a command.Check the cable to
the drive and makesure drive power is on.FLPY105WARNWrite
protection violationThe disk has write protection enabled.Remove
write protection from the disk oruse a disk that is not write
protected.FLPY106WARNMemory Card hardware errorMemory Card hardware
error is detected.Check Memory Card I/F unit connection orbattery
of the card.FLPY107WARNNot formatted cardThe Memory Card is not
formatted.Format the card with UTILITY menu onFILE
screen.FORC1WARNSensor board doesn't existForce control board
doesn't exist.1. Turn the controller OFF.2. Mount the force control
board.FORC2WARNSensor board doesn't exist 2Force controlboard
doesn't exist.1. Turn the controller OFF.2. Mount the force control
board.FORC3PAUSE.GForce control error (F:%d^1, E:%d^2)The error
occurred from theforce control board.Refer to the manual for the
forcecontrol board.FORC4SYSTEMCommunication errorThe system cannot
cammunicate with theforce control board.Please check the force
control board.FORC5WARNSensor board is disabledForce control board
has been disabledbecause of the alarm displayed at the same
time.Refer to the remedy of the alarm displayed at the same
time.FORC6WARNSensor board is disabled 2Force board has been
disabledbecause of the alarm displayed at the same time.Refer to
the remedy of the alarm displayed at the same
time.FORC11PAUSE.GForce group mismatchThe program cannot control
the specifiedmotion group.Please check the default motion groups
inthe program.FORC12PAUSE.GTime out error occurredThe system cannot
start force control.Please check the force control
board.FORC13PAUSE.GCommunications errorThe system cannot
communicate with theforce control board.Please check the force
control board.FORC14PAUSE.GInvalid tool numberThe tool number is
set to 0.Please set the correct tool number.FORC15PAUSE.GForce
sensor error exceed limitAs a result