Gazebo | Ignition | Community
Ask Your Question

yah130s's profile - activity

2021-11-08 03:52:59 -0600 received badge  Popular Question (source)
2021-10-08 21:41:08 -0600 received badge  Notable Question (source)
2021-10-08 21:41:08 -0600 received badge  Popular Question (source)
2021-09-29 05:13:52 -0600 asked a question robot not moving by ign topic in Fortress tutorial

robot not moving by ign topic in Fortress tutorial Issue Robot doesn't move when it's supposed to. I'm on Fortress tut

2021-09-27 23:52:31 -0600 edited question Unable to call parseURDF on robot model

Unable to call parseURDF on robot model Hi, I'm new to gazebo. Just installed whole software on Ubuntu14 with this one-

2021-01-12 12:48:16 -0600 answered a question Email notification may not be coming through

I guess I've actually received emails. My guess is that I thought I hadn't receive emails maybe because I received too f

2021-01-07 00:33:00 -0600 commented answer How to use for loop in launch file in gazebo?

Years passed, the link https://bitbucket.org/osrf/gazebo_models/src/e024fe922c810f468e2a7ab277750354465478cd/cart_front_

2021-01-07 00:30:40 -0600 received badge  Associate Editor (source)
2021-01-07 00:30:40 -0600 edited question How to use for loop in launch file in gazebo?

How to use for loop in launch file in gazebo? How can implement for loop concept in gazebo to spawn multiple robot model

2020-12-11 15:29:39 -0600 asked a question Email notification may not be coming through

Email notification may not be coming through I've noticed I don't have any emails sent from https://community.gazebosim.

2020-11-05 07:48:25 -0600 received badge  Taxonomist
2020-10-12 09:31:45 -0600 commented question ARIAC conveyor belt in other projects?

I'm also very interested in utilizing conveyor belt from ARIAC pkgs. That said, you might get better responses by asking

2020-10-12 09:26:15 -0600 edited question No image topic published on ROS1 (Dome ROS1 integration tutorial)

No image topic published on ROS1 (Dome ROS1 integration tutorial) Running dome/ros_integration and I do not see a camera

2020-10-12 09:25:22 -0600 asked a question No image topic published on ROS1 (Dome ROS1 integration tutorial)

No image topic published on ROS1 (Dome ROS1 integration tutorial) Running dome/ros_integration and I do not see a camera

2020-10-07 13:39:01 -0600 commented question Robot keeps "floating" using Planar Move plugin

@Pranshu Sorry I wasn't aware those 2 videos were not public. I set them to be unlisted so by clicking the link you shou

2019-04-06 15:06:25 -0600 commented answer Gazebo 7.0.0 crash on heightmap insertion

Actually it might not even be necessary to go that far, I was able to insert heightmaps using Gazebo 7.7. All you need a

2019-04-06 14:39:48 -0600 received badge  Critic (source)
2018-12-03 14:47:39 -0600 received badge  Commentator
2018-12-03 14:47:39 -0600 commented question How and Why (ode|bullet|dart|simbody) for Physics Engine. Why not Physx?

SDK3.4 will be opensourced https://news.developer.nvidia.com/announcing-physx-sdk-4-0-an-open-source-physics-engine/

2018-09-11 17:16:09 -0600 received badge  Famous Question (source)
2017-07-29 12:16:13 -0600 commented question Unable to find compiled ros-pkgs for Indigo and Gazebo 7

Cross posted on ros.org.

2017-07-24 05:09:34 -0600 received badge  Famous Question (source)
2017-06-19 07:52:21 -0600 received badge  Famous Question (source)
2017-05-17 18:22:06 -0600 commented question Set near/far clip distance for the visualization window camera

@Illuminatur please don't try hijacking the thread, instead open a new question :)

2017-05-17 10:26:06 -0600 edited answer Defining a Stereo Camera in URDF for usage in Gazebo Simulations

You're defining physical parameters, but you also need to write plugin to "mock" your own sensor output values, or use e

2017-05-17 10:24:49 -0600 answered a question Defining a Stereo Camera in URDF for usage in Gazebo Simulations

