You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When run darknet_ros_3d, there is a warn message camera\depth\registered\point with qos-reliability best-effort and not message will be sent. and never it is published darket_ros_3d\markeArray topic.
How can darknet receive message with best effort ???
Thnaks
Gracias
Florencio garcia
The text was updated successfully, but these errors were encountered:
Hi @lunanueva excuse me for the delay. Nowadays in the code the history policy is the one defined (keep last). Unfortunately this configuration you mention requires a little change in the code. In the file src/darknet_ros_3d/Darknet3D.cpp, in the line 58 you will find the subscription to Darknet ROS. Here you have to modify the second parameter which define the QoS. Here you have the API to see how the method works.
It would be great that the node could be configured with this new parameter from the yaml to be able to change the QoS policy without touching the code.
When run darknet_ros_3d, there is a warn message camera\depth\registered\point with qos-reliability best-effort and not message will be sent. and never it is published darket_ros_3d\markeArray topic.
How can darknet receive message with best effort ???
Thnaks
Gracias
Florencio garcia
The text was updated successfully, but these errors were encountered: