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

no sonor image #278

Open
huangbintao188 opened this issue Nov 10, 2023 · 25 comments
Open

no sonor image #278

huangbintao188 opened this issue Nov 10, 2023 · 25 comments

Comments

@huangbintao188
Copy link

huangbintao188 commented Nov 10, 2023

I used the git checkout 5344060071d0a72857a9efb558cc1f2d7c0052c6 method and catkin_make succeeded, when i try to run roslaunch nps_uw_multibeam_sonar sonar_tank_blueview_p900_nps_multibeam.launch https://field-robotics-lab.github.io/dave.doc/contents/dave_sensors/Multibeam-Forward-Looking-Sonar/ .My gazebo interface starts and runs normally, but the other window buleview_p900 is dark and has no sonar image. Check the configuration artificialVehicleVibration and it is true. Open rqt to check the sonar image and the values are all 0, which means it is not a computer problem. It may be some configuration error, but I No reason can be found at present.
14D56A518DD97C1893DB94A1D27FE29A

@gaoning0109
Copy link

Are you solved it ?

@huangbintao188
Copy link
Author

no, I don't know exactly why. It's the same with docker method.

@gaoning0109
Copy link

I found the P_Beams in gazebo_multibeam_sonar_ray_based.cpp is empty. Maybe the cuda cal something wrong.

@woensug-choi
Copy link
Collaborator

Let me get back to you after I finish merging pending PRs first.

@huangbintao188
Copy link
Author

I found the P_Beams in gazebo_multibeam_sonar_ray_based.cpp is empty. Maybe the cuda cal something wrong.

What is your CUDA version

@woensug-choi
Copy link
Collaborator

@huangbintao188 Checked on empty PBeams on CUDA 11.4.. The original code is developed on CUDA 11.1

@woensug-choi
Copy link
Collaborator

@huangbintao188 Oh! Are you using Docker? or On the Host??
I've tried on Ubuntu 22.04, NVIDIA 545, CUDA 12.3 and it works perfectly fine!
I am guessing mismatch between Docker CUDA version and the host CUDA version.

@huangbintao188
Copy link
Author

Yes, that should be my version mismatch. If you run well on Ubuntu 22, I can configure it on our server host. Does Dave and np_sonar support ROS2 on Ubuntu 22? How is the specific process for deploying Dave? Thank you

@huangbintao188
Copy link
Author

@woensug-choi

@woensug-choi
Copy link
Collaborator

Not for ROS2. I've tested with docker environmont meyhod on Ubuntu 22.04. Sonar worked fine :)

@Evintjh
Copy link

Evintjh commented Dec 6, 2023

Hi, I am using NVIDIA 535, docker ubuntu 20.04 and cuda version 11.1. But I am also not seeing any sonar images. Anyone knows why? @huangbintao188 @woensug-choi @gaoning0109

@woensug-choi
Copy link
Collaborator

for cuda 11.1 the nvidia 535 isnt compatible. Use 450 which is too old...

image

image

@Evintjh
Copy link

Evintjh commented Dec 6, 2023

Oh, but I tried NVIDIA 535, docker ubuntu 20.04 and cuda version 12.3 too and it gave me similar results @woensug-choi

@woensug-choi
Copy link
Collaborator

Ive just tried exact same environment yesterday and it worked. Does your host machine and docker has same cuda versions?? you can check by typing nvidia-ami both inside and outside docker

@huangbintao188
Copy link
Author

I plan to deploy it on a lab computer, it's Ubuntu22, cuda is 12.1, is this environment compatible with Dave's docker method? Do you need me to modify the e.g. docker file? @woensug-choi

@woensug-choi
Copy link
Collaborator

try docker method and see if cuda version matches inside and outside docker environment

@woensug-choi
Copy link
Collaborator

Ive just updated the document

@Evintjh
Copy link

Evintjh commented Dec 9, 2023

Hi @woensug-choi , when you used Ubuntu 22.04, which version of ROS did you use? I thought Noetic is not compatible with it?

@Evintjh
Copy link

Evintjh commented Dec 10, 2023

Screenshot from 2023-12-07 22-47-24
Screenshot from 2023-12-07 22-47-42

Both my host and docker are showing the same driver and cuda version. But I realised that I am using nvidia container toolkit, hence I did not have to physically install cuda toolkit in my docker container. Is there another specific set of instructions if I am using Nvidia container toolkit? @woensug-choi

@woensug-choi
Copy link
Collaborator

folliwing installation instruction on multibeam sonar document page will do

@woensug-choi
Copy link
Collaborator

@Evintjh Any updates?

@aimas-lund
Copy link

aimas-lund commented Feb 27, 2024

@Evintjh upgrading from Nvidia Driver 535, CUDA 12.2 to Driver 545, CUDA 12.3 seemed to solve this issue for me.
Notably my host OS is Ubuntu 22.04.4 LTE, should it be relevant.

@zxylov
Copy link

zxylov commented Mar 21, 2024

@woensug-choi I have followed installation instruction on multibeam sonar document page to configure docker ,but the version of cuda is 12.4,how to change the version to 12.3, or the version of 12.4 can also accept the image ?

@akgoins
Copy link

akgoins commented Apr 22, 2024

I had the same problem as others (black image) even with a newer NVidia/Cuda drivers. I tried 535, 545, and 550 with no luck. Turns out the problem was the version of nvcc used to compile the plugin with. In my docker, the debian of nvidia-cuda-toolkit gave nvcc version 11.5 but when I manually installed Cuda toolkitt 12.0 and rebuilt the plugin, the sonar images started working for me again.

@Aaronl6
Copy link

Aaronl6 commented Jul 8, 2024

@akgoins thank you very much. Solved the problem following your advice. Rebuild is important

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

8 participants