MQTT - IMU Brick 2.0

This is the description of the MQTT 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 MQTT API bindings is part of their general description.

Examples

The example code below is Public Domain (CC0 1.0).

Simple

Download (example-simple.txt)

1
2
3
4
5
6
# Change XXYYZZ to the UID of your IMU Brick 2.0

setup:
    # Get current quaternion
    subscribe to tinkerforge/response/imu_v2_brick/XXYYZZ/get_quaternion
    publish '' to tinkerforge/request/imu_v2_brick/XXYYZZ/get_quaternion

All Data

Download (example-all-data.txt)

1
2
3
4
5
6
7
8
9
# Change XXYYZZ to the UID of your IMU Brick 2.0

setup:
    # Handle incoming all data callbacks
    subscribe to tinkerforge/callback/imu_v2_brick/XXYYZZ/all_data
    publish '{"register": true}' to tinkerforge/register/imu_v2_brick/XXYYZZ/all_data # Register all_data callback
    
    # Set period for all data callback to 0.1s (100ms)
    publish '{"period": 100}' to tinkerforge/request/imu_v2_brick/XXYYZZ/set_all_data_period

Callback

Download (example-callback.txt)

1
2
3
4
5
6
7
8
9
# Change XXYYZZ to the UID of your IMU Brick 2.0

setup:
    # Handle incoming quaternion callbacks
    subscribe to tinkerforge/callback/imu_v2_brick/XXYYZZ/quaternion
    publish '{"register": true}' to tinkerforge/register/imu_v2_brick/XXYYZZ/quaternion # Register quaternion callback
    
    # Set period for quaternion callback to 0.1s (100ms)
    publish '{"period": 100}' to tinkerforge/request/imu_v2_brick/XXYYZZ/set_quaternion_period

API

All published payloads to and from the MQTT bindings are in JSON format.

If an error occures, the bindings publish a JSON object containing the error message as attribute "_ERROR". It is published on the corresponding response topic: .../response/... for .../request/... and .../callback/... for .../register/....

Basic Functions

request/imu_v2_brick/<UID>/get_orientation
Response payload:
 
  • heading -- int
  • roll -- int
  • pitch -- int

Returns the current orientation (heading, roll, pitch) of the IMU Brick as independent Euler angles in 1/16 degree. Note that Euler angles always experience a gimbal lock. We recommend that you use quaternions instead, if you need the absolute orientation.

The rotation angle has the following ranges:

  • heading: 0° to 360°
  • roll: -90° to +90°
  • pitch: -180° to +180°

If you want to get the orientation periodically, it is recommended to use the register/imu_v2_brick/<UID>/orientation callback and set the period with request/imu_v2_brick/<UID>/set_orientation_period.

request/imu_v2_brick/<UID>/get_linear_acceleration
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

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 request/imu_v2_brick/<UID>/get_gravity_vector.

If you want to get the linear acceleration periodically, it is recommended to use the register/imu_v2_brick/<UID>/linear_acceleration callback and set the period with request/imu_v2_brick/<UID>/set_linear_acceleration_period.

request/imu_v2_brick/<UID>/get_gravity_vector
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

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 request/imu_v2_brick/<UID>/get_linear_acceleration.

If you want to get the gravity vector periodically, it is recommended to use the register/imu_v2_brick/<UID>/gravity_vector callback and set the period with request/imu_v2_brick/<UID>/set_gravity_vector_period.

request/imu_v2_brick/<UID>/get_quaternion
Response payload:
 
  • w -- int
  • x -- int
  • y -- int
  • z -- int

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 register/imu_v2_brick/<UID>/quaternion callback and set the period with request/imu_v2_brick/<UID>/set_quaternion_period.

