xsol-taylor's profile - activity

Thanks - agreed, this is the approach we are going with, sampling the 200hz for the pointcloud, using CUDA to do the in

Sure I'll provide a little more context - we're transforming a pointcloud, 65k points, with a sensor that is giving us o

Sure I'll provide a little more context - we're transforming a pointcloud, 65k points, with a sensor that is giving us o

Optimal way to gather many transforms I need to collect transforms at a certain interval from time N to N + S, to use th

I am trying to fuse odometry from navsat_transform and an IMU using an ekf_localization_node, the orientation is working, but it is constantly stuck at 0, 0, 0.

The output of the odometry is broadcasting sensible output (which I can confirm by mapping it independently in RVIZ too):

I've turned on the debugging output file and when I open it I observe the following:

Subscribed to /odometry/gps (odom0)
    odom0_differential is false
    odom0_pose_rejection_threshold is 1.7977e+308
    odom0_twist_rejection_threshold is 1.7977e+308
    odom0_queue_size is 10
    odom0 pose update vector is [t  t  t  f  f  f  f  f  f  f  f  f  f  f  f  ]
    odom0 twist update vector is [f  f  f  f  f  f  f  f  f  f  f  f  f  f  f  ]
Subscribed to /os1_cloud_node/imu/fixed (imu0)
    imu0_differential is false
    imu0_pose_rejection_threshold is 1.7977e+308
    imu0_twist_rejection_threshold is 1.7977e+308
    imu0_linear_acceleration_rejection_threshold is 1.7977e+308
    imu0_remove_gravitational_acceleration is true
    imu0_queue_size is 10
        ///etc

What is strange is that there are thousands of mentions of the imu0 callback being activated, but past these lines odom0 is never mentioned again, in relation to anything.

So the callback for odom0 is never being called. is base_link.However I leave this node running and echo /odometry/gps and plenty of data comes out as shown previously.

Any idea why this is? Using ROS Melodic and the frame_id for /odometry/gps.

Thanks

Thanks for following up - our bag file timestamps were severely inaccurate (LIDAR stamps were seconds from device bootup

robot_localization not receiving odometer data despite listening I am trying to fuse odometry from navsat_transform and