The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
It appears the dynamic reconfigure request for raspicam_node is being initiated by the node itself. We can observe in the log that after calibrating, the node tries to load a device-specific calibration file but is unable to locate one, so default calibration parameters are used and then sent as part of a reconfigure request with these default values.
[ INFO] [1680486286.081100851]: camera calibration URL: file:///home/ubuntu/.ros/camera_info/camerav2_1280x960.yaml
[ INFO] [1680486286.081757617]: Unable to open camera calibration file [/home/ubuntu/.ros/camera_info/camerav2_1280x960.yaml]
[ WARN] [1680486286.082066000]: Camera calibration file /home/ubuntu/.ros/camera_info/camerav2_1280x960.yaml not found.
[ INFO] [1680486286.082351102]: No device specifc calibration found
[ INFO] [1680486286.222915249]: Reconfigure Request: contrast 0, sharpness 0, brightness 50, saturation 0, ISO 400, exposureCompensation 0, videoStabilisation 0, vFlip 1, hFlip 0, zoom 1.00, exposure_mode antishake, awb_mode auto, shutter_speed 0
Therefore, the dynamic reconfigure request isn't initiated by itself but instead triggers by raspicam_node as a fallback mechanism when it cannot locate a device-specific calibration file.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.