Skip to content
Snippets Groups Projects
Select Git revision
  • DeePC_dev
  • FES_dev
  • MPC_dev
  • RAMPC_dev
  • master default protected
  • uwbmaster
6 results
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.04May29Apr2827222014139743130Mar2728Feb8Dec6529Nov282625221928Oct2214417Sep14Aug25Jul1076123Jun16151413108764330May292221191413125423Apr2086422Mar21201814Feb131211109754330Jan1219Dec1817151211986529Oct127Sep261817161210987630Aug28276Jul29Jun2825248May75432130Apr27262524232019181716131092Mar22Feb10Jan8629Dec2827262218161054130Nov292726242322211918171512111095432131Oct282523Changed Get Agent Status service to return stringsAdded first attempt at node that offers a status-as-json service for the web interfacAdjust the size of the ViconData and CFOnboardEstimate queues to avoid processing old data (this may be the reason that the CF flys too high on first take-off when using CF onboard estimatesAdded more detail to .gitignore comment about not tracking Config.sh and Crazyflie.db filesAdded the Crazyflie.db database back to the repository with a default configuration of agent 1 controlling CF01 in a generously size boxAdded comment to web interface installation script for removing a user from a groupWeb interface now working for launching both the master and agent. VERY IMPORTANT is the command added to the web interface install script that the www-data user must be added to the plugdev group so that nodes launched by the web interface have permission to access the CrazyRadio USB dongleAdded the GyroMeasurements message to the CMakeListFixed error in CrazyRadio python node due to still invovling wrong send to commander functionFixed errors in CrazyRadio python script and tested to work with actual radio and Crazyflie 2.1 running the new dfall firmwareUpdated web interface with switchesProperly integrated both the mocap and crazyradio emulators with the data flow of state estimate data coming from onboard a simulated Crazyflie. Also updated the student controller service to work with either mocap data or onboard estimate data. Next step is to test on the real quad.added some rudimentary code for uploading files and having it store in the folder called uploadsConnected the CrazyRadioEmulator to its Quadrotor Simulator. Tested to be working, however, it is important that to not emulate both Mocap and Crazyradio at the same time. Next step is to add a visualization of the simulator to the System Config GUI.Corrected delaration of a quadrotor simulation in the CrazyRadioEmulator node, required editing the CMakeListStarted with adding a quad simultor to the CrazyRadio emulator node so that the code can be tested in simulation for flying based on onboard estimate dataAdded Kalman filter reset to the CrazyRadio python node anytime the flying state changes from motors off to something elseUpdated the flying agent client node so that can easily choose between mocap data or onboard estimate data, or both, by using the yaml parameters. Needs testing. Next step is to update the CrazyRadio emulator to simulate a quad so that these updates to the flying agent client can be tested in simulationExtended the FlyingVehicleState message definition to inlude a type, and velocities (both translational and angular). Update the Vicon and Qualisys publishers to fill in the type. Updated the CrazyRadio node to fill in this expanded FlyingVehicleState correctly, including adding a crazyflie name property to the CrazyRadioClient class. Removed all empty lines as end of message definitions.Changed the CrazyflieData message to be called FlyingVehicleData and changed the names of its properties from occluded to isValid and from crazyflieName to vehicleNameUpdated the Parameter Service node so that that yaml files are added to a map of Publishers and hence the sleep is only needed the first time an unknown yaml file is loaded. Changed the getParameterFloatVector function to be getParameterFloatVectorKnownLength. Added functionality to the GUI to hide and show the load YAML bar.Corrected small error in the Student controller for confirming with the new Control Command message definition. Cleaned up a few small things at the same time.Updated the Crazyflie firmware to correctly parse the new package type that was implement in the previous commit to the CrazyRadio node. Needs testing, but before testing, the next step is to make the flying agent client easily choose between Vicon or the CF state estimateAdded first attempt at a web interface. This was used for the IFAC video, but needs more work to be used of the home version of the pandsFixed some small BUUUUUGGGGGGGSSSS so that the student controller service now compiles, mainly missing semi-colons from Jeremys edits because he is not able to compile on his machine to find these BUGGGGGSSSUpdated also the Student Controller to be compatible with the new type of control command packageUpdated the Crazyradio node in prepartion for the new generic control command package type that is sent to the Crazyflie and also to log the state estimate back from the Crazyflie. All the Controllers are also updated and tested to compile with this new package type as the response. Needs to be tested in simulation. Next steps are to: 1) adjust the Crazyflie firmware to parse the package correctly, and 2) make the flying agent client easily choose between Vicon or the CF state estimateRemoved computeMotorPolyBackwards from StudentControllerService.cpp and instead included it in the GetParametersAndNamespaces.h and .cpp files with a new name newtons2cmd_for_crazyflie. Put some example yaml parameters in for students and commented in StudentControllerService.cpp where they should define class variables. Added a get debug values service.Added definition of the Get Debug Values ServiceVERSION NUMBER UPDATE: to reflect updating of firmware to support Crazyflie 2.1For the system config GUI, this commit comments out some debugging print out statements that fills the terminal with unecessary informationMade Vicon Data Publisher stop trying to connect after 3 attemptsVERSION NUMBER UPDATE: to reflect the addition of the Qualisys filesAdded the first working files for Qualisys integration. Next steps for Qualisys integration are to adjust the System Config GUI and mocap naming conventions so that the user can seemlessly choose between Vicon and Qualisys.VERSION NUMBER UPDATE: to reflect the upgrade to add a CS1 controller and other small GUI improvementsMerge branch 'cs1' into 'master'Corrected small error in the implemation of setstatus for the controller status bannerUpdated the csone picker remote template and tuning controllers to correctly respond to the is first controller call flagAdded a flag in the controller call so that the flying agent client node notifies the controller being call of whether this is the first call or not. The default controller and student controller correctly respond to this flag, while the other controllers need to be updated to take it into accountAdded zmin and zmax fields to the System Config GUI. All zones get the same height when clicking the save in DB button. It would be nice to do a further update where each zone can have a different vertical extent