Jonas Vautherin

Oh right, maybe there is some tuning to do there. The [message definition](https://mavlink.io/en/messages/common.html#LOG_REQUEST_LIST) doesn't say anything about a limit for LOG_REQUEST_LIST, so I would assume that the autopilot should do...

Is PX4 having an issue when there are "too many" logs? If that's the case, shouldn't that be fixed on the PX4 side?

I think it's usually more organic. There is no full time team paid by "someone" here. We are open to contributions and happy to help, and it's also possible to...

First, a quick fix: you can set `LD_LIBRARY_PATH`: ``` LD_LIBRARY_PATH=/ws/MAVSDK/install/lib/ ./install/bin/rid-transmitter ``` > I tried his recommendation on MAVSDK, and that did not fix the issue. What did you try?...

I actually watched the video you linked above, and it is a very nice presentation 😊. However, I don't think that setting the rpath to $ORIGIN will solve this particular...

> What about these three workarounds Those will work because they install MAVSDK on the system. I think the original issue is that they want to install MAVSDK locally and...

This one should work: `await drone.connect(system_address="udp://10.17.111.1:40000")` Which version of MAVSDK are you using?

Hmm I don't remember clearly, but it could be that this doesn't work with MAVSDK v1. I am pretty sure that it works with the `main` branch though (which will...

Your log should find openssl in `third_party/` (like the other dependencies), but it found it on the system (I cannot copy-paste the line because it is a screenshot, so you...

You have a typo in your code. It should read `udp://10.17.111.1:40000` (your code is missing `//`). Then are you certain that both mavproxy and MAVSDK can connect at the same...