This is the description of the Rust API bindings for the Temperature IR Bricklet 2.0. General information and technical specifications for the Temperature IR Bricklet 2.0 are summarized in its hardware description.
An installation guide for the Rust API bindings is part of their general description. Additional documentation can be found on docs.rs.
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 | use std::{error::Error, io};
use tinkerforge::{ip_connection::IpConnection, temperature_ir_v2_bricklet::*};
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your Temperature IR Bricklet 2.0.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let tir = TemperatureIrV2Bricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
// Get current ambient temperature.
let ambient_temperature = tir.get_ambient_temperature().recv()?;
println!("Ambient Temperature: {} °C", ambient_temperature as f32 / 10.0);
// Get current object temperature.
let object_temperature = tir.get_object_temperature().recv()?;
println!("Object Temperature: {} °C", object_temperature as f32 / 10.0);
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
ipcon.disconnect();
Ok(())
}
|
Download (example_callback.rs)
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 | use std::{error::Error, io, thread};
use tinkerforge::{ip_connection::IpConnection, temperature_ir_v2_bricklet::*};
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your Temperature IR Bricklet 2.0.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let tir = TemperatureIrV2Bricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
let object_temperature_receiver = tir.get_object_temperature_callback_receiver();
// Spawn thread to handle received callback messages.
// This thread ends when the `tir` object
// is dropped, so there is no need for manual cleanup.
thread::spawn(move || {
for object_temperature in object_temperature_receiver {
println!("Object Temperature: {} °C", object_temperature as f32 / 10.0);
}
});
// Set period for object temperature callback to 1s (1000ms) without a threshold.
tir.set_object_temperature_callback_configuration(1000, false, 'x', 0, 0);
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
ipcon.disconnect();
Ok(())
}
|
Download (example_water_boiling.rs)
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 | use std::{error::Error, io, thread};
use tinkerforge::{ip_connection::IpConnection, temperature_ir_v2_bricklet::*};
const HOST: &str = "localhost";
const PORT: u16 = 4223;
const UID: &str = "XYZ"; // Change XYZ to the UID of your Temperature IR Bricklet 2.0.
fn main() -> Result<(), Box<dyn Error>> {
let ipcon = IpConnection::new(); // Create IP connection.
let tir = TemperatureIrV2Bricklet::new(UID, &ipcon); // Create device object.
ipcon.connect((HOST, PORT)).recv()??; // Connect to brickd.
// Don't use device before ipcon is connected.
// Set emissivity to 0.98 (emissivity of water, 65535 * 0.98 = 64224.299)
tir.set_emissivity(64224).recv()?;
let object_temperature_receiver = tir.get_object_temperature_callback_receiver();
// Spawn thread to handle received callback messages.
// This thread ends when the `tir` object
// is dropped, so there is no need for manual cleanup.
thread::spawn(move || {
for object_temperature in object_temperature_receiver {
println!("Object Temperature: {} °C", object_temperature as f32 / 10.0);
println!("The water is boiling!");
}
});
// Configure threshold for object temperature "greater than 100 °C"
// with a debounce period of 10s (10000ms).
tir.set_object_temperature_callback_configuration(10000, false, '>', 100 * 10, 0);
println!("Press enter to exit.");
let mut _input = String::new();
io::stdin().read_line(&mut _input)?;
ipcon.disconnect();
Ok(())
}
|
To allow non-blocking usage, nearly every function of the Rust bindings returns a wrapper around a mpsc::Receiver. To block until the function has finished and get your result, call one of the receiver's recv variants. Those return either the result sent by the device, or any error occurred.
Functions returning a result directly will block until the device has finished processing the request.
All functions listed below are thread-safe, those which return a receiver are lock-free.
TemperatureIrV2Bricklet::
new
(uid: &str, ip_connection: &IpConnection) → TemperatureIrV2Bricklet¶Parameters: |
|
---|---|
Returns: |
|
Creates a new TemperatureIrV2Bricklet
object with the unique device ID uid
and adds
it to the IPConnection ip_connection
:
let temperature_ir_v2 = TemperatureIrV2Bricklet::new("YOUR_DEVICE_UID", &ip_connection);
This device object can be used after the IP connection has been connected.
TemperatureIrV2Bricklet::
get_ambient_temperature
(&self) → ConvertingReceiver<i16>¶Returns: |
|
---|
Returns the ambient temperature of the sensor.
If you want to get the value periodically, it is recommended to use the
TemperatureIrV2Bricklet::get_ambient_temperature_callback_receiver
callback. You can set the callback configuration
with TemperatureIrV2Bricklet::set_ambient_temperature_callback_configuration
.
TemperatureIrV2Bricklet::
get_object_temperature
(&self) → ConvertingReceiver<i16>¶Returns: |
|
---|
Returns the object temperature of the sensor, i.e. the temperature of the surface of the object the sensor is aimed at.
The temperature of different materials is dependent on their emissivity. The emissivity of the material
can be set with TemperatureIrV2Bricklet::set_emissivity
.
If you want to get the value periodically, it is recommended to use the
TemperatureIrV2Bricklet::get_object_temperature_callback_receiver
callback. You can set the callback configuration
with TemperatureIrV2Bricklet::set_object_temperature_callback_configuration
.
TemperatureIrV2Bricklet::
set_emissivity
(&self, emissivity: u16) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the emissivity that is
used to calculate the surface temperature as returned by
TemperatureIrV2Bricklet::get_object_temperature
.
The emissivity is usually given as a value between 0.0 and 1.0. A list of emissivities of different materials can be found here.
The parameter of TemperatureIrV2Bricklet::set_emissivity
has to be given with a factor of
65535 (16-bit). For example: An emissivity of 0.1 can be set with the
value 6553, an emissivity of 0.5 with the value 32767 and so on.
Note
If you need a precise measurement for the object temperature, it is absolutely crucial that you also provide a precise emissivity.
The emissivity is stored in non-volatile memory and will still be used after a restart or power cycle of the Bricklet.
TemperatureIrV2Bricklet::
get_emissivity
(&self) → ConvertingReceiver<u16>¶Returns: |
|
---|
Returns the emissivity as set by TemperatureIrV2Bricklet::set_emissivity
.
TemperatureIrV2Bricklet::
get_spitfp_error_count
(&self) → ConvertingReceiver<SpitfpErrorCount>¶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 Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
TemperatureIrV2Bricklet::
set_status_led_config
(&self, config: u8) → ConvertingReceiver<()>¶Parameters: |
|
---|
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:
TemperatureIrV2Bricklet::
get_status_led_config
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the configuration as set by TemperatureIrV2Bricklet::set_status_led_config
The following constants are available for this function:
For config:
TemperatureIrV2Bricklet::
get_chip_temperature
(&self) → ConvertingReceiver<i16>¶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.
TemperatureIrV2Bricklet::
reset
(&self) → ConvertingReceiver<()>¶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!
TemperatureIrV2Bricklet::
get_identity
(&self) → ConvertingReceiver<Identity>¶Return Object: |
|
---|
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.
TemperatureIrV2Bricklet::
set_ambient_temperature_callback_configuration
(&self, period: u32, value_has_to_change: bool, option: char, min: i16, max: i16) → ConvertingReceiver<()>¶Parameters: |
|
---|
The period is the period with which the TemperatureIrV2Bricklet::get_ambient_temperature_callback_receiver
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.
It is furthermore possible to constrain the callback with thresholds.
The option-parameter together with min/max sets a threshold for the TemperatureIrV2Bricklet::get_ambient_temperature_callback_receiver
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.
The following constants are available for this function:
For option:
TemperatureIrV2Bricklet::
get_ambient_temperature_callback_configuration
(&self) → ConvertingReceiver<AmbientTemperatureCallbackConfiguration>¶Return Object: |
|
---|
Returns the callback configuration as set by TemperatureIrV2Bricklet::set_ambient_temperature_callback_configuration
.
The following constants are available for this function:
For option:
TemperatureIrV2Bricklet::
set_object_temperature_callback_configuration
(&self, period: u32, value_has_to_change: bool, option: char, min: i16, max: i16) → ConvertingReceiver<()>¶Parameters: |
|
---|
The period is the period with which the TemperatureIrV2Bricklet::get_object_temperature_callback_receiver
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.
It is furthermore possible to constrain the callback with thresholds.
The option-parameter together with min/max sets a threshold for the TemperatureIrV2Bricklet::get_object_temperature_callback_receiver
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.
The following constants are available for this function:
For option:
TemperatureIrV2Bricklet::
get_object_temperature_callback_configuration
(&self) → ConvertingReceiver<ObjectTemperatureCallbackConfiguration>¶Return Object: |
|
---|
Returns the callback configuration as set by TemperatureIrV2Bricklet::set_object_temperature_callback_configuration
.
The following constants are available for this function:
For option:
Callbacks can be registered to receive time critical or recurring data from the device. The registration is done with the corresponding get_*_callback_receiver function, which returns a receiver for callback events.
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.
TemperatureIrV2Bricklet::
get_ambient_temperature_callback_receiver
(&self) → ConvertingCallbackReceiver<i16>¶Event: |
|
---|
Receivers created with this function receive Ambient Temperature events.
This callback is triggered periodically according to the configuration set by
TemperatureIrV2Bricklet::set_ambient_temperature_callback_configuration
.
The received variable is the same as TemperatureIrV2Bricklet::get_ambient_temperature
.
TemperatureIrV2Bricklet::
get_object_temperature_callback_receiver
(&self) → ConvertingCallbackReceiver<i16>¶Event: |
|
---|
Receivers created with this function receive Object Temperature events.
This callback is triggered periodically according to the configuration set by
TemperatureIrV2Bricklet::set_object_temperature_callback_configuration
.
The received variable is the same as TemperatureIrV2Bricklet::get_object_temperature
.
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.
TemperatureIrV2Bricklet::
get_api_version
(&self) → [u8; 3]¶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.
TemperatureIrV2Bricklet::
get_response_expected
(&mut self, function_id: u8) → bool¶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
TemperatureIrV2Bricklet::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:
TemperatureIrV2Bricklet::
set_response_expected
(&mut self, function_id: u8, response_expected: bool) → ()¶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 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:
TemperatureIrV2Bricklet::
set_response_expected_all
(&mut self, response_expected: bool) → ()¶Parameters: |
|
---|
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.
TemperatureIrV2Bricklet::
set_bootloader_mode
(&self, mode: u8) → ConvertingReceiver<u8>¶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 status:
TemperatureIrV2Bricklet::
get_bootloader_mode
(&self) → ConvertingReceiver<u8>¶Returns: |
|
---|
Returns the current bootloader mode, see TemperatureIrV2Bricklet::set_bootloader_mode
.
The following constants are available for this function:
For mode:
TemperatureIrV2Bricklet::
set_write_firmware_pointer
(&self, pointer: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
Sets the firmware pointer for TemperatureIrV2Bricklet::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.
TemperatureIrV2Bricklet::
write_firmware
(&self, data: [u8; 64]) → ConvertingReceiver<u8>¶Parameters: |
|
---|---|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
TemperatureIrV2Bricklet::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.
TemperatureIrV2Bricklet::
write_uid
(&self, uid: u32) → ConvertingReceiver<()>¶Parameters: |
|
---|
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.
TemperatureIrV2Bricklet::
read_uid
(&self) → ConvertingReceiver<u32>¶Returns: |
|
---|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
TemperatureIrV2Bricklet::
DEVICE_IDENTIFIER
¶This constant is used to identify a Temperature IR Bricklet 2.0.
The TemperatureIrV2Bricklet::get_identity
function and the IpConnection::get_enumerate_callback_receiver
callback of the IP Connection have a device_identifier
parameter to specify
the Brick's or Bricklet's type.
TemperatureIrV2Bricklet::
DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Temperature IR Bricklet 2.0.