Skip to content
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

Can't use ros2 launch yolo_bringup yolo.launch.py stuck when starting script. AGX Orin 64gb Developer kit #76

Open
xXMrPotatoXx opened this issue Feb 24, 2025 · 12 comments

Comments

@xXMrPotatoXx
Copy link

xXMrPotatoXx commented Feb 24, 2025

image

Its been like this for a long time and it doesnt move at all. I installed all the requirements and did everything like the guide said.

@bhavya-goyal-22
Copy link

bhavya-goyal-22 commented Feb 26, 2025

"Please verify the input topic that the node is subscribing to by checking it in RViz or using ros2 topic echo. Also, ensure that the camera topic is correctly set and that data is being published on the topic.

For example, you can check the camera topic with:
ros2 topic echo /image_raw

Try launching your file using the following command:
ros2 launch yolo_bringup yolo.launch.py input_image_topic:=<your_topic>

@Johnny-Hu-406
Copy link

Hello, I am facing the same issue.

To simulate the camera input, I am publishing the image to /camera/rgb/image_raw, and I can preview it in Rviz2, where it displays correctly.

However, the /yolo/dbg_image node still does not produce any output.

Image

Here is a screenshot of my terminal showing the following image
Image

I hope to receive your reply and assistance, as I would appreciate your help in understanding this issue. Thank you very much for your time and support.

@mgonzs13
Copy link
Owner

mgonzs13 commented Mar 2, 2025

Check the QoS of the /camera/rgb/image_raw and also check if the detection topics are publishing. The QoS of the publisher and subscriber must be the same.

@Johnny-Hu-406
Copy link

First, I use ros2 topic info /camera/rgb/image_raw --verbose to confirm that the QoS settings of the publisher and subscriber nodes appear to be consistent.

Image

Additionally, I also use ros2 docker --report to check the relationship between the publisher node and the subscriber node.
Image

I’m not sure what other directions I can try to solve this issue. Any suggestions? Thanks!

@mgonzs13
Copy link
Owner

mgonzs13 commented Mar 2, 2025

@Johnny-Hu-406, try ros2 topic echo /yolo/detections and ros2 topic echo /yolo/tracking to check if detection and tracking are getting done.

@Johnny-Hu-406
Copy link

@mgonzs13 When executing ros2 topic echo /yolo/detections, I can see the following output, and ros2 topic echo /yolo/tracking also has similar output.

Image

@mgonzs13
Copy link
Owner

mgonzs13 commented Mar 2, 2025

That means you are getting detections. Next, check the topics of the /yolo/debug_node. Also, try ros2 topic echo /yolo/dbg_image.

@Johnny-Hu-406
Copy link

First, I tried ros2 topic echo /yolo/detections and could see the output, such as coordinates and confidence

After that, I tried ros2 topic echo /yolo/dbg_image, but there was no output in the terminal.
Then, the terminal gets stuck on the following screen.
Image

I believe that /yolo/debug_node successfully receives input, but it is unable to output images to the /yolo/dbg_image topic. Additionally, ros2 topic echo /yolo/dbg_image does not produce a response. I'm not sure how to resolve this issue.

@mgonzs13
Copy link
Owner

mgonzs13 commented Mar 2, 2025

So, if the problem is in the /yolo/debug_node, check the QoS of its topics, include the image and detection topics.

@Johnny-Hu-406
Copy link

I use ros2 topic info /camera/rgb/image_raw --verbose to confirm that the QoS settings of the /camera/rgb/image_raw and /yolo/debug_node nodes appear to be consistent.

Image

@mgonzs13
Copy link
Owner

mgonzs13 commented Mar 2, 2025

@Johnny-Hu-406 are you using a depth camera? If not or if you don't want 3D detection, use use_3d:=False in your ros2 launch command.

@Johnny-Hu-406
Copy link

@mgonzs13 I'm not entirely sure what caused the issue, but after reinstalling your repository and Docker, the problem was successfully resolved.
Currently, the images from /yolo/debug_node are functioning properly.

I sincerely appreciate your patience and prompt responses—they have been incredibly helpful to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants