micro-ROS / micro-ROS/micro-ROS-demos

Application stuck on "Waiting for device"

Offen
#79 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Vorherrschende Sprache
C
Sterne
101
Forks
35
Ø Merge
4 T. 16 Std.
Gemergte PRs (30 T.)
3

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
c, docker-compose
Bereich
devops, embedded-iot
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
30/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.