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

tseco's profile - activity

2022-06-01 04:55:36 -0500 received badge  Popular Question (source)
2022-05-31 03:07:25 -0500 asked a question move base melodic distribution compilation type?

move base melodic distribution compilation type? Hi everyone, I would like to know if the move_base version installed i

2021-09-28 07:23:39 -0500 received badge  Famous Question (source)
2020-12-27 07:19:20 -0500 received badge  Notable Question (source)
2020-07-03 01:30:42 -0500 received badge  Popular Question (source)
2020-06-19 08:01:42 -0500 asked a question Problems fusing GPS data with AMCL

Problems fusing GPS data with AMCL Hello, We are using robot_localization and a AMCL with a previously recorded map to

2020-06-10 01:58:13 -0500 marked best answer Problem with GPS and robot_localization: map frame

Hello,

We are running two instances of robot_localization node (as recommended) in order to fuse the information provide by an imu, odometry and GPS-RTK (ardusimple). The first instance of robot_localizaiton fuses only relative values using the imu (imu/data) and the odometry data (/odom) and setting world_frame param to odom. The result is /odometry/filtered. The second instance fuses the information that comes from the imu (imu/data), the odometry (/odom) and the odometry from gps (/odometry/gps) obatined using the navsat_transform_node. In this case, world_frame is set to map. So, we obtained the transform from odom to base_link from the first robot_localization node and the transform from map to odom using the second one.

The navsat_tranform_node use the information provided by /odometry/filtered, by the gps (/gps/fix) and the heading provied also with a specific setup of our ardusimple gps-rtk (different from the other imu we use). We have checked that the /odometry/gps provided by this node is correctly oriented and the accuracy in terms of position and orientation is good enough.

These are the main parameters of the relative configuration:

map_frame: map
odom_frame: odom
base_link_frame: base_link
world_frame: odom 

odom0: /odom

odom0_config: [true,  true,  false,
               false, false, true,
               true, true, false,
               false, false, false,
               false, false, false]
odom0_queue_size: 2
odom0_nodelay: false
odom0_differential: true
odom0_relative: false

imu0: /imu/data
imu0_config: [false, false, false,
              false,  false,  false,
              false, false, false,
              false,  false,  true,
              false,  false,  false]
imu0_nodelay: false
imu0_differential: false
imu0_relative: true
imu0_queue_size: 5
imu0_pose_rejection_threshold: 0.8                 
imu0_twist_rejection_threshold: 0.8                
imu0_linear_acceleration_rejection_threshold: 0.8  
imu0_remove_gravitational_acceleration: true

The params used for the other robot_localizacion instance are:

map_frame: map              
odom_frame: odom            
base_link_frame: base_link 
world_frame: map           

odom0: /odom
odom0_config: [false,  false,  false,
               false, false, false,
               true, true, false,
               false, false, false,
               false, false, false]
odom0_queue_size: 10
odom0_nodelay: false
odom0_differential: true
odom0_relative: false  

#  Odometry that comes from gps data (navsat_transform_node)
odom1: /odometry/gps
odom1_config: [true, true, false,
 false, false, false,
 false, false, false,
 false, false, false,
 false, false, false]
odom1_differential: false
odom1_relative: false
odom1_queue_size: 10
odom1_pose_rejection_threshold: 5
odom1_twist_rejection_threshold: 1
odom1_nodelay: true

imu0: /imu/data
imu0_config: [false, false, false,
              false,  false,  false,
              false, false, false,
              false,  false,  true,
              false,  false,  false]
imu0_nodelay: false
imu0_differential: false
imu0_relative: true
imu0_queue_size: 10
imu0_pose_rejection_threshold: 0.8                 
imu0_twist_rejection_threshold: 0.8                
imu0_linear_acceleration_rejection_threshold: 0.8  
imu0_remove_gravitational_acceleration: true

Using these configurations, the odom frame is continously jumping with repect to map frame. You can see the effect in the next video:

