Logging and parameter frameworks

The aim of the logging and parameter framework is to easily be able to log data from the Crazyflie and to set variables during runtime.

Table of content (TOC)

The variables that are available for the logging/parameter framework are defined at compile-time for the Crazyflie firmware. C macros are used to define which variables that should be available to the framework.

A parameter or logging variable that is created with PARAM_ADD_CORE or LOG_ADD_CORE is considered stable API and will with a very high likelihood be available a cross firmware versions. All core parameters and logging variables must have documentation associated with it. None-core, development, parameter and logging variables should be indicated with only PARAM_ADD and LOG_ADD, which should indicate that no guarantee is given that this values will stay in later versions. See below for examples of the documentation syntax.

Below are two examples, one for a parameter and one for logging. This will make the parameters used to control the LED-ring expansion available as parameters. Note that they have different types and that neffect is read-only.

 * [Documentation for the ring group ...]

 * @brief [Documentation for the parameter below ...]
PARAM_ADD_CORE(PARAM_UINT8, effect, &effect)

 * @brief [Documentation for the parameter effect ...]

 * @brief [Documentation for the parameter effect ...]
PARAM_ADD_CORE(PARAM_UINT8, solidRed, &solidRed)


PARAM_ADD(PARAM_FLOAT, emptyCharge, &emptyCharge)
PARAM_ADD(PARAM_FLOAT, fullCharge, &fullCharge)

This will make the variables for roll/pitch/yaw/thrust available for the logging framework. These are the variables used to fill in the data in the Python cfclient FlightTab.

 * [Documentation for the stabilizer group ...]

 * @brief [Documentation for variable below ...]
LOG_ADD_CORE(LOG_FLOAT, roll, &eulerRollActual)

 * @brief [Documentation for variable below ...]
LOG_ADD_CORE(LOG_FLOAT, pitch, &eulerPitchActual)

 * @brief [Documentation for variable below ...]
LOG_ADD_CORE(LOG_FLOAT, yaw, &eulerYawActual)

 * @brief [Documentation for variable below ...]
LOG_ADD_CORE(LOG_UINT16, thrust, &actuatorThrust)


During the compilation a table of content (TOC) is created that holds all the available variables together with the type and access restrictions. There’s one TOC for each framework, one for logging and one for parameters. When the client connects it will download the TOC to know which variables can be used. It’s then easy to use the Python API (or another API) for accessing them.

All the variables have a name and belong to a group. So in the examples above there’s two groups defined: ring and stabilizer. To refer to a variable use the naming convention group.name. If you would like to log the roll variable in the stabilizer group it’s access by stabilizer.roll. And if you would like to set the effect variable in the ring group it’s accessed using ring.effect.

Log Variable length

Please use length upto 26 as total log variable length (group + name +1)


Using the parameter framework it’s possible to both read and write variables in run-time, but note the following:

  • There’s no thread protection on reading/writing. Since the architecture is 32bit and the largest parameter you can have is 32bit it’s safe to write one variable. But if you write a group of variables that should be used together (like PID parameters) you might end up in trouble.
  • Only use the parameter framework to read variables that are set during start-up. If variables change during runtime then use the logging framework.
  • The reading or writing of a parameter can be done at any time once you are connected to the Crazyflie.
  • if the PARAM_CALLBACK type is set, to get notified that it has changed, tha callback will run from the param task. It should not block and not take to long.

Persistent parameters

Is is possible to mark a parameter to be persistent. In this case, the value can be stored in persistent memory, which means the associated variable automatically will be set to this value after a re-boot.

To store a new value for a parameter, the new value must first be set and secondly, stored in persistent memory.

To mark a parameter as persistent, use the PARAM_PERSISTENT constant:



The logging framework is used to log variables from the Crazyflie at a specific interval. Instead of triggering a reading of the variables at certain intervals, the framework is used to set up a logging configuration to that will push data from the Crazyflie to the host. After the host has connected to a Crazyflie and downloaded the TOC it will be possible to setup one of these configurations. Once the configuration is set up and started the Crazyflie will start pushing data to the host. A configuration can be stopped and re-started again. Since there’s a finite amount of memory a configuration can be deleted to make room for new ones.

Note the following for the logging framework:

  • Once a Crazyflie is connected you can set up new logging configurations. It’s only possible to create/start/stop/remove configurations that’s already created.
  • The interval for a logging configuration is specified in 10th of milliseconds.

