sharing programs between robots

C.Crosby · August 27, 2021 at 8:49 PM

So my work has several R2000iA 164f machines with R-J3ib controller. Most of our robots have welding equipment setups. My boss was thinking it would be a good idea to setup one in its own cell for me to create programs on and test them out. Than we would transfer that program to a different machine we already have operating in a production welding cell. The thought being we would have less down time programming new parts on a production robot and there would be less pressure to hurry up and finish programing so we can get back to running production. I than can focus on trying new things, fine tuning things, etc on my own "test" robot cell.

what things should I take into account to achieve a smooth transfer of programs from one robot to another? All welding robots will have the same welding equipment on them and power source as well as the test cell robot.

what issues could I possibly run into?

I haven't really played around yet to see what stuff id run into other than thinking about different scenarios, just trying to get an idea as I'll be messing around with it in a week or two. anyone else do this and have experience to share?

Thanks

jmd2777 · August 27, 2021 at 10:08 PM Best Answer

1. We try to standardize the Input and Output numbering. For example, the "Mold Open" signal is always on DI[5], etc.

2. I don't know how welding programming works, but for pick and place projects Tool Frames and User Frames make it easier to transfer to a different robot.

keyboard7 · August 30, 2021 at 5:11 PM

The location of fixturing from the test cell to the production cells will be critical.

C.Crosby · August 30, 2021 at 5:30 PM

Quote from keyboard7

The location of fixturing from the test cell to the production cells will be critical.

can you explain more?

we use uFrames in our production cells.

Lemster68 · August 30, 2021 at 6:37 PM

Compare the cost of a Roboguide license compared to what it will cost to set up your cell. I think that the license will compare quite favorably.

keyboard7 · August 30, 2021 at 6:44 PM

Making sure the toolng can be located in the cell exactly the same in all the cells.

TitusLepic · August 30, 2021 at 7:05 PM

Quote from Lemster68

Compare the cost of a Roboguide license compared to what it will cost to set up your cell. I think that the license will compare quite favorably.

This

C.Crosby · August 30, 2021 at 7:34 PM

Quote from Lemster68

Compare the cost of a Roboguide license compared to what it will cost to set up your cell. I think that the license will compare quite favorably.

i've been pushing this for quite awhile. they won't go for it here. it's been quite frustrating.

Lemster68 · August 30, 2021 at 7:54 PM

Figure out what it will cost to build a duplicate cell and show management the $$$$$, it is hard to believe that they won't follow that argument. Not only that, but also in roboguide you could have each cell with its own setup, however minute the variations are from the "extra" cell to the real cell.

mosbe · September 1, 2021 at 1:26 AM

Despite things mentioned above, you should care about those UFrames. Those are most important "variables" if you have two same cells. At first runs use very low operating speed.

sharing programs between robots

Advertising from our partners

How to see your Job Posting (search or recruit) here in Robot-Forum.com