On Mon, Mar 22, 2010 at 10:01 PM, Blaise Gassend
<
blaise@willowgarage.com> wrote:
>> I actually did think about that. It could be useful to set a different
>> URL before running the calibration step. It would be easy to re-read
>> the "calibration/url" parameter in the set_camera_info service
>> callback. I didn't implement that in the initial version, but can
>> easily add it.
>
> I'd say don't worry about it unless your node becomes dynamically
> reconfigurable. It will be easy to add in when we move it to some
> upstream package.
It does have several parameters that can be reconfigured on the fly
(exposure, brightness, etc.). They are read every cycle using
getParamCached(). You can change them via "rosparam set" without
shutting down the driver.
By dynamically reconfigurable, do you to mean by an automatically
generated graphical user interface? I'd like to do that, but don't
have time to figure out how it works at the moment.
--
joq
(text/plain)