Closed jeffallen closed 9 years ago
This is the other way to do it: have the main control loop "jealously" guard access to the godrone.Firmware object, and then talk to it. I think I actually like this quite a lot now that I see it's not too messy. I can also see where my other future checkers will plug in to the main control loop.
This change still needs to be tested on a live drone. I tested it with "./godrone -dummy -addr=:8000".
Add a goroutine in the on-drone firmware to watch for pitch and roll getting too high. Make it communicate with the main control loop via a new field in the Request structure.
Add cutout display to the UI.
Other small typo fixes.