Felix Exner (fexner)

For noetic the same requirements as for the melodic release are valid. This cannot be released as a binary package as long as upstream dependencies aren't released. As soon as...

Description is still missing, so no.

I think, I never had that in mind, yes. Thanks for bringing that up. Currently, this is the communication scheme: The program node will exit once no data is sent...

Do you see any other output in the shell regarding a dropped connection to the reverse interface? Are you running a realtime kernel?

If you aren't using a real-time kernel and a dedicated network device for communicating with the robot, it can happen, that the connection to the program running on the robot...

With "dedicated" I meant indeed a direct connection between the control pc and the robot controller. Otherwise high load on the network might affect timings for network packages leading to...

Please have a look at our [controller documentation](https://github.com/UniversalRobots/Universal_Robots_ROS_Driver/blob/master/ur_robot_driver/doc/controllers.md). Indeed, sending trajectories to the trajectory controller's command topic with a high frequency isn't the very best choice, as that controller creates...

@fusano using the joint_group_pos_controller should indeed reduce the motion's influence to the controller running on the robot as that controller simply "forwards" the commands to the robot. And no, the...

I cannot quite follow what you are trying to accomplish. Could you please elaborate what (and with which timing) you are sending to the driver's interfaces? `Sending data through socket...

I cannot think of an "easy" implementation of this and we currently do not have the plan or resources for this. So, I'll mark it as "help wanted".