Dronecode Weekly Call: January 8, 2019

#1

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

#2

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

  • Auto-generation has been a focus in the last days
  • Python, is now entirely auto-generated and feature complete
  • Swift is manually generated, we are working on the auto-generation
  • Python distribution (packaging) should be the next step.

Avoidance

Update by @jkflying

  • Using a “racing drone” frame, trying to go small and lean, cpu tunning, more robust not crashing
  • 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

Flight Testing

Update by @Tony3dr

  • Back from holidays, picking up the PR queue and started daily master testing

QGC

Update by @rroche

  • No update this week.

PX4

Update by @dagar

  • v1.9 will happen once everything is stable
    • NuttX upgrade is still WIP
      • Compressed ROMFS, helps with flash size.
  • Snapdragon is now back working.

Action: Validate fix with flight tests.

MAVLink

  • No update this week.
  • Meeting Minutes from their first meeting of the year.

Messaging
Update by @rroche

  • No Update.

Response to question on a list of flight vehicles available to the flight test team

Flight testing list of vehicles

1 Like
#3

@jkflying, your avoidance work seems to be tackling similar requirements as the one done at JPL? I believe they’re presenting a paper at SciTech this week, let me see if I can find it and post it back here.

#5

Meeting recording