Fanuc MEMO Alarm Codes

Home > Fanuc > Alarm Codes > MEMO Alarm Codes

Fanuc MEMO Alarm Codes

MEMO-002 WARN Specified program is in use
Cause: The specified program is being edited or executing.
Remedy: Abort the specified program. Or select it again after selecting another program.
________________________________________________________________
MEMO-003 WARN Specified program is in use
Cause: The specified program is being edit or executing.
Remedy: Abort the specified program. Or select it once more after selecting another program.
________________________________________________________________
MEMO-004 WARN Specified program is in use
Cause: The specified program is being edited or executing.
Remedy: Abort the specified program. Or select it once more after selecting another program.
________________________________________________________________
MEMO-006 WARN Protection error occurred
Cause: The specified program is protected by user.
Remedy: Cancel the protection of the specified program.
________________________________________________________________
MEMO-007 WARN Invalid break number
Cause: The specified break number does not exist.
Remedy: Specify the correct break number.
________________________________________________________________
MEMO-008 WARN Specified line no. not exist
Cause: The specified line number does not exist in the specified or default program.
Remedy: Specify a correct line number.
________________________________________________________________
MEMO-010 WARN Program name error
Cause: The specified program name is different form that of the P-code file.
Remedy: Specify the same program name.
________________________________________________________________
MEMO-013 WARN Program type is different
Cause: The specified program type is different from that of the object being processed.
Remedy: Specify the same program type.
________________________________________________________________
MEMO-014 WARN Specified label already exists
Cause: The specified label id already exists in the program.
Remedy: Specify another label number.
________________________________________________________________
MEMO-015 WARN Program already exists
Cause: The specified program already exists in the system.
Remedy: Specify another program name. Or delete the registered program.
________________________________________________________________
MEMO-019 WARN Too many programs
Cause: The number of the programs and routines exceeded the maximum possible number ( 3200 ).
Remedy: Delete unnecessary programs or routines.
________________________________________________________________
MEMO-025 WARN Label does not exist
Cause: Specified label does not exist.
Remedy: Set the index to an existing label.
________________________________________________________________
MEMO-026 WARN Line data is full
Cause: The number of line data exceeded the maximum possible line number ( 65535 ).
Remedy: Delete unnecessary line data.
________________________________________________________________
MEMO-027 WARN Specified line does not exist
Cause: The specified line data does not exist.
Remedy: Specify another line number.
________________________________________________________________
MEMO-029 WARN The line data can’t be changed
Cause: The specified line data can’t be changed. The size of modified data is different from that of
original data when replacing it.
Remedy: Specify another line number or the data of same size.
________________________________________________________________
MEMO-032 WARN Specified program is in use
Cause: The specified program is being edited or executing.
Remedy: Abort the specified program. Or select it once more after selecting another program.
________________________________________________________________
MEMO-034 WARN The item can’t be changed
Cause: The specified item is locked to change by system.
Remedy: Specify another item.
________________________________________________________________
MEMO-038 WARN Too many programs
Cause: The number of the programs exceeded the maximum number.
Remedy: Delete unnecessary programs.
________________________________________________________________
MEMO-048 WARN Break point data doesn’t exist
Cause: The specified break point data does not exist.
Remedy: Specify another break point.
________________________________________________________________
MEMO-050 WARN Program does not exist
Cause: The specified program does not exist in the system.
Remedy: Specify another program or create the same program first.
________________________________________________________________
MEMO-056 WARN Program does not exist
Cause: The specified program does not exist in the system.
Remedy: Specify another program or create the same program first.
________________________________________________________________
MEMO-061 WARN No write access
Cause: The program must be opened with write access before attempting write operations
Remedy: Open the program with write access before writing.
________________________________________________________________
MEMO-065 WARN Too many opened programs
Cause: Too many CALL instructions is used. The number of opened programs exceeded the
maximum possible number( 100 ).
Remedy: Abort the unnecessary programs. Or, remove unnecessary CALL instructions.
________________________________________________________________
MEMO-068 WARN Specified program is in use
Cause: 1. The specified program is editing or executing. 2. The specified program is entried
to MACRO
Remedy: 1. Abort the specified program. Or select it once more after select another program. 2.
Remove the program form the MACRO entry.
________________________________________________________________
MEMO-071 WARN Position does not exist
Cause: The specified position data does not exist.
Remedy: Specify another position.
________________________________________________________________
MEMO-072 WARN Position data already exists
Cause: Position data already exists in the specified position you want to move.
Remedy: Specify another position. Or, delete the data in the specified position.
________________________________________________________________
MEMO-073 WARN Program does not exist
Cause: The specified program does not exist in the system.
Remedy: Specify another program or create the same program first.
________________________________________________________________
MEMO-074 WARN Program type is not TPE
Cause: The operation can be apply only to TPE programs.
Remedy: Select a TPE program.
________________________________________________________________
MEMO-075 WARN Program can’t be used
Cause: The program must be opened before attempting read or write operations.
Remedy: Open the program before reading or writing.
________________________________________________________________
MEMO-078 WARN Program can’t be used
Cause: The specified operation is not supported for this program type.
Remedy: Specify a program whose program type matches the operation.
________________________________________________________________
MEMO-080 WARN Protection error occurred
Cause: The specified program is protected by user.
Remedy: Cancel the protection of the specified program.
________________________________________________________________
MEMO-081 WARN Specified program is in use
Cause: The specified program is editing or executing.
Remedy: Abort the specified program. Or select it once more after select another program.
________________________________________________________________
MEMO-088 WARN Program does not exist
Cause: The specified position data does not exist.
Remedy: Specify another position.
________________________________________________________________
MEMO-093 WARN Specified program is in use
Cause: The specified program is editing or executing.
Remedy: Abort the specified program. Or select it once more after select another program.
________________________________________________________________
MEMO-094 WARN Parameters are different
Cause: A routine exists in memory with a different parameter definition than the routine in the
PC file being loaded.
Remedy: Update the calling convention in the KAREL program being loaded or delete the obsolete
routine from system memory.
________________________________________________________________
MEMO-098 WARN EOF occurs in file access
Cause: EOF occurs in file access. When P-code file was scaned, EOF occurs.
Remedy: The P-code data may be broken. Translate the specified KAREL program again. Then
reload the P-code.
________________________________________________________________
MEMO-099 WARN Program name is wrong
Cause: The program name length is different from that of the P-code data.
Remedy: Check the program name of the specified program.
________________________________________________________________
MEMO-103 WARN Check sum error occurred
Cause: The specified data was broken. This is the internal error.
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.
________________________________________________________________
MEMO-104 WARN Program already exists
Cause: The specified program already exists in the system.
Remedy: Specify another program name. Or delete the registered program.
________________________________________________________________
MEMO-112 WARN Break data already exists
Cause: The specified break point data already exists in the program.
Remedy: Specify another break point.
________________________________________________________________
MEMO-113 WARN File access error
Cause: The port that has the program you want to load is not connected.
Remedy: Check the port setting and the connected device.
________________________________________________________________
MEMO-114 WARN Break point can’t be removed
Cause: The break point data can not be overwriten. The program is protected by user or executing.
Remedy: Cancel the protection of the program. Or, abort the program.
________________________________________________________________
MEMO-115 WARN Break point can’t be removed
Cause: The break point data can not be removed. The program is protected by user or executing.
Remedy: Cancel the protection of the program. Or, abort the program.
________________________________________________________________
MEMO-119 WARN Application data doesn’t exist
Cause: The specified application data does not exist because the program does not correspond
to the specified application.
Remedy: Specify another application data. Then create the program in the current system.
________________________________________________________________
MEMO-120 WARN Application data doesn’t exist
Cause: The specified application data does not exist because the program does not correspond
to the specified application.
Remedy: Specify another application data. Create the program in the current system again.
________________________________________________________________
MEMO-123 WARN Application data doesn’t exist
Cause: The specified application data does not exist because the program does not correspond
to the specified application.
Remedy: Specify another application data. Create the program in the current system again.
________________________________________________________________
MEMO-124 WARN Program version is too new
Cause: KAREL program version number is newer than that of the system.
Remedy: Translate the program with an older version of the Translator.
________________________________________________________________
MEMO-125 WARN Program version is too old
Cause: KAREL program version number is older than that of the system.
Remedy: Translate the program with a newer version of the Translator.
________________________________________________________________
MEMO-126 WARN No more available memory
Cause: Lack of the memory which can be used.
Remedy: Delete unnecessary programs.
________________________________________________________________
MEMO-127 WARN Pos reference over 255 times
Cause: Reference of the same position exceeded the maximum count (256).
Remedy: Set new position ID for the referenced position.
________________________________________________________________
MEMO-128 WARN %s parameters are different
Cause: A routine exists in memory with a different parameter definition than the routine in the
PC file being loaded.
Remedy: Update the calling convention in the KAREL program being loaded or delete the obsolete
routine from system memory.
________________________________________________________________
MEMO-130 SYST Please power up again
Cause: The data of the system been broken.
Remedy: Please power up again.
________________________________________________________________
MEMO-131 SYST Please power up again
Cause: System data in CMOS has been broken..
Remedy: Turn power off and then back on.
________________________________________________________________
MEMO-132 WARN %s has been broken
Cause: Program data has been broken at the power fail recover.
Remedy: Delete the program and create it again. Press the RESET key to clear the error. If the error
is not cleared, document the events that led to the error and call your FANUC Robotics technical
representative.
________________________________________________________________
MEMO-133 SYST Please power up again
Cause: System data in CMOS has been broken..
Remedy: Turn power off and then back on.
________________________________________________________________
MEMO-134 WARN TPE program %s already exists
Cause: The TPE program which has the same name already exists.
Remedy: Delete the teach pendant (TP) program. Then load the specified KAREL program again.
________________________________________________________________
MEMO-135 WARN Cannot create TPE program here
Cause: The TPE program cannot be created in this start mode.
Remedy: Select the function menu to change the start mode.
________________________________________________________________
MEMO-136 WARN Cannot load P-code here
Cause: The KAREL program cannot be loaded in this start mode.
Remedy: Select the function menu to change the start mode.
________________________________________________________________
MEMO-137 WARN Load at Control Start Only
Cause: Specified KAREL program cannot be loaded in this mode. Because the same name program
has already been loaded at controlled start.
Remedy: Load the program at controlled start.
________________________________________________________________
MEMO-138 WARN Delete at Control Start Only
Cause: Specified program has already been loaded at controlled start. Because of this, you can only
delete the program at controlled start.
Remedy: Delete the program at controlled start.
________________________________________________________________
MEMO-144 WARN Header size too big
Cause: The TPE header size specified is too big. Must be less than 256.
Remedy: Change size to range of 1-256. If necessary, use multiple header records.
________________________________________________________________
MEMO-145 WARN TPE cannot have KAREL routine
Cause: The routine of the specified program has been already referred by the KAREL program.
Because of this, the specified program must be the KAREL program. The user cannot use the
specified program name as a TPE program.
Remedy: Change the program name, or delete the KAREL program which refers the routine of
the specified program.
________________________________________________________________
MEMO-146 WARN Invalid variable is used
Cause: Invalid variable is used in the specified KAREL program.
Remedy: Check the varialbe used in the specified KAREL program.
________________________________________________________________
MEMO-147 WARN Flash File access error(write)
Cause: The write access to the Flash File(F-ROM) failed. Some program may be lost.
Remedy: The Flash File(F-ROM) may be broken. Create or load the lost program again.
________________________________________________________________
MEMO-148 WARN Flash File access error(read)
Cause: The read access to the Flash File(F-ROM) failed. Some program may be lost.
Remedy: The Flash File(F-ROM) may be broken. Create or load the lost program again.
________________________________________________________________
MEMO-149 WARN Specified program is broken
Cause: Program data has been broken.
Remedy: Please power off and on. Then check the program data of the specified program.
________________________________________________________________
MEMO-151 WARN No more available memory(TEMP)
Cause: Lack of the temporary memory which can be used for the program.
Remedy: Delete unnecessary programs. Or, change the D-RAM module to the bigger one.
________________________________________________________________
MEMO-152 WARN Program %s is in use
Cause: The specified program is being edited or is executing.
Remedy: Perform one of the following:
• Abort the specified program or disable the teach pendant and press F3, CONTINUE
• Press F4, SKIP to skip over this file.
________________________________________________________________
MEMO-153 WARN %s is not deleted
Cause: The unused program can not be deleted.
Remedy: Cycle power and try the operation again.
________________________________________________________________
MEMO-154 WARN Parent program still exists
Cause: When the parent program exists, the daughter program cannot be deleted.
Remedy: Delete the parent program before deleting the daughter program.
________________________________________________________________
MEMO-155 WARN Too many positions
Cause: The total number of positions exceeds the maximum number(32766).
Remedy: Delete the unused positions.
________________________________________________________________
MEMO-156 WARN Renumber program failed
Cause: The renumber operation failed.
Remedy: Cycle power and try the operation again.
________________________________________________________________
MEMO-157 WARN Cannot execute this program
Cause: The specified program is broken.
Remedy: Delete the program and create it again. Press RESET to clear the error. If the error is
not cleared, document the events that led to the error and call your FANUC Robotics technical
representative.
________________________________________________________________
MEMO-158 WARN Type converted in %s
Cause: When loading the specified KAREL program the variable type definition required conversion.
The program was loaded and converted as needed.
Remedy: If conversion was expected, then no action is required. If conversion was not expected,
then maybe the loaded program was not the version of the program that was needed. Check for other
versions of this program and load them as needed.
________________________________________________________________
MEMO-159 WARN Convert failed in %s
Cause: When loading the specified KAREL program the variable type definition required conversion.
The variable reference could not be converted. Therefore, the program was not loaded as needed.
Remedy: See the diagnostic data file, FR:KRLCONV.LS, for more information about the specific
variable and program involved. Translate this program using a version of the translator that matches
the version of the controller. Then try to load the program again.
________________________________________________________________
MEMO-160 WARN Save failed for %s
Cause: When loading a KAREL program or dictionary, a backup copy could not be made to the
specified file. The program or dictionary was loaded into memory.
Remedy: Check that there is space available on the specified device. If not, remove some unneeded
files. Check the cause message for this alarm. It will provide the specific reason that the copy could
not complete.
________________________________________________________________
MEMO-161 WARN Converting KAREL program %s to version %s
Cause: When loading the specified KAREL program the variable type definition required conversion
to the specified version.
Remedy: If conversion was expected then no action is required. If conversion was not expected,
then maybe the loaded program was not the version of the program that was needed. Check for other
versions of this program and load them as needed.
________________________________________________________________
MEMO-162 WARN Line: %d Local variable mismatch not handled
Cause: The type definition for a local variable in a KAREL routine already exists but is of a different
type than what you are attempting to load.
Remedy: Translate this program using a version of the translator that matches the version of the
controller. Then try to load the program again.
________________________________________________________________
MEMO-163 WARN Line: %d Field mismatch not handled
Cause: The type definition for a field in a structure already exists but is of a different type than what
you are attempting to load.
Remedy: Translate this program using a version of the translator that matches the version of the
controller. Then try to load the program again.
________________________________________________________________
MEMO-164 WARN Line: %d Structure mismatch not handled
Cause: The type definition for a structure in a KAREL program already exists but is of a different
type than what you are attempting to load.
Remedy: Translate this program using a version of the translator that matches the version of the
controller. Then try to load the program again.
________________________________________________________________
MEMO-165 WARN Line: %d First field is different
Cause: The type definition for a structure in a KAREL program already exists but the first field is
different than what you are attempting to load.
Remedy: Translate this program using a version of the translator that matches the version of the
controller. Then try to load the program again.
________________________________________________________________
MEMO-166 WARN Path conversion failed
Cause: The type definition for a PATH in a KAREL program already exists but is of a different type
than what you are attempting to load.
Remedy: Translate this program using a version of the translator that matches the version of the
controller. Then try to load the program again.
________________________________________________________________
MEMO-167 WARN Restore failed for %s
Cause: Restore of a program failed. See error cause code for details.
Remedy: Consult cause code for more information.
________________________________________________________________
MEMO-168 WARN Backup failed for %s
Cause: A file backup was attempted uses the PROG_BACKUP() builtin. This specific program
failed to backup because of the reason specified in the cause code.
Remedy: Refer to the remedy on the cause code.
________________________________________________________________
MEMO-169 WARN Clear failed for %s
Cause: The program that you attempted to clear with the PROG_CLEAR builtin failed.
Remedy: Refer to the remedy on the cause code. Typically the cause of the error is that the program
is selected. In this case, unselect the program via the SELECT_TPE builtin before executing the
PROG_CLEAR builtin.