Invalid configuration #30
Comments
|
Should probably mention that even though I list the width and the height, the configuration is adjusted: ros2 run camera_ros camera_node --ros-args -p width:=800 -p height:=600 |
|
You can set the libcamera log level to debug via the environment variable export LIBCAMERA_LOG_LEVELS=*:DEBUG
ros2 run camera_ros camera_node --ros-args -p width:=160 -p height:=120to see what may cause this. Can you also show more of the log, specifically the pixel formats and modes which are shown on the terminal? Also, please use the markdown block/code format for terminal output to better distinguish between your text and the raw terminal output. |
|
Ok, so with the code snippet you provided, i.e And this is the output: And when I try this (saw that you gave that tip in a different thread): I get this output |
|
Thanks for helping me btw. When I run this I get this output (in case this is needed for you) |
|
But it does not help to change the height and width. I tried changing the command like this but I still run into an error |
|
The log says So I would assume that an unsupported format is requested. Have you tried to set a supported format explicitly? |
|
Sorry if I was being unclear. My question is: How do I set your script to SBGGR10? If I understand it correctly, this is what my camera provides, but I do not understand how I can give that variable to the Ros script. Sorry if this is considered very simple - I am new to this |
|
What I have tried is this which gives this output: |
|
The format ros2 run camera_ros camera_node --ros-args -p format:=YUYV |
|
Ok, so this got us further. By using your command I got this output: Created a file in /root/.ros/camera_info/with the expected name with this content First I get this output (which I thought was ok) but when I try to connect rqt_image_view I get this message again and again: If I add the debugging and run it I get this: Any pointers? |
If the libcamera log only shows that the requests are cancelled for no reason, I also don't know further. Look at the logs before the first request that was cancelled as this might show you why. All cancellations afterwards might just be because the request was never rescheduled. Also, could you reproduce the configuration with the standalone libcamera examples to see if this is caused by libcamera itself or the ROS node? |
|
I got the std::runtime_error and ran this command export LIBCAMERA_LOG_LEVELS=*:DEBUG my output was as follows ros2 run camera_ros camera_node --ros-args -p width:=160 -p height:=120 |
You do not have a camera connected or it is simply not detected by libcamera. How is this related to the issue? |
|
It's a pi camera v3 and it is connected. How then do I get it to be detected by libcamera? Also, I thought the issues were related due to bringing up the same error, sorry about that. |
I would first test with the examples in libcamera to check this. If the libcamera examples do not detect the camera, you have to open an issue with them. If it does, and the ROS node does not, you can create a new issue here. But otherwise, this repo only deals with the ROS specific bindings and not libcamera in general. |
|
Thanks |
|
@SchlackBoles If you do not have more information about what happens before the first request cancellation or a way to reproduce this, I would close the issue. |
|
I am closing this as it seems to be an issue with either the camera or libcamera. |
|
I assume this is the same issue as #64. The format |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi.
I tried to launch your file but get the following error (ros2 run camera_ros camera_node )
Tried to add a camera_params.yaml with
but it does not fix the issue. Any pointers? I am using the shutter camera on a raspberry pi5.
The text was updated successfully, but these errors were encountered: