PX4 Sync / Q&A: Jan 29, 2025Dronecode Calendar
Announcements
Future Events
Flight Testing Update
Release Discussion
Bug Report / Q&A
We are running a beta program with Ascend Engineering (Chicago). They will be running flight testing for the community as part of an arrangement with Dronecode
How to reach out to the team
GitHub: Tag user @PX4 /testflights
Discord: #flight-testing
Weekly on the PX4 Dev Call
How to Request Testing (GitHub)
Write down the steps to test your issue/pull request
Make sure to note the risk involved in flying
Write down things to look out for / anticipate - eg: “we are looking for no yaw jumps”
Add issue/pull request to the Flight Testing project board
Make sure to specify any hardware/software requirements as much as possible
Project Board
For release coordination, we will be using the project board.
GitHub
v1.16 Release
Discussion
1- @gillamkid How should one make contribution to QGC for their feature branch and the upstream QGroundcontrol since the upstream branch is going for some time now and no new release is cut?@bkueng @DonLakeFlyer @JulianOes in this regard.
2 - Limits for Gimbal MAVLINK Message: MAVLINK Common Message Set (common.xml) | MAVLink Guide
3- Which MAVLINK version is recommended to use?
Preferably, use version 2.0 since some message in v1.0 are no being used anymore.
4- Why is there no bias estimation for EV yaw like they do for EV Z position?
In most cases EV does not give very accurate heading estimate so having a bias estimation for that is not implemented.
5- Why was necessary for Modalai VOXL2 to decrease the icm42688 AAF Hz for accelerometer on their PX4 fork?
/****************************************************************************
*
* Copyright (c) 2020 PX4 Development Team. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
* 3. Neither the name PX4 nor the names of its contributors may be
* used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
show original
/****************************************************************************
*
* Copyright (c) 2020 PX4 Development Team. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
* 3. Neither the name PX4 nor the names of its contributors may be
* used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
show original
The preferred way is to get the raw data as much as possible from IMU always and then apply all the filters after over the whole frequency range of data instead of changing the AAF on the sensor side. You may also want to add more filtering on your VIO side later.
6- Implementing OpenVINS brings issues of crashing the drone and lacks compatibility of PX4?
The way OpenVINS initiates and handles the environment is way different and there should be way to figure out to make it compatible with PX4 like spoofing the positions at the beginning of each flight and also the ways to handle resets OpenVINS executes while in flights.
PX4:main ← gillamkid:gillamkid/fix-h480-yaw-limit-info
opened 08:45PM - 25 Jan 25 UTC
The h480 sim gimbal has no limit on its yaw axis. Before, it was reporting its y… awMax as -1e+16 (value came from typhoon_h480.sdf.jinja:247) and its yawMin as 1e+16 (value came from typhoon_h480.sdf.jinja:248). The sign of these 2 needed to be switched, which is the fix made by this commit.
The MAVLink GIMBAL_DEVICE_INFORMATION message does not specify how to represent infinity, but it does specify "positive: to the right, negative: to the left". Gazebo already considers the right the positive direction, and handles commands as expected. This commit just fixes the yawMin/yawMax limit reporting.
## Sponsor
This contribution was sponsored by [Firestorm](https://www.launchfirestorm.com/)
PX4:main ← PX4:pr-spacecraft-allocator-and-board
opened 09:24AM - 16 Jan 25 UTC
### Solved Problem
Provides support for spacecraft-like vehicles available in h… ttps://github.com/DISCOWER/PX4-Space-Systems . This PR introduces spacecraft board for SITL, as well as a barebones allocator for preliminary spacecraft build targets.
### Solution
- Add spacecraft SITL board
- Add barebones spacecraft control allocator
### Changelog Entry
For release notes:
```
Feature/Bugfix: Support for spacecraft vehicles
New parameter:
Documentation:
```
### Test coverage
- Unit/integration test: on next PR
- Simulation/hardware testing logs: on next PR
1 Like
PR for review (gazebo-classic)
PX4:main ← gillamkid:gillamkid/fix-h480-yaw-limit-info
opened 08:45PM - 25 Jan 25 UTC
The h480 sim gimbal has no limit on its yaw axis. Before, it was reporting its y… awMax as -1e+16 (value came from typhoon_h480.sdf.jinja:247) and its yawMin as 1e+16 (value came from typhoon_h480.sdf.jinja:248). The sign of these 2 needed to be switched, which is the fix made by this commit.
The MAVLink GIMBAL_DEVICE_INFORMATION message does not specify how to represent infinity, but it does specify "positive: to the right, negative: to the left". Gazebo already considers the right the positive direction, and handles commands as expected. This commit just fixes the yawMin/yawMax limit reporting.
## Sponsor
This contribution was sponsored by [Firestorm](https://www.launchfirestorm.com/)
1 Like
