Client Meeting January 25th - ProstheticFalconry/Capstone GitHub Wiki

Before meeting starts Dave and Mike tell us that the realisticness of our flight controller, velocity control and positional control are a no go for the quadcopter. Thus Adam and Jaden need some sort of external control loop to facilitate a more stable flight. First test for quadcopter flight is stability on the quadcopter rod. Second would likely be a testing of the sensors for the quadcopter in the a box to keep the quadcopter stable while hovering and moving from a collision. Dave explains to Austin the precise definition of the Roll Pitch Yaw EMG control. Jaden and Adam arrive, and Dave presents the clients with "magnificent" opportunity to learn more about control systems and flight stability due to the fact that the accelerometer would need to be much more expensive than a $20 accelerometer allocated for this project. To facilitate flight the project would require an external flight controller and an outer control loop which when coupled with the camera would give the desired Roll Pitch Yaw. Our largest problem involves the fact that this external control loop depends on both the machine learning of the client as well as the camera and accelerometer being fully implemented so as to give the motion. Can do it via internal visual servoing or via an external control loop which is corroborated by GPS. These quadcopter drift concerns were brought up due to a meeting with Geoff Fink earlier this day. These concerns compound causing a drift which we figured the quadcopter within minutes but after the meeting we determine the quadcopter would crash within seconds. Jaden hearing all of this dictates that we should stick to the intial accelerometer control loop so that A. We can have that loop available to the clients when they initialize internal servoing on the quadcopter and B. If this loop is not helpful Jaden would appreciate us making it so that the clients know to avoid come time for the machine learning.