Great video Joshua, I work with UR robots everyday and have sorted through a bunch of videos trying to figure stuff like all of this out. Someone who is starting out programming should really watch this as you do a great job explaining steps clearly
Biggest problem I see when people program these, is they get too many moves nested into each other. I try to make my programs as modules, where I use folders to separate the modules. Inside each folder I then got a MoveJ to do the travel moves, then a MoveL nested inside the travel move, where the MoveL is doing the work if inserting or grabbing a part, and when finished it is then going back to the MoveJ it came from. That both gives a structure where it is easy to see where it is doing the actual work, and where it is just traveling between operations, and changing the speed of travel and work is less places to go to edit too.
This is solid advice. I usually make things as modular as possible with folders and subroutines. My main program just calls a series of subroutines which makes it very easy to run individual things for testing.
Very informative video. I’m currently doing an Internship on a Ur3 robot arm. They want me to enable the robot make some cut (more or like writing task). How do you think I should go about such task?
Hello Thank you for this great Video 😊 What do you think about the Payload is the 5kg robot to move 8 Kg parts if the move speed is slower? Thank you so much
Sounds like a job for the UR16, it's basically the same size as the 5 but has a greater payload. But also to answer your question I think the UR5 in that scenario would lose accuracy and throw protective stops often. I don't think it would work smoothly.
Absolutely do not use a lower than rated robot. You'll potentially damage the joints if it runs at all or will error out constantly. I would stay 10% under the rated payload.
Planes can be set up in the installation tab under features, then there is a teach plane button and it's pretty simple to set one. The way I use them is to keep track of an area or section of program that may move. In the case of this video, all moves inside the machine are set relative to the main spindle. If something happens and I have to reset the location of the robot base. Instead of going back through the program and redefining each waypoint, I just reset the feature based on the main spindle and I'm done. I'm working on a video currently that is all about plane manipulation so if this doesn't explain it hopefully that will!
Almost all the movement is in a transient zone and when near possible pinch points the robot speed is sensing for pressure and at very low speed. The operator works well outside the reach of the robot with clear access to its controller. These robots have set inertial limits as well so even if a high speed is programmed, the payload is taken into account and speed is reduced automatically. I mean there are a lot of factors here on why I believe it is safe, is there something you saw that concerned you?
@@joshuayoungers the EOAT is operating at head/ neck level at a speed greater the 250mms. The machine door or lathe chucks are also not force or power limited. There is nothing stopping someone from being in those restricted zones during automatic operation.
Ah, for reference the spindles are just above waist level, the perspectives recorded make it appear higher. The machine cannot run without the doors shut and there is a table in the way probably not shown in the video.
Great video Joshua, I work with UR robots everyday and have sorted through a bunch of videos trying to figure stuff like all of this out. Someone who is starting out programming should really watch this as you do a great job explaining steps clearly
Glad you like it, thanks
Thanks for this great introductory tutorial.
Nice content, i have been thinking about adding one of these to our shop and I will definitely revisit this many times.
Biggest problem I see when people program these, is they get too many moves nested into each other. I try to make my programs as modules, where I use folders to separate the modules. Inside each folder I then got a MoveJ to do the travel moves, then a MoveL nested inside the travel move, where the MoveL is doing the work if inserting or grabbing a part, and when finished it is then going back to the MoveJ it came from. That both gives a structure where it is easy to see where it is doing the actual work, and where it is just traveling between operations, and changing the speed of travel and work is less places to go to edit too.
This is solid advice. I usually make things as modular as possible with folders and subroutines. My main program just calls a series of subroutines which makes it very easy to run individual things for testing.
Nice job Josh! Great video very informative.
I see that you are using some kind of Marposs Equipment, what is that for? 15:22
Great video!!
Is there a possibilty u can show us the relais setup with the cnc controller to the UR system?
Nice video. Can you let me know what light sensor you use?
Very informative video. I’m currently doing an Internship on a Ur3 robot arm. They want me to enable the robot make some cut (more or like writing task). How do you think I should go about such task?
Hello Thank you for this great Video 😊
What do you think about the Payload is the 5kg robot to move 8 Kg parts if the move speed is slower?
Thank you so much
Sounds like a job for the UR16, it's basically the same size as the 5 but has a greater payload. But also to answer your question I think the UR5 in that scenario would lose accuracy and throw protective stops often. I don't think it would work smoothly.
Absolutely do not use a lower than rated robot. You'll potentially damage the joints if it runs at all or will error out constantly. I would stay 10% under the rated payload.
I don’t understand feature Plane.
How to set ? How to use?
Planes can be set up in the installation tab under features, then there is a teach plane button and it's pretty simple to set one. The way I use them is to keep track of an area or section of program that may move. In the case of this video, all moves inside the machine are set relative to the main spindle. If something happens and I have to reset the location of the robot base. Instead of going back through the program and redefining each waypoint, I just reset the feature based on the main spindle and I'm done. I'm working on a video currently that is all about plane manipulation so if this doesn't explain it hopefully that will!
@@joshuayoungers
Thank you. and I have to know feature Conveyer tracking too.
Please explained it to me.
Thank you.
I am curious how you justify this as a safe deployment in accordance with ISO 15066 standard?
Almost all the movement is in a transient zone and when near possible pinch points the robot speed is sensing for pressure and at very low speed. The operator works well outside the reach of the robot with clear access to its controller. These robots have set inertial limits as well so even if a high speed is programmed, the payload is taken into account and speed is reduced automatically. I mean there are a lot of factors here on why I believe it is safe, is there something you saw that concerned you?
@@joshuayoungers the EOAT is operating at head/ neck level at a speed greater the 250mms. The machine door or lathe chucks are also not force or power limited. There is nothing stopping someone from being in those restricted zones during automatic operation.
Ah, for reference the spindles are just above waist level, the perspectives recorded make it appear higher. The machine cannot run without the doors shut and there is a table in the way probably not shown in the video.
Cable Management left the chat 😂
You put a mexican there and tell him what to do , you wont have to go through all this programming hassle to pick part from this turning machine 👨🔧