@@ -11,7 +11,7 @@ PycroCart 1.0 was largely based of off a version of a GUI made by Bitcraze who i
## PycroCart 2.0
Based off of some suggestions from sdmay23, and from feedback on MP-4 from previous years, sdmay24-32 decided to attempt slotting the existing PycroCart GUI into the rest of the MicroCART framework. Hence, PycroCart 2.0 was born. We were under the impression, with our very limited understanding of the framework at the time, that this would be a relatively straight forward task. We hoped that we could simply move calls to the cfclient library, down to the adapter level, and then send commands to the adapter, instead of directly to the crazyflie. Long story short, it was not quit that simple.
Based off of some suggestions from sdmay23, and from feedback on MP-4 from previous years, sdmay24-32 decided to attempt slotting the existing PycroCart GUI into the rest of the MicroCART framework. Hence, PycroCart 2.0 was born. We were under the impression, with our very limited understanding of the framework at the time, that this would be a relatively straight forward task. We hoped that we could simply move calls to the cfclient library, down to the adapter level, and then send commands to the adapter, instead of directly to the crazyflie. Long story short, it was not quite that simple.
As it stands, PycroCart 2.0 is hardly functioning. Unfortunately, cfclient is considerably baked into the functionality of PycroCart 1.0. This made the task far more tedious and difficult then we had anticipated at the beginning of the year. Functioning components of the GUI are, setting a parameter, getting a parameter, and connecting to a drone if the radio number is hardcoded into the python code. As a team, we quickly started to realized that this was not the best use of our time, so we decided to put this on the shelf for the second semester.