request/imu_v2_brick/<UID>/get_all_data
Response payload:
 
  • acceleration -- [int,int,int]
  • magnetic_field -- [int,int,int]
  • angular_velocity -- [int,int,int]
  • euler_angle -- [int,int,int]
  • quaternion -- [int,int,int,int]
  • linear_acceleration -- [int,int,int]
  • gravity_vector -- [int,int,int]
  • temperature -- int
  • calibration_status -- int

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.

  • bit 0-1: Magnetometer
  • bit 2-3: Accelerometer
  • bit 4-5: Gyroscope
  • bit 6-7: System

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 register/imu_v2_brick/<UID>/all_data callback and set the period with request/imu_v2_brick/<UID>/set_all_data_period.

request/imu_v2_brick/<UID>/leds_on

Turns the orientation and direction LEDs of the IMU Brick on.

request/imu_v2_brick/<UID>/leds_off

Turns the orientation and direction LEDs of the IMU Brick off.

request/imu_v2_brick/<UID>/are_leds_on
Response payload:
 
  • leds -- bool

Returns true if the orientation and direction LEDs of the IMU Brick are on, false otherwise.

Advanced Functions

request/imu_v2_brick/<UID>/get_acceleration
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

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 register/imu_v2_brick/<UID>/acceleration callback and set the period with request/imu_v2_brick/<UID>/set_acceleration_period.

request/imu_v2_brick/<UID>/get_magnetic_field
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

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 register/imu_v2_brick/<UID>/magnetic_field callback and set the period with request/imu_v2_brick/<UID>/set_magnetic_field_period.

request/imu_v2_brick/<UID>/get_angular_velocity
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

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 register/imu_v2_brick/<UID>/angular_velocity acallback nd set the period with request/imu_v2_brick/<UID>/set_angular_velocity_period.

request/imu_v2_brick/<UID>/get_temperature
Response payload:
 
  • temperature -- int

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

request/imu_v2_brick/<UID>/save_calibration
Response payload:
 
  • calibration_done -- bool

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.

request/imu_v2_brick/<UID>/set_sensor_configuration
Request payload:
 
  • magnetometer_rate -- int (has symbols)
  • gyroscope_range -- int (has symbols)
  • gyroscope_bandwidth -- int (has symbols)
  • accelerometer_range -- int (has symbols)
  • accelerometer_bandwidth -- int (has symbols)

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 default values are:

  • Magnetometer Rate 20Hz
  • Gyroscope Range 2000°/s
  • Gyroscope Bandwidth 32Hz
  • Accelerometer Range +/-4G
  • Accelerometer Bandwidth 62.5Hz

The following symbols are available for this function:

for magnetometer_rate:

  • "2Hz" = 0
  • "6Hz" = 1
  • "8Hz" = 2
  • "10Hz" = 3
  • "15Hz" = 4
  • "20Hz" = 5
  • "25Hz" = 6
  • "30Hz" = 7

for gyroscope_range:

  • "2000DPS" = 0
  • "1000DPS" = 1
  • "500DPS" = 2
  • "250DPS" = 3
  • "125DPS" = 4

for gyroscope_bandwidth:

  • "523Hz" = 0
  • "230Hz" = 1
  • "116Hz" = 2
  • "47Hz" = 3
  • "23Hz" = 4
  • "12Hz" = 5
  • "64Hz" = 6
  • "32Hz" = 7

for accelerometer_range:

  • "2G" = 0
  • "4G" = 1
  • "8G" = 2
  • "16G" = 3

for accelerometer_bandwidth:

  • "781Hz" = 0
  • "1563Hz" = 1
  • "3125Hz" = 2
  • "625Hz" = 3
  • "125Hz" = 4
  • "250Hz" = 5
  • "500Hz" = 6
  • "1000Hz" = 7

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/get_sensor_configuration
Response payload:
 
  • magnetometer_rate -- int (has symbols)
  • gyroscope_range -- int (has symbols)
  • gyroscope_bandwidth -- int (has symbols)
  • accelerometer_range -- int (has symbols)
  • accelerometer_bandwidth -- int (has symbols)

Returns the sensor configuration as set by request/imu_v2_brick/<UID>/set_sensor_configuration.

The following symbols are available for this function:

