micro-ROS / micro-ROS/micro-ROS-demos
Application stuck on "Waiting for device"
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- C
- Estrellas
- 101
- Forks
- 35
- Merge medio
- 4 d 16 h
- PR fusionados (30 d)
- 3
Descripción
## 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.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- c, docker-compose
- Área
- devops, embedded-iot
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 30/100