Hi @gvdhoorn, when you say "the robot's controller handles all the collaborative aspects locally", does that mean when using the ROS drivers the robot stays in collaborative mode? But if you were to turn off collaborative mode on the robot controller itself (through the pendant) using the ROS drivers would move the robot in non-collaborative mode?
What I meant with that sentence is that the driver does not know or take into account any collaborative features. If there is some collaborative action or limiting activated by the controller, it will be at the controller's initiative, and as always, the controller is in full control. The drivers are just user-level application programs, with no special access whatsoever.
does that mean when using the ROS drivers the robot stays in collaborative mode?
I cannot say anything conclusive here. In the end, the driver will just use regular J
moves. If that keeps everything "collaborative" (whatever that may mean in a specific context), then the answer would be yes. But other than that, the drivers do not do anything special, nor are aware of, nor are explicitly compatible with any collaborative features of the robot controller.
Summarising: from the driver's perspective, a collaborative Fanuc is just like ...