When the nodes are transitioned using the command line lifecycle utils the process dies unexpectedly. This doesn't happen when the nodes are transitioned automatically using autostart.
The issues seem to be related to an incompatible QoS generated by the deadline QoS usage. If this QoS is removed, it works as expected.
Describe the bug
When the nodes are transitioned using the command line lifecycle utils the process dies unexpectedly. This doesn't happen when the nodes are transitioned automatically using
autostart
.The issues seem to be related to an incompatible QoS generated by the deadline QoS usage. If this QoS is removed, it works as expected.
To Reproduce
Terminal 1:
Terminal 2:
Terminal 1:
Expected behavior
It is possible to use
ros2 lifecycle
to activate the nodes successfully.Desktop (please complete the following information):
Additional context Add any other context about the problem here.