Controls:
Anni + ??
Attitude Manager ??
Specifications
Target 1: Stable flight in all directions
Target 2: Fancy flight in all directions
How are we localizing - how does PM know to tell us which way to go!?
do we operate under one local heading as 0 and PM handles the rest of the spinny localization?
local or global reference frame? → not high priority (but I think local is easier?)
Timeline
development start by reading week.
Wednesday reading week → discuss how to approach this in terms of implementation
Manual controls with RAW PWM values can be done by E.O. reading week.
Implementing fancier methods later.
Meetings
October 7, 2021
Send E-mail to Stephen Smith Friday Oct 8th 2021 → end of day. (or early saturday).
come up with some ideas to send to him about controls
hopefully get guidance wrt our specific requirements → help us choose methods?!
Sending info to the drone as a spline (especially for autonomous flight)
→ see FRC 254 controls giving splines and not raw values (link to 254 presentation)
can fall back to raw pwm % difference if necessary
Focus on two aspects
teleop and autonomous. → both get pretty ok with vectors.
for autonomous → pm should give us a vector.
for tele-op, depending on how we handle it, calculate internally or in PM.
PM → tell you where to go | AM → figure out how to get there without crashing
Definitely can get manual control done by end of reading week with raw pwm values.
fancier flight will have to come later.
October, 2021:
Start development by the end of reading week.
Meet next Thursday 7:30.
Come with ideas. Be prepared to prepare documents.
Questions and critical areas to ask the experts.
Reach out on friday.
Take weekend to look over data
Try to meet next tuesday.
Aim for reading week start
Try to make applicable for hexapoter. Worry about fancier architecturse later.
Add Comment