ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Just an isolation of the issue -- rqt_reconfigure depends on dynamic_reconfigure and doesn't store any parameter information by itself. That said the incompatibility shouldn't occur on rqt_reconfigure level, and I assume it resides between dynamic_reconfigure and the component you're using.

I've also taken a brief look at camera1394/cfg/Camera1394.cfg on groovy but I couldn't find anything useful for this issue. I'm sure someone who are more familiar with dynamic_reconfigure especially on nodes sides (in this case camera1394).

Just an isolation of the issue -- rqt_reconfigure depends on uses dynamic_reconfigure to access parameters and doesn't store any parameter information by itself. That said the incompatibility shouldn't occur on rqt_reconfigure level, and I assume it resides between dynamic_reconfigure and the component you're using.

I've also taken a brief look at camera1394/cfg/Camera1394.cfg on groovy but I couldn't find anything useful for this issue. I'm sure someone who are more familiar with dynamic_reconfigure especially on nodes sides (in this case camera1394).

Just an isolation of the issue -- rqt_reconfigure uses dynamic_reconfigure to access parameters and doesn't store any parameter information by itself. That said the incompatibility shouldn't occur on rqt_reconfigure level, and I assume it resides between dynamic_reconfigure and the component you're using.

I've also taken a brief look at camera1394/cfg/Camera1394.cfg on groovy but I couldn't find anything useful for this issue. I'm sure someone someones who are more familiar with dynamic_reconfigure dynamic_reconfigure especially on nodes sides (in this case camera1394).) have insights.

Update) Not sure if this works, but you might want to give a shot to 3rd party plugin ParamEdit to get a similar feature.


Just an isolation of the issue -- rqt_reconfigure uses dynamic_reconfigure to access parameters and doesn't store any parameter information by itself. That said the incompatibility shouldn't occur on rqt_reconfigure level, and I assume it resides between dynamic_reconfigure and the component you're using.

I've also taken a brief look at camera1394/cfg/Camera1394.cfg on groovy but I couldn't find anything useful for this issue. I'm sure someones who are more familiar with dynamic_reconfigure especially on nodes sides (in this case camera1394) have insights.