-
Notifications
You must be signed in to change notification settings - Fork 283
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
启动ego_planner报错 #62
Comments
这个报错没有提供任何信息。你可以看看最后一行“log file: /home/lad/.ros/log/8e05f104-94bb-11ed-b8dc-08002717c910/iris_0_ego_planner_node-3*.log”这个日志文件的内容 |
好的谢谢! |
请问为什么找得到相应报错日志文件的文件夹(里面有master.log/rosoutl.log等),ls -a也试过,但是没有找到iris_0_ego_planner_node-3*.log文件,求助。 |
同找不到log文件... |
magic. |
我也遇到了相同问题,请问你已经解决了吗? |
先按我说的测试 |
我之前用catkin_build编译也遇到了这个问题,后来我换用catkin make编译就好了 |
默认是得用catkin make编译的,catkin_build没测试过 |
我认为这是玄学,但是我先试试TUT |
确实可以运行了,但是很快就挂了 |
我看报错信息,跑的xtdrone的仿真环境吧? |
Maybe,original code with a large probability is working. |
好的,各位我找到一个方法可以运行,XTdrone的docker环境是可以运行的,配置是这样的 |
ubuntu18.04 Melodic
执行以下命令/ran the command
roslaunch ego_planner single_uav.launch
报错如下/error
[ WARN] [1673777077.594699933, 1980.133000000]: Waiting for trigger from [n3ctrl] from RC [iris_0_ego_planner_node-3] process has died [pid 26423, exit code -9, cmd /home/lad/catkin_ws/devel/lib/ego_planner/ego_planner_node ~odom_world:=/vins_estimator/odometry ~planning/bspline:=/xtdrone/iris_0/planning/bspline ~planning/data_display:=/xtdrone/iris_0/planning/data_display ~planning/broadcast_bspline_from_planner:=/broadcast_bspline ~planning/broadcast_bspline_to_planner:=/broadcast_bspline ~grid_map/odom:=/xtdrone/iris_0/vins_estimator/odometry ~grid_map/cloud:=/iris_0/pcl_render_node/points ~grid_map/pose:=/iris_0/camera_pose ~grid_map/depth:=/iris_0/realsense/depth_camera/depth/image_raw __name:=iris_0_ego_planner_node __log:=/home/lad/.ros/log/8e05f104-94bb-11ed-b8dc-08002717c910/iris_0_ego_planner_node-3.log]. log file: /home/lad/.ros/log/8e05f104-94bb-11ed-b8dc-08002717c910/iris_0_ego_planner_node-3*.log
请问该怎么解决
The text was updated successfully, but these errors were encountered: