- Community Announcement
- Community Q&A
- Project Updates
- General Discussions
- Weekly Overview
- High priority queue
Check out the Control Allocation video!
- Specify what you are trying to achieve
- Specify what environment / platform you are using
- Prepare a Link or Document to help understand if possible
- First, ask the question on the Slack or create a Github Issue!
- If you take over 5 minutes for the question, please continue in Slack or a Github Issue.
Cons: Currently it’s tedious to enable the circuit breaker (need to set magic-number)
Pros: If we have a bit-flip or any bit errors, we don’t want to accidentally enable the circuit breaker.
Documentation on Circuit Breakers are not specific.
“Flight termination” behavior isn’t easy to predict with current documentation.
Flight Termination Circuit Breaker param is here.
Even if the geo fence violated ‘action’ is to Terminate, we don’t want to fight for this using this ‘circuit breaker’. User should rather be explicitly notified that vehicle WILL terminate, if the action setting is to ‘Terminate’.
Related PR : RFC Commander
Let’s kill a lot of the circuit breakers!
Putting second GPS to GPS 1, is it correct to do that? GPS signal is not coming in.
- Check baud rate
- Try out the gps commands (driver) in the console manually
- Start with first port, do the gps info & try out the other port as well
With a boat (which has an external mag & GPS), it was unclear what kind of setting I needed to apply for a magnetometer priorities.
It should be ok without touching the priorities (PX4 automatically sets external / internal mag’s priorities appropriately)
- Can check each
sensor_magmessage to check if it’s configured to be internal / mag
It would be nice to have an UI that shows which hardware is connected to where, in which rotation, which priorities and what attributes are related in a single view.
- CAN / MAVLink can add complexity
- Sharing the Device Tree to the UI (e.g. QGC) would be an option as well.
Using the docker to flash (via USB connection) was tricky. Building the firmware image itself is not a problem.
Giving the privilege when running the container could give permission to detect all the bootloader connections, etc - should be enough to flash the device.
Maybe check the
lsusb output within the container to check if board is detected
Junwoo is currently integrating PX4 into a Racing boat and posting updates via blog series in the forum. Please feel free to check it out if you are interested!
PR (For reference, is used for testing purposes): [WIP] Rover controller refactor by junwoo091400 · Pull Request #19957 · PX4/PX4-Autopilot · GitHub
- RC Speed Boat with PX4 - Episode 0 : Trying out the Boat and integrating Pixhawk
- RC Speed Boat with PX4 - Episode 1 : Using PX4 to control the boat!
Currently bought a helicopter to try out the PX4 support
There has been multiple reports of Cube orange having problems with PX4:
Let’s collect the problems here:
Cube Orange SD card logging dropouts are high - Alex
- Using STM32H7 SDMMC1 causes problem in DMA, so need to use STM32H7 SDMMC2.
sd benchcommand outputs to verify if there’s issue there first
- Maybe this might help?
This is pretty cool
- Package delivery in mission (gripper / winch) by junwoo091400 · Pull Request #19963 · PX4/PX4-Autopilot · GitHub
- Synthetic airspeed initialisation improvements by RomanBapst · Pull Request #19955 · PX4/PX4-Autopilot · GitHub
- Pixhawk 6c - Issue Tracking · Issue #19943 · PX4/PX4-Autopilot · GitHub
- Bug in master for MicroRTPS SITL bridge : px4_sitl_rtps doesn't work with px4_ros_com micrortps_bridge · Issue #19917 · PX4/PX4-Autopilot · GitHub
- Slack bot to encourage people to use / visit Discuss Forum
- Currently the Slack API doesn’t tell if a message is in a thread or not - Ramon
Discussion based on: High-Priority Queue · GitHub