gps map_odom problem

The issue is observed when the robot starts moving.

Any suggestions?

Thanks in advance

Edit: adding sensor message samples

/odom

header: 
  seq: 403
  stamp: 
    secs: 1583947075
    nsecs: 926265907
  frame_id: "odom"
child_frame_id: "base_link"
pose: 
  pose: 
    position: 
      x: -9.40900611877
      y: 158.370346069
      z: 0.0
    orientation: 
      x: 0.0
      y: 0.0
      z: 0.986108124256
      w: 0.166104823351
  covariance: [100.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 100.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 1000000.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0 ...
(more)
2020-06-10 01:58:13 -0500 received badge  Scholar (source)
2020-06-10 01:58:04 -0500 commented answer Problem with GPS and robot_localization: map frame

Thank you very much Tom. This remap solved one of my issues.

2020-06-01 08:54:34 -0500 received badge  Famous Question (source)
2020-05-13 05:13:48 -0500 commented question Problem with GPS and robot_localization: map frame

Hi Tom, did you have the chance to have a look to the data? Thanks in advance!

2020-05-13 05:13:48 -0500 received badge  Commentator
2020-05-04 07:31:26 -0500 received badge  Notable Question (source)
2020-05-04 06:39:17 -0500 commented question Problem with GPS and robot_localization: map frame

I have just added some samples for the sensors.

2020-05-04 06:38:10 -0500 answered a question Problem with GPS and robot_localization: map frame

/odom: header: seq: 403 stamp: secs: 1583947075 nsecs: 926265907 frame_id: "odom" child_frame_id: "bas

2020-05-04 03:42:28 -0500 commented question Problem with GPS and robot_localization: map frame

I have a 200 M bag, so I am going to reduce it. Apart from that, we are using a node in order to convert the heading dat

2020-05-04 03:24:37 -0500 commented answer robot_localization and navsat_transform_node results

Hi, I have some issues (https://answers.ros.org/question/347395/problem-with-gps-and-robot_localization-map-frame/) with

2020-04-15 01:41:27 -0500 commented question Problem with GPS and robot_localization: map frame

Any suggestions about this issue? Thanks in advance!

2020-04-01 07:12:36 -0500 received badge  Popular Question (source)
2020-03-26 02:30:05 -0500 received badge  Enthusiast
2020-03-24 08:45:14 -0500 asked a question Problem with GPS and robot_localization: map frame

Problem with GPS and robot_localization: map frame Hello, We are running two instances of robot_localization node (as r

2020-03-24 05:40:41 -0500 commented answer robot_localization with GPS map frame won't stay fixed

Hello, We have a similar problem but we can not solve it with your proposal. Did you find the reason it worked changing

2019-02-01 07:39:38 -0500 received badge  Nice Answer (source)
2018-11-11 23:02:31 -0500 received badge  Necromancer (source)
2018-11-11 23:02:31 -0500 received badge  Self-Learner (source)
2018-11-11 23:02:31 -0500 received badge  Teacher (source)
2016-12-01 03:13:31 -0500 answered a question How to cancel a move_base goal using smach SimpleActionState?

Hello! I got a solution, perhaps it is not the best one but it works.

I added a generic state to the smach state machine:

StateMachine.add('CANCEL', CancelGoal(),  transitions={'cancel_outcome':'cancel_aborted'})

The CancelGoal function implemented consits of publishing an empty goal in the /move_base/cancel topic:

class CancelGoal(smach.State):
  def  __init__(self):
    smach.State.__init__(self, outcomes=['cancel_outcome'])
    self.cancel_pub = rospy.Publisher('move_base/cancel', GoalID, queue_size=10)

  def execute(self, userdata):
     setCancelState(True)
     goalId = GoalID()
     self.cancel_pub.publish(goalId)    
     return 'cancel_outcome'

I hope this helps.

Best regards, Teresa

2016-11-30 13:40:02 -0500 received badge  Famous Question (source)
2016-09-19 11:50:21 -0500 commented answer Elevation mapping

Hi, I am using the last version of the elevation packing that Peter updated and it works for me. I had the same problem as you before the update. Are you using the last version?

2016-09-13 14:22:00 -0500 received badge  Famous Question (source)
2016-09-12 11:13:09 -0500 received badge  Notable Question (source)
2016-09-12 11:13:06 -0500 received badge  Popular Question (source)
2016-06-09 04:49:13 -0500 received badge  Notable Question (source)
2016-06-09 03:10:49 -0500 received badge  Student (source)
2016-06-09 02:24:04 -0500 asked a question Elevation mapping

Hello,

I am working with ROS Indigo and Ubuntu 14.04 and I am looking for elavation mapping packages in order to get a elevation map.

I found two packages:

ETH Zurich: https://github.com/ethz-asl/elevation...

Hector: hector_elevation_maping: https://github.com/tu-darmstadt-ros-p...

I have tried the ethz package but I have a core error when I launch the node, and now I am trying the hector elevation mapping package, but I do not find too much documentation about it.

Has anyone any experience working with elevation maps? Any suggestion about the best package to use and any sort of documentation would be grateful.

Thanks in advance,

Teresa

2016-05-13 01:36:14 -0500 received badge  Popular Question (source)
2016-04-29 05:27:54 -0500 asked a question How to cancel a move_base goal using smach SimpleActionState?

Hello,

I am using smach with a SimpleActionState to send navigation goals to move_base with:

StateMachine.add('GO_TO_DOCKING_ZONE',SimpleActionState('move_base',MoveBaseAction, goal_cb = goal_callback, result_cb=goToDocking_result_cb),transitions = {'succeeded':'IR_MONITOR'})

And I would like to cancel this goal. I know that the way to do that is with cancel_goal function, but I do not how to call it using smach.

Any suggestions?

Best regards,

Teresa

2014-04-09 02:53:04 -0500 received badge  Famous Question (source)
2013-09-05 02:09:20 -0500 received badge  Notable Question (source)
2013-08-05 10:41:00 -0500 received badge  Popular Question (source)
2013-07-12 01:29:36 -0500 asked a question Gazebo parse problem with Groovy

Hello,

I have just installed ros-groovy and when I try to run the gazebo example:

roslaunch gazebo_worlds empty_world.launch

there is no problem, but if I try to lauch any of the other examples with:

roslaunch gazebo_worlds office_world.launch

I have some errors:

Msg Waiting for master.Warning [parser.cc:377] SDF has no <sdf> element in
file[/opt/ros/groovy/stacks/simulator_gazebo/gazebo_worlds/worlds/simple_office.world]
Error:   Could not find the 'robot' element in the xml file
         at line 59 in
/tmp/buildd/ros-groovy-urdfdom-0.2.7-0precise-20130326-0224/urdf_parser/src/model.cpp
Error [parser_urdf.cc:1814] Unable to call parseURDF on robot model
Warning [parser.cc:377] SDF has no <sdf> element in file[urdf file]
Error [parser.cc:291] parse as old urdf model file failed.
Error [Server.cc:253] Unable to read sdf
file[/opt/ros/groovy/stacks/simulator_gazebo/gazebo_worlds/worlds/simple_office.world]
Segmentation fault (core dumped)
[gazebo-2] process has died [pid 29155, exit code 139, cmd
/opt/ros/groovy/stacks/simulator_gazebo/gazebo/scripts/gazebo
/opt/ros/groovy/stacks/simulator_gazebo/gazebo_worlds/worlds/simple_office.world
__name:=gazebo
__log:=/home/tseco/.ros/log/a6bdf53c-eae5-11e2-9efd-3cd92b6f7a37/gazebo-2.log].
log file:
/home/tseco/.ros/log/a6bdf53c-eae5-11e2-9efd-3cd92b6f7a37/gazebo-2*.log

Any suggestions?

Best regards,