Is there a way to minimize what is displayed in the alarm history. Like, if we get a call and the insulator discs is broken, when I pull up the alarm history to see if I can figure out why it was broken, the alarm history will be flooded with resets and imstp alarms. Then I can’t go far enough back to see what the root cause of the problem was. Any help with this will be appreciated.
Fanuc alarm history???
-
Beavissp82 -
August 4, 2018 at 3:06 AM -
Thread is marked as Resolved.
-
You can always pull a backup and look at the error log that way.
-
First, I only have access to R-30iB controllers and manuals, so I apologize if this does not work for you.
I used the Error Severity Table (Under Menu -> Setup). In it, you can choose any error code, then you can change its severity (upward only) and you can change what is done with the error code. All the details are in the HandlingTool Manual in Section 5.10, with the facility codes details in Section A.2.2 (Error Codes and Recovery).
-
First, I only have access to R-30iB controllers and manuals, so I apologize if this does not work for you.I used the Error Severity Table (Under Menu -> Setup). In it, you can choose any error code, then you can change its severity (upward only) and you can change what is done with the error code. All the details are in the HandlingTool Manual in Section 5.10, with the facility codes details in Section A.2.2 (Error Codes and Recovery).
Great Idea Robo_Eng_13! I do this on all new systems. Set the alarm as No Display or No Log and it won't muddy up your logs.
You can also change the system variable $EXTLOG_SIZ=1000 instead of 100. This will keep 1000 errors in your ERREXT.LS file in yoru backup. Also, check out the LOGBOOK.DG file, you can open it with a text editor. This shows the screens and what keys were pressed if you really want to do some investigating. I caught a customer messing with the robot after I left one night with the LOGBOOK.
Hope this helps.
-
Great Idea Robo_Eng_13! I do this on all new systems. Set the alarm as No Display or No Log and it won't muddy up your logs.
You can also change the system variable $EXTLOG_SIZ=1000 instead of 100. This will keep 1000 errors in your ERREXT.LS file in yoru backup. Also, check out the LOGBOOK.DG file, you can open it with a text editor. This shows the screens and what keys were pressed if you really want to do some investigating. I caught a customer messing with the robot after I left one night with the LOGBOOK.
Hope this helps.
Do you need to cycle power on the controller for the change to $EXTLOG_SIZ? When you say check out the LOGBOOK.DG file in text editor i'm assuming you mean take a backup off the robot onto a USB drive and open it on a computer? Or will this change allow you to look up more alarms in the history section of the controller?
-
First, I only have access to R-30iB controllers and manuals, so I apologize if this does not work for you.I used the Error Severity Table (Under Menu -> Setup). In it, you can choose any error code, then you can change its severity (upward only) and you can change what is done with the error code. All the details are in the HandlingTool Manual in Section 5.10, with the facility codes details in Section A.2.2 (Error Codes and Recovery).
When you say "details" is this where I can find the Fcodes for which alarms I would like to modify?
-
When you say "details" is this where I can find the Fcodes for which alarms I would like to modify?
In section A.2.2 (Error Codes and Recovery), yes. This will give you the code for the letter portion, and the numeric portion is direct entry.
-
Do you need to cycle power on the controller for the change to $EXTLOG_SIZ? When you say check out the LOGBOOK.DG file in text editor i'm assuming you mean take a backup off the robot onto a USB drive and open it on a computer? Or will this change allow you to look up more alarms in the history section of the controller?
I believe you do have to cycle power to get it to take effect. Taking an 'All of Above' backup or MD Copy backup will get you these files and you can view them on a PC. Or, if you want to just take a quick glance, just go to the FILE --> Set Device --> MD --> Find the Logbook or errext.ls file --> Click the view soft F-Key --> Scroll through it right on the teach pendant.
I also though after posting this, that on newer robots this is an Option i believe that you need to purchase. Its probably only a couple hundred bucks to get the PAC. But on older ones, you could backdoor it.
-
$ERNOHIS=2
this variable will get rid of all the "resets" from the alarm log
Advertising from our partners
