...
Finish the different stages
current calculations for the AM struct is in autosteer
there is no AM struct back to PM → will have to see where that affects the code
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
Noticed that fijo may not be recognized
cruising state
determine if we actually need to #ifdef the whole file or if we can reduce to just snippets of code because I do not like looking through 500+ lines of code
we currently never have an array of waypoints → is this something we should work on implementing
WaypointManager:
update rest of hpp and cpp
review the math for gps coordinates
add an initialize_waypoint function for landing/takeoff waypoint types
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???
