Updates from Project
Every project answers the following questions in 5min max:
- What did you work last week?
- What are you working on this week?
Dronecode SDK
Update by @JonasVautherin
- Python generation, good progress, autogenerating the function arguments, and we have an example and run a mission from the python
asyncio
auto-generated code, almost ready to go
- We had a contribution in the Makefile
-
offboard
pull request that will be merged soon.
-
beginner label on Github is leading to contributions
Avoidance
Update by @thomasgubler
- Improvements in stabilizing the architecture and code, unit tests, making codebase more robust
- Making the avoidance be able to fly faster using only 1 camera
- Pushing the speed limits we have currently, by a combination of working in the algorithm, plus config of sensors
Question: should we start testing regularly?
-
Action: Let’s bring testing up to team.
Flight Testing
Update by @Tony3dr
- Weekly report
- 31 flights, we had a couple of days of heavy rain
- 2 prs tests
- nuttx build
-
Action: when you mark something as not working that’s refering at your pixhawk mini, can we refrain this as an overall state of the board
QGC
Update by @rroche
PX4
Update by @dagar
- Hardware test rack is coming up
-
@david_s5 working in getting us in sync with NuttX
- Compressed ROMFS, helps with flash size.
- Will probably be part of v1.9 but not for at release
- Upstream NuttX build system to cmake
- New Contributor: someone helped with snapdragon builds, let’s get the test team flying again.
-
Action: flight test snapdragon, do it on master for now.
-
Action: get Jenkins to build snapdragon binaries
MAVLink
Messaging
Update by @thomasgubler
- Basically investigating a bug with the latest update of ROS2 the messaging ros com stopped working, there is a work around for people already using this, but we are looking for the breaking change, enganged with eprosima
- Plan is still to tie various loose ends before working with the avoidance team, making a new example with avoidance and messaging architecture,
- Very well planned with issues.
- Action: check with @TSC21 on dev call.
No Questions or Feedback.