OBC 2018 todo

[tridge]

Some things that need doing:

• fix RGB <-> BGR on map
• add lidar based height to mav_position.py
• only send ADSB_VEHICLE msgs if they are close enough to a vehicle
• send ADSB_VEHICLE msgs to both relay and retrieval vehicle
• delay takeoff if DNFZ blocking path
• can't measure distances in images in camera_air
• brightness control broken in mosaic
• fix rcout set_failsafe_pwm on ChibiOS
• place marker not working in camera_air
• image fetched marker not showing on map
• show image from map not working in camera_air
• disable SBUS failsafe handling parameter
• scale obstacle margin for obstacle speed and turn rate
• prevent pkts from 3G on porter from coming back down the rfd900x link
• send ADSB_VEHICLE pkts over all 3 links
• work up a list of OS configuration changes required on laptops which are to be "hands-off" (screensavers, automatic updates, crash-catching tools like whoopsie, ...)
• in search area WP_MAX_RADIUS should be zero. In main area should be 50
• add LZ exclusion areas for trees
• add method to reset battery state
• wp list gets stuck on companion
• look at bunny hop landing from 30th august
• allow ALT_OFFSET in terrain following mode
• cope with dual-aircraft NMEA
• adjust cuav_check parameter checking
• use USER WPs for AFS targets
• check GEOID for asterix data
• check GEOID for NMEA

From all-up test 2018-09-10:

• Kraken needs to get obstacle data. tridge's laptop will need to relay asterix data to Stephen's laptop as well as send it to vehicle; Stephen's needs to display but not process further
• fence auto-enable activated too late on Kraken; activated at WP1, should have been active earlier
• altitude is being read out too often (fix in mavinit scripts on both groundstations)
• Kraken struggled to reach altitude - review dataflash log
• motors were spinning when vehicle was still in NAV_WAIT_AIRSPACE
• Porter had no obstacles but did not pass through NAV_WAIT_AIRSPACE
• vehicles may be sending ADSB packets to ground - stop that!
• Optus Pi dead (doesn't ping)
• check for compass failure on Kraken
• need to fit df13 to USB externder to Porter (get from Ranger?)
• display collision data on ground while disarmed
• need another all-up test using quadstar and the Ranger
• need to make sure airspeed calibration is done!
• GREG: pull-ring on e-stop
• GREG: file down connector
• GREG: safety pin for GPS
• check scheduling on Porter
• log counts of objects currently being held for avoidance
• add into list of things to consider when plotting mission: choose first waypoint to avoid trees!
• add minimum flight time for Porter; full-fuel-loadout makes for hard second-takeoffs!
• DF-13 extender for Pixhawk in Porter (steal from Ranger?)
• add 5-second skies-are-clear-so-I'm-going message
• check data rates on GCS
• check why secondary links from Porter weren't helping links be non-claggy
• turn off IMU batch sample logging
• PETER: work out why mavlinklogdump won't write ISBD packets
• fix no-obstacles-on-Kraken issue
• add to checklist: turn camera on on Kraken
• ensure alt readout rates are correct for feet in mavinit.scr
• set numcells for Kraken in mavinit.scr
• consider motor stopping on descent at far site
• sudden drop after levelling off in takeoff
• ensure thermal throttling is off in ESCs.
• get to bottom of erratic avoidance
• look at Leonard's PR to aid in climb-out at remote site (prioritize climb vs yaw)
• consider getting HIL working
• improve filtering on GCS for obstacles
• use SITL to reproduce avoidance issues (erratic aircraft)
• AVDM doesn't do fence-avoidance logging

[stephendade]

Turns out georeferencing is actually done on the air side, so that saves a tonne of work :)