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

Nothing happens #19

Open
esh64 opened this issue Nov 27, 2023 · 1 comment
Open

Nothing happens #19

esh64 opened this issue Nov 27, 2023 · 1 comment

Comments

@esh64
Copy link

esh64 commented Nov 27, 2023

Hello I'm a beginner with ROS and Gazebo. I'm using ROS Noetic and gazebo 11.11.0 in a docker container and when I run this command: roslaunch velo2cam_gazebo mono_mono_p1_s3_real.launch nothing happens and get stuck. This is the output of the mentioned command.

... logging to /root/.ros/log/7a8414ac-8d5e-11ee-8fa5-dc215cf5e731/roslaunch-Koumakan-63.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://Koumakan:37851/

SUMMARY

PARAMETERS

  • /gazebo/enable_ros_network: True
  • /rosdistro: noetic
  • /rosversion: 1.16.0
  • /sensor2: <?xml version="1....
  • /sensors: <?xml version="1....
  • /target: <?xml version="1....
  • /use_sim_time: True

NODES
/
gazebo (gazebo_ros/gzserver)
spawn_sensor_model (gazebo_ros/spawn_model)
spawn_sensor_model2 (gazebo_ros/spawn_model)
spawn_target_model (gazebo_ros/spawn_model)

auto-starting new master
process[master]: started with pid [77]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 7a8414ac-8d5e-11ee-8fa5-dc215cf5e731
process[rosout-1]: started with pid [87]
started core service [/rosout]
process[gazebo-2]: started with pid [94]
process[spawn_target_model-3]: started with pid [98]
process[spawn_sensor_model-4]: started with pid [100]
process[spawn_sensor_model2-5]: started with pid [101]
INFO: cannot create a symlink to latest log directory: [Errno 17] File exists: '/root/.ros/log/7a8414ac-8d5e-11ee-8fa5-dc215cf5e731' -> '/root/.ros/log/latest'
[INFO] [1701114743.554870, 0.000000]: Loading model XML from ros parameter target
[INFO] [1701114743.557055, 0.000000]: Loading model XML from ros parameter sensors
[INFO] [1701114743.557574, 0.000000]: Loading model XML from ros parameter sensor2
[INFO] [1701114743.558239, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[INFO] [1701114743.561032, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
[INFO] [1701114743.561567, 0.000000]: Waiting for service /gazebo/spawn_urdf_model
Gazebo multi-robot simulator, version 11.11.0
Copyright (C) 2012 Open Source Robotics Foundation.
Released under the Apache 2 License.
http://gazebosim.org

[ INFO] [1701114743.731663605]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1701114743.733016483]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 192.168.0.6
[Msg] Loading world file [/catkin_ws/src/velo2cam_gazebo/velo2cam_gazebo/worlds/calibration_scene.world]
[ INFO] [1701114744.184739415]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1701114744.199140631, 12498.766000000]: Physics dynamic reconfigure ready.
[INFO] [1701114744.465051, 12499.027000]: Calling service /gazebo/spawn_urdf_model
[INFO] [1701114744.466367, 12499.028000]: Calling service /gazebo/spawn_urdf_model
[INFO] [1701114744.466773, 12499.028000]: Calling service /gazebo/spawn_urdf_model
[INFO] [1701114744.598249, 12499.120000]: Spawn status: SpawnModel: Successfully spawned entity
[INFO] [1701114744.824690, 12499.321000]: Spawn status: SpawnModel: Successfully spawned entity
[INFO] [1701114745.048125, 12499.522000]: Spawn status: SpawnModel: Successfully spawned entity
[spawn_target_model-3] process has finished cleanly
log file: /root/.ros/log/7a8414ac-8d5e-11ee-8fa5-dc215cf5e731/spawn_target_model-3*.log
[spawn_sensor_model-4] process has finished cleanly
log file: /root/.ros/log/7a8414ac-8d5e-11ee-8fa5-dc215cf5e731/spawn_sensor_model-4*.log
[spawn_sensor_model2-5] process has finished cleanly
log file: /root/.ros/log/7a8414ac-8d5e-11ee-8fa5-dc215cf5e731/spawn_sensor_model2-5*.log

Is this the expected output? Should something else happens? How should I get the calibration results?

@tdcsu
Copy link

tdcsu commented Jun 15, 2024

Hi, I was confused with the same questions, have you found how to solve it?
BS
Di Tian

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