-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Resolution of 640x480 is not available for L515, color image (/camera/color/image_raw not available) #1555
Comments
Thanks @kashishdhal for the info. I referred some people to this issue and hope to have an answer soon enough. |
Hi @kashishdhal As per the l515 datasheet, 640x480 is not a supported RGB resolution. https://dev.intelrealsense.com/docs/lidar-camera-l515-datasheet Thanks |
Hello @RealSenseSupport , Thanks for the reply! This is the reason that I opened a pull request #1536 to update the launch file but it was closed by @doronhi I was under the impression that it may help other users. If this resolution is not supported please accept my pull request and replace the dimensions into launch file. Thanks! |
@kashishdhal I understand now that you are correct, as well as @krazycoder2k was back in #1297 . |
@doronhi , looks good to me, it solves the problem, approved from my side but you need to modify the launch file as well. There is no purpose we should have invalid frame dimensions in the launch file. |
There is no point in keeping default values matching all the different devices when the librealsense2 SDK keeps track of them. |
Hello @doronhi,
With reference to #1523 and #1536 I am creating this issue. I do not see /camera/color/image_raw when I launch rs_camera.launch. However, when I change the resolution of the RGB image in the launch I am able to successfully see those topics.
Please see the output of rs-enumerate-devices which you asked me to do in the pull request. Please note that I am using an ARM computer (RPI 4 ), I don't know if that is making a difference here.
The text was updated successfully, but these errors were encountered: