Community Q&A : Maximum 3 - 5 min limit for each question. If the discussion isn’t finished, ask the Questioner to create a Github Issue about it and continue discussion there.
Limit discussions to maximum 5 min, then it should be continued in In-Depth discussions.
Always consider the perspective of community members who may not have a deep understanding on certain concepts
Couldn’t find an answer in the user guide - what happens when an SD card fills up from logging for a long period of time? Do old logs get rolled over, or does everything just stop? (edited)
At 300 MB limit, would it not log?
There are cases where customers can be logging for days in a row.
I found it confusing that home position can move around & be non-zero (not at origin). As well as the exact definition of when and how local position coordinate gets defined. Is there a good documentation on this? If not, I would like to create it, so could anyone share some thoughts / experiences on this?
Magnetometer rotation isn’t relative to the Board’s orientation, but rather it’s an absolute rotation compared to body FRD frame, isn’t this confusing for the users?
Can we unify mag & accelerometer calibration? How?
Auto Mag rotation detection doesn’t return a correct value (after calibration, the magnetometer value doesn’t make sense) - Charles
@dagar : Auto Mag Rotation Detection depends on ‘internal magnetometer’. So it doesn’t work without an internal mag!
@david_s5 : Can we have prioritization of certain mag models over another?
Tough to say, since mag location and external factors matter as well.
In this scenario, if offboard is only trying to perform altitude hold, there is no way to say “I want to control position, but only check validity for z”, since the offboard_control_mode message does not have an “altitude” flag or any other method of telling commander what to perform checks for.
Currently resolved in the private codebase, not general for upstream support.
I asked this awhile ago and @dagar gave some good insight but what is the status on 1) knowing what happens when a FW goes into land mode with use terrain enabled and an accurate altitude sensor is present (i.e. a lidar) and 2) how can this be tested in gazebo to verify. It has always been the assumption that it will crash into the ground because of the text here https://docs.px4.io/master/en/flight_modes/land.html#fixed-wing-fw so has been avoided entirely. Also, after getting some clarity I would like to change the docs to reflect what will occur.
We recently had an issue where our pusher propeller started spinning as soon as the safety switch was pressed. There is no log file, which indicates that the drone was not armed. Since servos are powered during prearm mode, one of my theories is that the wrong mixer configuration was loaded and the pusher motor was treated as a servo. We have not been able to reproduce the issue though, and I don’t see how the mixer configuration could change from one boot to another.
We use PX4 1.12.3 on a Cube Orange with a BabyShark VTOL airframe. Any theories or tips for where to look while troubleshooting would be greatly appreciated.
Community Announcement
Community Q&A
Project Updates
General Discussions
DEV CALL LAST WEEK
SLACK LAST WEEK
GITHUB LAST WEEK
High priority queue
Release