Note that variables can be logged as different types from what they have been declared as in the firmware. I.e if a variable is declared as a uint32_t you can log it as a uint8_t (this is being done for the motors in the UI).

Logging using a function

It is possible to use a function to acquire log values instead of reading from a memory location. The idea is to support more complex use cases where, for instance computations are required to produce the log value.

The macro


is used to add a log to a group. TYPE and NAME works the same way as for variable logging, but ADDRESS should point at a logByFunction_t struct instead of a variable. The struct contains a function pointer to the function to call when acquiring data, as well as a void pointer with user data passed that is passed on in the function call.


    float myLogValueFunction(uint32_t timestamp, void* data) {
        // Return the log value
        return 47.11;

    logByFunction_t myLogger = {.aquireFloat = myLogValueFunction, .data = 0};

    LOG_ADD_BY_FUNCTION(LOG_FLOAT, myLog, &myLogger)

Note: The logging function is only called if the log is part of an active log configuration. It will be called (approximately) at the interval that is setup in the log configuration.

Logging rates

A common usecase is to log rates (events / s) and there are a set of macros to simplify this task.

The rate logger uses a struct to store data, it is called statsCntRateCounter_t and is initialize using the STATS_CNT_RATE_INITmacro. The struct contains a counter, time information and the latest calculated rate. The initialization macro takes a parameter that specifies the update interval (in ms) and defines how often the rate (delta count / delta time) is calculated. The update interval should match the expected event rate to give meaningful results.

With the STATS_CNT_RATE_DEFINE macro, the struct can be defined and initialized in one line.

To register an event, that is to increase the counter, use the STATS_CNT_RATE_EVENTmacro.

Register the rate counter in a log group witht the STATS_CNT_RATE_LOG_ADD macro.


    static const uint32_t one_second = 1000;
    static statsCntRateLogger_t myCounter;
    static STATS_CNT_RATE_DEFINE(myOtherCounter, one_second);

    void myInit() {
        STATS_CNT_RATE_INIT(&myCounter, one_second);

    void theFcnThatIWantTheCallRateFor() {

        // The logging type is implicitly LOG_FLOAT
        STATS_CNT_RATE_LOG_ADD(rtCall, &myCounter)
        STATS_CNT_RATE_LOG_ADD(rtCall2, &myOtherCounter)

Note: The rate computation function is called from the logging framework with the interval specifed in the logging configuration. The rate, on the other hand, is calculated if the time since last computation exceeds the configured update time of the rate logger, and if the logging intervall is longer than the update intervall, updates will be done for each logging call.

Parameter callback function to get notified when a parameter has been updated.

Using the macro PARAM_ADD_WITH_CALLBACK it is possible to register a callback function that will be called when the parameter gets updated. This callback will run from the parameter task so it is important to not block in this callback or make it run for too long.


     void myCallbackFunction(void)
        // The parameter has been updated before the callback and the new parameter value can be used
        digitalWrite(DECK_GPIO_IO1, pinValue);


     PARAM_ADD_WITH_CALLBACK(PARAM_UINT8, setIO1pin, &pinValue, &myCallbackFunction)

Debug logging

Sometimes it is useful to log data when debugging a module, but we want the logs to be disabled by default to avoid adding to the size of the TOC. There is a set of macros to support this, all ending in _DEBUG.


These macros behaves the same way as the “normal” macros without the _DEBUG extension, but they are ignored unless CONFIG_DEBUG_LOG_ENABLE is defined. The intended use is to add a define in a C file before the log.h or statsCnt.h is included to enable the macros.


// Uncomment this line to enable extra logs when debugging
#include "log.h"
#include "statsCnt.h"

#define ONE_SECOND 1000



static float someData;
static float otherData;

void aFunction(float aValue, bool doStuff) {
  someData = aValue;

  if (doStuff) {
    otherData = someData * 2.0f;

// These will always be available
LOG_ADD(LOG_FLOAT, someData, &someData)
STATS_CNT_RATE_LOG_ADD(firstRt, &firstRate)

// These will only be available if CONFIG_DEBUG_LOG_ENABLE is defined
LOG_ADD_DEBUG(LOG_FLOAT, otherData, &otherData)
STATS_CNT_RATE_LOG_ADD_DEBUG(secondRt, &secondRate)