Ask Your Question
1

dynamic_reconfigure parameters not known until runtime. How?

asked 2013-03-05 06:23:36 -0500

ssafarik gravatar image

updated 2013-03-05 14:46:23 -0500

joq gravatar image

As I understand it, the dynamic_reconfigure requires a .cfg file to specify the parameters that will be used (and I've used this successfully, both C and python).

I'm working on a GenICam camera driver, and can't know which parameters the camera supports until runtime. Hence I can't make a .cfg file since I don't know what the parameters will be. Is there a way to use dynamic_reconfigure, but to set up the parameter specs after we've queried the camera? Thanks.

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2013-03-09 19:34:43 -0500

Chad Rockey gravatar image

Actually, some dynamic reconfigure improvements did land into Groovy thanks to Ben Ballard. However, without a clear maintainer, these were not documented.

Here's an example usage of updating the limits at runtime: https://github.com/ros-drivers/urg_node/blob/groovy-devel/src/urg_node.cpp#L78

edit flag offensive delete link more
0

answered 2013-03-05 14:45:53 -0500

joq gravatar image

If I understand your question correctly, different cameras end up needing different parameters. Camera1394 has a similar problem.

There is currently no way to do that with dynamic reconfigure. I ended up including all possible parameters on the reconfigure GUI, which unfortunately makes it longer than necessary.

Various dynamic reconfigure enhancements have been requested to deal with this and similar problems, but I don't know if anyone is working on them.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2013-03-05 06:23:36 -0500

Seen: 275 times

Last updated: Mar 09 '13