You're defining physical parameters, but you also need to write plugin to "mock" your sensor output values.

2017-04-29 02:31:48 -0600 edited answer Launching openni directly bound ROS packages in Gazebo

Spawn a model that implements Openni Kinect ROS plugin, which publishes the topics defined in the associated SDF. Then y

2017-04-28 21:42:05 -0600 answered a question Launching openni directly bound ROS packages in Gazebo

Spawn a model that implements Openni Kinect ROS pluging, which starts publishing the topics defined in the associated SD

2017-02-21 09:41:17 -0600 received badge  Civic Duty (source)
2017-02-09 18:50:38 -0600 edited answer How to include QR in gazebo

Hi, If you want I created python scripts to automatically generate AR tags models in gazebo. This might save you some time : https://github.com/keulYSMB/gazebo_mo...

Method used: texture square in blender and generate sdf files accordingly.

Hope this helps,

2016-11-11 06:10:20 -0600 received badge  Notable Question (source)
2016-11-08 23:50:14 -0600 received badge  Popular Question (source)
2016-11-08 10:48:53 -0600 received badge  Student (source)
2016-11-07 22:42:27 -0600 asked a question A model in a merged PR missing in the database

Some human models were merged more than an year ago, but today I don't see person_{standing, walking}models on http://models.gazebosim.org. I see e.g. person_standing in source forlder. A few other people sitting next to me are seeing the same and on their Gazebo 2.2.3 on Ubuntu Trusty it's not available even though they have a bunch of other models loaded. Any idea's appreciated.

2016-10-13 16:28:53 -0600 received badge  Notable Question (source)
2016-10-11 11:53:43 -0600 received badge  Popular Question (source)
2016-10-07 13:13:32 -0600 asked a question "no namespace found" error meaning

In quite a few question threads (eg. 1, 2, 3) I can see the error a set of lines in the output:

Warning [gazebo.cc:215] Waited 1seconds for namespaces.
Error [Node.cc:90] No namespace found

What do these mean? Especially how do users use "No namespace found" info?

2016-09-12 21:14:58 -0600 edited question Controller Spawner couldn't reach controller_manager to take down controllers

When I Tried this tutorial http://gazebosim.org/tutorials?tut=ro..., the result output of the rrbot_control.launch terminal was always as follows:

[INFO] [WallTime: 1431386440.414532] [0.000000] Controller Spawner: Waiting for service controller_manager/load_controller
[INFO] [WallTime: 1431386440.421600] [0.000000] Controller Spawner: Waiting for service controller_manager/switch_controller
[INFO] [WallTime: 1431386440.427941] [0.000000] Controller Spawner: Waiting for service controller_manager/unload_controller
[INFO] [WallTime: 1431386440.436520] [0.000000] Loading controller: joint_state_controller
[INFO] [WallTime: 1431386441.193234] [20.148000] Loading controller: joint1_position_controller
[INFO] [WallTime: 1431386441.691031] [20.635000] Loading controller: joint2_position_controller
[INFO] [WallTime: 1431386441.803746] [20.722000] Controller Spawner: Loaded controllers: joint_state_controller, joint1_position_controller, joint2_position_controller
Traceback (most recent call last):
  File "/home/comex/catkin_ws/src/ros_control/controller_manager/scripts/spawner", line 212, in <module>
    if __name__ == '__main__': main()
  File "/home/comex/catkin_ws/src/ros_control/controller_manager/scripts/spawner", line 204, in main
    resp = switch_controller(loaded, [], 2)
  File "/opt/ros/indigo/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/indigo/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 525, in call
    raise ServiceException("transport error completing service call: %s"%(str(e)))
rospy.service.ServiceException: transport error completing service call: unable to receive data from sender, check sender's logs for details
[INFO] [WallTime: 1431386459.030696] [20.728000] Shutting down spawner. Stopping and unloading controllers...
[WARN] [WallTime: 1431386490.032891] [20.728000] Controller Spawner couldn't reach controller_manager to take down controllers. Waited for 30 second(s).

