micro-ROS / micro-ROS/micro_ros_setup

micro_ros_agent not found when launching sensor_combined_listener.launch.py

Ouverte
#609 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Shell
Étoiles
509
Forks
183
Merge moyen
22 h 26 min
PR mergées (30 j)
7

Description

Background: I have a ros2-px4 docker container with micro-ROS installed (ros2 foxy).
I can successfully launch the micro-ros-agent with the command:
ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888

But when I start another terminal and launch the sensor_combined_listener.launch.py-file in the px4_ros_com/launch package, I get the following error output:

```bash
[INFO] [micro_ros_agent udp4 --port 8888 -v -1]: process started with pid [529904]
[INFO] [sensor_combined_listener-2]: process started with pid [529906]
[micro_ros_agent udp4 --port 8888 -v -1] /bin/sh: 1: micro_ros_agent: not found
[ERROR] [micro_ros_agent udp4 --port 8888 -v -1]: process has died [pid 529904, exit code 127, cmd 'micro_ros_agent udp4 --port 8888 -v '].
```

It seems like the command micro_ros_agent is not recognized even though it was just used and started an agent.
In the default sensor_combined_listener.launch.py-file, the command for starting the agent was previously called "micro-ros-agent" which I have changed to "micro_ros_agent", which fixed previous errors, but this error is new and unknown to me.
(I have sourced the ros installation and ros workspace). I can do a colcon build in the ros workspace with only stderr outputs as errors, rest is built successfully (i.e. no packages fail to build), which does not say much specific.
This workspace contains both px4-dependencies and micro-ROS source files, but micro-ROS is supposed to be used together with PX4-Autopilot. The PX4-Autopilot-repo is located in a separate src-folder.

Thankful for any help!

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par px4_ros_com/launch/sensor_combined_listener.launch.py et comparez la commande de l’agent avec l’invocation réussie `ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888`. Vérifiez comment le processus de launch résout l’exécutable dans l’environnement sourcé ; c’est terminé lorsque le launch démarre l’agent micro-ROS sans le code de sortie 127 et que le sensor listener démarre également.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
python, shell
Domaine
embedded-iot, robotics
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.