Note
This Brick is currently in the prototype stage and the software/hardware as well as the documentation is in an incomplete state.
This is the description of the C/C++ API bindings for the IMU Brick 2.0. General information and technical specifications for the IMU Brick 2.0 are summarized in its hardware description.
An installation guide for the C/C++ API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Every function of the C/C++ bindings returns an integer which describes an error code. Data returned from the device, when a getter is called, is handled via call by reference. These parameters are labeled with the ret_ prefix.
Possible error codes are:
as defined in ip_connection.h.
All functions listed below are thread-safe.
Creates the device object imu_v2 with the unique device ID uid and adds it to the IPConnection ipcon:
IMUV2 imu_v2;
imu_v2_create(&imu_v2, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected (see examples above).
Removes the device object imu_v2 from its IPConnection and destroys it. The device object cannot be used anymore afterwards.
Return all of the available data of the IMU Brick.
The calibration status consists of four pairs of two bits. Each pair of bits represents the status of the current calibration.
A value of 0 means for "not calibrated" and a value of 3 means "fully calibrated". In your program you should always be able to ignore the calibration status, it is used by the calibration window of the Brick Viewer and it can be ignored after the first calibration. See the documentation in the calibration window for more information regarding the calibration of the IMU Brick.
If you want to get the data periodically, it is recommended to use the callback IMU_V2_CALLBACK_ALL_DATA and set the period with imu_v2_set_all_data_period().
Turns the orientation and direction LEDs of the IMU Brick on.
Turns the orientation and direction LEDs of the IMU Brick off.
Returns true if the orientation and direction LEDs of the IMU Brick are on, false otherwise.
Returns the calibrated acceleration from the accelerometer for the x, y and z axis in 1/100 m/s².
If you want to get the acceleration periodically, it is recommended to use the callback IMU_V2_CALLBACK_ACCELERATION and set the period with imu_v2_set_acceleration_period().
Returns the calibrated magnetic field from the magnetometer for the x, y and z axis in 1/16 µT (Microtesla).
If you want to get the magnetic field periodically, it is recommended to use the callback IMU_V2_CALLBACK_MAGNETIC_FIELD and set the period with imu_v2_set_magnetic_field_period().
Returns the calibrated angular velocity from the gyroscope for the x, y and z axis in 1/16 °/s.
If you want to get the angular velocity periodically, it is recommended to use the callback IMU_V2_CALLBACK_ANGULAR_VELOCITY and set the period with imu_v2_set_angular_velocity_period().
Returns the temperature of the IMU Brick. The temperature is given in °C. The temperature is measured in the core of the BNO055 IC, it is not the ambient temperature
Returns the current orientation (heading, roll, pitch) of the IMU Brick as Euler angles in 1/16 degree. Note that Euler angles always experience a gimbal lock.
We recommend that you use quaternions instead.
The rotation angle has the following ranges:
If you want to get the orientation periodically, it is recommended to use the callback IMU_V2_CALLBACK_ORIENTATION and set the period with imu_v2_set_orientation_period().
Returns the linear acceleration of the IMU Brick for the x, y and z axis in 1/100 m/s².
The linear acceleration is the acceleration in each of the three axis of the IMU Brick with the influences of gravity removed.
It is also possible to get the gravity vector with the influence of linear acceleration removed, see imu_v2_get_gravity_vector().
If you want to get the linear acceleration periodically, it is recommended to use the callback IMU_V2_CALLBACK_LINEAR_ACCELERATION and set the period with imu_v2_set_linear_acceleration_period().
Returns the current gravity vector of the IMU Brick for the x, y and z axis in 1/100 m/s².
The gravity vector is the acceleration that occurs due to gravity. Influences of additional linear acceleration are removed.
It is also possible to get the linear acceleration with the influence of gravity removed, see imu_v2_get_linear_acceleration().
If you want to get the gravity vector periodically, it is recommended to use the callback IMU_V2_CALLBACK_GRAVITY_VECTOR and set the period with imu_v2_set_gravity_vector_period().
Returns the current orientation (w, x, y, z) of the IMU Brick as quaternions.
You have to divide the returns values by 16383 (14 bit) to get the usual range of -1.0 to +1.0 for quaternions.
If you want to get the quaternions periodically, it is recommended to use the callback IMU_V2_CALLBACK_QUATERNION and set the period with imu_v2_set_quaternion_period().
A call of this function saves the current calibration to be used as a starting point for the next restart of continuous calibration of the IMU Brick.
A return value of true means that the calibration could be used and false means that it could not be used (this happens if the calibration status is not "fully calibrated").
This function is used by the calibration window of the Brick Viewer, you should not need to call it in your program.
Returns the version of the API definition (major, minor, revision) implemented by this API bindings. This is neither the release version of this API bindings nor does it tell you anything about the represented Brick or Bricklet.
Returns the response expected flag for the function specified by the function ID parameter. It is true if the function is expected to send a response, false otherwise.
For getter functions this is enabled by default and cannot be disabled, because those functions will always send a response. For callback configuration functions it is enabled by default too, but can be disabled by imu_v2_set_response_expected(). For setter functions it is disabled by default and can be enabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.
See imu_v2_set_response_expected() for the list of function ID defines available for this function.
Changes the response expected flag of the function specified by the function ID parameter. This flag can only be changed for setter (default value: false) and callback configuration functions (default value: true). For getter functions it is always enabled and callbacks it is always disabled.
Enabling the response expected flag for a setter function allows to detect timeouts and other error conditions calls of this setter as well. The device will then send a response for this purpose. If this flag is disabled for a setter function then no response is send and errors are silently ignored, because they cannot be detected.
The following function ID defines are available for this function:
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Enables the status LED.
The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.
The default state is enabled.
Disables the status LED.
The status LED is the blue LED next to the USB connector. If enabled is is on and it flickers if data is transfered. If disabled it is always off.
The default state is enabled.
Returns true if the status LED is enabled, false otherwise.
Returns the firmware and protocol version and the name of the Bricklet for a given port.
This functions sole purpose is to allow automatic flashing of v1.x.y Bricklet plugins.
Returns the temperature in °C/10 as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has an accuracy of +-15%. Practically it is only useful as an indicator for temperature changes.
Calling this function will reset the Brick. Calling this function on a Brick inside of a stack will reset the whole stack.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
Returns the UID, the UID where the Brick is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be '0'-'8' (stack position).
The device identifier numbers can be found here. There is also a constant for the device identifier of this Brick.
Registers a callback with ID id to the function callback. The user_data will be given as a parameter of the callback.
The available IDs with corresponding function signatures are listed below.
Sets the period in ms with which the IMU_V2_CALLBACK_ACCELERATION callback is triggered periodically. A value of 0 turns the callback off.
The default value is 0.
Returns the period as set by imu_v2_set_acceleration_period().
Sets the period in ms with which the IMU_V2_CALLBACK_MAGNETIC_FIELD callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_magnetic_field_period().
Sets the period in ms with which the IMU_V2_CALLBACK_ANGULAR_VELOCITY callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_angular_velocity_period().
Sets the period in ms with which the IMU_V2_CALLBACK_TEMPERATURE callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_temperature_period().
Sets the period in ms with which the IMU_V2_CALLBACK_ORIENTATION callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_orientation_period().
Sets the period in ms with which the IMU_V2_CALLBACK_LINEAR_ACCELERATION callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_linear_acceleration_period().
Sets the period in ms with which the IMU_V2_CALLBACK_GRAVITY_VECTOR callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_gravity_vector_period().
Sets the period in ms with which the IMU_V2_CALLBACK_QUATERNION callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_quaternion_period().
Sets the period in ms with which the IMU_V2_CALLBACK_ALL_DATA callback is triggered periodically. A value of 0 turns the callback off.
Returns the period as set by imu_v2_set_all_data_period().
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the imu_v2_register_callback() function. The parameters consist of the device object, the callback ID, the callback function and optional user data:
void my_callback(int p, void *user_data) { printf("parameter: %d\n", p); } imu_v2_register_callback(&imu_v2, IMU_V2_CALLBACK_EXAMPLE, (void *)my_callback, NULL);
The available constants with corresponding callback function signatures are described below.
Note
Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.
void callback(int16_t x, int16_t y, int16_t z, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_acceleration_period(). The parameters are the acceleration for the x, y and z axis.
void callback(int16_t x, int16_t y, int16_t z, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_magnetic_field_period(). The parameters are the magnetic field for the x, y and z axis.
void callback(int16_t x, int16_t y, int16_t z, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_angular_velocity_period(). The parameters are the angular velocity for the x, y and z axis.
void callback(int8_t temperature, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_temperature_period(). The parameter is the temperature.
void callback(int16_t x, int16_t y, int16_t z, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_linear_acceleration_period(). The parameters are the linear acceleration for the x, y and z axis.
void callback(int16_t x, int16_t y, int16_t z, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_gravity_vector_period(). The parameters gravity vector for the x, y and z axis.
void callback(int16_t heading, int16_t roll, int16_t pitch, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_orientation_period(). The parameters are the orientation (heading (yaw), roll, pitch) of the IMU Brick in Euler angles. See imu_v2_get_orientation() for details.
void callback(int16_t w, int16_t x, int16_t y, int16_t z, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_quaternion_period(). The parameters are the orientation (x, y, z, w) of the IMU Brick in quaternions. See imu_v2_get_quaternion() for details.
void callback(int16_t acceleration[3], int16_t magnetic_field[3], int16_t angular_velocity[3], int16_t euler_angle[3], int16_t quaternion[4], int16_t linear_acceleration[3], int16_t gravity_vector[3], int8_t temperature, uint8_t calibration_status, void *user_data)
This callback is triggered periodically with the period that is set by imu_v2_set_all_data_period(). The parameters are as for imu_v2_get_all_data().
This constant is used to identify a IMU Brick 2.0.
The imu_v2_get_identity() function and the IPCON_CALLBACK_ENUMERATE callback of the IP Connection have a device_identifier parameter to specify the Brick's or Bricklet's type.