February 22, 2023
- Community Announcement
- Community Q&A
- General Discussions
A.1 : XRCE-DDS Documentation is finally out!!!
- Please give it a try & any feedbacks would be welcome! (In #ros channel in Discord server)
- E.g. Whether it works / tutorial requests / etc
A.2 : Next week 2022 Contributor report coming
- Wait for it!!
A.3: QGC Call this Thursday
Feel free to join QGC call this Thursday, as we need a lot of help resurrecting the development efforts there!
Please add it to your calender by visiting here: https://www.dronecode.org/calendar/
Community Q&A (No deep technical discussions)
Guideline for asking a Question
- 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 Discord or create a Github Issue!
- If you take over 5 minutes for the question, please continue in Discord or a Github Issue.
Q.1 : Namespace convention collision for multi vehicle simulation
PR up by Benjamin here:
Action Items: Discuss with @Jaeyoung-Lim (already approved the PR). Probably the best person with full context.
Q.2: Iridium driver, how to send the info via MAVLink?
- Confusion in where the MAVLink parsing is happening.
mavlink_receiver, daniel will send the link.
Q.3: What is the current status of the System Failure Injection feature?
- It notes that it only works in Simulation & is in development status as of PX4 1.12
- Would be nice to have this feature working for the flight testings
Answer: Should work with some modifications. Daniel already started initial effort (making it work in real vehicle).
Action Item: @danielhonies will check on implementation & catch up with Daniel on what needs to be done & try it out.
Q.4: How to install px4 firmware on mateksys f405-wmn FC
Answer: F4 version probably hasn’t been supported yet, although other MATEK boards (H743) have been tried out successfully in the past. Although it is not documented as an officially supported board: Community Supported & Experimental Autopilots | PX4 User Guide
However, supporting F4 boards probably won’t be desirable.
Note: @Sir_MuEL check out Flight Controller Porting Guide | PX4 User Guide, for getting a sense on how to support a new board.
Q.5: Simulating RC inputs - Josh
I have a RC controller connected to sitl as a Joystick device. I would like that to appear to sitl as RC input not as overrides via a joystick attached to a GCS. (To test arming switches or well any other switch.)
Discord message: Discord
Answer: Currently QGC sends
Manual control setpoint message to stream the RC data from the joystick, however ideally we would send
RC (data?) message.
Relevant doc: Joystick · QGroundControl User Guide
Q.6: Turning off optimizations in SITL? - Josh
Currently when we set breakpoint to monitor a specific variable (RTL time estimate), but compiler optimizes the code compilation, and debugging is hard.
Answer: Daniel does it on ‘per module’ basis. He used to have debug build that doesn’t do any optimizations. In the
CMakeList, add compile option
volatile int j = 0 and add
j++ near the breakpoint, it should always hit via debugger - David
Related: Why does Visual C++ not hit a breakpoint in, or step through a specific function? - Stack Overflow
Q.7: Documentation for Underwater Unmanned Vehicle - shenchris
Trying to control UUV with PX4 (with Computer Vision). However documentation in UUV is limited. What kind of references are there?
Currently tried IMU based estimation, but position estimate drifts significantly.
Answer: There is UUV controller code in the repository. Otherwise, documentation isn’t so helpful for development.
Answer2: If there are events underwater, it’s good to use VIO, but otherwise DVL would be better to use. Using just IMUs could be possible. - Farhang
Note: Please share questions/progress in #uuv channel in Discord as well! Check out odometry doc as well: Visual Inertial Odometry (VIO) | PX4 User Guide
D.1 : Is Bot in Discord annoying?
- Reminder to write questions in the forum helps articulating the question