for magnetometer_rate:

  • "2Hz" = 0
  • "6Hz" = 1
  • "8Hz" = 2
  • "10Hz" = 3
  • "15Hz" = 4
  • "20Hz" = 5
  • "25Hz" = 6
  • "30Hz" = 7

for gyroscope_range:

  • "2000DPS" = 0
  • "1000DPS" = 1
  • "500DPS" = 2
  • "250DPS" = 3
  • "125DPS" = 4

for gyroscope_bandwidth:

  • "523Hz" = 0
  • "230Hz" = 1
  • "116Hz" = 2
  • "47Hz" = 3
  • "23Hz" = 4
  • "12Hz" = 5
  • "64Hz" = 6
  • "32Hz" = 7

for accelerometer_range:

  • "2G" = 0
  • "4G" = 1
  • "8G" = 2
  • "16G" = 3

for accelerometer_bandwidth:

  • "781Hz" = 0
  • "1563Hz" = 1
  • "3125Hz" = 2
  • "625Hz" = 3
  • "125Hz" = 4
  • "250Hz" = 5
  • "500Hz" = 6
  • "1000Hz" = 7

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/set_sensor_fusion_mode
Request payload:
 
  • mode -- int (has symbols)

If the fusion mode is turned off, the functions request/imu_v2_brick/<UID>/get_acceleration, request/imu_v2_brick/<UID>/get_magnetic_field and request/imu_v2_brick/<UID>/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.

By default sensor fusion is on.

The following symbols are available for this function:

for mode:

  • "Off" = 0
  • "On" = 1
  • "OnWithoutMagnetometer" = 2
  • "OnWithoutFastMagnetometerCalibration" = 3

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/get_sensor_fusion_mode
Response payload:
 
  • mode -- int (has symbols)

Returns the sensor fusion mode as set by request/imu_v2_brick/<UID>/set_sensor_fusion_mode.

The following symbols are available for this function:

for mode:

  • "Off" = 0
  • "On" = 1
  • "OnWithoutMagnetometer" = 2
  • "OnWithoutFastMagnetometerCalibration" = 3

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/set_spitfp_baudrate_config
Request payload:
 
  • enable_dynamic_baudrate -- bool
  • minimum_dynamic_baudrate -- int

The SPITF protocol can be used with a dynamic baudrate. If the dynamic baudrate is enabled, the Brick will try to adapt the baudrate for the communication between Bricks and Bricklets according to the amount of data that is transferred.

The baudrate will be increased exponentially if lots of data is send/received and decreased linearly if little data is send/received.

This lowers the baudrate in applications where little data is transferred (e.g. a weather station) and increases the robustness. If there is lots of data to transfer (e.g. Thermal Imaging Bricklet) it automatically increases the baudrate as needed.

In cases where some data has to transferred as fast as possible every few seconds (e.g. RS485 Bricklet with a high baudrate but small payload) you may want to turn the dynamic baudrate off to get the highest possible performance.

The maximum value of the baudrate can be set per port with the function request/imu_v2_brick/<UID>/set_spitfp_baudrate. If the dynamic baudrate is disabled, the baudrate as set by request/imu_v2_brick/<UID>/set_spitfp_baudrate will be used statically.

The minimum dynamic baudrate has a value range of 400000 to 2000000 baud.

By default dynamic baudrate is enabled and the minimum dynamic baudrate is 400000.

New in version 2.0.10 (Firmware).

request/imu_v2_brick/<UID>/get_spitfp_baudrate_config
Response payload:
 
  • enable_dynamic_baudrate -- bool
  • minimum_dynamic_baudrate -- int

Returns the baudrate config, see request/imu_v2_brick/<UID>/set_spitfp_baudrate_config.

New in version 2.0.10 (Firmware).

request/imu_v2_brick/<UID>/get_send_timeout_count
Request payload:
 
  • communication_method -- int (has symbols)
Response payload:
 
  • timeout_count -- int

Returns the timeout count for the different communication methods.

