The coordinator row and (dis-)connect,  start-stop bar are now fully connected and fully generalised for operating as both an agent and a coordinator GUI

Yaml connections working (for student and demo controller), and title is now proper. Ready for testing on real system before cleaning up the controllers and their interface

Started connecting the Connect Start Stop Bar of the GUI. Now needs some GUI settings to be changed with Qt

Have setup the basic framework of the coordinator connections. Next step to connect all GUI buttons for (dis-)connect, start,stop,off,and select controller. And then test.

Added link to use custom controller and safe controller. Need to see what happens if we change yaml file name on the run

added disconnect command, need to test. Also added protection when disconnected to change flying state. Also buttons are now really disabled when disconnected

Now if the CF disconnects, the state goes back to motors off so when we start over we dont have the device flying

Reconnection working now. Need to discuss if it is better to have scripts called from GUI or the way it is done now

Crazyradio publishes now the battery voltage and can be accessed either in the terminal by using rostopic echo /studentnumber/cfbattery OR by making a listener that listens to the topic cfbattery

solved issued on data record. extended Student.launch with rqt dashboard plugin to send manually configured topics.

Crazyradio logs batterz status and writes to bag file. Conversion issue and bagdata is useless. But battery status and stabilizer logs are already printed to console at 1000ms rate