Example for multimove with 2+ robots and 2+ external axes?

Honestly, even confirmation that this is unsupported would be some progress.

Not surprisingly I also got no where.

I have raised a support case with the factory support team - can take some days for a reply if they are busy on cases that affect production.

Will let you know the answer once received.

Fantastic, we have one as well. Unresolved for month and probably just closed by abb now :slight_smile:

The reference case for this is: AU190808-367796

Reply is that this system configuration is possible.

They think it should be able to be done without a customised motion configuration file - but if not then they will have to build a custmised motion configuration file.

We asked for a quote for such a configuration file and we are still waiting.
I think they made one and found it wouldn’t work.

We cannot wait around for things that never happen. I was considering making a complaint but no idea where.

Anyways, very disappointed with the whole thing.

The factory team are working on proving if a customised config file is needed.

That would be a miracle (fingers crossed). How did you do this?
Thanks a million times again

So abb sales come by promising a happy ending. We see about that…

5 months and 4 different people in they are “still investigating” the problem

It should not be that difficult to get a multi-move system for this.
would let one robot control the drives for external axis and the other robot follow the first one by moving the work object.
it was performed at Abb 2010 , they should be able to do this at this point!!
no difference in this and a welding table where there are rotating axis.

How does the second robots coordinate system get updated then? I am sure this has been done and I am baffled at how abb is unable to handle this question.
They have been talking about (but have been unable to provide) an addition al configuration file we have to buy. Your solution wouldn’t need that ?

I send your idea to support and we are back in the waiting game with it. Happy new year

Have you received help with this from ABB yet?
I totally missed that you answered me.

  1. Robot is moved by “Base Frame”
    " Base Frame" is move by EX-axis.

Same Robot is using a “WorkObj”

robot2, Robot is folowing Multi move “Workobj” hold by Robot 1.

Have you made your “cell & application” work?
Many welding robot cells with a K-positioner should use similar settings as u, and they can use a traveling track as well. Same settings almoste but you have it standing upp.

Think it is bad with configuration information and examples of this, for real systems from ABB.
Also, Robot studio does not support all settings in MOC.cfg etc.

Robot Studio “team”, is trying to make some thing of ther own to control external axis.
ABB “Robotic motion system” and RSO have, does´t seem to have developed in 15 years regarding this.
Two different ABB companies that don’t care what they do in my opinion.
The developers at ABB do not understand what they are doing and create multiple instances that overlap and completely without connections to each other..’
What works in RSO may not work in RC, Versa.
I use RSO more as a guide and guideline.

Thanks for your reply, nothing useful from abb (we are investigating…). Looks like we need to file a formal complain.

I check your replyout as sson as I am back in the office

The point of difference is that the BaseFrame of both robots is moving with MultiMove the common moving frame is a Wobj is not a Baseframe.

I would in this case, when the robots are mounted on a Track & drive unit, move the BaseFrame, Parameter: “BaseFrame Move By”
( is it a possible that both robots can be moved with the same mechanical unit in the MOC.cfg file. i dont now)
and use MultiMove - to cordinate in between Tool´s by using Wobj as you (graemepaulin) propose to get relations in “World zero frame”

looking at this also., can give you a hint for traveling “Track” and one way of bilding a machanical unit and move Base frame!.

As I understand it the reason a custmised moc file is required is that both robots can not be moved by the same mechanical unit.

Thanks for everybody’s help.
For obvious reasons I am considering using ROS (robotic operating system) or siemens NX another software with less limitations and just streaming targets.
Anybody has some experience with that they can share?

Moving both robots can be moved with the same mechanical results in the controller unable to startup again.
No useful errors just plain broken

6 month no resolution. abb is asking for CAD drawings and an nda. We already send the same robotstudio station 3 times.

@graemepaulin mind explaining me the official complaint process please?