convert the language from top/bottom to front/back, it is clearer to understand by looking at the quad what is meant
clean up the analytics output to be easier to read
record analytics of the angular position and pid calculations
add the throttle to the analytics, but remove from the motor power until we know what to do with it
reset the angular position to zero every ten seconds to make it easier to debug
renamed the props so they are easier to understand
remove testing code, ensure pulse is only updated to a range that is safe
added a faux calculated pulse, this is to make sure that small float values add up to something meaningful
convert the pid dude to use floats, this gives me more control to set fine grained configuration values
move the throttle to a neutral (50%) position, zero isn't helpful; ensure the analytics print out the right props on the right axis
remove the reset every 60 seconds, ensure that the pid is used to set not update. this means that the pid will behave more functional
ensure that at zero throttle the quad is powered off; normalise the throttle to have some control while attempting a test flight
added grafana as a way to display what is happening to the quad