PX4 Tech Dev Call: November 21, 2018

#1

Wednesday 5PM CET, 11AM EST, 8AM PST (subscribe to calendar)

Join the call: https://zoom.us/j/625711763
Meeting ID: 625 711 763
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
  • International numbers available
#2
1 Like
#3
#4

QGC and Firmware flashing

The conversation started from qgroundcontrol/Issue#2797

Proposal: Very light schema and transaction protocol for firmware negotiation with an HTTP endpoint.

  • HTTP rest server for firmware payloads
  • Firmware parameter metadata (no metadata if you flash from QGC right now)

Direct motor control access

Pedro-Roque: We need a direct interface to the motors. Currently, you can’t send a motor PWM of 2000, and we needed something that was easy enough to use

Action: Dev team has some feedback on implementation.

VTOL rate control improvements

Rebased and ready for testing, the test team will fly again.

UAVCAN support

Test team needs help setting up their test units; we don’t have proper documentation for setup on dev.px4.io

ESCs
MotorId should start at index 0 and be unique

Motor 1: 0
Motor 2: 1
Motor 3: 2
Motor 4: 3

Nodeid can be random numbers as long as they are unique

Motor 1: 11
Motor 2: 12
Motor 3: 13
Motor 4: 14

Make sure to set the voltage to at least 20 on VOLT_PARAM

Action: Flight testing of UAVCAN vehicles should happen at least once a week

Action: Get UAVCAN hardware for CI and Developers

Localization

Lorenz will propose next week on PX4 dev call, there’s a massive push for localization and there are messages in the firmware that need localization

#5

Audio recording (click jpg)