I couldn't figure out why this always happen. I use Ubuntu 14.04 and gazebo 2.2.3 with ROS Indigo.Can someone help?

2016-07-23 18:05:49 -0600 commented answer gazebo_gui-3 error when starting gazebo with roslaunch

+1 for raising attention to those 2 options. I still have the same question as the one I made at [this post](http://answers.gazebosim.org/question/4153/gazebo-crashes-immediately-using-roslaunch-after-installing-gazebo-ros-packages/?answer=12620#post-id-12620).

2016-07-23 17:57:03 -0600 edited answer gazebo_gui-3 error when starting gazebo with roslaunch

The problem is that roslaunch secretly adds two arguments when starting a node's executable: __name and __log. If the node's executable is not ROS interoperable, then the executable may fail because it doesn't know how to handle the __name and __log arguments that were added on by roslaunch. This is the case here, since roslaunch is calling the "gzclient" script, which executes "gzclient" with arguments passed in by roslaunch. gzclient dies because it doesn't know how to handle the __name and __log arguments passed in from roslaunch.

The workaround you found works because it uses rosrun to start the gzclient instead of roslaunch. rosrun doesn't add those pesky "__name" and "__log" parameters.

2016-07-23 17:53:08 -0600 commented answer gazebo crashes immediately using roslaunch after installing gazebo ros packages

Your explanation sounds like that Gazebo processes should always die when they are called from `roslaunch`? There are number of successful .launch files out there so I think that's not the case.

2016-07-23 17:46:34 -0600 edited question gazebo crashes immediately using roslaunch after installing gazebo ros packages

Hello,

after installing everything properly I am following the tutorials to test the tools (using groovy, gazebo 1.9 and gazebo_ros_pkgs). I have a problem using roslaunch to start gazebo following this tutorial

http://gazebosim.org/wiki/Tutorials/1...

when I want to start with command roslaunch gazebo_ros willowgarage_world.launch gazebo crashes after one sec and I get this error:

[gazebo_gui-3] process has died [pid 15649, exit code 139, cmd /home/usr/catkin_ws/src/gazebo_ros_pkgs/gazebo_ros/scripts/gzclient __name:=gazebo_gui __log:=/home/shahed/.ros/log/8981441a-03ea-11e3-8d2b-0017c4a8146b/gazebo_gui-3.log].
log file: /home/usr/.ros/log/8981441a-03ea-11e3-8d2b-0017c4a8146b/gazebo_gui-3*.log

this problem happens with all world files( mud_world.launch, shapes_world.launch, rubble_world.launch), except the empty and willowgarage_world, both of them can be started using roslaunch tool but not always from the first attempt. Mostly from the second try.

I also followed “Creating a Custom World File” in the same tutorial and still the same problem occurred.

Any help plz!

Thanks in advance.

2016-07-23 17:41:11 -0600 commented answer gazebo crashes immediately using roslaunch after installing gazebo ros packages

Minor correction; `__name` and `__log`, I guess double underscore instead of single.

2016-07-23 17:26:56 -0600 edited question gazebo_gui-3 error when starting gazebo with roslaunch

Hey

I have this problem that's happening more often the whole last week when starting gazebo using roslaunch, I haven't installed any updates though. Is there any permanent solution for it because it so annoying not to start gazebo right away and it works only after 5 to 6 times attempts

The system: gazebo 1.9.1, groovy, gazebo_ros_package

Segmentation fault (core dumped)
[gazebo_gui-3] process has died [pid 16577, exit code 139, cmd /home/zahraa/catkin_ws/src/gazebo_ros_pkgs/gazebo_ros/scripts/gzclient __name:=gazebo_gui __log:=/home/zahraa/.ros/log/4139ed3a-13e2-11e3-9765-6c626d02622d/gazebo_gui-3.log].
log file: /home/zahraa/.ros/log/4139ed3a-13e2-11e3-9765-6c626d02622d/gazebo_gui-3*.log

I tried to find the error by going to 4139ed3a-13e2-11e3-9765-6c626d02622d but this directory doesn't not have gazebo_gui-3*.log file and it has other log files such as spawn_urdf.log and master.log etc..

thanks in advance!