Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the time of imu error #89

Open
gavinwangpj opened this issue May 2, 2018 · 3 comments
Open

the time of imu error #89

gavinwangpj opened this issue May 2, 2018 · 3 comments

Comments

@gavinwangpj
Copy link

gavinwangpj commented May 2, 2018

hello everyone, i have run cartographer in turtlebot3 waffle pi, but can't use imu to make a map. no_imu is ok. and the error log as follow:
[ INFO] [1525244437.574660587]: I0502 15:00:37.000000 3937 collated_trajectory_builder.cc:72] scan rate: 4.92 Hz 2.03e-01 s +/- 2.32e-02 s (pulsed at 99.70% real time)
t_:636608412387287190, t: 636608412387222648,dt=-0.0064542
F0502 15:00:38.786036 3937 ordered_multi_queue.cc:112] Check failed: last_dispatched_time_ <= next_data->GetTime() (636608412387287190 vs. 636608412387222648) Non-sorted data added to queue: '(0, imu)'
[FATAL] [1525244438.787813602]: F0502 15:00:38.000000 3937 ordered_multi_queue.cc:112] Check failed: last_dispatched_time_ <= next_data->GetTime() (636608412387287190 vs. 636608412387222648) Non-sorted data added to queue: '(0, imu)'
*** Check failure stack trace: ***
@ 0x76eb986e google::LogMessage::Fail()
@ 0x76ebae6a google::LogMessage::SendToLog()
@ 0x76eb951c google::LogMessage::Flush()
@ 0x76ebb48c google::LogMessageFatal::~LogMessageFatal()
@ 0x1bacd8 cartographer::sensor::OrderedMultiQueue::Dispatch()
@ 0x1bb482 cartographer::sensor::OrderedMultiQueue::Add()
@ 0x1bc3e0 cartographer::sensor::Collator::AddSensorData()
@ 0x21280e cartographer::mapping::CollatedTrajectoryBuilder::AddData()
@ 0x213c8c cartographer::mapping::CollatedTrajectoryBuilder::AddSensorData()
@ 0x1a1bd8 cartographer_ros::SensorBridge::HandleOdometryMessage()
@ 0x183fc0 cartographer_ros::Node::HandleOdometryMessage()
@ 0x18d468 boost::detail::function::void_function_obj_invoker1<>::invoke()
@ 0x195520 ros::SubscriptionCallbackHelperT<>::call()
@ 0x76772bbc ros::SubscriptionQueue::call()
@ 0x767382e4 ros::CallbackQueue::callOneCB()
@ 0x76738fa0 ros::CallbackQueue::callAvailable()
@ 0x76775a24 ros::SingleThreadedSpinner::spin()
@ 0x767650fc ros::spin()
@ 0x17ecf6 cartographer_ros::(anonymous namespace)::Run()
@ 0x17c54e main
@ 0x763668aa __libc_start_main
[cartographer_node-1] process has died [pid 3937, exit code -6, cmd /home/sunny/gcatkin_ws/install_isolated/lib/cartographer_ros/cartographer_node -configuration_directory /home/sunny/catkin_ws/src/turbot3/turbot3_slam/config -configuration_basename turbot3_lidar_2d.lua scan:=/scan __name:=cartographer_node __log:=/home/sunny/.ros/log/dea8386a-4dcb-11e8-9d35-e470b8ea7c52/cartographer_node-1.log].
log file: /home/sunny/.ros/log/dea8386a-4dcb-11e8-9d35-e470b8ea7c52/cartographer_node-1*.log

why not the time of imu data ,publish one by one; or some choke ?

@sradmard
Copy link

sradmard commented Jul 4, 2018

@justin-changqi
Copy link

Hi @sradmard, how do you print the FATAL messages? ([FATAL] [1525244438.787813602]: F0502 15:00:38.000000 3937 ordered_multi_queue.cc:112] ... in your case). I fail to run the demo_backpack_2d.launch with the official bag file on Ubuntu20.04, and it showed "[cartographer_node-2] process has died [pid 156314, exit code -11, cmd....". It is hard to find out what happed if it does not show the FATAL message.

@Milalaa
Copy link

Milalaa commented Mar 29, 2022

hi!@sradmard I meet the same problem. How do you solve it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants