Fanuc PICK Alarm Codes

Home > Fanuc > Alarm Codes > PICK Alarm Codes

Fanuc PICK Alarm Codes

PICK-002 PAUSE GET_VAR failed %s
Cause: Data could not be obtained from the data source.
Remedy: Check the data source.
________________________________________________________________
PICK-003 PAUSE SET_VAR failed %s
Cause: Data could not be set in data source.
Remedy: Check the data source.
________________________________________________________________
PICK-004 WARN Data modification disallowed
Cause: The robot is in production. Setup data cannot be changed during production.
Remedy: Wait until production is aborted, and then make the changes.
________________________________________________________________
PICK-005 WARN No more groups installed
Cause: The user is attempting to change groups but there is only one installed group.
Remedy: None.
________________________________________________________________
PICK-006 WARN Robot Grp %s is already master
Cause: The user is attempting to set the master for more than one robot or robot group.
Remedy: The user should first set Master = FALSE for the robot for which Master is already set
to TRUE.
________________________________________________________________
PICK-007 WARN Robot not assigned to network
Cause: The Host Comm setup is not done for this robot. The robot hostname and IP address are
important for the part Queue manager to communicate with and between robots.
Remedy: From the Host Comm setup menu, assign a name and a valid IP address for this robot. Also,
enter the names and IP addresses of all the other robots on the network.
________________________________________________________________
PICK-008 WARN Error communicating with Robs
Cause: An error occurred while this robot tried to get data from another robot over the robot ring
or Ethernet.
Remedy: Check if all robots have a valid IP address and PickTool software. If ok, then document
the events that led to the error and provide information on the program and line number where this
error occurred to your FANUC Robotics technical representative.
________________________________________________________________
PICK-009 ABORT No robot is a master
Cause: No robot has been set as a master.
Remedy: Set one of the robots as master in the Setup menu. Also make sure that there is only
one master.
________________________________________________________________
PICK-010 ABORT More than 1 robot is a master
Cause: More than one robot has been set as master.
Remedy: Check the setup menus of all the robots and set only one of them as master.
________________________________________________________________
PICK-011 WARN Error reading LT boundary
Cause: An error occurred reading Line track boundary data.
Remedy: Check the line track setup menu and ensure that for the schedule you intend to use, and the
boundary set you intend to use, proper values exist. Also check the PK robot setup menu to see if you
have entered the proper values for the schedule and the boundary number.
________________________________________________________________
PICK-012 WARN Error reading LT enc scale
Cause: An error occurred reading the Line tracking encoder scale.
Remedy: Check the line track setup menu and ensure that for the schedule you intend to use, a proper
value for encoder scale exists. If not, teach it. Also check the PK robot setup menu to see if you
entered the proper line track schedule number.
________________________________________________________________
PICK-013 WARN Max num of robots exceeded
Cause: The maximum number of robots that Picktool can handle has been exceeded.
Remedy: PickTool can handle a maximum of 10 robot groups. Reduce the number of groups or
robots to less than 10.
________________________________________________________________
PICK-014 WARN Error getting rob data %s
Cause: An error occurred while reading data from robot ROBOT_NAME in the robot ring.
Remedy: Look at the cause code with the error. Make sure that Ethernet is set up correctly with all
the robots. Check the Host Comm menu on each robot and make sure that all members are listed on
each controller. Make sure ROSIPCFG.XML in FRS: refers to all members in the Host Comm menu.
________________________________________________________________
PICK-015 WARN Move-TO could not execute
Cause: An error was encountered while trying to move to a taught position. It could be due to a
motion limit error or an incorrectly taught point.
Remedy: Make sure to record the position correctly. Check the associated cause code if available.
________________________________________________________________
PICK-016 WARN Frame must be taught!
Cause: Without completing frame teaching of all 3 positions, you cannot proceed to the next step.
Remedy: Teach the frame positions correctly.
________________________________________________________________
PICK-017 WARN MOVE TO done
Cause: The robot completed a move-to operation.
Remedy: None.
________________________________________________________________
PICK-018 WARN Position has not been taught
Cause: The position has not been taught yet.
Remedy: The position must be taught.
________________________________________________________________
PICK-019 PAUSE Position is not reachable
Cause: The position the robot is trying to move to is not reachable.
Remedy: Verify that the value of $UTOOL and/or $MNUTOOL are correct
________________________________________________________________
PICK-020 WARN Invalid Conveyor DO[]
Cause: The DOUT port number specified for the conveyor is invalid.
Remedy: Check if the I/O point is configured correctly.
________________________________________________________________
PICK-021 WARN The ID # of the robot unknown.
Cause: The ID# of the robot could not be determined.
Remedy: Check the PK Robot setup menu and make sure the ID exists, and is unique amongst
the set of robots.
________________________________________________________________
PICK-022 ABORT Total util of all robots < 100
Cause: The utilization percent for each robot does not add up to 100 percent. This prevents load
balancing from working properly.
Remedy: In the PK Robot menu of each robot, specify percent utilization so that they add up to 100.