This is the description of the C/C++ API bindings for the IMU Bricklet 3.0. General information and technical specifications for the IMU Bricklet 3.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).
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_imu_v3.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your IMU Bricklet 3.0
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
IMUV3 imu;
imu_v3_create(&imu, UID, &ipcon);
// Connect to brickd
if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
fprintf(stderr, "Could not connect\n");
return 1;
}
// Don't use device before ipcon is connected
// Get current quaternion
int16_t w, x, y, z;
if(imu_v3_get_quaternion(&imu, &w, &x, &y, &z) < 0) {
fprintf(stderr, "Could not get quaternion, probably timeout\n");
return 1;
}
printf("Quaternion [W]: %f\n", w/16383.0);
printf("Quaternion [X]: %f\n", x/16383.0);
printf("Quaternion [Y]: %f\n", y/16383.0);
printf("Quaternion [Z]: %f\n", z/16383.0);
printf("Press key to exit\n");
getchar();
imu_v3_destroy(&imu);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 0;
}
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_imu_v3.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your IMU Bricklet 3.0
// Callback function for quaternion callback
void cb_quaternion(int16_t w, int16_t x, int16_t y, int16_t z, void *user_data) {
(void)user_data; // avoid unused parameter warning
printf("Quaternion [W]: %f\n", w/16383.0);
printf("Quaternion [X]: %f\n", x/16383.0);
printf("Quaternion [Y]: %f\n", y/16383.0);
printf("Quaternion [Z]: %f\n", z/16383.0);
printf("\n");
}
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
IMUV3 imu;
imu_v3_create(&imu, UID, &ipcon);
// Connect to brickd
if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
fprintf(stderr, "Could not connect\n");
return 1;
}
// Don't use device before ipcon is connected
// Register quaternion callback to function cb_quaternion
imu_v3_register_callback(&imu,
IMU_V3_CALLBACK_QUATERNION,
(void (*)(void))cb_quaternion,
NULL);
// Set period for quaternion callback to 0.1s (100ms)
imu_v3_set_quaternion_callback_configuration(&imu, 100, false);
printf("Press key to exit\n");
getchar();
imu_v3_destroy(&imu);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 0;
}
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_imu_v3.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your IMU Bricklet 3.0
// Callback function for all data callback
void cb_all_data(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) {
(void)user_data; // avoid unused parameter warning
printf("Acceleration [X]: %f m/s²\n", acceleration[0]/100.0);
printf("Acceleration [Y]: %f m/s²\n", acceleration[1]/100.0);
printf("Acceleration [Z]: %f m/s²\n", acceleration[2]/100.0);
printf("Magnetic Field [X]: %f µT\n", magnetic_field[0]/16.0);
printf("Magnetic Field [Y]: %f µT\n", magnetic_field[1]/16.0);
printf("Magnetic Field [Z]: %f µT\n", magnetic_field[2]/16.0);
printf("Angular Velocity [X]: %f °/s\n", angular_velocity[0]/16.0);
printf("Angular Velocity [Y]: %f °/s\n", angular_velocity[1]/16.0);
printf("Angular Velocity [Z]: %f °/s\n", angular_velocity[2]/16.0);
printf("Euler Angle [Heading]: %f °\n", euler_angle[0]/16.0);
printf("Euler Angle [Roll]: %f °\n", euler_angle[1]/16.0);
printf("Euler Angle [Pitch]: %f °\n", euler_angle[2]/16.0);
printf("Quaternion [W]: %f\n", quaternion[0]/16383.0);
printf("Quaternion [X]: %f\n", quaternion[1]/16383.0);
printf("Quaternion [Y]: %f\n", quaternion[2]/16383.0);
printf("Quaternion [Z]: %f\n", quaternion[3]/16383.0);
printf("Linear Acceleration [X]: %f m/s²\n", linear_acceleration[0]/100.0);
printf("Linear Acceleration [Y]: %f m/s²\n", linear_acceleration[1]/100.0);
printf("Linear Acceleration [Z]: %f m/s²\n", linear_acceleration[2]/100.0);
printf("Gravity Vector [X]: %f m/s²\n", gravity_vector[0]/100.0);
printf("Gravity Vector [Y]: %f m/s²\n", gravity_vector[1]/100.0);
printf("Gravity Vector [Z]: %f m/s²\n", gravity_vector[2]/100.0);
printf("Temperature: %d °C\n", temperature);
printf("Calibration Status: %u\n", calibration_status);
printf("\n");
}
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
IMUV3 imu;
imu_v3_create(&imu, UID, &ipcon);
// Connect to brickd
if(ipcon_connect(&ipcon, HOST, PORT) < 0) {
fprintf(stderr, "Could not connect\n");
return 1;
}
// Don't use device before ipcon is connected
// Register all data callback to function cb_all_data
imu_v3_register_callback(&imu,
IMU_V3_CALLBACK_ALL_DATA,
(void (*)(void))cb_all_data,
NULL);
// Set period for all data callback to 0.1s (100ms)
imu_v3_set_all_data_callback_configuration(&imu, 100, false);
printf("Press key to exit\n");
getchar();
imu_v3_destroy(&imu);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 0;
}
|
Most functions of the C/C++ bindings return an error code (e_code
).
Data returned from the device, when a getter is called,
is handled via output parameters. 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.
imu_v3_create
(IMUV3 *imu_v3, const char *uid, IPConnection *ipcon)¶Parameters: |
|
---|
Creates the device object imu_v3
with the unique device ID uid
and adds
it to the IPConnection ipcon
:
IMUV3 imu_v3;
imu_v3_create(&imu_v3, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected.
imu_v3_destroy
(IMUV3 *imu_v3)¶Parameters: |
|
---|
Removes the device object imu_v3
from its IPConnection and destroys it.
The device object cannot be used anymore afterwards.
imu_v3_get_orientation
(IMUV3 *imu_v3, int16_t *ret_heading, int16_t *ret_roll, int16_t *ret_pitch)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current orientation (heading, roll, pitch) of the IMU Brick as independent Euler angles. Note that Euler angles always experience a gimbal lock. We recommend that you use quaternions instead, if you need the absolute orientation.
If you want to get the orientation periodically, it is recommended
to use the IMU_V3_CALLBACK_ORIENTATION
callback and set the period with
imu_v3_set_orientation_callback_configuration()
.
imu_v3_get_linear_acceleration
(IMUV3 *imu_v3, int16_t *ret_x, int16_t *ret_y, int16_t *ret_z)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the linear acceleration of the IMU Brick for the
x, y and z axis. The acceleration is in the range configured with
imu_v3_set_sensor_configuration()
.
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_v3_get_gravity_vector()
.
If you want to get the linear acceleration periodically, it is recommended
to use the IMU_V3_CALLBACK_LINEAR_ACCELERATION
callback and set the period with
imu_v3_set_linear_acceleration_callback_configuration()
.
imu_v3_get_gravity_vector
(IMUV3 *imu_v3, int16_t *ret_x, int16_t *ret_y, int16_t *ret_z)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current gravity vector of the IMU Brick for the x, y and z axis.
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_v3_get_linear_acceleration()
.
If you want to get the gravity vector periodically, it is recommended
to use the IMU_V3_CALLBACK_GRAVITY_VECTOR
callback and set the period with
imu_v3_set_gravity_vector_callback_configuration()
.
imu_v3_get_quaternion
(IMUV3 *imu_v3, int16_t *ret_w, int16_t *ret_x, int16_t *ret_y, int16_t *ret_z)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current orientation (w, x, y, z) of the IMU Brick as quaternions.
You have to divide the return 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 IMU_V3_CALLBACK_QUATERNION
callback and set the period with
imu_v3_set_quaternion_callback_configuration()
.
imu_v3_get_all_data
(IMUV3 *imu_v3, int16_t ret_acceleration[3], int16_t ret_magnetic_field[3], int16_t ret_angular_velocity[3], int16_t ret_euler_angle[3], int16_t ret_quaternion[4], int16_t ret_linear_acceleration[3], int16_t ret_gravity_vector[3], int8_t *ret_temperature, uint8_t *ret_calibration_status)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Return all of the available data of the IMU Brick.
imu_v3_get_acceleration()
)imu_v3_get_magnetic_field()
)imu_v3_get_angular_velocity()
)imu_v3_get_orientation()
)imu_v3_get_quaternion()
)imu_v3_get_linear_acceleration()
)imu_v3_get_gravity_vector()
)imu_v3_get_temperature()
)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 IMU_V3_CALLBACK_ALL_DATA
callback and set the period with
imu_v3_set_all_data_callback_configuration()
.
imu_v3_get_acceleration
(IMUV3 *imu_v3, int16_t *ret_x, int16_t *ret_y, int16_t *ret_z)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the calibrated acceleration from the accelerometer for the
x, y and z axis. The acceleration is in the range configured with
imu_v3_set_sensor_configuration()
.
If you want to get the acceleration periodically, it is recommended
to use the IMU_V3_CALLBACK_ACCELERATION
callback and set the period with
imu_v3_set_acceleration_callback_configuration()
.
imu_v3_get_magnetic_field
(IMUV3 *imu_v3, int16_t *ret_x, int16_t *ret_y, int16_t *ret_z)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the calibrated magnetic field from the magnetometer for the x, y and z axis.
If you want to get the magnetic field periodically, it is recommended
to use the IMU_V3_CALLBACK_MAGNETIC_FIELD
callback and set the period with
imu_v3_set_magnetic_field_callback_configuration()
.
imu_v3_get_angular_velocity
(IMUV3 *imu_v3, int16_t *ret_x, int16_t *ret_y, int16_t *ret_z)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the calibrated angular velocity from the gyroscope for the
x, y and z axis. The angular velocity is in the range configured with
imu_v3_set_sensor_configuration()
.
If you want to get the angular velocity periodically, it is recommended
to use the IMU_V3_CALLBACK_ANGULAR_VELOCITY
acallback nd set the period with
imu_v3_set_angular_velocity_callback_configuration()
.
imu_v3_get_temperature
(IMUV3 *imu_v3, int8_t *ret_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the temperature of the IMU Brick. The temperature is measured in the core of the BNO055 IC, it is not the ambient temperature
imu_v3_save_calibration
(IMUV3 *imu_v3, bool *ret_calibration_done)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
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.
imu_v3_set_sensor_configuration
(IMUV3 *imu_v3, uint8_t magnetometer_rate, uint8_t gyroscope_range, uint8_t gyroscope_bandwidth, uint8_t accelerometer_range, uint8_t accelerometer_bandwidth)¶Parameters: |
|
---|---|
Returns: |
|
Sets the available sensor configuration for the Magnetometer, Gyroscope and Accelerometer. The Accelerometer Range is user selectable in all fusion modes, all other configurations are auto-controlled in fusion mode.
The following constants are available for this function:
For magnetometer_rate:
For gyroscope_range:
For gyroscope_bandwidth:
For accelerometer_range:
For accelerometer_bandwidth:
imu_v3_get_sensor_configuration
(IMUV3 *imu_v3, uint8_t *ret_magnetometer_rate, uint8_t *ret_gyroscope_range, uint8_t *ret_gyroscope_bandwidth, uint8_t *ret_accelerometer_range, uint8_t *ret_accelerometer_bandwidth)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the sensor configuration as set by imu_v3_set_sensor_configuration()
.
The following constants are available for this function:
For ret_magnetometer_rate:
For ret_gyroscope_range:
For ret_gyroscope_bandwidth:
For ret_accelerometer_range:
For ret_accelerometer_bandwidth:
imu_v3_set_sensor_fusion_mode
(IMUV3 *imu_v3, uint8_t mode)¶Parameters: |
|
---|---|
Returns: |
|
If the fusion mode is turned off, the functions imu_v3_get_acceleration()
,
imu_v3_get_magnetic_field()
and imu_v3_get_angular_velocity()
return uncalibrated
and uncompensated sensor data. All other sensor data getters return no data.
Since firmware version 2.0.6 you can also use a fusion mode without magnetometer. In this mode the calculated orientation is relative (with magnetometer it is absolute with respect to the earth). However, the calculation can't be influenced by spurious magnetic fields.
Since firmware version 2.0.13 you can also use a fusion mode without fast magnetometer calibration. This mode is the same as the normal fusion mode, but the fast magnetometer calibration is turned off. So to find the orientation the first time will likely take longer, but small magnetic influences might not affect the automatic calibration as much.
The following constants are available for this function:
For mode:
imu_v3_get_sensor_fusion_mode
(IMUV3 *imu_v3, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the sensor fusion mode as set by imu_v3_set_sensor_fusion_mode()
.
The following constants are available for this function:
For ret_mode:
imu_v3_get_spitfp_error_count
(IMUV3 *imu_v3, uint32_t *ret_error_count_ack_checksum, uint32_t *ret_error_count_message_checksum, uint32_t *ret_error_count_frame, uint32_t *ret_error_count_overflow)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
imu_v3_set_status_led_config
(IMUV3 *imu_v3, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following constants are available for this function:
For config:
imu_v3_get_status_led_config
(IMUV3 *imu_v3, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by imu_v3_set_status_led_config()
The following constants are available for this function:
For ret_config:
imu_v3_get_chip_temperature
(IMUV3 *imu_v3, int16_t *ret_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the temperature 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 bad accuracy. Practically it is only useful as an indicator for temperature changes.
imu_v3_reset
(IMUV3 *imu_v3)¶Parameters: |
|
---|---|
Returns: |
|
Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
imu_v3_get_identity
(IMUV3 *imu_v3, char ret_uid[8], char ret_connected_uid[8], char *ret_position, uint8_t ret_hardware_version[3], uint8_t ret_firmware_version[3], uint16_t *ret_device_identifier)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here. There is also a constant for the device identifier of this Bricklet.
imu_v3_register_callback
(IMUV3 *imu_v3, int16_t callback_id, void (*function)(void), void *user_data)¶Parameters: |
|
---|
Registers the given function
with the given callback_id
. The
user_data
will be passed as the last parameter to the function
.
The available callback IDs with corresponding function signatures are listed below.
imu_v3_set_acceleration_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_ACCELERATION
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_acceleration_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_acceleration_callback_configuration()
.
imu_v3_set_magnetic_field_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_MAGNETIC_FIELD
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_magnetic_field_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_magnetic_field_callback_configuration()
.
imu_v3_set_angular_velocity_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_ANGULAR_VELOCITY
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_angular_velocity_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_angular_velocity_callback_configuration()
.
imu_v3_set_temperature_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_TEMPERATURE
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_temperature_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_temperature_callback_configuration()
.
imu_v3_set_orientation_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_ORIENTATION
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_orientation_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_orientation_callback_configuration()
.
imu_v3_set_linear_acceleration_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_LINEAR_ACCELERATION
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_linear_acceleration_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_linear_acceleration_callback_configuration()
.
imu_v3_set_gravity_vector_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_GRAVITY_VECTOR
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_gravity_vector_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_gravity_vector_callback_configuration()
.
imu_v3_set_quaternion_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_QUATERNION
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_quaternion_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_quaternion_callback_configuration()
.
imu_v3_set_all_data_callback_configuration
(IMUV3 *imu_v3, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the IMU_V3_CALLBACK_ALL_DATA
callback
is triggered periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
imu_v3_get_all_data_callback_configuration
(IMUV3 *imu_v3, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by imu_v3_set_all_data_callback_configuration()
.
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the imu_v3_register_callback()
function:
void my_callback(int value, void *user_data) { printf("Value: %d\n", value); } imu_v3_register_callback(&imu_v3, IMU_V3_CALLBACK_EXAMPLE, (void (*)(void))my_callback, NULL);
The available constants with corresponding 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.
IMU_V3_CALLBACK_ACCELERATION
¶void callback(int16_t x, int16_t y, int16_t z, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_acceleration_callback_configuration()
. The parameters are the acceleration
for the x, y and z axis.
IMU_V3_CALLBACK_MAGNETIC_FIELD
¶void callback(int16_t x, int16_t y, int16_t z, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_magnetic_field_callback_configuration()
. The parameters are the magnetic
field for the x, y and z axis.
IMU_V3_CALLBACK_ANGULAR_VELOCITY
¶void callback(int16_t x, int16_t y, int16_t z, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_angular_velocity_callback_configuration()
. The parameters are the angular
velocity for the x, y and z axis.
IMU_V3_CALLBACK_TEMPERATURE
¶void callback(int8_t temperature, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_temperature_callback_configuration()
. The parameter is the temperature.
IMU_V3_CALLBACK_LINEAR_ACCELERATION
¶void callback(int16_t x, int16_t y, int16_t z, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_linear_acceleration_callback_configuration()
. The parameters are the
linear acceleration for the x, y and z axis.
IMU_V3_CALLBACK_GRAVITY_VECTOR
¶void callback(int16_t x, int16_t y, int16_t z, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_gravity_vector_callback_configuration()
. The parameters gravity vector
for the x, y and z axis.
IMU_V3_CALLBACK_ORIENTATION
¶void callback(int16_t heading, int16_t roll, int16_t pitch, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_orientation_callback_configuration()
. The parameters are the orientation
(heading (yaw), roll, pitch) of the IMU Brick in Euler angles. See
imu_v3_get_orientation()
for details.
IMU_V3_CALLBACK_QUATERNION
¶void callback(int16_t w, int16_t x, int16_t y, int16_t z, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_quaternion_callback_configuration()
. The parameters are the orientation
(w, x, y, z) of the IMU Brick in quaternions. See imu_v3_get_quaternion()
for details.
IMU_V3_CALLBACK_ALL_DATA
¶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)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
imu_v3_set_all_data_callback_configuration()
. The parameters are as for
imu_v3_get_all_data()
.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object. They can be called without the corresponding IP Connection object being connected.
imu_v3_get_api_version
(IMUV3 *imu_v3, uint8_t ret_api_version[3])¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the version of the API definition 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.
imu_v3_get_response_expected
(IMUV3 *imu_v3, uint8_t function_id, bool *ret_response_expected)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
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_v3_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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
imu_v3_set_response_expected
(IMUV3 *imu_v3, uint8_t function_id, bool response_expected)¶Parameters: |
|
---|---|
Returns: |
|
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.
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 sent and errors are silently ignored, because they cannot be detected.
The following constants are available for this function:
For function_id:
imu_v3_set_response_expected_all
(IMUV3 *imu_v3, bool response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
imu_v3_set_bootloader_mode
(IMUV3 *imu_v3, uint8_t mode, uint8_t *ret_status)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following constants are available for this function:
For mode:
For ret_status:
imu_v3_get_bootloader_mode
(IMUV3 *imu_v3, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current bootloader mode, see imu_v3_set_bootloader_mode()
.
The following constants are available for this function:
For ret_mode:
imu_v3_set_write_firmware_pointer
(IMUV3 *imu_v3, uint32_t pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for imu_v3_write_firmware()
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
imu_v3_write_firmware
(IMUV3 *imu_v3, uint8_t data[64], uint8_t *ret_status)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
imu_v3_set_write_firmware_pointer()
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
imu_v3_write_uid
(IMUV3 *imu_v3, uint32_t uid)¶Parameters: |
|
---|---|
Returns: |
|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
imu_v3_read_uid
(IMUV3 *imu_v3, uint32_t *ret_uid)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
IMU_V3_DEVICE_IDENTIFIER
¶This constant is used to identify a IMU Bricklet 3.0.
The imu_v3_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.
IMU_V3_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a IMU Bricklet 3.0.