micro-ROS / micro-ROS/micro_ros_setup

open device error after openCR reset

未关闭
#630 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
Shell
星标
509
派生
183
平均合并
22 小时 26 分钟
30 天内合并 PR
7

描述

## Issue template

- Hardware description: openCR 1.0
- RTOS: Linux ubuntu 20.04 host
- Installation type: micro_ros_setup
- Version or commit hash: galactic

#### Steps to reproduce the issue

```
source /opt/ros/$ROS_DISTRO/setup.bash
cd ~/ros2_ws/src
git clone -b $ROS_DISTRO https://github.com/micro-ROS/micro_ros_setup.git
```
```
sudo apt update && rosdep update
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
```
```
sudo apt-get install python3-pip
```
```
cd ~/ros2_ws
colcon build --packages-select micro_ros_setup
source install/local_setup.bash
```
```
cd ~/ros2_ws
ros2 run micro_ros_setup create_agent_ws.sh
ros2 run micro_ros_setup build_agent.sh
source install/local_setup.bash
```
```
sudo chmod 777 /dev/ttyACM0
ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0
```
#### Expected behavior
![a](https://user-images.githubusercontent.com/117966644/231086295-ade85e4d-39c6-4da2-98a2-5823ac4e64b8.png)

#### Actual behavior
![s](https://user-images.githubusercontent.com/117966644/231086461-b0f31afa-1c20-4871-9f05-fb527f3993bf.png)

#### Additional information
when I use micro-ROS package I want to get result like picture of Expected behavior.
but actually the result is like picture of Actual behavior. When the system wait for connection of serial port, I pushed reset button of openCR. Should I do for this result other than Steps to reproduce the issue?

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

Start with the micro_ros_agent serial command and the micro_ros_setup agent build flow described in the reproduction steps. Reproduce on Ubuntu 20.04 with Galactic and an openCR 1.0, including pressing the reset button while waiting for the serial connection. Done means identifying why the post-reset device error differs from the expected behavior and documenting or correcting it.

由索引模型根据 Issue 内容生成。

评估

技术栈
linux, shell, ubuntu
领域
cli, embedded-iot
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。