I have an M20-iA from an OEM that gets to loading os.... and then the screen goes blank. It will not do a controlled start either. The real problem is I do not have a complete image backup. I do have a vendor supplied file backup. Has anyone done or used the emergency backup function? If so how does it work and did you get favorable results?
Emergency backup function
-
RJensen0246 -
October 27, 2017 at 6:18 PM -
Thread is marked as Resolved.
-
-
I do not have any answers regarding the backup question, however i believe there are some fuse/electrical issues that can cause similar behavior at the teach pendant. What controller do you have? R-30iB is all i am familiar with.
-
Try checking Fuse 3 on the E-Stop board inside the controller cabinet. Attached is (hopefully) an image showing the location of the fuse on the board. This is the board for a Fanuc America, R-30iB controller, A Cabinet E Stop board with the 3 fuses called out. My notes say that Fuse 3 being bad can cause the screen to go blank, and if the fuse is blown, the cause is likely damage to the TP cable, the TP itself, or the E Stop board. If you have another robot which you can swap out part by part to narrow down the issue, that would be the path i would try.
-
It is an R30iB and all the fuses on the E-stop board are good. My OEM sent me what they called a "back up of the controller" but the file structure did not look correct to me and when I tried to use it, it told me "This operation causes fatal damage to this controller".
-
What your OEM should have given you is the image backup (*.IMG files). The number of files depends on the type of FROM/SRAM module size. In R-30iB, it normally confirms if you have the correct number of files at the moment of restore the backup.
-
yes I know and that is not the file set they gave me. At this time I am trying to take the file set they gave me, restore it in RoboGuide and then convert to a file to use to restore my physical robot.
-
What does the file structure look like? Post a screenshot and we may be able to determine what to do with it.
Sent from my SM-G930V using Tapatalk
-
this is the first part of the file list
-
We had the same thing happen to us, and the "fix" was to unplug the ethernet cable while booting. Something on the network was conflicting with the controller and caused it to halt during boot-up. I know it sounds crazy, but try it.
-
What you have is an "all of the above" backup. I don't think that will help in your situation since some of those files need to be loaded in a controlled start.
If they have an image backup or the original load software then you could try to restore it.
Of course it may not be a software issue at all.
Sent from my SM-G930V using Tapatalk
-
The ethernet thing worked!!! that is crazy. what i found was the robots (only 2 of the three) don't like it when my HMI for the cell is plugged into the nerwork. I will work this out later they are able to run. Thank you all for you assistance!!
-
Glad to hear it got you going.
We had this happen right after a power flicker in our plant and still don't know what was conflicting our network since it seems to have went away.