The CLI is the base of the communication with the Crazyflie drone. It can optionally be used for basic tasks. You shouldn’t need to interact with the CLI during the course of the lab, but it can be useful for debugging if something goes wrong. It can be opened by adding a “nogui” flag to the end of the crazyCART script. crazycart <radiochannel> nogui
Run commands with ./Cli <command><parameters>...
Further usage details can be found by appending --help to the end of a command. The following commands are currently implemented.
| **Command** | **Description** |
| ------ | ------ |
| ./Cli outputoverride (enable) (Time) (Throttle) (Pitch) (Roll) (Yaw) | output override will send a setpoint that lasts a set amount of time with the specified throttle, roll pitch and yaw. With enable set to 1 it will send the setpoint as a rate and 2 will send the setpoint as an angle|
| ./Cli getparam (block_id or 'block_name') (param_id or 'param_name')| Get param will get the value of specified param. Note only the param id is used for this command. The param id is found in the logging TOC, use getlogfile 1 command to find this file|
| ./Cli setparam (block_id or 'block_name') (param_id or 'param_name') (value)| Set param will set the value of the specified param|
| ./Cli getlogfile (id)| Get log file will get a certain log specified by the id of: 0: data log 1: param id 2: logging toc |
| ./Cli logblockcommand (id)| The log block command performs specific tasks on log files for the specified id of: 0: delete all log blocks 1: refresh all log blocks 2: load log blocks 3: delete log block 4: resumelog block 5: pause log block
