Closed ZdenekM closed 3 hours ago
Sorry for the noise, it seems that it was caused by publishing from outside the docker container, while the driver is running within the container (with network_mode: host
and real-time capabilities). So it is not related to the driver. When trying to publish from the container, it works as expected. Another issue is that vg10_grip()
does not work, but that is a different story.
Affected ROS2 Driver version(s)
2.4.10-1noble.20240922.120253
Used ROS distribution.
Other
Which combination of platform is the ROS driver running on.
Ubuntu Linux with realtime patch
How is the UR ROS2 Driver installed.
From binary packets
Which robot platform is the driver connected to.
UR E-series robot
Robot SW / URSim version(s)
5.16.0
How is the ROS driver used.
Through the robot teach pendant using External Control URCap
Issue details
Summary
The ultimate goal is to control VGC10 suction by sending urscript commands. As a first test, I tried to send some trivial stuff, but found out, that it is, for some reason, highly unreliable. For instance, I tried to control digital out:
by setting it on and off. And it works (the command gets printed by the interface and executed on the robot) only sporadically.
Issue details
It seems to be the same without specified QoS, with inline code, etc.
Steps to Reproduce
Run external control program, put robot into remote mode, run ROS driver, publish urscript command.
Expected Behavior
I would expect that every sent valid script will be executed.
Actual Behavior
The sent script gets executed only sporadically (most of the time it is simply ignored).
Relevant log output
No response
Accept Public visibility