The methods 0-2 are available for all Bricks, 3-7 only for Master Bricks.

This function is mostly used for debugging during development, in normal operation the counters should nearly always stay at 0.

The following symbols are available for this function:

for communication_method:

  • "None" = 0
  • "USB" = 1
  • "SPIStack" = 2
  • "Chibi" = 3
  • "RS485" = 4
  • "WIFI" = 5
  • "Ethernet" = 6
  • "WIFIV2" = 7

New in version 2.0.7 (Firmware).

request/imu_v2_brick/<UID>/set_spitfp_baudrate
Request payload:
 
  • bricklet_port -- string
  • baudrate -- int

Sets the baudrate for a specific Bricklet port ('a' - 'd'). The baudrate can be in the range 400000 to 2000000.

If you want to increase the throughput of Bricklets you can increase the baudrate. If you get a high error count because of high interference (see request/imu_v2_brick/<UID>/get_spitfp_error_count) you can decrease the baudrate.

If the dynamic baudrate feature is enabled, the baudrate set by this function corresponds to the maximum baudrate (see request/imu_v2_brick/<UID>/set_spitfp_baudrate_config).

Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in you applications we recommend to not change the baudrate.

The default baudrate for all ports is 1400000.

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/get_spitfp_baudrate
Request payload:
 
  • bricklet_port -- string
Response payload:
 
  • baudrate -- int

Returns the baudrate for a given Bricklet port, see request/imu_v2_brick/<UID>/set_spitfp_baudrate.

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/get_spitfp_error_count
Request payload:
 
  • bricklet_port -- string
Response payload:
 
  • error_count_ack_checksum -- int
  • error_count_message_checksum -- int
  • error_count_frame -- int
  • error_count_overflow -- int

Returns the error count for the communication between Brick and Bricklet.

The errors are divided into

  • ACK checksum errors,
  • message checksum errors,
  • framing errors and
  • overflow errors.

The errors counts are for errors that occur on the Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.

New in version 2.0.5 (Firmware).

request/imu_v2_brick/<UID>/enable_status_led

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.

request/imu_v2_brick/<UID>/disable_status_led

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.

request/imu_v2_brick/<UID>/is_status_led_enabled
Response payload:
 
  • enabled -- bool

Returns true if the status LED is enabled, false otherwise.

request/imu_v2_brick/<UID>/get_protocol1_bricklet_name
Request payload:
 
  • port -- string
Response payload:
 
  • protocol_version -- int
  • firmware_version -- [int,int,int]
  • name -- string

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.

request/imu_v2_brick/<UID>/get_chip_temperature
Response payload:
 
  • temperature -- int

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.

request/imu_v2_brick/<UID>/reset

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!

request/imu_v2_brick/<UID>/get_identity
Response payload:
 
  • uid -- string
  • connected_uid -- string
  • position -- string
  • hardware_version -- [int,int,int]
  • firmware_version -- [int,int,int]
  • device_identifier -- int (has symbols)
  • _display_name -- string

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. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.

The display name contains the IMU 2.0's name in a human readable form.

Callback Configuration Functions

request/imu_v2_brick/<UID>/set_acceleration_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/acceleration callback is triggered periodically. A value of 0 turns the callback off.

The default value is 0.

request/imu_v2_brick/<UID>/get_acceleration_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_acceleration_period.

request/imu_v2_brick/<UID>/set_magnetic_field_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/magnetic_field callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_magnetic_field_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_magnetic_field_period.

request/imu_v2_brick/<UID>/set_angular_velocity_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/angular_velocity callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_angular_velocity_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_angular_velocity_period.

request/imu_v2_brick/<UID>/set_temperature_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/temperature callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_temperature_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_temperature_period.

request/imu_v2_brick/<UID>/set_orientation_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/orientation callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_orientation_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_orientation_period.

request/imu_v2_brick/<UID>/set_linear_acceleration_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/linear_acceleration callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_linear_acceleration_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_linear_acceleration_period.

