micro-ROS / micro-ROS/micro-ROS-demos
Application stuck on "Waiting for device"
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- C
- Estrelas
- 101
- Forks
- 35
- Merge médio
- 4d 16h
- PRs com merge (30d)
- 3
Descrição
## Issue template
- Hardware description: STM32L4 IoT Disovery Kit
- RTOS: Zephyr 10.2.0
- Installation type: Installed through https://github.com/micro-ROS/micro-ROS_sensors_demo
- Version or commit hash: 7fd84a2664fbfcc8aaccd4c483b3e87114272673
#### Steps to reproduce the issue
Run the application on an Ubuntu 22.04.3 VM on a Windows 11 machine
Launch the application normally through "Docker-compose up -d"
#### Expected behavior
Board is recognized
#### Actual behavior
App stuck on "Waiting for device"
#### Additional information
I've tried everything that came to mind, the connection is there, the firmware is properly configured and the board is recognized. I granted every access permission I could think of, as well.
I'd really appreciate any help or advice, and please let me know if you'd like me to provide more information.
Update: After days of trying, it magically seems to have resolved itself. However, when I list the ros2 topics in my terminal, nothing seems to appear. When I try to publish on the LEDs, it can't find any subscriptions either.
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Start by reproducing the issue with docker-compose up -d on the stated Ubuntu VM and inspect the application output while the board is connected. Verify whether the device is recognized and whether the expected ROS 2 topics and LED subscriptions become available; the issue provides no file or test entry point.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- c, docker-compose
- Domínio
- devops, embedded-iot
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 30/100