Dronecode Weekly Call: November 20, 2018

[rroche]

Tuesdays 5:30 PM CET, 11:30 AM EST, 8:30 AM PST (subscribe to calendar)

Join the call: https://zoom.us/j/229568741
Meeting ID: 229 568 741
Dial(for higher quality, dial a number based on your current location):

• Switzerland: +41 (0) 31 528 0988
• US: +1 646 876 9923 or +1 669 900 6833 or +1 408 740 3766
• Germany: +49 (0) 30 3080 6188
• Mexico: +52 554 161 4288
• Australia: +61 (0) 2 8015 2088
• United Kingdom: +44 (0) 20 3695 0088
• South Korea: +82 (0) 2 6022 2322
• Spain: +34 91 198 0188
• Israel: +972 (0) 3 978 6688
• Brazil: +55 21 3958 7888 or +55 11 4680 6788
• International numbers available

Agenda:

• 30min update from projects and working group leads
• General Q&A

Meeting notes below

[rroche]

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

• Calibration plugin for Swift (https://github.com/Dronecode/DronecodeSDK-Swift/pull/94).
• Bug fixing deadlocks (https://github.com/Dronecode/DronecodeSDK/pull/590)
• Adding compiler warnings to prevent things down the line (https://github.com/Dronecode/DronecodeSDK/pull/597).

Avoidance

• Ground Interaction on avoidance
• Found a bug in the system, implementation works on simulation.
• We now have “basic” feedback in QGC about the avoidance system.
• Merged a library to handle some of the avoidance, if you fly manually and want to have some avoidance.

Flight Testing

• Last week report available on forums
• VTOL rate control improvements
  • ordered replacement convergence vehicle for testing.
• Commander cleanup still testing.
• FMUv5 performance investigations still open.
• Action: document UAVCAN as a result of testing setup inconsistencies.

QGC

• Issue triaging and community coordination underway
• Action: stale bot investigation.

PX4

• Big board re-organization, finally pushing this through.
• Action: Make sure Hamish reads through PR.
• https://github.com/PX4/Devguide/pull/654#issuecomment-440332683

MAVLink

• New UTM Message proposal RFC
• Discussion on mavlink change request on how frames are handled
• RFC for a mavlink test suite coming soon (days)
  • Action: rally community to gather feedback.
• Microservices, some developers are worried about complexity.
  • Action: discuss in PX4 call. Why should we care?

Messaging

• NA from last week.

---

Open Session

3DR / Yuneec About to release their new joint venture this week

• Already taking orders
• H520 based vehicle.
• Integration enabled by the DronecodeSDK-Swift
• Proposal to work on the next Dronecode based Yuneec platform (probably Mantis!)
• Looking for next platforms.

[thomasgubler]

Avoidance (Auterion):

add additional component_id fields for obstacle avoidance and VIO

Add a collision avoidance library which uses range data

libmavconn: add the possibility to override the source component ID

[rroche]

Can I please get sign-off from attendees on meeting minutes, just post a comment with OK or LIKE this post, post a comment for requesting edits.

@JonasVautherin @JulianOes @thomasgubler @Tony3dr @dagar @laurenwinter

[rroche]

Meeting recording, thanks again to everyone who joined the call and everyone who find this post (and recording), please join us on Slack and say hi!

Thanks for listening!