Skip to content

20221026 Dev Meeting

Jump to bottom Edit New page
Hamish Willee edited this page Oct 26, 2022 · 13 revisions

General:

Notes

  • Winch extended support #1899

    • This particular case is a gripper - it is separate functionality grafted to same hardware.
    • Were it integrated with normal winch behaviour then it could be done either as a gripper or as an integrated instruction.
    • We'd take proposals on that if there is a stakeholder that has a hook like that.
    • AO HamishW to update the issue

  • Add note about endianness in serialisation #491

    • Very few systems are endian, so this note probably doesn't need to say as much.
    • AO HamishW to cut it down to just mention the over the wire endianness.

  • Extend MAV_CMD_NAV_VTOL_TAKEOFF #1875

    • AO Auturgy to take to the ArduPilot devcall.

  • Airspeed message: update #1900

    • How is data to be used? If this is always for display then perhaps should be CAS and not include the pressure info. If this is for something else then we need to understand what that is to know what the values should be.
    • AO JamesP to query.

  • HIL message support for airflow sensor #1893

    • It would be nice to separate the HIL messages into their own dialect file.
    • General problem still exists that this makes standardization less likely.
    • Unless we have a px4.xml this would still have to be pulled into common.
    • No AO at this time.

  • BATTERY_STATUS_V2

    • Remove capacity remaining? https://github.com/dronecan/DSDL/pull/7#discussion_r1000957711
      • No. A power monitor based battery would then have no way to indicate full battery without being forced to send the smart battery info. We don't want that to be a requirement.
    • How to handle battery slots requirement
      • Not a requirement without a clear stakeholder and use case. We don't have that.
      • But we think it could be done as a field on SMART_BATTERY_INFO if needed.
      • Do nothing for now.
    • Interesting discussion on how to manage multi-battery systems.
      • PX4 just uses lowest battery voltage to trigger warning. Simplistic.
      • ArduPilot supports a battery function to indicate that subsequent ids are "synthesized sum" - so batteries are assumed to be in parallel, but if you see this particular function, the following batter ids are treated as "in series".
      • PX4 might do this with something like component information IMO.

  • General discussion on how to manage change better in wip and development.xml.

    • Not much concrete other than "yes, we need to purge it from common"
    • Let's do investigation and see if we can establish some "standard" stuff.
    • AO Hamish to see if https://github.com/Auterion/ras-a-testing-suite can be adjusted to perform some generic testing.

  • Disentangle long running commands? https://github.com/PX4/PX4-Autopilot/pull/20331#discussion_r1005095865

    • Discussed a bit as part of above.
    • It is a limitation of protocol that you can't have multiples of the same command active at a time.
    • It is very useful but perhaps could have been done in a more compatible way.
    • Yes, needs to be no longer WIP if there are implementations.

Attendees: Hamish, ThomasDb, JamesP, JulianO

Add a custom footer
Add a custom sidebar
Clone this wiki locally