Here is where ours are located. You will see on the left side, the black battery box. Above the name plate. There are small blue wires attached to it.
Posts by cobenson
-
-
Not sure if you have tried this or not, but lately I have had a few of these where the wires coming from the battery on the door, going to the connector inside the robot cabinet have been damaged. The area I have seen is right at the connector where they have the clamp inside the connector. If that makes sense.
-
I think what he is saying is if you go to Menu, setup, macro, he sees the text there. But there is not a program associated with it. You know how Fanuc defines some generic names in the macro table.
So he has to create a program first, then associate it in the macro table.
-
It does not collide with anything it is in midair when the fault happens and again it does not matter what axis I move (even in joint) the fault happens on A3. Also the voltages check good, there is another 410 feed from the same control panel that is operating normally. I have run the robot via the TP and listened for any abnormal sounds and have not hear anything, and there has not been a PM or greasing done recently.I am confused. You say no matter what, it collision detects. But then you say you move it via the TP with no sounds. So which is it, please?
-
This may sound weird, but have you checked the collision detect settings? If it is set too high, then you can collision detect in air moves. I was just trying this today.
-
Pretty sure if he cannot boot the robot, he cannot get to the init start. But I could be wrong.
-
You will need your F-Number and will need to call Fanuc and have them reburn it for you!
-
Just an FYI. It will only create 1 file (TPSCRN.LS). So if you take 5 screenshots, it will be 1 file with all 5 screenshots. They will go in order from top to bottom. So don't expect 5 different screenshots.
Unless of course you delete the file before every screenshot.
I usually use roboguide to make my screenshots if I need them.
-
Sounds like you don't have a card in the MC slot. Or if you do, it is too big, not formatted correctly, or Fanuc doesn't recognize it.
-
what's this?This is an option you but from Fanuc!
-
-
I got this error when I went to roboguide version 9.xx SR1. I was told by Fanuc they have fixed this in the new roboguide that just came out a week ago or so. I installed it, and my issue went away.
Mine was when I would work on anything that was running version 8.xx
-
I always press the data button, then I can do what I want.
-
You can download from Fanuc's website.
-
Set these to 100.
$SCR.$JOGOVLIM
$SCR.$RUNOVLIM -
-
What we do is make a background program that monitors the teach pendant switch. And/or we run a background program that monitors if the robot position moves more than 25mm, we automatically abort the robot.
Maybe one of these might be helpful?
-
You can always pull a backup and look at the error log that way.
-
The other thing you can do is some custom code when it goes to drop off. In PLONPAL, you can modify the actual place point. For example, if PR5 is your place position, you can do something like this:
PR[66]=PR[66]-PR[66] (This zeros out that register.)
PR[66]=PR[5] This moves the drop position in PR[5] into PR[66] for use later
PR[66,6]=PR[66]+5 (This will take your actual drop position and move J6 position plus 5 degrees of rotation into that register.)
L PR[66] (This will then be your official drop point)I have tried it with just adding the offset to PLONPAL directly on the drop PR, but sometimes Fanuc gets weird. So now we just use offsets like this. The hard part is when you rotate the bag 180 degrees, if you do. You will need to make your condition based upon that. So custom code gets kind of ugly that way.
-
You can use interference zone checking option. Think it might be called space check now, though. This way it doesn't really matter.
Another way is to share some I/O between them via a PLC if one is attached.