Dev call May 20 2024

Issues & Pull Requests


Copter & Rover

Attendee count (max): 20

UTC1100 - AP_HAL_SITL: add packet loss and delay to each uart by robertlong13 · Pull Request #25775 · ArduPilot/ardupilot · GitHub

  • Add latency and packet loss to serial links
  • Just use Linux’s “tc” (traffic control” link quality simulation for packet loss?
  • Using the word “packet” at the serial link level is bad
  • List of parameter structures….
    • Should do better
  • Need to do latency on a per-packet basis, loss on a per-byte basis
  • Use an ObjectBuffer rather than a deque?

UTC1118 - AP_OSD: Add configurable sidebar horizontal and vertical size extensions by rmaia3d · Pull Request #26359 · ArduPilot/ardupilot · GitHub

  • Add configurable sidebar horizontal and vertical size extensions
  • Merged

UTC1122 - AP_OSD: add BTFL sidebar symbols by rmaia3d · Pull Request #26360 · ArduPilot/ardupilot · GitHub

  • Add BTFL sidebar symbols
  • Merged!

UTC1124 - Fix infinite climb bug when using EK3_OGN_HGT_MASK by peterbarker · Pull Request #26917 · ArduPilot/ardupilot · GitHub

  • Fix climb bug when using EK3_OGN_HGT_MASK
  • Need Paul to look at it

UTC1129 - ArduPlane Terrain Following not functional in Guided mode · Issue #26953 · ArduPilot/ardupilot · GitHub

  • terrain following not function in guided mode?
  • Tridge tested on call and it worked for him
  • Maybe the GCS isn’t sending the frame through?
    • MAVProxy allows specification of the frame
  • Logs actually say that it ‘s coming in absolute (see MAVC log message)
  • Need QGC to show AGL height

UTC1135 - AP_Scripting: add lua-language-server checks and docs generation. by IamPete1 · Pull Request #27001 · ArduPilot/ardupilot · GitHub

  • LUA language checks and docs generation
  • Now without brew
  • Downloads release from github
  • New scripts, no skipping errors please!
  • May need to pip install a release downloader thingy
  • Perhaps we need a requirements.txt in the root of the tree?
  • merged!

UTC1142 - AP_HAL_ChibiOS: add hwdef for Flywoo/Goku F405 HD 1-2S ELRS AIO v2 by rotorman · Pull Request #27036 · ArduPilot/ardupilot · GitHub

  • Add Flywoo/Goku F405 GD
  • Commits need fixing
  • Henry will review and fix up the commits

UTC1143 - AP_Bootloader: ID reserve for FlywooF405HD_AIOv2 by rotorman · Pull Request #27037 · ArduPilot/ardupilot · GitHub

  • Reserve IDs for Flywoo
  • MergeOnCIPass

UTC1146 - AP_Param: Summarize the type definitions settings by muramura · Pull Request #27042 · ArduPilot/ardupilot · GitHub

  • Tidy AP_Param code a little
  • Merged!

UTC1147 - AP_NavEKF3: accept set origin even when using GPS by rmackay9 · Pull Request #27081 · ArduPilot/ardupilot · GitHub

  • Accept set-origin even when using GPS
  • GPS/OF combination is difficult ATM as we don’t allow setting origin if you have a GPS
  • Extreme ArduPilot allowed for better origin handling
  • Some F4 boards can’t cicumnavigate the planet
  • H7 isn’t a problem

UTC1148 - Remove reduntant @Values from parameter documentation by peterbarker · Pull Request #27082 · ArduPilot/ardupilot · GitHub

  • Remove @Values/@Bitmask in same paramn doc
  • A couple of fixes but can then be merged

UTC1157 - SITL: added SIM_WIND_TC by tridge · Pull Request #27083 · ArduPilot/ardupilot · GitHub

  • Disabling GPS in SITL?
    • SIM_GPS_DISABLE doesn’t stop feeding data in, just the fix type to 1
    • Set SIM_GPS_TYPE instead?
    • Byte loss
    • There are actually a lot of options to stuff around with it
  • merged!

UTC0004 - Plane:correct Q_ASSIST metadata by Hwurzburg · Pull Request #27092 · ArduPilot/ardupilot · GitHub

  • Q_ASSIST metadata fixes
    • Must set to -1 rather than 0
  • Merged!

UTC0007 - AP_BattMonitor: FuelLevel_Analog: set has_current true so capacity is reported by IamPete1 · Pull Request #27099 · ArduPilot/ardupilot · GitHub

  • Set has_current true so capacity works
  • Merged!

UTC0008 - AP_TECS: modify max climb estimate to prevent throttle bouncing on limit by jschall · Pull Request #27106 · ArduPilot/ardupilot · GitHub

  • Modify TECS climb estimate to prevent throttle bouncing on limit
  • Marked for Paul to look at
  • Poor tuning
    • But should you misbehave like this?

UTC0015 - Plane 4.5.x issue tracking · Issue #26202 · ArduPilot/ardupilot · GitHub

  • 4.5.3beta
    • Want to get 4.5.3 out ASAP
    • No reports from any beta testers….
    • Release next Monday?
    • We need more beta-testing!
      • Releases too often?
      • New hardware is coming out very rapidly
      • 6 month cadence is too much?
      • Limit beta releases to just hardware?
        • Need bugfixes too
      • Many people out there already keen on 4.6….
      • “Hard-and-fast rules don’t work”
      • Leonard sees the amount of work Randy and tridge do for the releases
        • He thinks a 9 month release cycle might be a good idea
          • More DevTeam members testing would be good
            • Very expensive vehicles, ‘though!
            • Get more cheap hardware into DevTeam hands?
            • Henry flies a lot, but doesn’t explicitly fly the betas
            • How do you know what to test in the release?
            • Most changes can be tested in SITL….
            • Some imagination + SITL can recreate the cvast majority of our problems
  • [10:19 AM]rmackay9: I think we should hire a beta tester…
  • [10:19 AM]BrandonMacDougall: I do some testing ASAP.
  • [10:21 AM]Buzz: drop the beta’s and do 4 releases a year and stop backporting?
  • [10:22 AM]rmackay9: I think people just aren’t that interested in beta testing because the releases tend to be much smaller changes than in the old days
  • [10:23 AM]rmackay9: AP is also very stable so it’s already working well
  • [10:25 AM]Ferruccio1984: I try and test each beta (on heli). Weather has not been on my side in the last 3 weeks though…field not practicable :slightly_frowning_face:
  • [10:26 AM]jschall: or half million dollar vehicles…
  • [10:26 AM]Buzz: I’m unable to test more becasue I have a day job and not enough spare time to fly, its not about the money, its about the time. :slightly_smiling_face:
  • [10:26 AM]rmackay9: i agree that funding in some form could help
  • [10:27 AM]Peter Hall: For us the problem is not having vehicles, its having a space to fly them.
  • [10:27 AM]Leonard: Yeh, I was thinking that is one of my challenges with all the changes in regulations.
  • [10:30 AM]Buzz: Would changing to a ‘bleeding-edge’ + ‘stable’ , and no betas/s help? …maybe stable could be called ‘LTS’, and new-hardware would go into ‘bleeding’?
  • [10:30 AM]Buzz: … ie no betas.
  • Tim points out that it’s only been a couple of days since the beta was put out
  • How to test?
    • Do we need to call out explicitly what we want tested?
    • Release notes cover this?
    • Formalise the testing a bit?
      • E.g. a google poll
    • Can’t increase the workload of Randy/tridge
    • We used to list the people that helped with the beta reporting but it was too much work
    • Should we pay someone to beta-test?
    • Upload logs, we extract what’s been tested
      • Or extract data from log and push it online
    • Shows a lot of people downloaded it
  • How about some GCS support to make it easier for people to provide feedback?

UTC0048 - Copter/Rover-4.5.0 issues list · Issue #26103 · ArduPilot/ardupilot · GitHub

  • Copter update
  • ETF fix
  • Still several issues outstanding
  • Rover watchdog
    • Confirmed issue
  • Perhaps they’ve got USB connected and they’ve put a 2MB firmware on a 1MB file?
    • All-zeroes watchdog…
  • Separate issue watchdog Discord
  • Randy’s testing QGC 4.4 release
    • Highly motivated to get this one out
      • New camera and gimbal control screen
      • David’s got an APK file for a HereLink
  • Have different application ID for beta vs stable
  • Easier to use SimOnHardware when using other ground stations

UTC0104 - from the floor

  • LD06
  • There’s a guide-to-being-DevTeam-member document, on #DevTeam

UTC0105 - Plane: fix rangefinder correction when terrain follow is off by jschall · Pull Request #23658 · ArduPilot/ardupilot · GitHub

  • If terrain is disabled and you specify a height-other-than-zero for land waypoint then you will crash
  • Won’t flare or will flare really high
    • Terrain delta is the error
  • Tridge will work with JS on this one

UTC0113 - AP_Compass: magcal keeps soft iron matrix + scale bugfix by jschall · Pull Request #27107 · ArduPilot/ardupilot · GitHub

  • Change large-vehicle-mag-cal to maintain the diags and off-diags
  • This Can’t be the default
  • Maybe just do this off-board instead?
  • Make it a little LUA script?
    • Maybe a compass option bit to keep the off-diags?

UTC0020 - Plane: check for terrain enable in terrain-rangefinder consistency check by jschall · Pull Request #27115 · ArduPilot/ardupilot · GitHub

  • Check for terrain enable tin terrain rangefinder consistency
  • Tridge wants to see some logs

UTC0125 - close

Re: beta testing (somewhat Rover specific, but I think the sentiment likely applies across the board):

For a while, the major feature set was growing rapidly, and fixes to major underlying libraries/components were regular and clearly impactful across the spectrum of vehicles and users (AHRS/EKF improvements, nav changes, GPS features, etc). Since the official release of Rover’s PSC-based navigation system, the predominance of work has been on new hardware support, camera/gimbal support/enhancements, and smaller bug fixes. There have been few significant QoL improvements or feature additions that would catch the attention of a wide audience. If a user isn’t specifically using that new hardware or in need of a specific added feature/bug fix, the motivation to beta test is fairly low. For example, the past few betas have largely included changes I really don’t even have the means to test.

At a minimum, I think a specific list and/or methodology for testing each release would be helpful as an accompaniment to the laundry list of what tend to be very terse release note bullets.

1 Like