Feature Request
I would like a new pilot_logo OSD element to be added. It would allow users to define a pilot logo that would be visible during flight. Current methods for doing this are hacky from a user perspective: like creating a custom font and editing editing the craft_name. This is especially true for 2 or 3 row logos.

Possible Solution
One way we could remedy the problem is by

There seems to be some issues with the landing function in ./software/px4_mavros_scripts/1_px4_mavros_offboard_controller/commander.py.

To do:

1. Test the land function and report if it works well.
2. Fix if there is an issue.

fix: remove the api about avoid obstacle//commit 5e38044cf41583acf451da909d9829b86d0988b2

in api document describe use collision avoidance,
but in code why remove that api?

At the moment if the digital twin model does not have the plugins built, we can not communicate them them thus we get the following error,
Timeout communicating with flight control plugin.
It would be helpful if the error message included a message reminding the user to check to make sure the plugin is built, or better yet do the check automatically.

• F4 Wiring diagram
• Note on powering external sensors
• low-latency USB timer (see rosflight/rosflight#98)
• updated VSCode debugging instructions.
• Using the secondary serial device (which leads to 3DR Radio Instructions) (see #350)
• Post-Processing Bag files

Add environment to fork/contribute to devframe docs