Fanuc FXTL Alarm Codes

Home > Fanuc > Alarm Codes > FXTL Alarm Codes

Fanuc FXTL Alarm Codes

FXTL-001 WARN File parsing error
Cause: A file parsing error has occurred. An error exists in one of the model files.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-002 WARN Not enough values on line
Cause: Not enough values on line. There are not enough values on a line in one of the model files.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-003 WARN Numeric conversion error
Cause: A numeric conversion error has occurred. A value on a line in a model file is not a valid
numeric value.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-004 WARN Output buffer too small
Cause: The output buffer is too small. A file output line exceeds the size of the buffer.
Remedy: Document the events that led to the error, and contact your FANUC technical representative.
________________________________________________________________
FXTL-005 WARN Internal library error
Cause: An unexpected internal library error has occurred.
Remedy: Document the events that led to the error, and contact your FANUC technical representative.
________________________________________________________________
FXTL-006 WARN Invalid unit number
Cause: An invalid unit number was specified in a command or within a model file.
Remedy: Specify a unit number that is valid for the particular tray.
________________________________________________________________
FXTL-007 WARN Invalid CPU number
Cause: An invalid CPU number was specified in the mapping assignment.
Remedy: Specify a CPU number that is valid for this controller configuration. The range is 0 – 2,
depending on the hardware.
________________________________________________________________
FXTL-008 WARN Invalid motion group
Cause: Invalid motion group. An invalid motion group was specified in the mapping assignment.
Remedy: Specify a motion group that is valid for this controller configuration. The range is 1 – 6,
depending on the hardware.
________________________________________________________________
FXTL-009 WARN Loop number out of range
Cause: Loop number out of range. A LOOP number in a model program is out of range.
Remedy: Correct the model file and copy it to the controller. A valid loop number range is 1 – 20.
________________________________________________________________
FXTL-010 WARN Too many sensor offsets
Cause: There are too many offsets or no offsets specified on a SENSOR_READ line.
Remedy: Correct the model file and copy it to the controller. The maximum number of offsets is 20.
________________________________________________________________
FXTL-011 WARN Maximum payload exceeded
Cause: A payload was specified that exceeds the maximum for the particular unit.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-012 WARN Invalid sensor slot
Cause: An invalid sensor slot was specified in an OFFSET line in a model file.
Remedy: Correct the model file and copy it to the controller. Slot numbers must be in the range
of 1 – 20.
________________________________________________________________
FXTL-013 WARN Invalid model name
Cause: An invalid model name was specified in a MODEL line in a model file.
Remedy: Correct the model file and copy it to the controller. Model names can be up to 18 characters
long.
________________________________________________________________
FXTL-014 WARN Invalid model number
Cause: An invalid model number was specified in a MODEL_NUM line in a model file.
Remedy: Correct the model file and copy it to the controller. Model numbers must be in the range
of 1 – 99.
________________________________________________________________
FXTL-015 WARN No index file: T%d
Cause: A NEWMODEL.PTS file was not found in the tray’s root directory or could not be opened.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-016 WARN Invalid index file: T%d
Cause: An invalid index file exists: T%d. An entry in the NEWMODEL.PTS file could not be
processed.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-017 WARN Memory allocation error
Cause: Memory for the tray data structures could not be allocated.
Remedy: Document the events that led to the error, and contact your FANUC technical representative.
________________________________________________________________
FXTL-018 WARN File open error
Cause: A file specified in the NEWMODEL.PTS file could not be found and/or opened.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-019 WARN No cell data file: T%d
Cause: No cell data file exists: T%d. A cell data file was not found in the tray’s root directory or
could not be opened.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-020 WARN No model program file: T%d
Cause: No model program file exists: T%d. A model program file that was specified in the
NEWMODEL.PTS file was not found in the tray’s root directory or could not be opened.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-021 WARN Invalid model file set
Cause: There was an error during processing the set of model files for the tray.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-022 WARN Invalid positioner variant
Cause: An invalid mechanical unit type was specified in a command or within a model file.
Remedy: Specify a supported variant type.
________________________________________________________________
FXTL-023 WARN Error in cell data file: T%d
Cause: An error was found in the cell data file for the tray.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-024 WARN Invalid keyword in file
Cause: An unrecognized keyword was found when reading one of the model files.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-025 WARN No unit mapping file: T%d
Cause: The unit cpu/group mapping file was not found in the tray’s root directory or could not
be opened.
Remedy: Correct or create the file.
________________________________________________________________
FXTL-026 WARN Invalid unit mapping file: T%d
Cause: The unit cpu/group mapping file contains incorrect entries and could not be opened.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-027 WARN Wrong number of units in prog
Cause: A model program has the wrong number of units vs. the number specified in the cell data file.
Remedy: Correct the model file and copy it to the controller.
________________________________________________________________
FXTL-028 WARN Error in program file: T%d
Cause: A model program file has incorrect or invalid lines and could not be processed.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-029 WARN Invalid model assignment: T%d
Cause: Model numbers must all be specified or all set to the defaults.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-030 WARN Duplicate model numbers: T%d
Cause: More than one model program has the same model number specified.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-031 WARN Missing MOVE subkeys
Cause: A POSITIONER_MOVE statement was not followed by any move command subkeys.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-032 WARN Duplicate BUILD_BEGIN or END
Cause: More than one BUILD_BEGIN or BUILD_END line was found in a model file.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-033 WARN Duplicate LOOP number
Cause: More than one LOOP_BEGIN/END statement specifies the same loop number.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-034 WARN Invalid POSITIONER_MOVE subkey
Cause: A subkey following a POSITIONER_MOVE is invalid or in the wrong place.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-035 WARN Unmatched BUILD_BEGIN or loop
Cause: A BUILD_BEGIN did not have a BUILD_END, a LOOP_BEGIN did not have a
LOOP_END, or there was some other error in matching looping statements.
Remedy: Correct the model files and copy them to the controller.
________________________________________________________________
FXTL-036 WARN Error writing model file: T%d
Cause: An error occurred while creating or writing a new version of one of the model files.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-037 WARN Tray has unmapped units: T%d
Cause: The tray has one or more units that have not been mapped to a CPU and motion group.
Remedy: Assign or correct the unit mappings and restart.
________________________________________________________________
FXTL-038 WARN Tray has mapping conflict: T%d
Cause: The tray has one or more units that are mapped to the same CPU and the motion group as
another unit on the controller.
Remedy: Assign or correct the unit mappings, and restart.
________________________________________________________________
FXTL-039 WARN Unit not mapped: T%d U%d
Cause: The specified unit has not been mapped to a CPU and motion group.
Remedy: Assign or correct the unit mappings and restart.
________________________________________________________________
FXTL-040 WARN Map conflict: T%d U%d, T%d U%d
Cause: The specified units have the same CPU and group mapping.
Remedy: Assign or correct the unit mappings and restart.
________________________________________________________________
FXTL-041 WARN Unit mapping error(s)
Cause: There were errors in the assignment of positioners to specific CPUs and motion groups. The
specified units have the same CPU and group mapping.
Remedy: Check the error log for more specific details, then assign or correct the unit mappings
and restart.
________________________________________________________________
FXTL-042 WARN Tray verification failed: T%d
Cause: Verification of the tray model files failed due to an error in the files or in the system
configuration.
Remedy: Check the error log for more specific details, then make the required corrections.
________________________________________________________________
FXTL-043 WARN Prog conversion process error
Cause: An error occurred in the process of converting the model programs to their internal TPP form.
Remedy: Check the error log for the specific details.
________________________________________________________________
FXTL-044 WARN Variant type mismatch: T%d U%d
Cause: The mechanical variant type specified in the cell data does not match the actual positioner for
the specified tray and unit.
Remedy: Correct the model files or the physical unit configuration.
________________________________________________________________
FXTL-045 WARN Tray has variant mismatch
Cause: The tray has one or more mismatches of mechanical variants specified in the cell data file
vs. the actual configuration.
Remedy: Check the error log for more specific details, then make the required corrections.
________________________________________________________________
FXTL-046 WARN Error writing TPP file
Cause: An error occurred while creating or writing a new TPP file for a model program for a
particular unit.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-047 WARN Invalid tray number
Cause: An invalid unit number was specified in a command.
Remedy: Specify a tray number that is valid for the particular configuration. The valid range is 1 – 2.
________________________________________________________________
FXTL-048 WARN Invalid program number: T%d P%d
Cause: An invalid program number was specified in a command or by the PLC.
Remedy: Specify a program number that is valid for the configuration.
________________________________________________________________
FXTL-049 WARN Program conversion err: T%d P%d
Cause: An error occurred while converting the model program to the internal TPP format.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-050 WARN No CPU RIPE communications
Cause: No CPU RIPE communications exist. There are no internal network communication
connections with one or more of the CPU boards in the controller cabinet.
Remedy: Verify that the internal network connections and the Ethernet switch are correctly connected
and powered on. Turn off the controller and then turn it on again.
________________________________________________________________
FXTL-051 WARN Program conversion timed out
Cause: Program conversion timed out. A request to convert a model program to a TP program has
taken too long to complete.
Remedy: Turn off the controller and then turn it on again. If the problem persists, document the
events that led to the error and contact your FANUC Representative.
________________________________________________________________
FXTL-052 WARN Program file transfer failed
Cause: A TP program converted from a model program failed to be copied to its destination location.
Remedy: Check the error log and listing for more details about the specific error.
________________________________________________________________
FXTL-054 WARN Invalid move command
Cause: The model move command has specified a program or step number that does not exist.
Remedy: Correct the command data or the model program files and retry the operation.
________________________________________________________________
FXTL-055 WARN Not all units enabled
Cause: One or more units on the tray that are required for the model move are not enabled.
Remedy: Enable all units and retry the operation.
________________________________________________________________
FXTL-056 WARN Tray not in valid state
Cause: The tray is not in a valid position in order to do a legal model step move.
Remedy: Check the positions of the units. Use the model move OVERRIDE option if the move can
be safely performed.
________________________________________________________________
FXTL-057 WARN Move command out of sequence
Cause: The requested model move is out of sequence according to the model program.
Remedy: Correct the command data or use the OVERRIDE option to force the move.
________________________________________________________________
FXTL-058 WARN Move command rejected: T%d
Cause: The requested model move has been rejected. The move was not initiated.
Remedy: Check the error log for more details on the exact cause.
________________________________________________________________
FXTL-059 WARN Tray is busy
Cause: The command is rejected because the tray or one or units on the tray are busy completing a
previous operation that cannot be interrupted.
Remedy: Wait for the tray to finish the previous operation, and retry the operation again.
________________________________________________________________
FXTL-060 WARN Not all units verified
Cause: One or more units on the tray that are required for the model move do not have the proper
programs loaded and verified.
Remedy: Initiate a full initialization or data verification for the tray.
________________________________________________________________
FXTL-061 WARN Tray is in AUTO mode
Cause: The PLC interface has put the tray into AUTO mode and the requested operation can not be
executed.
Remedy: Use the PLC to put the tray into MANUAL mode, and retry the operation.
________________________________________________________________
FXTL-062 WARN PLC CR not cleared: T%d
Cause: The PLC did not clear the CR bit within the allowable time after the controller accepted the
command.
Remedy: Check and correct the PLC program.
________________________________________________________________
FXTL-063 WARN Invalid axis number
Cause: An invalid axis number was specified in a command.
Remedy: Specify an axis number that is valid for the particular positioner.
________________________________________________________________
FXTL-064 WARN Unit is bypassed
Cause: The specified positioner has been disabled or bypassed.
Remedy: Undo the bypass or change the unit number.
________________________________________________________________
FXTL-065 WARN Tray %d in HOLD state
Cause: The tray is in a HOLD state because the PLC NOHLD bit is OFF.
Remedy: Clear the HOLD condition from the PLC, and retry.
________________________________________________________________
FXTL-066 WARN Invalid group number
Cause: An invalid positioner group number was specified in a GROUP statement.
Remedy: Specify a valid group number in the range from 1 – 20.
________________________________________________________________
FXTL-067 WARN Duplicate group number
Cause: A duplicate positioner group number was specified in a GROUP statement.
Remedy: Edit the file so that each GROUP specifies a unique number in the range from 1 – 20.
________________________________________________________________
FXTL-068 WARN Invalid PLC command: T%d
Cause: The PLC sent a command that is invalid or not supported.
Remedy: Correct the PLC logic to send only valid command codes.
________________________________________________________________
FXTL-069 WARN Invalid PLC data value: T%d
Cause: A data value sent by the PLC is not valid, such as the unit number, program number, or
step number.
Remedy: Correct the PLC logic to send only valid command values.
________________________________________________________________
FXTL-070 WARN Tray %d ESR not possible
Cause: Error state recovery is not possible for this tray at this time. The previous commanded
state cannot be determined.
Remedy: Put the tray into a valid state by using the model move override feature, and proceed
from there.
________________________________________________________________
FXTL-071 WARN Invalid I/O configuration
Cause: There is an invalid value assigned for the rack and/or slot number for the fieldbus I/O device
for the tray.
Remedy: Assign the correct rack and slot for the fieldbus interface that is actually installed and
configured on the controller.
________________________________________________________________
FXTL-072 WARN Invalid program step number
Cause: An invalid program step number was specified. The step number is out of range or is not a
valid step for the specified operation.
Remedy: Use the correct step number for the specified program.
________________________________________________________________
FXTL-073 WARN Error %s line %d
Cause: A model file processing error occurred in the file as shown at the specified line number.
Remedy: Check the other entries in the alarm log for the type of error that was detected, then correct
the file, copy it to the model file directory, and retry the operation.
________________________________________________________________
FXTL-074 WARN Step number sequence error
Cause: A step number in the model file is out of sequence. Steps must be numbered sequentially with
no missing numbers.
Remedy: Correct the model file by fixing or renumbering the cell step lines.
________________________________________________________________
FXTL-075 WARN Invalid program number
Cause: An invalid program number was specified.
Remedy: Specify a program number that is valid for the configuration.
________________________________________________________________
FXTL-076 WARN Shim value out of range
Cause: A shim was calculated or specified that is out of range of the limits specified for this unit.
Remedy: Specify a smaller shim value, change the limits in the celldata.pts file, or use the TEACH
function to change the nominal position value for this step.
________________________________________________________________
FXTL-151 WARN Press Shift Key.
Cause: The shift key is not pressed
Remedy: Press the shift key.
________________________________________________________________
FXTL-152 WARN No Unit Assigned.
Cause: No unit has been assigned.
Remedy: Use this menu to map a unit number with a physical unit.
________________________________________________________________
FXTL-153 WARN Unit(%d) Invaild Mapping.
Cause: The unit has invalid mapping.
Remedy: Check the hardware to make sure the mapping is correct.
________________________________________________________________
FXTL-154 WARN No Tray is Defined.
Cause: No tray has been defined.
Remedy: Perform a data verify first.
________________________________________________________________
FXTL-155 WARN Invalid Step number.
Cause: The Step number is not valid.
Remedy: Perform a data verify first, then select the valid step number.
________________________________________________________________
FXTL-156 WARN Program is Undefined.
Cause: Not all units are in the correct position for a model move. The Tray cannot determine which
program it is in.
Remedy: Go to the model move menu and move the tray to a model move position.
________________________________________________________________
FXTL-157 WARN Cannot Copy File to Same Dev
Cause: You cannot copy a file back to its device.
Remedy: Select a different device for the file copy operation.
________________________________________________________________
FXTL-158 WARN No unit in the Tray.
Cause: No unit in the Tray. No unit is defined for the tray.
Remedy: Check the unit mapping and Unit enable menu. Then check the celldata.pts and do a
data verify.
________________________________________________________________
FXTL-159 WARN Program has no step.
Cause: The program has no motion step.
Remedy: Check the model file offline and copy the file to the controller. Then do a data verify.
________________________________________________________________
FXTL-201 WARN Inverse Kinematic Error.
Cause: The calibrated inverse kinematics does not converge to a solution.
Remedy: The unit is close or at a singular position. Correct the position and then continue.
________________________________________________________________
FXTL-202 WARN Invalid wrist type.
Cause: The wrist type is not supported.
Remedy: Turn off/on the controller to get correct wrist type.
________________________________________________________________
FXTL-204 WARN Invalid program name.
Cause: The program is not in the model program list.
Remedy: Make sure to do a data verify before running the program.
________________________________________________________________
FXTL-205 WARN Invalid TP position type.
Cause: The teach pendant program has an invalid position data type.
Remedy: Make sure to do a data verify before running the program.
________________________________________________________________
FXTL-206 WARN Singular position.
Cause: The robot is close to a singularity point where there is no solution for the inverse kinematics.
Remedy: Jog the unit away from singular position and continue the operation.
________________________________________________________________
FXTL-207 WARN Invalid TOOL vector.
Cause: Invalid TOOL vector exists.
Remedy: Make sure the tool vector is defined.