micro-ROS / micro-ROS/micro_ros_arduino

open device error when openCR reset

Open
#1,382 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
576
Forks
146
PR merge metrics
No merged PRs in 30d

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a source file or test. Start by reproducing the `micro_ros_agent serial --dev /dev/ttyACM0` command on Ubuntu with the openCR 1.0 reset sequence, then inspect the serial-agent and OpenCR integration entry points. Done would require a clearly identified cause and a verified connection result matching the expected behavior, but the issue does not define a code change or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
arduino, linux, 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.