Posts by ASUA1

you may also want to check the "brake" cable. It may have developed a short from the operation.

Quote from gumpus

the DI/DO come with additional purchases no?

not true. you can use DI/DO without major purchase. Each Robot comes with a plug that can be used to wire DI/DO.

It sounds like you dont really need a CAD to path situation here. That is unless you have imported a sketch that details the path you want to robot to take. If you don't have a sketch with the "path" then you will have to use targets or a similar method.

From your question, it seems like CAD to path is not needed and you just need to use some offsets to "rotate around J6"

Some images of the cell and a better description of the path the robot needs to take would let us help you better.

That is the review page

Quote from Abhi2024

Thank you for reply, where to find this review page?

as if you can see below image for error

You need to go back one page to "8" and add the R651 option and then it should work

If you're talking about the software options you can select it usually has a review page that tells you which options you need to change or which options you need to add to make the ones you've already selected happy.

You may need to set the static IP address of the tablet. It wont be the same as the Host com subnet it will be something internal.

I had a similar issue and setting the tablet IP solved it

It is going to be under setup Under the collabo Robot setup Tab. You will have to disable the collaborative mode along with some other settings

You may want to consider using the skip function in your program instead of BG logic. To me this seems like it would have more control over the situation and can trigger movements as needed whereas BG cant trigger movements. Doing it this way you can stop the robot from performing the move if it has dropped the part and you can "recover" faster

Id take a look at this video from Fanuc

FANUC Skip Function

It should cover what you're trying to do here

FANUC robot software options are authorized using a PAC which is a code Fanuc will provide you based on the controller SW ID along with some other details. They are Robot specific and won't work on other robots. I had to get the Basic interference check on 8 Lr mate robots all running the same version of the overall software but each robot had a unique code to authorize the install.

Using one robot to get software for another won't work.

Only thing Ive seen from FANUC would be Roboguide but its a more comprehensive simulation package than the ABB program you referenced. You might want to see if Robodk will work for your need. They have a web version and a local trial version you can test out to see if it'll work for your need.

The pins youre looking for are going to be part of the Robot connection cable. Youre better off not messing with that. If you're already in the controller why not just use the DO/DI?

If you dont care about seeing the EAOT move from the tool holder then Id just set up like normal with each tool cad being set as the EAOT and the tool will only be visible on the robot when that tool frame is active. Then simply call Each tool frame when you want that EAOT to appear. Youll need a third Blank tool frame but Id do that anyways when switching tools

A little late to the game but hopefully It can help someone else who has this issue.

I've seen this error several times and found that deleting and redoing the instruction solves the problem. It is usually after copying the program from one robot to another that the error occurs. Disconnecting the tool and reconnecting it can also help.

It can run on those specs listed aside from the disk space. I recommend 20 GB free and it can need even more depending on the options you install and the number of robot libraries.

Without lag is another story. Even higher-end specs lag for me depending on the size of the CAD files I'm working with. Otherwise, Id say it can run on a potato

You can use the Joint values from the factory delivery. Or you can just "Fold" it up the best you can to protect it during transit.

Breadcrumb mentality is good for recovery in auto from auto. You use registers basically to update where the robot was at in a program when it was stopped your recovery program sees that and knows it needs to back out of the position to a safer position then on to its "Home".

For any recovery after manual movement, it gets much trickier as the robot doesn't really have a reference to rely on for it position or surrounding obstacles. Scara are easy though as you can send it to a known good z height and then home.

For full safety though a risk assessment is always going to be recommended.

This is a software option that needs to be purchased from FANUC and authorized using a PAC and installed. Option R577

Alternatively you can use the Ipendant customization tools to build a HMI screen.

FANUC Custom HMI Screens on iPendant

This video details how to use FANUC iPendant Customization to make simple touch-screen HMI pages right on your existing Teach Pendant.

Id follow this video from Fanuc as it should help fill in the blanks

RoboGuide Machines: Conveyor and Indexer Motion

A tutorial with some advanced techniques showing how to create linear or rotary motion within a RoboGuide FANUC Simulation use "Machines".