- Community Announcement
- Community Q&A
- Project Updates
- General Discussions
- Weekly Overview
- High priority queue
- 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.
Possible by adding streams at runtime on the console using something like
mavlink stream -d /dev/ttyS5 -r 50 -s POSITION_TARGET_LOCAL_NED or hardcoding them in PX4-Autopilot/mavlink_main.cpp at main · PX4/PX4-Autopilot · GitHub
There is an example on how to fetch parameters but the issue is that the data type of the parameter is not clear. The only current way to go about it is to cache all parameters to know the type and manage that on the user side. It could be done within MAVSDK but that would be more heavy-weight. Otherwise the MAVLink parameter protocol would need to be changed.
It would be cool to have a unified parameter file format that could just be sent over via MAVLink. Also there should be a full export and full import for parameters that’s intuitively available.
Should documentation get moved to ROS Humble LTS? Humble possibly works but we should move over and update the documentation. @JulianOes just went through and got it all working. Let’s update the docs with these findings.
This helped to get things working:
Suggestion to bring it in the PX4 repo. But the
colcon build system requires a certain directory structure. We should double check. The idea is that ROS 2 being another platform you can run PX4 on/with. See PX4-Autopilot/platforms/ros2 at main · PX4/PX4-Autopilot · GitHub, PX4-Autopilot/package.xml at main · PX4/PX4-Autopilot · GitHub
Goal: Mission gets checked immediately upon upload and not even saved if it’s not feasible. Current pr refactors the checks into a library and unit tests it. Let’s get it rebased and merged.
It’s working on a side-branch in a hard-coded way not supporting all chips but some H7. You get one rpm telemetry per set out command back. So after e.g. 4 cycles you get the telemetry for all motors on a quad. It’s currently work in progress.
Commands to start simulation are now
make px4_sitl gazebo_iris
Now the discussion is to change everything to gazebo_classic.
make px4_sitl sitl_gazebo to just build sitl gazebo.
Discussion based on: High-Priority Queue · GitHub