Vladimir Ermakov

@Zaaler i'm not sure what i've changed, but now i can receive topics (status, diag, imu), call some of services (e.g. params pull). Sometimes i have troubles with `/mavros/set_mode` using...

Yes, i tried to use `mav sys` after hanging (and killing) `ros2 service`. But i'm unsure whether it be related to amount of runner threads or not. In my case...

@Michel1968 current ros2 branch has group set for command plugin. But all plugins share same multithreaded runner. Also each plugin is separate node, so i'm not quire sure that we...

I could not understand what you are trying to achieve. Mavros is a bridge between Flight Control software (a firmware) which runs somewhere, on a Flight Control Unit, such as...

Then you first need to connect all the hardware, like thrusters ESC's, RC receiver (at least to have kill-switch) etc, to the FCU which runs Ardupilot (i suppose that you...

@Scarf195 yes, i only have plans to make possible to write GCS-plugins for ROS2. For mavros 1 it's unlikely to make any new big changes. My suggestion - use pymavlink...

Probably confusion here caused by GCS proxy feature, which simply forwards FCU messages to GCS. For @Scarf195 's objective, he needs to act as FCU, so GCS could talk to...

Does it work if you blacklist only hil? It feels that problem not in one single plugin, rather than somewhere in common code. And alignment is highly dependant on compiler...

From logs it looks like firmware do not accept incoming messages. Since apm2.6 quite old, i suppose that it do not support Mavlink 2.0, so try to set `fcu_protocol: v1.0`.

@elonv you probably done it wrong: ``` /mavros/fcu_protocol: v2.0 ```