Fanuc RIPE Alarm Codes

Home > Fanuc > Alarm Codes > RIPE Alarm Codes

Fanuc RIPE Alarm Codes

RIPE-001 WARN Time is resynchronized
Cause: System network timing has been lost. The system has automatically been reestablished.
Remedy: If this continues to happen, the physical Network wiring configuration and setup should be
checked for errors. Usually this is just a result of a re-power of one of the controllers.
________________________________________________________________
RIPE-002 WARN FRS:ROSIPCFG.XML not found
Cause: System network timing has been lost but the system has automatically reestablished timing.
Remedy: If this continues to happen, the configuration and setup should be checked for errors.
________________________________________________________________
RIPE-003 WARN FRS:ROSIPCFG.XML has %d warnings
Cause: The syntax of ROSIPCFG.XML is not correct.
Remedy: Consult TD:RIPINIT.TXT for detailed warnings and correct them.
________________________________________________________________
RIPE-004 WARN Tracking error
Cause: An internal error has occurred.
Remedy: Document the events that led to the error, and call your FANUC Robotics technical
representative.
________________________________________________________________
RIPE-006 WARN Bad destination CPU ID
Cause: An internal error has occurred.
Remedy: Document the events that led to the error, and call your FANUC Robotics technical
representative.
________________________________________________________________
RIPE-007 WARN %s is offline
Cause: This is a notification that a robot has gone offline. This is posted whenever a member robot
is turned off or unplugged.
Remedy: None
________________________________________________________________
RIPE-008 WARN %s is online
Cause: This is a notification that a robot has gone offline. This is posted whenever a member robot
is turned on or plugged in.
Remedy: None
________________________________________________________________
RIPE-009 WARN Member data is updated
Cause: Information about a member is updated. This is only posted in a system which is not
automatically synchronized.
Remedy: None
________________________________________________________________
RIPE-010 WARN %s has been reset
Cause: The indicated robot has had its protocol reset. This might be the cause of some other error.
Remedy: None
________________________________________________________________
RIPE-011 WARN This robot is not in the ring
Cause: The IP address of this robot is not found anywhere in FRS:ROSIPCFG.XML.
Remedy: The configuration must include the correct IP addresses.
________________________________________________________________
RIPE-012 WARN Initial time synchronization
Cause: An initial tick time synchronization has occured. This message is posted after all robots
are powered up.
Remedy: None
________________________________________________________________
RIPE-013 WARN Robot not found in ring data
Cause: A robot specified in a destination is not part of the ring defined in ROSIPCFG.XML.
Remedy: The configuration must include information on all robots in the ring.
________________________________________________________________
RIPE-014 WARN Packet is too large
Cause: The system has attempted to send a packet which is too large. The limit is 1472 bytes.
Remedy: Document the events that led to the error, and call your FANUC Robotics technical
representative.
________________________________________________________________
RIPE-015 WARN Packet cannot round trip
Cause: A packet sent to all robots cannot be a round trip packet.
Remedy: Document the events that led to the error, and call your FANUC Robotics technical
representative.
________________________________________________________________
RIPE-016 WARN Robot time not synchronized
Cause: A call was made to get network tick before the system ticks are synchronized.
Remedy: Wait for the synchronized message before requesting tick value.