Beat Küng
Beat Küng
Yes splitting it up would help, but I'm not really familiar with that part of the code.
I don't know how the emlid reach works internally. But if someone wants to add support I'd much appreciate it, and I can help out.
@barchstien started to work on this (https://github.com/PX4/GpsDrivers/pull/38).
> The Emlid Base is stand alone, and uses a web interface to configure it, so driving it directly from QGC is probably out of context ? Yes, I don't...
@dev10110 this is already possible. Make sure to start `uxrce_dds_client` [with the `-c` flag](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/uxrce_dds_client/uxrce_dds_client.cpp#L746), then you can customize fastdds on the agent side with a profile. Create an xml: ```...
> If I launch the code with -c flag, it will only have any impact #if defined(UXRCE_DDS_CLIENT_UDP) which means when I'm doing a serial connection with my offboard Linux computer...
Indeed, PX4 doesn't implement it. I once implemented the protocol w/o `TERRAIN_CHECK`, but it's not used anymore either.
Yes as part of the arming reporting. You can check generically if you can run the mission mode. If it fails you get a list of reasons why you cannot...
> but not sure what it means to "standardize" this behaviour so flight stacks and GCS can implement to it without having to know about each other There's a common...
Yes, you can specify the output format with `--format qgc`: https://github.com/PX4/pyulog/blob/main/pyulog/params.py#L34