request/imu_v2_brick/<UID>/set_gravity_vector_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/gravity_vector callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_gravity_vector_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_gravity_vector_period.

request/imu_v2_brick/<UID>/set_quaternion_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/quaternion callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_quaternion_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_quaternion_period.

request/imu_v2_brick/<UID>/set_all_data_period
Request payload:
 
  • period -- int

Sets the period in ms with which the register/imu_v2_brick/<UID>/all_data callback is triggered periodically. A value of 0 turns the callback off.

request/imu_v2_brick/<UID>/get_all_data_period
Response payload:
 
  • period -- int

Returns the period as set by request/imu_v2_brick/<UID>/set_all_data_period.

Callbacks

Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding .../register/... topic and an optional suffix. This suffix can be used to deregister the callback later.

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.

register/imu_v2_brick/<UID>/acceleration
Request payload:
 
  • register -- bool
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/acceleration[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/acceleration[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_acceleration_period. The callback payload members are the acceleration for the x, y and z axis.

register/imu_v2_brick/<UID>/magnetic_field
Request payload:
 
  • register -- bool
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/magnetic_field[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/magnetic_field[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_magnetic_field_period. The callback payload members are the magnetic field for the x, y and z axis.

register/imu_v2_brick/<UID>/angular_velocity
Request payload:
 
  • register -- bool
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/angular_velocity[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/angular_velocity[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_angular_velocity_period. The callback payload members are the angular velocity for the x, y and z axis.

register/imu_v2_brick/<UID>/temperature
Request payload:
 
  • register -- bool
Response payload:
 
  • temperature -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/temperature[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/temperature[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_temperature_period. The callback payload is the temperature.

register/imu_v2_brick/<UID>/linear_acceleration
Request payload:
 
  • register -- bool
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/linear_acceleration[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/linear_acceleration[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_linear_acceleration_period. The callback payload members are the linear acceleration for the x, y and z axis.

register/imu_v2_brick/<UID>/gravity_vector
Request payload:
 
  • register -- bool
Response payload:
 
  • x -- int
  • y -- int
  • z -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/gravity_vector[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/gravity_vector[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_gravity_vector_period. The callback payload members gravity vector for the x, y and z axis.

register/imu_v2_brick/<UID>/orientation
Request payload:
 
  • register -- bool
Response payload:
 
  • heading -- int
  • roll -- int
  • pitch -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/orientation[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/orientation[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_orientation_period. The callback payload members are the orientation (heading (yaw), roll, pitch) of the IMU Brick in Euler angles. See request/imu_v2_brick/<UID>/get_orientation for details.

register/imu_v2_brick/<UID>/quaternion
Request payload:
 
  • register -- bool
Response payload:
 
  • w -- int
  • x -- int
  • y -- int
  • z -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/quaternion[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/quaternion[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_quaternion_period. The callback payload members are the orientation (x, y, z, w) of the IMU Brick in quaternions. See request/imu_v2_brick/<UID>/get_quaternion for details.

register/imu_v2_brick/<UID>/all_data
Request payload:
 
  • register -- bool
Response payload:
 
  • acceleration -- [int,int,int]
  • magnetic_field -- [int,int,int]
  • angular_velocity -- [int,int,int]
  • euler_angle -- [int,int,int]
  • quaternion -- [int,int,int,int]
  • linear_acceleration -- [int,int,int]
  • gravity_vector -- [int,int,int]
  • temperature -- int
  • calibration_status -- int

A callback can be registered for this event by publishing to the .../register/imu_v2_brick/<UID>/all_data[/<SUFFIX>] topic with the payload "true". An added callback can be removed by publishing to the same topic with the payload "false". To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.

If the callback is triggered, a message with it's payload is published under the corresponding .../callback/imu_v2_brick/<UID>/all_data[/<SUFFIX>] topic for each registered suffix.

This callback is triggered periodically with the period that is set by request/imu_v2_brick/<UID>/set_all_data_period. The callback payload members are as for request/imu_v2_brick/<UID>/get_all_data.