micro-ROS / micro-ROS/micro_ros_setup
micro_ros_agent not found when launching sensor_combined_listener.launch.py
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 509
- 派生
- 183
- 平均合并
- 22 小时 26 分钟
- 30 天内合并 PR
- 7
描述
Background: I have a ros2-px4 docker container with micro-ROS installed (ros2 foxy).
I can successfully launch the micro-ros-agent with the command:
ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888
But when I start another terminal and launch the sensor_combined_listener.launch.py-file in the px4_ros_com/launch package, I get the following error output:
[INFO] [micro_ros_agent udp4 --port 8888 -v -1]: process started with pid [529904]
[INFO] [sensor_combined_listener-2]: process started with pid [529906]
[micro_ros_agent udp4 --port 8888 -v -1] /bin/sh: 1: micro_ros_agent: not found
[ERROR] [micro_ros_agent udp4 --port 8888 -v -1]: process has died [pid 529904, exit code 127, cmd 'micro_ros_agent udp4 --port 8888 -v '].
It seems like the command micro_ros_agent is not recognized even though it was just used and started an agent.
In the default sensor_combined_listener.launch.py-file, the command for starting the agent was previously called "micro-ros-agent" which I have changed to "micro_ros_agent", which fixed previous errors, but this error is new and unknown to me.
(I have sourced the ros installation and ros workspace). I can do a colcon build in the ros workspace with only stderr outputs as errors, rest is built successfully (i.e. no packages fail to build), which does not say much specific.
This workspace contains both px4-dependencies and micro-ROS source files, but micro-ROS is supposed to be used together with PX4-Autopilot. The PX4-Autopilot-repo is located in a separate src-folder.
Thankful for any help!
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 px4_ros_com/launch/sensor_combined_listener.launch.py 开始,并将其中的 agent 命令与成功的调用 ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888 进行比较。检查 launch 进程如何在已 source 的环境中解析可执行文件;当 launch 在没有退出代码 127 的情况下启动 micro-ROS agent,并且 sensor listener 也启动时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python, shell
- 领域
- embedded-iot, robotics
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100