Closed mrsp closed 5 years ago
Sorry @mrsp for the late reply, guess you have figured your problem out by now.
We encourage you to ask questions on ROS Answers in the future following the ROS support guidelines
I ran into the exact same error traceback. How did you solve it? @mrsp
I didn't
@mrsp I think I have solved it. I was using dynamic_reconfigure for a plugin. The error came up because there's a registered dynamic reconfigure yet the node cannot be found (as it is "hiding" under another architecture of code), so the name goes empty and generates the error. I resolved the error by giving the node handle a specific name.
ros::NodeHandle nh;
vs
ros::NodeHandle nh("~/" + name);
If the context applies, I hope it helps.
Hi
Any ideas on the following error when launching rqt_reconfigure:
Thx in advance