This is the description of the Java 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 Java 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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickIMUV2;
import com.tinkerforge.BrickIMUV2.Quaternion;
public class ExampleSimple {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XXYYZZ to the UID of your IMU Brick 2.0
private static final String UID = "XXYYZZ";
// Note: To make the example code cleaner we do not handle exceptions. Exceptions
// you might normally want to catch are described in the documentation
public static void main(String args[]) throws Exception {
IPConnection ipcon = new IPConnection(); // Create IP connection
BrickIMUV2 imu = new BrickIMUV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Get current quaternion
Quaternion quaternion = imu.getQuaternion(); // Can throw com.tinkerforge.TimeoutException
System.out.println("Quaternion [W]: " + quaternion.w/16383.0);
System.out.println("Quaternion [X]: " + quaternion.x/16383.0);
System.out.println("Quaternion [Y]: " + quaternion.y/16383.0);
System.out.println("Quaternion [Z]: " + quaternion.z/16383.0);
System.out.println("Press key to exit"); System.in.read();
ipcon.disconnect();
}
}
|
Download (ExampleCallback.java)
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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickIMUV2;
public class ExampleCallback {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XXYYZZ to the UID of your IMU Brick 2.0
private static final String UID = "XXYYZZ";
// Note: To make the example code cleaner we do not handle exceptions. Exceptions
// you might normally want to catch are described in the documentation
public static void main(String args[]) throws Exception {
IPConnection ipcon = new IPConnection(); // Create IP connection
BrickIMUV2 imu = new BrickIMUV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Add quaternion listener
imu.addQuaternionListener(new BrickIMUV2.QuaternionListener() {
public void quaternion(short w, short x, short y, short z) {
System.out.println("Quaternion [W]: " + w/16383.0);
System.out.println("Quaternion [X]: " + x/16383.0);
System.out.println("Quaternion [Y]: " + y/16383.0);
System.out.println("Quaternion [Z]: " + z/16383.0);
System.out.println("");
}
});
// Set period for quaternion callback to 0.1s (100ms)
imu.setQuaternionPeriod(100);
System.out.println("Press key to exit"); System.in.read();
ipcon.disconnect();
}
}
|
Download (ExampleAllData.java)
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 | import com.tinkerforge.IPConnection;
import com.tinkerforge.BrickIMUV2;
public class ExampleAllData {
private static final String HOST = "localhost";
private static final int PORT = 4223;
// Change XXYYZZ to the UID of your IMU Brick 2.0
private static final String UID = "XXYYZZ";
// Note: To make the example code cleaner we do not handle exceptions. Exceptions
// you might normally want to catch are described in the documentation
public static void main(String args[]) throws Exception {
IPConnection ipcon = new IPConnection(); // Create IP connection
BrickIMUV2 imu = new BrickIMUV2(UID, ipcon); // Create device object
ipcon.connect(HOST, PORT); // Connect to brickd
// Don't use device before ipcon is connected
// Add all data listener
imu.addAllDataListener(new BrickIMUV2.AllDataListener() {
public void allData(short[] acceleration, short[] magneticField,
short[] angularVelocity, short[] eulerAngle,
short[] quaternion, short[] linearAcceleration,
short[] gravityVector, byte temperature,
short calibrationStatus) {
System.out.println("Acceleration [X]: " + acceleration[0]/100.0 + " m/s²");
System.out.println("Acceleration [Y]: " + acceleration[1]/100.0 + " m/s²");
System.out.println("Acceleration [Z]: " + acceleration[2]/100.0 + " m/s²");
System.out.println("Magnetic Field [X]: " + magneticField[0]/16.0 + " µT");
System.out.println("Magnetic Field [Y]: " + magneticField[1]/16.0 + " µT");
System.out.println("Magnetic Field [Z]: " + magneticField[2]/16.0 + " µT");
System.out.println("Angular Velocity [X]: " + angularVelocity[0]/16.0 + " °/s");
System.out.println("Angular Velocity [Y]: " + angularVelocity[1]/16.0 + " °/s");
System.out.println("Angular Velocity [Z]: " + angularVelocity[2]/16.0 + " °/s");
System.out.println("Euler Angle [Heading]: " + eulerAngle[0]/16.0 + " °");
System.out.println("Euler Angle [Roll]: " + eulerAngle[1]/16.0 + " °");
System.out.println("Euler Angle [Pitch]: " + eulerAngle[2]/16.0 + " °");
System.out.println("Quaternion [W]: " + quaternion[0]/16383.0);
System.out.println("Quaternion [X]: " + quaternion[1]/16383.0);
System.out.println("Quaternion [Y]: " + quaternion[2]/16383.0);
System.out.println("Quaternion [Z]: " + quaternion[3]/16383.0);
System.out.println("Linear Acceleration [X]: " + linearAcceleration[0]/100.0 + " m/s²");
System.out.println("Linear Acceleration [Y]: " + linearAcceleration[1]/100.0 + " m/s²");
System.out.println("Linear Acceleration [Z]: " + linearAcceleration[2]/100.0 + " m/s²");
System.out.println("Gravity Vector [X]: " + gravityVector[0]/100.0 + " m/s²");
System.out.println("Gravity Vector [Y]: " + gravityVector[1]/100.0 + " m/s²");
System.out.println("Gravity Vector [Z]: " + gravityVector[2]/100.0 + " m/s²");
System.out.println("Temperature: " + temperature + " °C");
System.out.println("Calibration Status: " + Integer.toBinaryString(calibrationStatus));
System.out.println("");
}
});
// Set period for all data callback to 0.1s (100ms)
imu.setAllDataPeriod(100);
System.out.println("Press key to exit"); System.in.read();
ipcon.disconnect();
}
}
|
Generally, every method of the Java bindings that returns a value can
throw a TimeoutException
. This exception gets thrown if the
device did not respond. If a cable based connection is used, it is
unlikely that this exception gets thrown (assuming nobody unplugs the
device). However, if a wireless connection is used, timeouts will occur
if the distance to the device gets too big.
Beside the TimeoutException
there is also a NotConnectedException
that
is thrown if a method needs to communicate with the device while the
IP Connection is not connected.
Since Java does not support multiple return values and return by reference is not possible for primitive types, we use small classes that only consist of member variables. The member variables of the returned objects are described in the corresponding method descriptions.
The package for all Brick/Bricklet bindings and the IP Connection is
com.tinkerforge.*
All methods listed below are thread-safe.
BrickIMUV2
(String uid, IPConnection ipcon)¶Parameters: |
|
---|---|
Returns: |
|
Creates an object with the unique device ID uid
:
BrickIMUV2 imuV2 = new BrickIMUV2("YOUR_DEVICE_UID", ipcon);
This object can then be used after the IP Connection is connected.
BrickIMUV2.
getOrientation
()¶Return Object: |
|
---|
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 OrientationListener
listener and set the period with
setOrientationPeriod()
.
BrickIMUV2.
getLinearAcceleration
()¶Return Object: |
|
---|
Returns the linear acceleration of the IMU Brick for the
x, y and z axis. The acceleration is in the range configured with
setSensorConfiguration()
.
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 getGravityVector()
.
If you want to get the linear acceleration periodically, it is recommended
to use the LinearAccelerationListener
listener and set the period with
setLinearAccelerationPeriod()
.
BrickIMUV2.
getGravityVector
()¶Return Object: |
|
---|
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 getLinearAcceleration()
.
If you want to get the gravity vector periodically, it is recommended
to use the GravityVectorListener
listener and set the period with
setGravityVectorPeriod()
.
BrickIMUV2.
getQuaternion
()¶Return Object: |
|
---|
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 QuaternionListener
listener and set the period with
setQuaternionPeriod()
.
BrickIMUV2.
getAllData
()¶Return Object: |
|
---|
Return all of the available data of the IMU Brick.
getAcceleration()
)getMagneticField()
)getAngularVelocity()
)getOrientation()
)getQuaternion()
)getLinearAcceleration()
)getGravityVector()
)getTemperature()
)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 AllDataListener
listener and set the period with
setAllDataPeriod()
.
BrickIMUV2.
ledsOn
()¶Turns the orientation and direction LEDs of the IMU Brick on.
BrickIMUV2.
ledsOff
()¶Turns the orientation and direction LEDs of the IMU Brick off.
BrickIMUV2.
areLedsOn
()¶Returns: |
|
---|
Returns true if the orientation and direction LEDs of the IMU Brick are on, false otherwise.
BrickIMUV2.
getAcceleration
()¶Return Object: |
|
---|
Returns the calibrated acceleration from the accelerometer for the
x, y and z axis. The acceleration is in the range configured with
setSensorConfiguration()
.
If you want to get the acceleration periodically, it is recommended
to use the AccelerationListener
listener and set the period with
setAccelerationPeriod()
.
BrickIMUV2.
getMagneticField
()¶Return Object: |
|
---|
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 MagneticFieldListener
listener and set the period with
setMagneticFieldPeriod()
.
BrickIMUV2.
getAngularVelocity
()¶Return Object: |
|
---|
Returns the calibrated angular velocity from the gyroscope for the
x, y and z axis. The angular velocity is in the range configured with
setSensorConfiguration()
.
If you want to get the angular velocity periodically, it is recommended
to use the AngularVelocityListener
alistener nd set the period with
setAngularVelocityPeriod()
.
BrickIMUV2.
getTemperature
()¶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
BrickIMUV2.
saveCalibration
()¶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.
BrickIMUV2.
setSensorConfiguration
(short magnetometerRate, short gyroscopeRange, short gyroscopeBandwidth, short accelerometerRange, short accelerometerBandwidth)¶Parameters: |
|
---|
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 magnetometerRate:
For gyroscopeRange:
For gyroscopeBandwidth:
For accelerometerRange:
For accelerometerBandwidth:
New in version 2.0.5 (Firmware).
BrickIMUV2.
getSensorConfiguration
()¶Return Object: |
|
---|
Returns the sensor configuration as set by setSensorConfiguration()
.
The following constants are available for this function:
For magnetometerRate:
For gyroscopeRange:
For gyroscopeBandwidth:
For accelerometerRange:
For accelerometerBandwidth:
New in version 2.0.5 (Firmware).
BrickIMUV2.
setSensorFusionMode
(short mode)¶Parameters: |
|
---|
If the fusion mode is turned off, the functions getAcceleration()
,
getMagneticField()
and getAngularVelocity()
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:
New in version 2.0.5 (Firmware).
BrickIMUV2.
getSensorFusionMode
()¶Returns: |
|
---|
Returns the sensor fusion mode as set by setSensorFusionMode()
.
The following constants are available for this function:
For mode:
New in version 2.0.5 (Firmware).
BrickIMUV2.
setSPITFPBaudrateConfig
(boolean enableDynamicBaudrate, long minimumDynamicBaudrate)¶Parameters: |
|
---|
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 sent/received and decreased linearly if little data is sent/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
setSPITFPBaudrate()
. If the dynamic baudrate is disabled, the baudrate
as set by setSPITFPBaudrate()
will be used statically.
New in version 2.0.10 (Firmware).
BrickIMUV2.
getSPITFPBaudrateConfig
()¶Return Object: |
|
---|
Returns the baudrate config, see setSPITFPBaudrateConfig()
.
New in version 2.0.10 (Firmware).
BrickIMUV2.
getSendTimeoutCount
(short communicationMethod)¶Parameters: |
|
---|---|
Returns: |
|
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 constants are available for this function:
For communicationMethod:
New in version 2.0.7 (Firmware).
BrickIMUV2.
setSPITFPBaudrate
(char brickletPort, long baudrate)¶Parameters: |
|
---|
Sets the baudrate for a specific Bricklet port.
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 getSPITFPErrorCount()
) you can decrease the
baudrate.
If the dynamic baudrate feature is enabled, the baudrate set by this
function corresponds to the maximum baudrate (see setSPITFPBaudrateConfig()
).
Regulatory testing is done with the default baudrate. If CE compatibility or similar is necessary in your applications we recommend to not change the baudrate.
New in version 2.0.5 (Firmware).
BrickIMUV2.
getSPITFPBaudrate
(char brickletPort)¶Parameters: |
|
---|---|
Returns: |
|
Returns the baudrate for a given Bricklet port, see setSPITFPBaudrate()
.
New in version 2.0.5 (Firmware).
BrickIMUV2.
getSPITFPErrorCount
(char brickletPort)¶Parameters: |
|
---|---|
Return Object: |
|
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 Brick side. All Bricklets have a similar function that returns the errors on the Bricklet side.
New in version 2.0.5 (Firmware).
BrickIMUV2.
enableStatusLED
()¶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.
BrickIMUV2.
disableStatusLED
()¶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.
BrickIMUV2.
isStatusLEDEnabled
()¶Returns: |
|
---|
Returns true if the status LED is enabled, false otherwise.
BrickIMUV2.
getChipTemperature
()¶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 an accuracy of ±15%. Practically it is only useful as an indicator for temperature changes.
BrickIMUV2.
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!
BrickIMUV2.
getIdentity
()¶Return Object: |
|
---|
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 is the position in the stack from '0' (bottom) to '8' (top).
The device identifier numbers can be found here. There is also a constant for the device identifier of this Brick.
BrickIMUV2.
setAccelerationPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the AccelerationListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getAccelerationPeriod
()¶Returns: |
|
---|
Returns the period as set by setAccelerationPeriod()
.
BrickIMUV2.
setMagneticFieldPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the MagneticFieldListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getMagneticFieldPeriod
()¶Returns: |
|
---|
Returns the period as set by setMagneticFieldPeriod()
.
BrickIMUV2.
setAngularVelocityPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the AngularVelocityListener
listener is
triggered periodically. A value of 0 turns the listener off.
BrickIMUV2.
getAngularVelocityPeriod
()¶Returns: |
|
---|
Returns the period as set by setAngularVelocityPeriod()
.
BrickIMUV2.
setTemperaturePeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the TemperatureListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getTemperaturePeriod
()¶Returns: |
|
---|
Returns the period as set by setTemperaturePeriod()
.
BrickIMUV2.
setOrientationPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the OrientationListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getOrientationPeriod
()¶Returns: |
|
---|
Returns the period as set by setOrientationPeriod()
.
BrickIMUV2.
setLinearAccelerationPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the LinearAccelerationListener
listener is
triggered periodically. A value of 0 turns the listener off.
BrickIMUV2.
getLinearAccelerationPeriod
()¶Returns: |
|
---|
Returns the period as set by setLinearAccelerationPeriod()
.
BrickIMUV2.
setGravityVectorPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the GravityVectorListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getGravityVectorPeriod
()¶Returns: |
|
---|
Returns the period as set by setGravityVectorPeriod()
.
BrickIMUV2.
setQuaternionPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the QuaternionListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getQuaternionPeriod
()¶Returns: |
|
---|
Returns the period as set by setQuaternionPeriod()
.
BrickIMUV2.
setAllDataPeriod
(long period)¶Parameters: |
|
---|
Sets the period with which the AllDataListener
listener is triggered
periodically. A value of 0 turns the listener off.
BrickIMUV2.
getAllDataPeriod
()¶Returns: |
|
---|
Returns the period as set by setAllDataPeriod()
.
Listeners can be registered to receive
time critical or recurring data from the device. The registration is done
with add*Listener()
functions of the device object.
The parameter is a listener class object, for example:
device.addExampleListener(new BrickIMUV2.ExampleListener() {
public void property(int value) {
System.out.println("Value: " + value);
}
});
The available listener classes with inherent methods to be overwritten
are described below. It is possible to add several listeners and
to remove them with the corresponding remove*Listener()
function.
Note
Using listeners 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.
BrickIMUV2.
AccelerationListener
()¶This listener can be added with the addAccelerationListener()
function.
An added listener can be removed with the removeAccelerationListener()
function.
acceleration
(short x, short y, short z)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setAccelerationPeriod()
. The parameters are the acceleration
for the x, y and z axis.
BrickIMUV2.
MagneticFieldListener
()¶This listener can be added with the addMagneticFieldListener()
function.
An added listener can be removed with the removeMagneticFieldListener()
function.
magneticField
(short x, short y, short z)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setMagneticFieldPeriod()
. The parameters are the magnetic
field for the x, y and z axis.
BrickIMUV2.
AngularVelocityListener
()¶This listener can be added with the addAngularVelocityListener()
function.
An added listener can be removed with the removeAngularVelocityListener()
function.
angularVelocity
(short x, short y, short z)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setAngularVelocityPeriod()
. The parameters are the angular
velocity for the x, y and z axis.
BrickIMUV2.
TemperatureListener
()¶This listener can be added with the addTemperatureListener()
function.
An added listener can be removed with the removeTemperatureListener()
function.
temperature
(byte temperature)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setTemperaturePeriod()
. The parameter is the temperature.
BrickIMUV2.
LinearAccelerationListener
()¶This listener can be added with the addLinearAccelerationListener()
function.
An added listener can be removed with the removeLinearAccelerationListener()
function.
linearAcceleration
(short x, short y, short z)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setLinearAccelerationPeriod()
. The parameters are the
linear acceleration for the x, y and z axis.
BrickIMUV2.
GravityVectorListener
()¶This listener can be added with the addGravityVectorListener()
function.
An added listener can be removed with the removeGravityVectorListener()
function.
gravityVector
(short x, short y, short z)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setGravityVectorPeriod()
. The parameters gravity vector
for the x, y and z axis.
BrickIMUV2.
OrientationListener
()¶This listener can be added with the addOrientationListener()
function.
An added listener can be removed with the removeOrientationListener()
function.
orientation
(short heading, short roll, short pitch)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setOrientationPeriod()
. The parameters are the orientation
(heading (yaw), roll, pitch) of the IMU Brick in Euler angles. See
getOrientation()
for details.
BrickIMUV2.
QuaternionListener
()¶This listener can be added with the addQuaternionListener()
function.
An added listener can be removed with the removeQuaternionListener()
function.
quaternion
(short w, short x, short y, short z)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setQuaternionPeriod()
. The parameters are the orientation
(w, x, y, z) of the IMU Brick in quaternions. See getQuaternion()
for details.
BrickIMUV2.
AllDataListener
()¶This listener can be added with the addAllDataListener()
function.
An added listener can be removed with the removeAllDataListener()
function.
allData
(short[] acceleration, short[] magneticField, short[] angularVelocity, short[] eulerAngle, short[] quaternion, short[] linearAcceleration, short[] gravityVector, byte temperature, short calibrationStatus)Parameters: |
|
---|
This listener is triggered periodically with the period that is set by
setAllDataPeriod()
. The parameters are as for
getAllData()
.
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.
BrickIMUV2.
getAPIVersion
()¶Return Object: |
|
---|
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.
BrickIMUV2.
getResponseExpected
(byte functionId)¶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 listener configuration
functions it is enabled by default too, but can be disabled by
setResponseExpected()
. 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 functionId:
BrickIMUV2.
setResponseExpected
(byte functionId, boolean responseExpected)¶Parameters: |
|
---|
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 listener 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 functionId:
BrickIMUV2.
setResponseExpectedAll
(boolean responseExpected)¶Parameters: |
|
---|
Changes the response expected flag for all setter and listener 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.
BrickIMUV2.
getProtocol1BrickletName
(char port)¶Parameters: |
|
---|---|
Return Object: |
|
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.
BrickIMUV2.
writeBrickletPlugin
(char port, short offset, short[] chunk)¶Parameters: |
|
---|
Writes 32 bytes of firmware to the bricklet attached at the given port. The bytes are written to the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickIMUV2.
readBrickletPlugin
(char port, short offset)¶Parameters: |
|
---|---|
Returns: |
|
Reads 32 bytes of firmware from the bricklet attached at the given port. The bytes are read starting at the position offset * 32.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
BrickIMUV2.
DEVICE_IDENTIFIER
¶This constant is used to identify a IMU Brick 2.0.
The getIdentity()
function and the
IPConnection.EnumerateListener
listener of the IP Connection have a deviceIdentifier
parameter to specify
the Brick's or Bricklet's type.
BrickIMUV2.
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a IMU Brick 2.0.