blaine141's profile - activity

@alperenkeser

The problem is when you republish the image message. Your image message needs to have the timestamp in the header set. C

@alperenkeser Most camera drivers add a timestamp to the camera feed. If I remember correctly I had a node that took in

I recently had this issue and it was because my values in my yaml file were strings rather than numbers. getParam was al

When I run robot_localization in simulation I get the following warning every 2 seconds

[ WARN] [1599417511.143838658, 4.002000000]: Transform from puddles/imu_link to puddles/base_link was unavailable for the time requested. Using latest instead.

While this warning does not cause any immediate issues, I am concerned it means I have poorly implemented tf or simulated time somewhere. This occurs in simulation but I have been unable to test it on our actual system. I have use_sim_time set to true, all of my tf publishers are publishing very frequently, and the only way I can get the warning to go away is to set a transform_timeout in robot_localization, which causes failed to update warnings. The systems I have tested this on have been Ubuntu 18.04 ROS Melodic.

This is an underwater application, so I only have 3 sensors, IMU, depth, and DVL. IMU is the only sensor that has ever been referred to in this warning. Here are some more information about my system.

EKF_localization_node params

frequency: 30
silent_tf_failure: false
two_d_mode: false
transform_time_offset: 0.0
transform_timeout: 0.0
print_diagnostics: true
debug: false
debug_out_file: /path/to/debug/file.txt
publish_tf: true
publish_acceleration: false

imu0: imu/data
imu0_config: [false, false, false,
              true,  true,  true,
              false, false, false,
              true,  true,  true,
              true,  true,  true]
imu0_queue_size: 5
imu0_remove_gravitational_acceleration: true
gravitational_acceleration: 9.81604

twist0: dvl/twist
twist0_config: [false, false, false,
                false, false, false,
                true,  true,  true,
                false, false, false,
                false, false, false]

pose0: depth/pose
pose0_config: [false, false, true,
               false, false, false,
               false, false, false,
               false, false, false,
               false, false, false]

IMU message published at 100 Hz:

header: 
  seq: 1953
  stamp: 
    secs: 19
    nsecs: 716000000
  frame_id: "puddles/imu_link"
orientation: 
  x: 0.0523333914357
  y: -0.35588218556
  z: 0.0330905279149
  w: 0.932477400854
orientation_covariance: [0.0001, 0.0, 0.0, 0.0, 0.0001, 0.0, 0.0, 0.0, 0.0001]
angular_velocity: 
  x: -3.59392461073e-11
  y: 8.47498014701e-12
  z: -2.18380955198e-11
angular_velocity_covariance: [1.1519236000000001e-07, 0.0, 0.0, 0.0, 1.1519236000000001e-07, 0.0, 0.0, 0.0, 1.1519236000000001e-07]
linear_acceleration: 
  x: 6.53786067743
  y: 0.726375271311
  z: 7.26436473382
linear_acceleration_covariance: [1.6e-05, 0.0, 0.0, 0.0, 1.6e-05, 0.0, 0.0, 0.0, 1.6e-05]

If you know anything about what this warning is referring to, how to fix it, or how to suppress it, please let me know

It works. I use revolute joints for the sim in gazebo, make a node that remaps it to a fixed joint, then pass that to th

Ok. I will try to make fixed copies of the joints and map the sensor msgs to the static joint.

Yes, some of my joints are not fixed and they have to be to simulate in gazebo properly.

Yes, some of my joints are not fixed and they have to be to simulate in gazebo properly

https://imgur.com/a/LRyGjDL

I have used static before and it didn't work. I tried it again and the warning kept coming every 2 seconds. I should als

Transform from ____ to ____ was unavailable for the time requested. Using latest instead. When I run robot_localization

Turns out it was because my image topic did not have a timestamp. Video_recorder checks the timestamp for frame rate lim

video_recorder is not saving correctly I am trying to take the contents of a bag file and record them to a video file us

Rqt_launch launching locally I can not use rqt_launch with a remote master. It keeps trying to launch locally