-
Notifications
You must be signed in to change notification settings - Fork 607
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
Bouncy version #128
Bouncy version #128
Conversation
…ng '' (/dev/video0) at 640x480 via mmap (mjpeg) at 30 FPS outbuf size mismatch. pic_size: 1036800 bufsize: 614400 ros-drivers#103
…something in the image message is wrong?) Had to make many changes to debug original issue which mainly was not created the img_ before trying to assign to it. It seems that ros2 run hides crashes silently so they are harder to debug. Every usb_cam method returns a bool but some things should throw exceptions instead. Many functions are run still without any checks on teh return value, which the throws would solve ros-drivers#103
…'t image_tools showimage?), but the frame rate is very slow ros-drivers#103
…pping the exposure time in low light ros-drivers#103
…aunch file the same as ros2 run usb_cam usb_cam_node __params:=src/usb_cam/config/params.yaml
…amera has short exposure, there may be a display issue with framerate- showimage.py shouldn't be used for high framerates, try imgui_ros next
thanks for getting things started here. Do you mind if we tackle the most recent ros2 version instead of bouncy? I feel like we should either get a version merged which is compliant with Foxy or ROS2 master. |
i just made a PR to @lucasw's bouncy branch with minor updates to get it functioning for foxy. tested on a usb camera and I can confirm it is functioning. if he merges that PR it should update this PR as well to work for foxy then |
I haven't touched this (or ros2) in a while, but it should be a reasonable starting point. A few things would be nice to see ported over to a noetic branch.
Looking at the number commits now it looks like an aggressive rebase -i would be good to squash this down.
Begins to address #103