Gazebo | Ignition | Community
Ask Your Question

Wojciech's profile - activity

2016-06-20 04:12:18 -0500 received badge  Famous Question (source)
2016-04-25 06:41:43 -0500 received badge  Notable Question (source)
2016-04-08 12:18:03 -0500 received badge  Popular Question (source)
2016-04-07 13:06:58 -0500 asked a question No joints are being published in /joint_states topic

Hello,

I have a problem (in my opinion) with joint_state_controller. My configuration file is as follows:

elektron_control.yaml:

elektron:
  joint_state_controller:
    type: joint_state_controller/JointStateController
    publish_rate: 50

request of the following service:

rosservice call /gazebo/get_model_properties "model_name: 'elektron'"

returns:

parent_model_name: ''
canonical_body_name: ''
body_names: ['base_link', 'base_link_left_front_wheel_link', 'base_link_left_rear_wheel_link', 'base_link_left_wheel_link', 'base_link_right_front_wheel_link', 'base_link_right_rear_wheel_link', 'base_link_right_wheel_link']
geom_names: ['base_link_collision', 'base_link_collision_base_link_1', 'base_link_left_front_wheel_link_collision', 'base_link_left_rear_wheel_link_collision', 'base_link_left_wheel_link_collision', 'base_link_right_front_wheel_link_collision', 'base_link_right_rear_wheel_link_collision', 'base_link_right_wheel_link_collision']
joint_names: ['base_link_left_front_wheel_joint', 'base_link_left_rear_wheel_joint', 'base_link_left_wheel_joint', 'base_link_right_front_wheel_joint', 'base_link_right_rear_wheel_joint', 'base_link_right_wheel_joint']
child_model_names: []
is_static: False
success: True
status_message: GetModelProperties: got properties

request of a single joint properties:

rosservice call /gazebo/get_joint_properties "joint_name: 'base_link_left_wheel_joint'"

returns:

type: 0
damping: []
position: [1.781694179303628e-05]
rate: [2.6227222368309366e-08]
success: True
status_message: GetJointProperties: got properties

echo of the /elektron/joint_states returns:

---
header: 
  seq: 845
  stamp: 
    secs: 45
    nsecs: 269000000
  frame_id: ''
name: []
position: []
velocity: []
effort: []
---
header: 
  seq: 846
  stamp: 
    secs: 45
    nsecs: 289000000
  frame_id: ''
name: []
position: []
velocity: []
effort: []
---

It seams like the joint_state_controller somehow cannot publish known properties of known joints. Did anyone meet similar issue? I use ROS Jade release and compiled from source gazebo_ros_pkg package.

2014-01-28 12:26:44 -0500 received badge  Famous Question (source)
2013-10-29 15:58:02 -0500 received badge  Notable Question (source)
2013-10-01 01:47:50 -0500 answered a question Spawning URDF in Hydro, Gazebo 1.9 has (core dumped) issue

Try:

killall gzserver

then:

LANG="C"

In the end it worked.

2013-09-27 02:27:15 -0500 received badge  Popular Question (source)
2013-09-25 21:40:35 -0500 received badge  Student (source)
2013-09-25 18:04:20 -0500 commented answer Spawning URDF in Hydro, Gazebo 1.9 has (core dumped) issue

I have the same problem, I tried to reinstall but it did not help.

2013-09-25 17:26:00 -0500 received badge  Editor (source)
2013-09-23 20:00:19 -0500 asked a question roslaunch rrbot_gazebo rrbot_world.launch & rrbot_description rrbot_rviz.launch

Hi,

I tried to plugin camera sensor form tutorial: http://gazebosim.org/wiki/Tutorials/1.9/ROSMotorandSensorPlugins

After launching rviz:

roslaunch rrbot_description rrbot_rviz.launch

I get(in gazebo terminal):

[gazebo-1] process has died [pid 6887, exit code 139, cmd /home/wojciech/catkinws/src/gazeborospkgs/gazeboros/scripts/gzserver /home/wojciech/catkinws/src/gazeborosdemos/rrbotgazebo/worlds/rrbot.world _name:=gazebo _log:=/home/wojciech/.ros/log/dc769250-24b1-11e3-ae77-78e400c426ae/gazebo-1.log]. log file: /home/wojciech/.ros/log/dc769250-24b1-11e3-ae77-78e400c426ae/gazebo-1*.log

If anyone knows or has any ideas what's wrong, please feel free to suggest. Many thanks!

log file end:

[roslaunch][INFO] 2013-09-26 00:19:58,035: [gazebo_gui-2] process has finished cleanly
log file: /home/wojciech/.ros/log/f96e53ce-262e-11e3-ae7c-78e400c426ae/gazebo_gui-2*.log
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,035: ProcessMonitor.unregister[gazebo_gui-2] starting
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,036: ProcessMonitor.unregister[gazebo_gui-2] complete
[roslaunch][INFO] 2013-09-26 00:19:58,036: all processes on machine have died, roslaunch will exit
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,136: ProcessMonitor._post_run <ProcessMonitor(ProcessMonitor-1, started daemon 140267168605952)>
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,137: ProcessMonitor._post_run <ProcessMonitor(ProcessMonitor-1, started daemon 140267168605952)>: remaining procs are []
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,139: ProcessMonitor exit: cleaning up data structures and signals
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,140: ProcessMonitor exit: pmon has shutdown
[roslaunch][INFO] 2013-09-26 00:19:58,185: process monitor is done spinning, initiating full shutdown
[roslaunch][INFO] 2013-09-26 00:19:58,186: runner.stop()
[roslaunch][INFO] 2013-09-26 00:19:58,186: shutting down processing monitor...
[roslaunch][INFO] 2013-09-26 00:19:58,186: shutting down processing monitor <ProcessMonitor(ProcessMonitor-1, stopped daemon 140267168605952)>
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,186: ProcessMonitor.shutdown <ProcessMonitor(ProcessMonitor-1, stopped daemon 140267168605952)>
[roslaunch][INFO] 2013-09-26 00:19:58,186: ... shutting down processing monitor complete
[roslaunch][INFO] 2013-09-26 00:19:58,186: done
[roslaunch.pmon][INFO] 2013-09-26 00:19:58,187: ProcessMonitor.shutdown <ProcessMonitor(ProcessMonitor-1, stopped daemon 140267168605952)>
[rospy.core][INFO] 2013-09-26 00:19:58,187: signal_shutdown [atexit]

Best, Wojciech