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

Lidar cannot publish /cloud topic #1065

Open
jiaminguo1995 opened this issue Dec 11, 2024 · 4 comments
Open

Lidar cannot publish /cloud topic #1065

jiaminguo1995 opened this issue Dec 11, 2024 · 4 comments

Comments

@jiaminguo1995
Copy link

I try to get the pointcloud. But the Lidar seems not work, the topic of the pointcloud did not be published. I check the log and did not found the error related to this issue.

Here are two logs I guess may be related to this issue, but I am not sure.
Error Code 13 Msg: Directory doesn't exist[/home/jamie/.ignition/fuel/fuel.gazebosim.org/openrobotics/models/artifact proximity detector/tip]
WARNING: no messages received and simulated time is active.
Is /clock being published?

@peci1
Copy link
Collaborator

peci1 commented Dec 11, 2024

Please, share more details about what and how you are trying to do.

Your OS, how you launch subt, how you test the pointcloud topic. Also, post the output of the following script from the same console where you test the topic subscription:

rosparam get /use_sim_time
echo $IGN_TRANSPORT_TOPIC_STATISTICS
echo $IGN_PARTITION
echo $ROS_MASTER_URI

@jiaminguo1995
Copy link
Author

Please, share more details about what and how you are trying to do.

Your OS, how you launch subt, how you test the pointcloud topic. Also, post the output of the following script from the same console where you test the topic subscription:

rosparam get /use_sim_time
echo $IGN_TRANSPORT_TOPIC_STATISTICS
echo $IGN_PARTITION
echo $ROS_MASTER_URI

Thank you for your help. I am so sorry that I reply late, because I have many examinations these days. I want to test the algorithm fast_lio in the underground environment. The first step is to subscribe the point cloud and the IMU information of subt. And then I found that the point cloud was not be published. I tried 2 robots and they have the seem problem. So I guess it may caused by the sensors. The order I tried were as follows:

  1. LC_ALL=C ign launch -v 4 ~/subt_ws/src/subt/submitted_models/explorer_spot_sensor_config_1/launch/example.ign robotName:=X1 ros:=true champ:=true

  2. ign launch -v 4 competition.ign worldName:=tunnel_circuit_practice_01 circuit:=tunnel robotName1:=X1 robotConfig1:=X1_SENSOR_CONFIG_1 levels:=false

——————————————————————————————————————————————————————

The outputs of the orders are as follows:

jamie@jamie:$ rosparam get /use_sim_time
true
jamie@jamie:
$ echo $IGN_TRANSPORT_TOPIC_STATISTICS

jamie@jamie:~$ echo $IGN_PARTITION

jamie@jamie:~$ echo $ROS_MASTER_URI
http://localhost:11311

order 2 and order 3 return nothing.

@jiaminguo1995
Copy link
Author

@peci1 Hello, and sorry to bother you! I followed your suggestions and input the instructions, and I shared the related output about two months ago. Would you have a chance to take a look when you’re free? Let me know if you need anything else from my side! Thanks!

@peci1
Copy link
Collaborator

peci1 commented Mar 10, 2025

Hi, I'm sorry, I also got totally swamped lately :)

There may still be many reasons why you don't see the output.

Which topics do you subscribe?

Please, post the output of rostopic list and rostopic info <your scan topic> .

Also, let's have a look at the Ignition topics. Please, do export IGN_TRANSPORT_TOPIC_STATISTICS=1 in a console and then ign topic -l. Try to find the scan topics and echo them with ign topic -e -t <topic>. Do you get some output?

Next, it would be great if you could share the whole startup log of the simulator (competition.ign).

Last thing to check, please find a log file ogre2.log inside ~/.ignition and share it.

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

2 participants