Junwoo Hwang
Junwoo Hwang
Interestingly, it seems like rover attitude control was intentionally removed at one point in PX4 : https://github.com/PX4/PX4-Autopilot/pull/12239
Currently in the Rover Position Control, it seems to use the `trajectory_setpoint` to overwrite the `position_setpoint_triplet` data (thus modifying the position setpoint :thinking:). Silvan hinted that Rover probably shouldn't even...
Is it still relevant?
Applied the comments in the latest change :wink:
Currently the output JSON file is like this: ``` { "board_info": [ { "board_name": "mRo X2.1", "target_name": "mro_x21", "description": "Firmware for the mRo X2.1 board", "board_id": 33, "image_max_size": 2080768, "build_variants":...
Current problems to unblock: 1. **How do we deal with targets that doesn't have `defconfig` or `firmware.prototype`, or doesn't have the specific config key we are interested in (e.g. Vendor...
## Status of the QGC PR: ### Automatic detection of the board/target based on the manifest data Now the old bootloader ID to build target mapping list is gone, and...
> This is because unlike rovers boats have a low damping on yaw and therefore actuator inputs do not map directly to yaw rates What does this mean? I am...
Don't think we really need this Issue :+1:, we can discuss everything in separate baby step PRs
Is this PR still relevant?