Fanuc SYST Alarm Codes

Home > Fanuc > Alarm Codes > SYST Alarm Codes

Fanuc SYST Alarm Codes

SYST-001 PAUSE HOLD button is being pressed
Cause: You attempted an operation while the hold button (input) is pressed.
Remedy: Clear the hold button (input), and try the same operation.
________________________________________________________________
SYST-002 PAUSE HOLD is locked by program
Cause: 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 program, the held condition can only be
cleared by the same program using the UNHOLD statement/action, or by aborting the program. If a
motion is attempted in such condition, this error message is displayed.
Remedy: Wait until the UNHOLD statement is executed by the karel program, or abort the karel
program.
________________________________________________________________
SYST-003 WARN TP is enabled
Cause: The attempted operation could not be done because the teach pendant is enabled.
Remedy: Disable the teach pendant, and try the same operation again.
________________________________________________________________
SYST-004 WARN SOP is enabled
Cause: The attempted operation could not be done because the System Operator Panel is enabled.
Remedy: Turn the REMOTE switch on the SOP to REMOTE side, and try the same operation again.
________________________________________________________________
SYST-005 WARN UOP is the master device
Cause: The attempted operation could not be done because the User Operator Panel is enabled.
Remedy: Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the
$RMT_MASTER system variable correctly. Refer to the Software Reference Manual, Chapter 2
&qout;System Variables&qout;, for more information on system variables.
________________________________________________________________
SYST-006 WARN KCL is the master device
Cause: The attempted operation could not be done because KCL is the master device.
Remedy: Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the
$RMT_MASTER system variable correctly. Refer to the SYSTEM RJ-2 Software Reference Manual,
Chapter 2 &qout;System Variables&qout;, for more information on system variables.
________________________________________________________________
SYST-007 WARN NETWORK is the master device
Cause: The attempted operation could not be done because the NETWORK command processor
is the master device.
Remedy: Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the
$RMT_MASTER system variable correctly. Refer to the Software Reference Manual, Chapter 2
&qout;System Variables&qout;, for more information on system variables.
________________________________________________________________
SYST-008 WARN Nothing is the master device
Cause: The system variable $RMT_MASTER is set to disable all devices. Therefore, no remote
device can issue motion.
Remedy: Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the
$RMT_MASTER system variable correctly. Refer to the Software Reference Manual, Chapter 2
&qout;System Variables&qout;, for more information on system variables.
________________________________________________________________
SYST-009 WARN Safety Fence open
Cause: The attempted operation could not be done because the safety fence is open.
Remedy: Close the safety fence, and try the same operation again.
________________________________________________________________
SYST-010 WARN Max num task reached
Cause: The number of task has reached the maximum.
Remedy: Abort one of the running task.
________________________________________________________________
SYST-011 WARN Failed to run task
Cause: The system has failed to run the program.
Remedy: Refer to the error cause code. Use MENU to display the Alarm Log screen.
________________________________________________________________
SYST-012 WARN Not in remote
Cause: Remote condition is not satisfied.
Remedy: Turn the remote switch on.
________________________________________________________________
SYST-013 WARN Invalid program number
Cause: The specified PNS number is not in the range of 1 to 9999.
Remedy: Specify correct program number.
________________________________________________________________
SYST-014 WARN Program select failed
Cause: PNS operation has failed by some reason.
Remedy: Refer to the error cause code. Use MENU to display the Alarm Log screen.
________________________________________________________________
SYST-015 WARN Robot Service Request failed
Cause: RSR operation has failed by some reason.
Remedy: Refer to the error cause code. Use MENU to display the Alarm Log screen.
________________________________________________________________
SYST-016 WARN ENBL signal is off
Cause: ENBL signal in UOP is off
Remedy: Set ENBL signal ON
________________________________________________________________
SYST-017 WARN Single step operation effective
Cause: Single step operation is effective
Remedy: Disable single step switch
________________________________________________________________
SYST-018 WARN Continuing from different line
Cause: Attempt to continue program from different line from paused line
Remedy: Respond YES or NO in the prompt box on at the teach pendant
________________________________________________________________
SYST-019 WARN Program not selected
Cause: Program has not been selected
Remedy: Select a program from the program select menu on the teach pendant, or using PNS
________________________________________________________________
SYST-020 WARN Program not verified by PNS
Cause: The program specified by PNS is different from the currently selected program. This error
occurs in Mate controllers only.
Remedy: Select a correct program from the program select menu on the teach pendant.
________________________________________________________________
SYST-021 WARN System not ready, press reset
Cause: An error has been detected by the system
Remedy: Press RESET to clear error condition
________________________________________________________________
SYST-022 WARN PNS not zero, cannot continue
Cause: The paused program cannot be continued if the PNS input ports are not zero. This error
occurs in Mate controllers only.
Remedy: Set all PNS input ports to OFF.
________________________________________________________________
SYST-023 SYSTEM Teach Pendant communication error
Cause: A communication cable is broken.
Remedy: Check the teach pendant cable. Replace the cable if necessary.
________________________________________________________________
SYST-024 WARN PNSTROBE is OFF. Cannot start exec
Cause: Because PNSTROBE is off, prod_start could not be processed
Remedy: Set PNSTROBE input to ON
________________________________________________________________
SYST-025 WARN Teach Pendant is different type
Cause: The type of teach pendant being connected, is different from the one that was disconnected.
Remedy: Connect the same type of teach pendant as disconnected.
________________________________________________________________
SYST-026 WARN System normal power up
Cause: System has executed normal power startup
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-027 PAUSE HOT start failed (Error:%d)
Cause: HOT start has failed for one of the following reasons: 1. Power failed during system start
up. 2. Flash ROM module was changed. 3. A run-time error occurred. 4. System internal error 1.
5. System internal error 2.
Remedy: COLD start is selected automatically.
________________________________________________________________
SYST-028 WARN (%s) Program timed out
Cause: $PWR_HOT,$PWR_SEMI program has been aborted by the system due to time out (40sec)
Remedy: Decrease program size so that it can be executed within the time out limit
________________________________________________________________
SYST-029 PAUSE Robot was connected (Group:%d)
Cause: The connect/isolate key was turn to the connect side
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-030 PAUSE Robot was isolated (Group:%d)
Cause: The connect/isolate key was turn to the isolate side
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-031 SYSTEM F-ROM parity
Cause: An error has occurred accessing F-ROM
Remedy: Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the
SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If
the error is not cleared, document the events that led to the error and call your FANUC Robotics
technical representative.
________________________________________________________________
SYST-032 WARN ENBL signal from UOP is lost
Cause: ENBL input signal from UOP is lost
Remedy: Determine and correct the cause of loss of this signal.
________________________________________________________________
SYST-033 WARN SFSPD signal from UOP is lost
Cause: SFSPD input signal from UOP is lost
Remedy: Determine and correct the cause of loss of this signal.
________________________________________________________________
SYST-034 WARN HOLD signal from SOP/UOP is lost
Cause: HOLD input signal from SOP/UOP is lost
Remedy: Determine and correct the cause of loss of this signal.
________________________________________________________________
SYST-035 WARN Low or No Battery Power on MAIN
Cause: Battery in PSU board is low in power.
Remedy: Replace the Old Battery with a new battery of same kind.
________________________________________________________________
SYST-036 WARN Semi power failure recovery
Cause: System did semi-hot start
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-037 SVAL1 Key switch broken
Cause: Improper input from Key switch
Remedy: Please fix the CE Sign key switch
________________________________________________________________
SYST-038 SVAL1 Operation mode T1 Selected
Cause: Operation mode T1 Selected
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-039 SVAL1 Operation mode T2 Selected
Cause: Operation mode T2 Selected
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-040 SVAL1 Operation mode AUTO Selected
Cause: Operation mode AUTO Selected
Remedy: This is just a notification. You do not have to do anything for this warning message.
________________________________________________________________
SYST-041 PAUSE Ovrd Select could not ENABLED
Cause: DI index is invalid
Remedy: Please set valid DI index
________________________________________________________________
SYST-042 SVAL1 DEADMAN defeated
Cause: The mode switch was changed from T1 or T2 mode to AUTO mode and the DEADMAN was
already pressed. The DEADMAN must be released when switching to AUTO mode
Remedy: Release the DEADMAN and press RESET.
________________________________________________________________
SYST-043 PAUS TP disabled in T1/T2 mode
Cause: The mode selector is in T1 or T2 and the TP ON/OFF switch is in the OFF position
Remedy: Turn the TP ON/OFF switch to ON. Press RESET.
________________________________________________________________
SYST-044 SYSTEM (Abnormal) TP disabled in T1/T2 mode
Cause: The mode selector is in T1 or T2 and the TP ON/OFF switch is in the OFF position and
SVON is ON. This is an abnormal condition.
Remedy: Call your FANUC Robotics technical representative.
________________________________________________________________
SYST-045 PAUSE TP enabled in AUTO mode
Cause: The mode selector is in AUTO and the TP ON/OFF switch is in the ON position
Remedy: Turn the TP ON/OFF switch to OFF. Press RESET.
________________________________________________________________
SYST-046 SYSTEM Control Reliable/CE Mark config mismatch
Cause: Either 1.Control Reliable or CE Mark hardware exists but the CR or CE Mark option has
not been loaded,or 2.The Control Reliable/CE Mark option has been loaded but the hardware is not
available.
Remedy: If the Control Reliable/CE Mark option has not been loaded, load the Control Reliable/
CE Mark option. If it has been loaded then this is a system without the Control Reliable/ CE Mark
hardware and the system must be totally reloaded WITHOUT the Control Reliable/CE Mark option.
________________________________________________________________
SYST-047 WARN Continuing from distant position
Cause: Attempt to continue program from distant position from stopped position.
Remedy: Respond ABORT or CONTINUE in the prompt box on at the teach pendant
________________________________________________________________
SYST-048 ABORT NECALC couldn’t get work memory
Cause: OS couldn’t give NECALC soft part enough memory
Remedy: Please increase Controller’s memory
________________________________________________________________
SYST-049 ABORT SFCALC couldn’t get work memory
Cause: OS couldn’t give SFCALC soft part enough memory
Remedy: Please increase Controller’s memory
________________________________________________________________
SYST-050 WARN Invalid time in trigger request
Cause: Invalid time used in TG request
Remedy: Time must be less than 6,000,000 us
________________________________________________________________
SYST-051 PAUSE SYTG overrun: %d %d %x %d %d
Cause: Excessive time iin trigger routines First number indicates event routine (1) or scan routine (2).
Second number indicates individual overrrun (1) or excessive cumative CPU use (2). Third number:
event number(hexadecimal) or scan routine address Fourth number: limit (microseconds or 100ths of
one pct) Fifth number: time used (microseconds or 100ths of one pct)
Remedy: Event or scan routine need to be made more efficient, scan rate reduced, or system variable
values increased to permit more CPU usage.
________________________________________________________________
SYST-052 WARN Trigger slot already used: %d
Cause: Specified entry already used
Remedy: Use cancel request to delete old entry
________________________________________________________________
SYST-053 WARN Invalid fast_DIN no: %d
Cause: Specified Fast-DIN number is invalid
Remedy: Use Valid Fast-DIN
________________________________________________________________
SYST-054 WARN Event-ID already used: %d
Cause: Specified event ID already in use
Remedy: Use unique event ID or cencel previous request
________________________________________________________________
SYST-055 WARN Event-ID not found: %d
Cause: Specified event ID is not presently in use
Remedy: Check event ID
________________________________________________________________
SYST-056 WARN Scan routine list full
Cause: A call to syscnrtn was made when the scan list was full. A maximum of 10 scan routines,
including the standard table scanning routine, may be active at one time.
Remedy: Either cancel scan routines that are no longer needed or combine scan routines
________________________________________________________________
SYST-057 WARN Illegal interval
Cause: The interval parameter in a call to syscnrtn was greater than 1000000 (1 second).
Remedy: Use a value in the range 1-1000000
________________________________________________________________
SYST-058 WARN Duplicate scan routine
Cause: syscnrtn was called specifying a routine and data_p that is already being scanned
Remedy: Don’t request the same rtn/data_p twice
________________________________________________________________
SYST-059 WARN Scan routine not active
Cause: syclclsc was called with a routine and data_p that that does not match any active scans
Remedy: Don’t cancel a non-existent scan
________________________________________________________________
SYST-060 WARN Duplicate cond/act table
Cause: syaddtbl called with pointer to table that is already in the scan list
Remedy: Add table only once
________________________________________________________________
SYST-061 WARN Scan table list full
Cause: syaddtbl called when all 10 condition/action table slots are already in use
Remedy: Cancel tables that are no longer needed or combine tables.
________________________________________________________________
SYST-062 WARN Scan table not active
Cause: sycncltb called with cond/act table that is not active.
Remedy: Check for duplicate sycncltb call or wrong table pointer
________________________________________________________________
SYST-063 WARN Scan time record seq error
Cause: System error: consecutive time interval start calls
Remedy: Contact Fanuc Robotcs wth information on events leading up to error
________________________________________________________________
SYST-064 WARN Bad scan table data
Cause: System error: Invalid data in scan table The following can result in this error: Too many
cond/action sets (max = 10) Invalid condition code Invalid action code Too many actions (max = 3)
Remedy: Contact Fanuc Robotcs wth information on events leading up to error
________________________________________________________________
SYST-065 ABORT SFCALC overrun
Cause: SFCALC task can’t get enough MPU power.
Remedy: Please reduce some software options or disable some motion groups which had been
enabled.
________________________________________________________________
SYST-066 PAUSE Teach Pendant communication error
Cause: Communication with the advanced Teach Pendant was interrupted.
Remedy: Too much communication may have caused the interrupt. Check the teach pendant cable.
Replace the cable if necessary.
________________________________________________________________
SYST-067 SYSTEM Panel HSSB disconnect
Cause: Panel HSSB communication is disconnected.
Remedy: Check panel HSSB hardware connection.
________________________________________________________________
SYST-069 WARN Program number out of range
Cause: The selected style number is zero or greater than the size of the style table.
Remedy: Select a valid style number, or adjust the size of the table.
________________________________________________________________
SYST-070 WARN No program name in table
Cause: There is no program name in the style table.
Remedy: Put a valid program name in the proper place in the style table.
________________________________________________________________
SYST-071 WARN Program not found
Cause: The selected style program does not exist on the controller.
Remedy: Create a program for the style, or put a valid program name in the style table.
________________________________________________________________
SYST-072 WARN Program not enabled
Cause: The selected style program is not enabled.
Remedy: Set the VALID field to YES in the style table.
________________________________________________________________
SYST-073 WARN Manual selection mismatch
Cause: The style input does not match the manually selected style.
Remedy: The PLC must send a style code that matches the manual selection.
________________________________________________________________
SYST-074 WARN Karel shell failed
Cause: Communications with the Karel shell extension failed.
Remedy: Cold start the controller.
________________________________________________________________
SYST-075 WARN Shell init failure
Cause: The shell was unable to start due to resource allocation failures.
Remedy: Cold start the controller.
________________________________________________________________
SYST-076 WARN Shell condition setup failure
Cause: The shell could not set up its required condition handlers.
Remedy: Cold start the controller.
________________________________________________________________
SYST-077 WARN Entered INTERLOCK mode
Cause: The controller is interlocked with the PLC
Remedy: This is an informational message. There is no error.
________________________________________________________________
SYST-078 WARN Entered ISOLATE mode
Cause: The controller is isolated from PLC control.
Remedy: This is an informational message. There is no error
________________________________________________________________
SYST-079 WARN Startup check failed
Cause: One or more of the pre-startup system checks failed.
Remedy: Look for a previous message that indicates exactly which check failed and take corrective
action.
________________________________________________________________
SYST-080 WARN Fault must be reset
Cause: The system is in a faulted state.
Remedy: Reset the fault before trying the operation again.
________________________________________________________________
SYST-081 WARN Not at home position
Cause: The program can not start because the robot is not at the defined home position.
Remedy: Move the robot to the home position.
________________________________________________________________
SYST-082 WARN Not within resume tolerance
Cause: The program can not be resumed because the robot has been moved from the position on the
path where it stopped.
Remedy: Jog the robot back to the correct position.
________________________________________________________________
SYST-083 WARN I/O is simulated
Cause: One or more I/O points are simulated.
Remedy: Unsimulate all I/O before trying to start the program.
________________________________________________________________
SYST-084 WARN I/O forced unsimulated
Cause: The system has forced all I/O to be unsimulated.
Remedy: This is an informational message.
________________________________________________________________
SYST-085 WARN Gen override not 100%
Cause: The general speed override is not 100%
Remedy: Set the override to 100%.
________________________________________________________________
SYST-086 WARN Gen override forced to 100%
Cause: The system has forced the general speed override to 100%
Remedy: This is an informational message.
________________________________________________________________
SYST-087 WARN Prog override not 100%
Cause: The program override is not 100%.
Remedy: Set the override to 100%.
________________________________________________________________
SYST-088 WARN Prog override forced to 100%
Cause: The system has forced the program speed override to 100%.
Remedy: This is an informational message.
________________________________________________________________
SYST-089 WARN Machine lock on
Cause: The machine lock is on, motion can not occur.
Remedy: Turn off the machine lock.
________________________________________________________________
SYST-090 WARN Machine lock forced off
Cause: The system has forced machine lock to the off state.
Remedy: This is an informational message.
________________________________________________________________
SYST-091 WARN Single step active
Cause: The program is in single-step mode.
Remedy: Take the system out of single-step mode.
________________________________________________________________
SYST-092 WARN Single step forced off
Cause: The system has forced single-stepping to be off.
Remedy: This is an informational message.
________________________________________________________________
SYST-093 WARN Process not ready
Cause: The program can not start because the process is not ready.
Remedy: Make the process equipment ready for running a program.
________________________________________________________________
SYST-094 WARN Process forced ready
Cause: The system has forced the process equipment to the ready state.
Remedy: This is an informational message.
________________________________________________________________
SYST-095 ABORT Remote diagnose internal error
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-096 ABORT Designated task is not valid
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-097 WARN Fail to initialize Modem
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-098 WARN Card Modem is removed
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-099 WARN Card Modem is not responded
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-100 WARN DSR in Modem OFF
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-101 WARN Connection is stopped
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-102 ABORT HDI not recorded
Cause: Internal Error in Remote Diagnose function.
Remedy: Internal error
________________________________________________________________
SYST-103 WARN Not-home ignored
Cause: User bypassed not-home condition at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-104 WARN Resume tolerance ignored
Cause: User bypassed TCP position tolerance at program resume.
Remedy: None needed – warning only.
________________________________________________________________
SYST-105 WARN Simulated I/O ignored
Cause: User bypassed I/O simulated at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-106 WARN Gen override ignored
Cause: User bypassed general override < 100% at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-107 WARN Prog override ignored
Cause: User bypassed program override < 100% at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-108 WARN Machine lock ignored
Cause: User bypassed machine lock at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-109 WARN Single step ignored
Cause: User bypassed single-step condition at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-110 WARN Process ready ignored
Cause: User bypassed process not ready at program startup.
Remedy: None needed – warning only.
________________________________________________________________
SYST-111 WARN No home pos defined
Cause: No home position defined for motion group 1.
Remedy: Enable at least one reference position for group 1 as a home position, or disable the home
position startup check.
________________________________________________________________
SYST-112 WARN No production start input defined
Cause: The production start input, which is required with the current program selection options,
has not been defined.
Remedy: Set up a production start input in the Cell Input I/O menu and restart the robot.
________________________________________________________________
SYST-113 WARN No style input group defined
Cause: The style number input group, which is required with the current program selection options,
has not been defined.
Remedy: Set up a style number input group in the Cell Input I/O and Group I/O menus and restart
the robot.
________________________________________________________________
SYST-114 WARN No RSR input defined
Cause: One or more RSR inputs, which are required with the current program selection options,
have not been defined.
Remedy: Set up the RSR inputs in the Cell Input I/O menu and restart the robot.
________________________________________________________________
SYST-115 WARN No PNS select input defined
Cause: One or more PNS selection inputs, which are required with the current program selection
options, have not been defined.
Remedy: Set up the PNS selection inputs in the Cell Input I/O and Group I/O menus and restart
the robot.
________________________________________________________________
SYST-116 WARN No RSR echo output defined
Cause: One or more RSR echo outputs, which are required with the current program selection
options, have not been defined.
Remedy: Set up the RSR echo outputs in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-117 WARN No PNS echo output defined
Cause: The PNS echo outputs, which are required with the current program selection options, have
not been defined.
Remedy: Set up the PNS echo outputs in the Cell Output I/O and Group I/O menus and restart
the robot.
________________________________________________________________
SYST-118 WARN No PNS strobe input defined
Cause: The PNS strobe input, which is required with the current program selection options, has
not been defined.
Remedy: Set up a PNS strobe input in the Cell Input I/O menu and restart the robot.
________________________________________________________________
SYST-119 WARN No echo strobe output defined
Cause: The acknowledgement strobe output, which is required with the current program selection
options, has not been defined.
Remedy: Set up an acknowledgement strobe output in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-120 WARN No style option input defined
Cause: One or more style option inputs, which are required with the current program selection
options, have not been defined.
Remedy: Set up the style option inputs in the Cell Input I/O menu and restart the robot.
________________________________________________________________
SYST-121 WARN No decision input group defined
Cause: The decision code input group, which is required with the current program selection options,
has not been defined.
Remedy: Set up a decision code input group in the Cell Input I/O and Group I/O menus and restart
the robot.
________________________________________________________________
SYST-122 WARN No style output group defined
Cause: The echo/manual style output group, which is required with the current program selection
options, has not been defined.
Remedy: Set up a style output group in the Cell Output I/O and Group I/O menus and restart the robot.
________________________________________________________________
SYST-123 WARN No option output defined
Cause: One or more style option outputs, which are required with the current program selection
options, have not been defined.
Remedy: Set up the style option outputs in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-124 WARN No decision output group defined
Cause: The decision code output group, which is required with the current program selection options,
has not been defined.
Remedy: Set up a decision code output group in the Cell Output I/O and Group I/O menus and
restart the robot.
________________________________________________________________
SYST-125 WARN No in-cycle output defined
Cause: The in-cycle output, which is required with the current program selection options, has not
been defined.
Remedy: Set up an in-cycle output in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-126 WARN No task-OK output defined
Cause: The task_OK output, which is required with the current program selection options, has
not been defined.
Remedy: Set up a task-OK output in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-127 WARN No isolate output defined
Cause: The isolate mode output, which is required with the current program selection options,
has not been defined.
Remedy: Set up an isolate mode output in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-128 WARN No interlock output defined
Cause: The interlock mode output, which is required with the current program selection options,
has not been defined.
Remedy: Set up an interlock mode output in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-129 WARN No manual style output defined
Cause: The manual style request output, which is required with the current program selection options,
has not been defined.
Remedy: Set up a manual style request output in the Cell Output I/O menu and restart the robot.
________________________________________________________________
SYST-130 WARN Program still running
Cause: The shell is already running an active program.
Remedy: Finish or abort the current program before requesting a new program selection.
________________________________________________________________
SYST-131 WARN Invalid manual style request
Cause: The manual style request cannot be done. There is also a secondary error posted that gives
the reason.
Remedy: Examine the secondary error message.
________________________________________________________________
SYST-132 WARN Manual request timed out
Cause: The specified manual style was not requested by the PLC within the allowable time period.
Remedy: Determine why the PLC did not respond to the request, or increase the timeout value.
________________________________________________________________
SYST-133 WARN System trigger request early
Cause: A request for a system trigger function (scan routine, etc) was made before the tables for
these are initialized.
Remedy: Defer any of these requests until late in the cold-start process
________________________________________________________________
SYST-134 WARN Max. freq. exceeded ch.: %d
Cause: A frequency input connected to one of the HDI inputs momentarily or for an extended time
had a frequency exceeding the setting for the maximum. The channel or input number is indicated
in the alarm text.
Remedy: Reduce or eliminate the noise on the signal with additional grounding or shielding. If the
frequency dip switch setting on the HDI Pulse Module is for the low range (640 Hz) and normal input
frequencies will be above this, change the settings. Change the dip switch setting to the high range
(1000 Hz) and the system variable $FQINT_SETUP[n].$FREQ_MAX_AL to 1020. If the frequency
dip switch setting on the HDI Pulse Module is for the high range (1000 Hz) and normal input
frequencies will always be below the low range change the setting to the low range. If the device
providing the frequency (a flow meter for example) is providing frequencies above 1000 Hz, either
change settings on the meter or change the type of meter so that the frequency provided is reduced. To
disable this alarm, change the setting of the system variable $FQINT_SETUP[n].$FREQ_MAX_AL
to 1200 if using the HDI Pulse Module or to 0 otherwise.
________________________________________________________________
SYST-135 WARN Invalid Clock, Please Reset
Cause: The system clock has an invalid time. The clock may not have been set.
Remedy: Reset the system Clock using the SYSTEM Clock TP page
________________________________________________________________
SYST-136 WARN System Time was reset
Cause: The system clock was reset by either an Operator or by the SNTP protocol (if SNTP is
enabled).
Remedy: Check the system Clock using the SYSTEM Clock teach pendant screen.
________________________________________________________________
SYST-137 WARN Device not found
Cause: The requested device is not installed on the motherboard.
Remedy: Request only valid devices.
________________________________________________________________
SYST-138 WARN Motherboard not installed
Cause: The specified motherboard is not installed.
Remedy: Specify only installed motherboards.
________________________________________________________________
SYST-139 WARN Invalid motherboard request
Cause: The specified motherboard index is not a valid value.
Remedy: This is a programming error. Specify only index 0 or 1
________________________________________________________________
SYST-140 WARN Invalid IRQ specified
Cause: An invalid interrupt number was specified by the device driver.
Remedy: Specify an IRQ from 3 through 7 only.
________________________________________________________________
SYST-141 WARN BMON was updated
Cause: BMON was automatically updated because of a newer version.
Remedy: Check BMON version.
________________________________________________________________
SYST-142 WARN ABS time in sytmrev in past
Cause: The time specified for a timed event has already passed The event will trigger immediately
Remedy: Specify a later time for the event
________________________________________________________________
SYST-143 WARN pkt_data_size too big
Cause: pkt_data_size parameter in syinpev_gen call is too big.
Remedy: Use size < = MAX_PKT_DATA in sytglib.h
________________________________________________________________
SYST-144 WARN Bad DO specfied by %s
Cause: Invalid or unassigned DOUT number specified in the indicated system variable.
Remedy: Set the sysem variable to zero (no port used) or to a valid port number and ensure that the
indicated DOUT is assigned.
________________________________________________________________
SYST-145 WARN DO specfied by %s OFFLINE
Cause: DOUT specified in the indicated system variable is Off-line.
Remedy: Set the device to which the DOUT is assigned On-line.
________________________________________________________________
SYST-146 WARN n_pkts invalid
Cause: n_pkts_parameter in syinpev_gen call is invalid.
Remedy: Use value in the range of 1 to 20, or zero if evnt_rtn_2 not used
________________________________________________________________
SYST-148 PAUSE Dynamic Brake is Disabled
Cause: Dynamic Brake is disabled by dynamic brake release request signal
(DI[$DYN_BRK.$DI_IDX]).
Remedy: If you would like to turn on servo, please turn off dynamic brake release request signal.
________________________________________________________________
SYST-149 WARN Dynamic Brake is Enabled
Cause: Dynamic Brake is enabled because dynamic brake release request is turned off.
Remedy: It is message only.
________________________________________________________________
SYST-150 WARN Cursor is not on line 1
Cause: The program is started except from the 1st line.
Remedy: Respond YES or NO in the prompt box on at the teach pendant
________________________________________________________________
SYST-151 WARN Start again (%s, %d)
Cause: After the program is started except from the 1st line, respond YES in the prompt box on
at the teach pendant.
Remedy: Start the same program again.
________________________________________________________________
SYST-152 WARN Cannot force DO’s in AUTO mode
Cause: Attempt to force output signal while controller is in AUTO mode
Remedy: Exit AUTO mode before doing this operation
________________________________________________________________
SYST-153 WARN Cannot SIM/UNSIM DO’s in AUTO mode
Cause: Attempt to force output signal while controller is in AUTO mode
Remedy: Exit AUTO mode before doing this operation
________________________________________________________________
SYST-154 WARN No start in ISOLATE/BYPASS mode
Cause: Production start received when controller is in ISOLATE or BYPASS mode
Remedy: Put controller into AUTO or INTERLOCK mode before doing this operation
________________________________________________________________
SYST-155 SVAL1 ABC overrun
Cause: ARM Bending Control function cannot get enough MPU power.
Remedy: Reduce some software options or disable some motion groups which had previously been
enabled, and then try the operation again.
________________________________________________________________
SYST-156 SYSTEM Unknown hard ware
Cause: This PCB is not used on this controller.
Remedy: Mount the correct PCB.
________________________________________________________________
SYST-157 SYSTEM CE/RIA software does not exist
Cause: CE/RIA software does not exist in this controller.
Remedy: Install CE/RIA option to this controller.
________________________________________________________________
SYST-158 PAUSE Robot cannot move in T2 mode
Cause: The mode selector is in T2. Robot cannot move in T2 mode.
Remedy: Change the mode switch to T1 or AUTO mode.
________________________________________________________________
SYST-159 WARN GO %d for Error Output not configured
Cause: GO dedicated for the Error Output feature is not configured.
Remedy: Configure GO dediocated for the Error Output feature.
________________________________________________________________
SYST-160 WARN Value output to GO %d out of limit
Cause: Value to be outputted to GO with Error Output feature is out of limit for this group output.
Remedy: Configure GO using more digital outputs.
________________________________________________________________
SYST-161 WARN Cannot start Remote diagnostic
Cause: Remote diagnostics are not started because the servo status is on.
Remedy: Turn off the servo then retry the remote diagnostics.
________________________________________________________________
SYST-162 PAUSE Servo On during Remote diagnostic
Cause: The servo is turned on during remote diagnostics.
Remedy: Turn off the servo before attempting remote diagnostics.
________________________________________________________________
SYST-163 WARN Cannot operate IO during Remote diagnostic
Cause: An attempt was made to operate I/O during remote diagnostics.
Remedy: Do not operate I/O during remote diagnostics.
________________________________________________________________
SYST-164 WARN Teach Pendant communication error
Cause: Communication with the teach pendant was interrupted.
Remedy: Too much communication may have caused the interrupt. Check that the teach pendant
cable is working properly. Replace the cable if necessary.
________________________________________________________________
SYST-165 PAUSE TP intermittent communication error
Cause: Intermittent errors occurred during communication with the teach pendant.
Remedy: Check to determine if there is any source of electrical noise. Check that the teach pendant is
working properly. Replace the teach pendant if necessary.
________________________________________________________________
SYST-166 WARN TP intermittent communication error
Cause: Intermittent errors occurred during communication with the teach pendant.
Remedy: Perform the following:
1. Check to determine if there is any source of electrical noise.
2. Check that the teach pendant is working properly.
3. Replace the teach pendant if necessary.
________________________________________________________________
SYST-168 WARN Robot(G:%d) is isolated
Cause: An attempt was made to operate an isolated Robot.
Remedy: Do not operate an isolated Robot.
________________________________________________________________
SYST-169 WARN S/W Registration is temporary
Cause: S/W Registration is in effect. This alarm is posted when there are more than 28 days until
registration expires.
Remedy: Display the S/W Registration screen:
1. Press MENUS.
2. Select STATUS.
3. Contact FANUC Robotics to obtain an authorization key to extend the time.
________________________________________________________________
SYST-170 WARN S/W Reg. expires in %d days
Cause: S/W Registration is in effect. This alarm is posted when there are between 14 and 28 days
until registration expires.
Remedy: Display the S/W Registration screen:
1. Press MENUS.
2. Select STATUS.
3. Contact FANUC Robotics to obtain an authorization key to extend the time.
________________________________________________________________
SYST-171 PAUSE S/W Reg. expires in %d days
Cause: S/W Registration is in effect. This alarm is posted when there are between 1 and 14 days
until registration expires.
Remedy: Display the S/W Registration screen:
1. Press MENUS.
2. Select STATUS.
3. Contact FANUC Robotics to obtain an authorization key to extend the time.
________________________________________________________________
SYST-172 PAUSE S/W Registration has expired
Cause: S/W Registration is in effect. This alarm is posted when registration has expired. The robot
cannot be operated in any automatic mode until registration is extended.
Remedy: Display the S/W Registration screen:
1. Press MENUS.
2. Select STATUS.
3. Contact FANUC Robotics to obtain an authorization key to extend the time.
________________________________________________________________
SYST-173 WARN See S/W Reg Screen (STATUS)
Cause: S/W Registration is in effect. Display to the S/W Registration screen for more details.
Remedy: Display the S/W Registration screen:
1. Press MENUS.
2. Select STATUS.
3. Contact FANUC Robotics to obtain an authorization key to extend the time.
________________________________________________________________
SYST-174 SYSTEM S/W Reg. active, option missing
Cause: Software Registration is in effect but the Software Registration option is not loaded.
Remedy: Load the Software Registration Option.
________________________________________________________________
SYST-175 WARN System was updated
Cause: S/W Registration is in effect. The System was updated. This message is for reference only.
No action is required.
Remedy: The System was updated. This message is for reference only. No action is required.
________________________________________________________________
SYST-176 WARN Software was updated
Cause: The system software is updated by the Auto Software update function.
Remedy: None.
________________________________________________________________
SYST-177 WARN RobotLink master is the master
Cause: The attempted operation could not be done because the robot is under control of the
RobotLink Master robot.
Remedy: Make sure that the Remote/Local Setup item in the System Configuration Menu is set to
LOCAL, and try the operation again.
________________________________________________________________
SYST-188 WARN book(%d) was not created
Cause: The book of operation logbook was not created.
Remedy: Reduce the number of books or $LOG_BUFF[ ].$SIZE to allocate book.
________________________________________________________________
SYST-189 WARN There is no book
Cause: There is no book of operation logbook.
Remedy: None.
________________________________________________________________
SYST-190 WARN HMI Mode – key unavailable
Cause: iPendant HMI Mode is enabled and this specific key is disabled.
Remedy: Enable the key in the iPendant Setup screen.
________________________________________________________________
SYST-195 PAUSE TP (on Rob#%d) enabled in T2 mode
Cause: More than one teach pendant is enabled while in T2 mode within the multi-arm ring.
Remedy: Disable the teach pendant which is not being used for the desired operation.
________________________________________________________________
SYST-196 WARN Enabled TP exists (H%x)
Cause: The desired operation could not be performed because teach pendants were enabled within the
multi-arm ring.
Remedy: Disable the teach pendants which are not being used for the desired operation.
________________________________________________________________
SYST-197 PAUSE Multi-arm Watchdog alarm
Cause: The master robot did not receive a heartbeat message from the slave robots within the time
specified by the $rkmashconf.$heartbt_tmo system variable.
Remedy: Check and repair any broken network connections.
________________________________________________________________
SYST-198 WARN Slave Robot Not Ready
Cause: Some slave robots are not ready to run a program.
Remedy: All slave robots have Auto/T1/T2 switch to be AUTO. $RMT_MASTER system variable
must be 4 (Robot Link). Refer to the FANUC Robotics Software Reference Manual, Chapter 2
&qout;System Variables&qout;, for more information on system variables. The variable settings
can be:
• 0:User Operator Panel
• 1:CRT/KB
• 2:Host computer
• 3:Remote device none
• 4:RobotLink master
________________________________________________________________
SYST-199 WARN Def Prog NOT change (TP disbl)
Cause: The selected robot program could not be changed because the robot has been defined as a
slave to a master robot, and the teach pendant is disabled.
Remedy: If you are selecting the program using a teach pendant, enable the teach pendant to select
a different program name.
________________________________________________________________
SYST-200 WARN Only Master TP may FWD/BWD
Cause: Only the teach pendant on the master robot can perform the SHIFT-FWD/BWD operation for
multi-arm programs.
Remedy: Use the teach pendant on the master robot to perform the SHIFT-FWD/BWD operation.
________________________________________________________________
SYST-201 WARN Master mismatch
Cause: The master robot number does not match with the one specified in the slave header.
Remedy: Verify the master robot number in the slave program header.
________________________________________________________________
SYST-202 WARN Incorrect $rmt_master on Slave robot
Cause: One or more of the specified slave robots does not accept the command from the master robot
because of $rmt_master system variable value.
Remedy: Verify that the system variable $RMT_MASTER is set to 4 on all slave robots.
________________________________________________________________
SYST-203 WARN Robot #%d has become online
Cause: This is a notification that a robot has been successfully added to the robot link network
as a slave robot.
Remedy: None.
________________________________________________________________
SYST-204 WARN Multi Program start in progress
Cause: The program run sequence is still in progress.
Remedy: Wait until the previous request is taken care of before you continue.
________________________________________________________________
SYST-205 WARN NO action specified
Cause: The teach pendant FWD or BWD key was pressed without also pressing the SHIFT key.
Remedy: Press the SHIFT key in addition to pressing the FWD or BWD key.
________________________________________________________________
SYST-206 WARN Operation canceled by RESET key
Cause: The operation was canceled by pressing the RESET key.
Remedy: None.
________________________________________________________________
SYST-207 PAUSE Message posted at Rob#%d (%s)
Cause: An error message has been posted on another robot.
Remedy: Display the error history screen of the robot where the error was posted, and perform the
remedy stated in the error message.
________________________________________________________________
SYST-208 PAUSE Feature NOT supported
Cause: The attempted operation is not supported. For example, you tried to run separate programs
for dual-arm robots.
Remedy: Be sure to perform only the supported operations.
________________________________________________________________
SYST-210 PAUSE Process Sync Time-out error
Cause: The process synchronization condition was not satisfied within the specified time-out limit.
Remedy:
1. Check the program logic (for a seq_id inconsistency, for example).
2. Specify a longer time-out limit (in the synchronization schedule).
________________________________________________________________
SYST-211 SYSTEM Comm processor Time-out error
Cause: The communications processor did not respond within the specified time-out limit.
Remedy: Turn off the controller and then turn it on again. If the alarm persists document the events
that led to the error, and call your FANUC Robotics technical representative.
________________________________________________________________
SYST-212 PAUSE Need to apply to DCS param
Cause: Mastering data or robot parameters are changed, but they are not applied to the DCS parameter.
Remedy: Press F3(APPLY) in the DCS menu.
________________________________________________________________
SYST-213 PAUSE User power cycle
Cause: A user cycled power from the function menu.
Remedy: None
________________________________________________________________
SYST-214 PAUSE DCS ESTOP
Cause: A DCS ESTOP occurred. This occurs only when $DCS_CFG.$TEST_PARAM1 bit 0 is 1.
Remedy: Set $DCS_CFG.$TEST_PARAM1 to 0.
________________________________________________________________
SYST-215 PAUSE DCS CSTOP
Cause: A DCS ESTOP occurred. This occurs only when $DCS_CFG.$TEST_PARAM1 bit 0 is 1.
Remedy: Set $DCS_CFG.$TEST_PARAM1 to 0.
________________________________________________________________
SYST-216 PAUSE DCS DCSALM
Cause: A DCS DCSALM occurred. This occurs only when $DCS_CFG.$TEST_PARAM1 bit 0 is 1.
Remedy: Set $DCS_CFG.$TEST_PARAM1 to 0.
________________________________________________________________
SYST-217 PAUSE DCS pos./speed is not available
Cause: The DCS position/speed process setting is set to ENABLE, when the hardware is not DCS
type or the DCS option is not loaded.
Remedy: Set the DCS position/speed process to DISABLE, or load the DCS option, or change
the hardware to DCS type.
________________________________________________________________
SYST-220 PAUSE Sync Time-out error
Cause: The process synchronization condition was not satisfied within the specified time-out limit.
Remedy:
1. Check the program logic (seq_id inconsistency, etc.)
2. Use a longer time-out limit (in the sync schedule).
________________________________________________________________
SYST-221 PAUSE Sync Schedule mismatch
Cause: The sync schedule does not match between robots.
Remedy:
1. Make sure same schedule number is used in the program between robots.
2. Make sure the schedule content (robot mask, etc.) is the same between robots.
________________________________________________________________
SYST-223 WARN Image backup failed(0x%x)
Cause: Image backup failed.
Remedy: 0x%x shows the cause of the failure. Find the definition in the list below. Remove the
cause of the failure and try the backup again.
• 0x%x Cause and remedy 0x1 This isn’t used. 0x2 Memory allocation failed. Call your FANUC
Robotics technical representative.
• 0x3 Information in FROM cannot be acquired. Call your FANUC Robotics technical
representative.
• 0x4 Make sure there is enough free space on the MC. Make sure a FLASH ATA card is inserted
in the MC card slot.
• 0x5 Controller could not open FROM***.IMG. Destination device might be broken.
• 0x6 Controller could not read FROM. FROM module or main board FROM might be broken.
• 0x7 Controller could not write data to FROM***.IMG. Destination device might be broken.
• 0x8 Controller could not close FROM***.IMG. The following are possible causes:
— There are already backup files on the destination device and they are write-protected.
— MC was removed during backup.
— Communication was disconnected during backup to TFTP server.
— TFTP server is not running.
• 0x9 Make sure there is enough free space on MC. Make sure FLASH ATA card is inserted to
MC card slot.
• 0xa Controller cannot open SRAM***.IMG. Destination device might be broken.
• 0xb Controller could not write data to SRAM***.IMG. Destination device might be broken.
• 0xc Controller could not close SRAM***.IMG. The following are possible causes:
— There are already backup files on the destination device and they are write-protected.
— MC was removed during backup.
— Communication was disconnected during backup to TFTP server.
— TFTP server is not running.
• 0xd File for internal use may be broken. Try the backup again.
• 0xe File for internal use may be broken. Try the backup again.
• 0xf After power was cycled by image backup function, a backup file was found on the MC. This
happens if power is turned off during automatic image backup. Retry backup from file screen
again.
• 0x20 Initialization of network failed. Confirm wiring and BOOTP server is running.
________________________________________________________________
SYST-230 WARN RCRON: Action successful
Cause: RCRON command was executed.
Remedy: This notification can be disabled by setting the system variable $RCRON.$POST_OK
to FALSE.
________________________________________________________________
SYST-231 WARN RCRON: Action failed
Cause: RCRON command could not be executed. This is caused by either an incorrect crontab file or
by the corresponding module not being loaded on the controller.
Remedy: Check md:crontab.dg for errors.
________________________________________________________________
SYST-232 WARN RCRON: Tick missed
Cause: RCRON was prevented from running on time.
Remedy: Too many RCRON jobs might be executing. Check md:crontab.dg and remove non-critical
entries.
________________________________________________________________
SYST-233 WARN RCRON: No response from MAIN
Cause: A job on the MAIN processor was not completed on time.
Remedy: Too many RCRON jobs might be executing on MAIN. Check md:crontab.dg and remove
non-critical entries.
________________________________________________________________
SYST-242 WARN Invalid RPS code
Cause: The RPS code is an invalid BCD in BCD mode.
Remedy: Check the status of RPS1, RPS2, … RPS128.
________________________________________________________________
SYST-243 WARN RPS failed(%s)
Cause: The program selection by RPS has failed.
Remedy: Refer the cause code. Typically, the program does not exist.
________________________________________________________________
SYST-244 WARN Auto mode is required
Cause: This operation requires Auto mode.
Remedy: Change the mode switch to Auto.
________________________________________________________________
SYST-245 WARN Local mode is required
Cause: This operation requires Local mode.
Remedy: Change the mode to Local.
________________________________________________________________
SYST-246 WARN Teach mode is required
Cause: This operation requires Teach mode.
Remedy: Change the mode switch to Teach mode.
________________________________________________________________
SYST-247 WARN Master ON is required
Cause: This operation requires a Master ON situation.
Remedy: Ensure that the Master ON situation exists.
________________________________________________________________
SYST-248 WARN Alarm condition
Cause: This operation requires no alarm situation.
Remedy: Clear the alarm situation.
________________________________________________________________
SYST-249 WARN No system ready input
Cause: This operation requires the System Ready input.
Remedy: Check the status of the System Ready input.
________________________________________________________________
SYST-250 WARN No robot ready input
Cause: This operation requires the Robot Ready input.
Remedy: Check the status of the Robot Ready input.
________________________________________________________________
SYST-251 WARN No teach plug ON input
Cause: This operation requires the Teach Plug ON input.
Remedy: Check the status of the Teach Plug ON input.
________________________________________________________________
SYST-252 WARN Teach plug ON input
Cause: This operation requires no Teach Plug ON input.
Remedy: Check the status of the Teach Plug ON input.
________________________________________________________________
SYST-253 WARN No safe stop input
Cause: This operation requires the Safe Stop input.
Remedy: Check the status of the Safe Stop input.
________________________________________________________________
SYST-254 WARN Safe stop input
Cause: This operation requires no Safe Stop input.
Remedy: Check the status of the Safe Stop input.
________________________________________________________________
SYST-255 WARN No Teach OK input
Cause: This operation requires the Teach OK input.
Remedy: Check the status of the Teach OK input.
________________________________________________________________
SYST-256 WARN Servo OFF input
Cause: This operation requires the Servo OFF input.
Remedy: Check the status of the Servo OFF input.
________________________________________________________________
SYST-257 WARN No Ext. Hold Relase input
Cause: This operation requires the External Hold Release input.
Remedy: Check the status of the External Hold Release input.
________________________________________________________________
SYST-258 WARN Operator panel hold
Cause: This operation requires that the HOLD/RUN switch on the Panel is set to RUN.
Remedy: Check the status of the HOLD/RUN switch on the Panel.
________________________________________________________________
SYST-259 WARN UI signals are disabled
Cause: This operation requires that UI signals are enabled.
Remedy: Check the setting of ‘Enable UI signals’ in the system config menu.
________________________________________________________________
SYST-266 WARN Please cycle power
Cause: Robot controller power must be cycled.
Remedy: Cycle power manually.
________________________________________________________________
SYST-267 WARN System is being initialized
Cause: System initialization is not finished.
Remedy: Wait a moment for system to be initialized.
________________________________________________________________
SYST-268 WARN Resume program(%s) execution
Cause: The program cannot be selected by PNSTROBE pulse signal while resume program is being
executed.
Remedy:
1. Do not input the PNSTROBE pulse signal while resume program is being executed. (
2. Input the PNSTROBE pulse signal after ending the resume program(program name) when you
input the PNSTROBE pulse signal.
________________________________________________________________
SYST-269 WARN FFR sequence(%s) execution
Cause: The program cannot be selected by the PNSTROBE pulse signal while fast fault recovery
sequence is being executed.
Remedy:
1. Do not input the PNSTROBE pulse signal while fast fault recovery sequence is being executed.
2. Input the PNSTROBE pulse signal after ending the FFR sequence(program name) when you
input the PNSTROBE pulse signal.