micro-ROS / micro-ROS/micro_ros_setup

open device error after openCR reset

Open
#630 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
509
Forks
183
Avg merge
22h 26m
Merged PRs (30d)
7

Description

## 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?

Contributor guide

Open the contributing guide

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell, ubuntu
Domain
cli, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.