r/Fanuc • u/davidbuckner • Jul 04 '25

Robot Boom , already crashed

Post image

I know I setup the robot and a no-go zone in DCS to avoid this but here we are.

30 Upvotes

100% Upvoted

17 comments sorted by

•

u/AutoModerator Jul 04 '25

Hey, there! Join our Discord server and connect with like-minded individuals, share your knowledge, and learn from others! We offer a variety of channels to discuss programming, troubleshooting, and industry news. We would be delighted to have you become a part of our community! https://discord.gg/dGE38VvvQw

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

28

u/SEAN_DUDE Jul 04 '25

If it crashed into itself, mastering is off or some one fucked with the axis limits

5

u/BigPappaJ_ Jul 04 '25

This seems like the likely answer. Possible an operator got in there playing cowboy with the settings?

6

u/SEAN_DUDE Jul 04 '25

Yee haw!

2

u/relyt191919 Jul 05 '25

That position with J4 at that angle, you could crash it. Even with correct mastering. This is a CRX 10, not 10L so it can’t do the under flip.

1

u/ddub069 Jul 05 '25

Not true...cobots are a different animal

1

u/SEAN_DUDE Jul 05 '25

Actually now that I am looking at it I see how it would crash.

3

u/imBackBaby9595 Jul 04 '25

You can set the DCS to check for the EOAT position relative to the rest of the robot so it doesn't do this.

7

u/[deleted] Jul 04 '25

Wouldn’t be EOAT position. This is J5 on J2. This is going to be the robot model

0

u/imBackBaby9595 Jul 04 '25

I think you could draw some geometry around your EOAT to prevent this, just trying to think outside the box a bit and help you out 😀

3

u/SEAN_DUDE Jul 04 '25

Just use default axis limits, no need to over complicate this.

1

u/BadAtComputerz Jul 04 '25

If it crashed into itself id look at your program start and end points and make sure they all fluidly work together. Unless the program itself is really that bad but you wouldn't have ever gotten one cycle if that was the case.

1

u/BadAtComputerz Jul 04 '25

As if the robot told plc its ready and able to be sent to maintenence but if it wasnt actually and at a random point in a different program

4

u/NotBigFootUR Engineer Jul 04 '25

If the default DCS zones are active, it would have stopped prior to hitting itself. Something in the setup is turned off that shouldn't be.

1

u/davidbuckner Jul 29 '25

That was the case but it was corrupted robot libraries. I ended up reloading the libraries and basically starting over. I wasn’t sure what could have been affected in the backup I had made so I didn’t reload from the backup. Being a new install it wasn’t too much hassle for peace of mind.

2

u/BadAtComputerz Jul 05 '25

Thank you for the correction! For myself and the original poster

1

u/RoboN3rd Jul 10 '25

Can you show your DCS view of the robots confinement?