micro-ROS / micro-ROS/micro-ROS-Agent

Connectivity Drop with More Than 5 Devices in Micro-ROS Agent on Docker (Raspberry Pi 5)

Abierto
#233 3 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
C++
Estrellas
201
Forks
111
Merge medio
1 d 6 h
PR fusionados (30 d)
10

Descripción

Description:
I am running a micro-ROS agent in a Docker container using the prebuilt image (humble) on a Raspberry Pi 5. I have several ESP32 devices with micro-ROS (Humble). When I attempt to connect more than five devices to the agent, I experience connectivity dropouts, where some devices fail to stay connected. With 5 devices, they are successful in subscribing to topics.

I suspect this issue might be related to the configuration flags in the micro-ROS build, particularly those related to client and resource limits. I came across the following parameters:

  • RMW_UXRCE_MAX_CLIENTS
  • RMW_UXRCE_MAX_SUBSCRIPTIONS
  • RMW_UXRCE_MAX_SESSIONS
  • RMW_UXRCE_MAX_NODES
  • RMW_UXRCE_MAX_PUBLISHERS
  • RMW_UXRCE_MAX_SERVICES
  • RMW_UXRCE_MAX_WAIT_SETS
  • RMW_UXRCE_MAX_GUARD_CONDITION
  • RMW_UXRCE_MAX_TOPICS

These parameters seem critical to configuring the agent, especially as I'm dealing with multiple devices where each subscribes to three topics. I suspect increasing the RMW_UXRCE_MAX_CLIENTS value might help, but I'm not entirely sure.

What I've Tried:

  • I attempted to experiment by manually setting RMW_UXRCE_MAX_CLIENTS to 1 (as a test), but it did not yield the expected results, as multiple clients could still connect.
  • I've tried searching through the documentation, including Vulcanexus for guidance, but I haven't been able to solve the issue.

Question:
In order to adjust these flags and rebuild the micro-ROS agent from source, do I need to modify the build configuration in the following file?

Or should the changes be made in this file instead?

I believe the latter might be where the flags should be set, but I'm uncertain. Has anyone else experienced similar connectivity issues when connecting more than five devices to a micro-ROS agent on Docker? If so, how did you resolve it?

(I've also noticed a colcon.meta file in the /src folder of my workspace, should the be used?)

Any guidance on where exactly to set the flags for a manual source installation would be greatly appreciated - Or even the correct approach to setting up an agent to allow for more than 20 clients!

Thanks in advance for your help!

System Details:

  • Hardware: Raspberry Pi 5
  • Docker Image: Prebuilt micro-ROS agent
  • Micro-ROS Version: Humble on ESP32 devices
  • Number of Devices: 5+ ESP32 devices
  • Topics per Device: 3 Topics per device

Links to Documentation:

Thank you!

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza comparando src/micro_ros_setup/config/host/generic/client-host-colcon.meta con src/uros/rmw_microxrcedds/rmw_microxrcedds_c/CMakeLists.txt y /src/colcon.meta del workspace. Reproduce la pérdida de conexión con más de cinco dispositivos ESP32 mientras recopilas los registros del agente y del cliente. Se considerará terminado cuando se haya establecido la ruta de configuración correcta y una configuración probada admita el número de clientes previsto sin pérdidas de conectividad.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
cmake, cpp, docker
Área
devops, embedded-iot, networking
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

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.