10:00am: Randy - Copter update
running a bit behind on support
proximity / slam / sf0c
dronesync
tx1 initially
dataflash logs streaming to companion computer
sync to cloud
simple configurator
create AP / connect to AP
MQTT
Someone has written a mavlink <-> MQTT bridge mqtt.org https://github.com/mqtt/mqtt.github.io/wiki/MQTT%20Protocol
vs rtps?
enRoute’s end-of-year demos worked well
10:26am: tridge sensor update
Brushed motor support added to master
Only on stm32 ATM
16kHz
Flies well on little tiny drone (120g)
Quiet!
Small patches to Rover required to support brushed motors
Output-groups
D-shot
Tridge has started to look at what it would take to implement https://github.com/ArduPilot/ardupilot/issues/5300
Blheli and kiss support this protocol
Not a pulse-based protocol (pulse-based protocols are one-way and suffer precision issues at small timing windows)
D-shot is a serial, packet-based protocol similar to S.BUS and the like
14-bits/packet
Very high clock rate
e.g. 100-1200kHz
Will need DMA-to-a-pin for these sorts of rates
Construct packets as bits-in-a-buffer
Attah DMA channel to a timer
Tell timer to go
It consumes bits from that buffer, pushing packets out wire at specified data rate
May have problems with number of DMA channels available
Two-way communication may allow RPM, current monitoring
And possibly updating the firmware
11:00am: rover update with Grant
One bug found and fixed
One of Grant’s customers is now advertising “Powered by ArduPilot”
Stadium lighting
One bug to find and fix for release
Khancyr has patch for brushed-motor patch
11:07: MdB - Mission item support
Our storage of mission items is awful
Leads to inconsistencies in interface
Probably want to move to variable-length packets
Michael points out that he’s really more worried about information about exactly how we interpret current messages
Randy points out that Copter does this reasonably well, and that Plane should have an equivalent page
11:07: MdB - GPS fixes
Various fixes going into master soon
11:18: Tom - casting
Question as to what our default should be
General agreement that if a dev prefers the C++ casting then they should be allowed
Devs will have to get used to the C+±stle
12:14: Call for things from the floor
Reminder that there’s a partner’s call tomorrow
2 hours earlier than last time
Randy is up at 6am
Michael’s created an issue for the plane mixer failing