-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto exposure and other parameter names #260
Comments
@javieryu thanks for reporting this! I'll look into it and circle back this weekend. |
Seem i am also running into this as well:
my |
@javieryu this would be an awesome awesome feature! Just not sure how to implement it 😅 PR's / implementation ideas welcome 🙏🏼 |
@twdragon thanks for your contribution, I look forward to your PR |
Hardcoding them to match Stretch's cameras until ros-drivers#260 is resolved
Just hit this too. It would be nice for parameters that fail to set to print to We hardcoded our parameters in a fork here for the time being: https://github.com/hcrlab/usb_cam/ Our camera's parameters (teleop fisheye cameras from Hello Robot Stretch, in case others are searching):
|
Some of the parameters for my device seem to have names that are slightly different than those set using this library. For instance, the ros parameter for
autoexposure
is set using the device controlexposure_auto
, but for my device it isauto_exposure
according tov4l2-ctl --device=0 --all
. This seems to result in a outcome where theautoexposure
setting does not change anything when I set it in the params file or withros2 param set ...
.Output from
v4l2-ctl --device=0 --all
:Result when running
ros2 run usb_cam usb_cam_node_exe --ros-args --params-file params.yaml
:It seems like the naming conventions that is different for my camera/drivers? So far my workaround is to use the
v4l2-ctl --device=0 --set-ctrl=...
command after running the usb_cam node. Is there a better way to do this?The text was updated successfully, but these errors were encountered: