Things to do
State classes → redefine crusiing, takeoff/landing, transition? states
Define PM-TM and PM-AM structs
redefine waypoint datatype using info from cv (PathData in WM → requires lat, long, alt, is it takeoff?landing?pathfollow?home?)
altitude → macro
Determine next directions with the getNextDirectionsCommand
WaypointManager.hpp
#define IS_FIXED_WING FALSE
WaypointManager:
review the math for gps coordinates
Link the current position (given from sensor fusion) and target(future) waypoint (needing for path following math)
calculating desired track between target and waypoint after target (need to also link these)
Pathfollow requires track and position → calculate this
Is there a situation where we would need to edit flight path (on the way from a→b, change to a → d → b)
Vector???
Add Comment