ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Robotnik's profile - activity

2016-02-03 01:57:33 -0500 received badge  Good Question (source)
2015-12-07 11:40:56 -0500 answered a question Problems with 2 Dynamixels MX-28 over USB2Dynamixel

I have solved it by changing the return-delay param

~/catkin_ws/src/dynamixel_motor/dynamixel_driver/scripts$ python set_servo_config.py --port=/dev/ttyUSB1 --baud=57600 --return-delay=4 1 {'baud': 57600, 'return_delay': 4, 'max_voltage_limit': None, 'min_voltage_limit': None, 'baud_rate': None, 'ccw_angle_limit': None, 'cw_angle_limit': None, 'port': '/dev/ttyUSB1'} Configuring Dynamixel motor with ID 1 Setting return delay time to 8 us done

2015-03-12 03:24:53 -0500 received badge  Famous Question (source)
2014-10-25 23:02:02 -0500 received badge  Popular Question (source)
2014-10-25 23:02:02 -0500 received badge  Notable Question (source)
2014-02-19 13:29:56 -0500 received badge  Famous Question (source)
2014-02-19 13:29:56 -0500 received badge  Popular Question (source)
2014-02-19 13:29:56 -0500 received badge  Notable Question (source)
2013-10-17 01:12:31 -0500 answered a question planning scene collision distance

Solved. The problem was related with the collision matrix generated from the setup_assistant. Just manually disabling some additional joints on the SRDF file, the following code does work:

 // Collision check
  robot_state::RobotState& current_state = planning_scene_ptr_->getCurrentStateNonConst();
  current_state = *kinematic_state_;
  collision_detection::CollisionRequest collision_request;
  collision_detection::CollisionResult collision_result;
  collision_request.group_name = "arm_tcp";  
  collision_request.distance = true;
  collision_result.clear();
  planning_scene_ptr_->checkSelfCollision(collision_request, collision_result, current_state);
  if (collision_result.collision) ROS_ERROR("Robot in SELF-COLLISION");
  ROS_INFO("Collision result %5.10f", collision_result.distance);
2013-10-16 07:30:04 -0500 received badge  Editor (source)
2013-10-16 07:29:14 -0500 asked a question planning scene collision distance

Hi,

I am using Groovy with Ubuntu 12.04.

I am trying to call the planning_planning_scene::PlanningScene::distanceToCollision functions, but the returned value is always a constant huge number. The call to selfCollisionCheck does work perfectly.

... // Collision check

robot_state::RobotState& current_state = planning_scene_ptr_->getCurrentStateNonConst(); current_state = *kinematic_state_; collision_detection::CollisionRequest collision_request; collision_detection::CollisionResult collision_result; collision_request.group_name = "arm_tcp";
collision_result.clear(); planning_scene_ptr_->checkSelfCollision(collision_request, collision_result, current_state); if (collision_result.collision) ROS_ERROR("Robot in SELF-COLLISION");

double distance_to_collision = planning_scene_ptr_->distanceToCollision( current_state);

...

a working example measuring the distance to the nearest collision would be much appreciated.

Thanks and best regards,

Roberto

2013-09-10 05:22:30 -0500 commented question segmentation fault error in Rviz 1.10.6 with Hardy ...

I get the same fault after rviz starts, but when pressing the Display->Add button.

2013-03-17 11:43:43 -0500 commented question Gazebo stuck waiting for Master in Groovy

Hi, I have the same problem. Did you solve it?

2013-01-15 11:42:24 -0500 received badge  Famous Question (source)
2012-11-16 01:17:02 -0500 answered a question summit hokuyo data

Hi,

yes, you just need to modify the height of the laser link

<joint name="hokuyo_laser_joint" type="fixed"> <axis xyz="0 1 0"/> <origin xyz="0.226 0 0.120"/>
<parent link="base_link"/> <child link="hokuyo_laser_link"/> </joint>

2012-09-25 14:16:16 -0500 received badge  Notable Question (source)
2012-09-24 20:51:33 -0500 commented question Fuerte - gazebo - can't see laser rays

"it works" means that I am able to see the measurements in rviz, so the data is being published correctly. "any more" means that I was able to see the rays in the ROS electric version.

2012-09-24 15:16:27 -0500 answered a question Fuerte - gazebo - can't see laser rays

'it works' means that the laser is measuring correctly, as I can see in rviz. So the messages are published correctly. 'any more' means that the laser rays were visible in electric but not in fuerte.

2012-09-18 12:02:49 -0500 received badge  Popular Question (source)
2012-09-16 23:42:50 -0500 asked a question Fuerte - gazebo - can't see laser rays

Hi,

I am spawning urdf robot models in gazebo that include laser rangers, and it works (the sensor is working), but the laser rays are not displayed any more.

Any idea?

Roberto

2012-09-11 21:55:37 -0500 received badge  Notable Question (source)
2012-09-11 21:55:37 -0500 received badge  Famous Question (source)
2012-07-19 23:17:59 -0500 received badge  Popular Question (source)
2012-01-11 03:00:47 -0500 commented answer move_base - moving backwards
You are right, thanks.
2012-01-11 02:39:34 -0500 received badge  Nice Question (source)
2012-01-11 01:49:58 -0500 commented answer move_base - moving backwards
Hi, thank you, I will test this right now. I have just realized that the path published by /move_base_node/SBPLLatticePlanner/plan is the sequence of poses, but without orientation information (just x,y fields are used), so it might be hard for the planner to decide where to move forward and backward...
2012-01-10 23:11:25 -0500 received badge  Student (source)
2012-01-10 22:37:10 -0500 commented answer move_base - moving backwards
Thanks for the response and the testing. I tried with "dwa: true" and false of the base_local_planner but both generate only forward motion...
2012-01-10 19:33:35 -0500 asked a question move_base - moving backwards

Is there a way to configure move_base to follow paths forward and backward?

I have been able to create paths composed of forward and backward segments with SBPL, but move_base tries always to complete the path rotating and moving forward.

Thanks,

Robert

2011-12-31 12:48:41 -0500 marked best answer rviz error wxWidgets couldn't load a png image

We had exactly the same error message. Deleting the entire .rviz directory in the home directory fixed the problem for us.

2011-09-25 11:26:52 -0500 asked a question rviz error wxWidgets couldn't load a png image

Hi everybody,

I am trying to run rviz and get this response. I have upgraded libpng, but with no result:

trurl@trurl:/opt/ros/electric/stacks/visualization/rviz$ rosrun rviz rviz
[ INFO] [1316992589.920372061]: rviz revision number 1.6.4
[ INFO] [1316992589.920459084]: ogre_tools revision number 1.6.2
[ INFO] [1316992589.920486881]: compiled against OGRE version 1.7.3 (Cthugha)
[ INFO] [1316992589.969539903]: Loading general config from [/home/trurl/.rviz/config]
[ INFO] [1316992589.969961674]: Loading display config from [/home/trurl/.rviz/display_config]

[ WARN] [1316992589.973563250]: wxWidgets Warning [Application was compiled with png.h from libpng-1.2.42]

[ WARN] [1316992589.973616050]: wxWidgets Warning [Application  is  running with png.c from libpng-1.4.3]

[ WARN] [1316992589.973658653]: wxWidgets Warning [Incompatible libpng version in application and library]

[ERROR] [1316992589.973709637]: wxWidgets Error [Couldn't load a PNG image - file is corrupted or not enough memory.]

Best Regards,

Robert