This is the description of the C/C++ API bindings for the Thermal Imaging Bricklet. General information and technical specifications for the Thermal Imaging Bricklet 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 44 45 46 47 48 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_thermal_imaging.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Thermal Imaging Bricklet
// Callback function for high contrast image callback
void cb_high_contrast_image(uint8_t *image, uint16_t image_length, void *user_data) {
(void)image; (void)image_length; (void)user_data; // avoid unused parameter warning
// image is an array of size 80*60 with a 8 bit grey value for each element
}
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
ThermalImaging ti;
thermal_imaging_create(&ti, 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 high contrast image callback to function cb_high_contrast_image
thermal_imaging_register_callback(&ti,
THERMAL_IMAGING_CALLBACK_HIGH_CONTRAST_IMAGE,
(void (*)(void))cb_high_contrast_image,
NULL);
// Enable high contrast image transfer for callback
thermal_imaging_set_image_transfer_config(&ti,
THERMAL_IMAGING_IMAGE_TRANSFER_CALLBACK_HIGH_CONTRAST_IMAGE);
printf("Press key to exit\n");
getchar();
thermal_imaging_destroy(&ti);
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.
thermal_imaging_create
(ThermalImaging *thermal_imaging, const char *uid, IPConnection *ipcon)¶Parameters: |
|
---|
Creates the device object thermal_imaging
with the unique device ID uid
and adds
it to the IPConnection ipcon
:
ThermalImaging thermal_imaging;
thermal_imaging_create(&thermal_imaging, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected.
thermal_imaging_destroy
(ThermalImaging *thermal_imaging)¶Parameters: |
|
---|
Removes the device object thermal_imaging
from its IPConnection and destroys it.
The device object cannot be used anymore afterwards.
thermal_imaging_get_high_contrast_image
(ThermalImaging *thermal_imaging, uint8_t *ret_image, uint16_t *ret_image_length)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current high contrast image. See here for the difference between High Contrast and Temperature Image. If you don't know what to use the High Contrast Image is probably right for you.
The data is organized as a 8-bit value 80x60 pixel matrix linearized in a one-dimensional array. The data is arranged line by line from top left to bottom right.
Each 8-bit value represents one gray-scale image pixel that can directly be shown to a user on a display.
Before you can use this function you have to enable it with
thermal_imaging_set_image_transfer_config()
.
thermal_imaging_get_temperature_image
(ThermalImaging *thermal_imaging, uint16_t *ret_image, uint16_t *ret_image_length)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current temperature image. See here for the difference between High Contrast and Temperature Image. If you don't know what to use the High Contrast Image is probably right for you.
The data is organized as a 16-bit value 80x60 pixel matrix linearized in a one-dimensional array. The data is arranged line by line from top left to bottom right.
Each 16-bit value represents one temperature measurement in either
Kelvin/10 or Kelvin/100 (depending on the resolution set with thermal_imaging_set_resolution()
).
Before you can use this function you have to enable it with
thermal_imaging_set_image_transfer_config()
.
thermal_imaging_get_statistics
(ThermalImaging *thermal_imaging, uint16_t ret_spotmeter_statistics[4], uint16_t ret_temperatures[4], uint8_t *ret_resolution, uint8_t *ret_ffc_status, bool ret_temperature_warning[2])¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the spotmeter statistics, various temperatures, current resolution and status bits.
The spotmeter statistics are:
The temperatures are:
The resolution is either 0 to 6553 Kelvin or 0 to 655 Kelvin. If the resolution is the former, the temperatures are in Kelvin/10, if it is the latter the temperatures are in Kelvin/100.
FFC (Flat Field Correction) Status:
Temperature warning bits:
The following constants are available for this function:
For ret_resolution:
For ret_ffc_status:
thermal_imaging_set_resolution
(ThermalImaging *thermal_imaging, uint8_t resolution)¶Parameters: |
|
---|---|
Returns: |
|
Sets the resolution. The Thermal Imaging Bricklet can either measure
The accuracy is specified for -10°C to 450°C in the first range and -10°C and 140°C in the second range.
The following constants are available for this function:
For resolution:
thermal_imaging_get_resolution
(ThermalImaging *thermal_imaging, uint8_t *ret_resolution)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the resolution as set by thermal_imaging_set_resolution()
.
The following constants are available for this function:
For ret_resolution:
thermal_imaging_set_spotmeter_config
(ThermalImaging *thermal_imaging, uint8_t region_of_interest[4])¶Parameters: |
|
---|---|
Returns: |
|
Sets the spotmeter region of interest. The 4 values are
The spotmeter statistics can be read out with thermal_imaging_get_statistics()
.
thermal_imaging_get_spotmeter_config
(ThermalImaging *thermal_imaging, uint8_t ret_region_of_interest[4])¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the spotmeter config as set by thermal_imaging_set_spotmeter_config()
.
thermal_imaging_set_high_contrast_config
(ThermalImaging *thermal_imaging, uint8_t region_of_interest[4], uint16_t dampening_factor, uint16_t clip_limit[2], uint16_t empty_counts)¶Parameters: |
|
---|---|
Returns: |
|
Sets the high contrast region of interest, dampening factor, clip limit and empty counts.
This config is only used in high contrast mode (see thermal_imaging_set_image_transfer_config()
).
The high contrast region of interest consists of four values:
The algorithm to generate the high contrast image is applied to this region.
Dampening Factor: This parameter is the amount of temporal dampening applied to the HEQ (history equalization) transformation function. An IIR filter of the form:
(N / 256) * previous + ((256 - N) / 256) * current
is applied, and the HEQ dampening factor represents the value N in the equation, i.e., a value that applies to the amount of influence the previous HEQ transformation function has on the current function. The lower the value of N the higher the influence of the current video frame whereas the higher the value of N the more influence the previous damped transfer function has.
Clip Limit Index 0 (AGC HEQ Clip Limit High): This parameter defines the maximum number of pixels allowed to accumulate in any given histogram bin. Any additional pixels in a given bin are clipped. The effect of this parameter is to limit the influence of highly-populated bins on the resulting HEQ transformation function.
Clip Limit Index 1 (AGC HEQ Clip Limit Low): This parameter defines an artificial population that is added to every non-empty histogram bin. In other words, if the Clip Limit Low is set to L, a bin with an actual population of X will have an effective population of L + X. Any empty bin that is nearby a populated bin will be given an artificial population of L. The effect of higher values is to provide a more linear transfer function; lower values provide a more non-linear (equalized) transfer function.
Empty Counts: This parameter specifies the maximum number of pixels in a bin that will be interpreted as an empty bin. Histogram bins with this number of pixels or less will be processed as an empty bin.
thermal_imaging_get_high_contrast_config
(ThermalImaging *thermal_imaging, uint8_t ret_region_of_interest[4], uint16_t *ret_dampening_factor, uint16_t ret_clip_limit[2], uint16_t *ret_empty_counts)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the high contrast config as set by thermal_imaging_set_high_contrast_config()
.
thermal_imaging_set_flux_linear_parameters
(ThermalImaging *thermal_imaging, uint16_t scene_emissivity, uint16_t temperature_background, uint16_t tau_window, uint16_t temperatur_window, uint16_t tau_atmosphere, uint16_t temperature_atmosphere, uint16_t reflection_window, uint16_t temperature_reflection)¶Parameters: |
|
---|---|
Returns: |
|
Sets the flux linear parameters that can be used for radiometry calibration.
See FLIR document 102-PS245-100-01 for more details.
New in version 2.0.5 (Plugin).
thermal_imaging_get_flux_linear_parameters
(ThermalImaging *thermal_imaging, uint16_t *ret_scene_emissivity, uint16_t *ret_temperature_background, uint16_t *ret_tau_window, uint16_t *ret_temperatur_window, uint16_t *ret_tau_atmosphere, uint16_t *ret_temperature_atmosphere, uint16_t *ret_reflection_window, uint16_t *ret_temperature_reflection)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the flux linear parameters, as set by thermal_imaging_set_flux_linear_parameters()
.
New in version 2.0.5 (Plugin).
thermal_imaging_set_ffc_shutter_mode
(ThermalImaging *thermal_imaging, uint8_t shutter_mode, uint8_t temp_lockout_state, bool video_freeze_during_ffc, bool ffc_desired, uint32_t elapsed_time_since_last_ffc, uint32_t desired_ffc_period, bool explicit_cmd_to_open, uint16_t desired_ffc_temp_delta, uint16_t imminent_delay)¶Parameters: |
|
---|---|
Returns: |
|
Sets the FFC shutter mode parameters.
See FLIR document 110-0144-03 4.5.15 for more details.
The following constants are available for this function:
For shutter_mode:
For temp_lockout_state:
New in version 2.0.6 (Plugin).
thermal_imaging_get_ffc_shutter_mode
(ThermalImaging *thermal_imaging, uint8_t *ret_shutter_mode, uint8_t *ret_temp_lockout_state, bool *ret_video_freeze_during_ffc, bool *ret_ffc_desired, uint32_t *ret_elapsed_time_since_last_ffc, uint32_t *ret_desired_ffc_period, bool *ret_explicit_cmd_to_open, uint16_t *ret_desired_ffc_temp_delta, uint16_t *ret_imminent_delay)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Sets the FFC shutter mode parameters.
See FLIR document 110-0144-03 4.5.15 for more details.
The following constants are available for this function:
For ret_shutter_mode:
For ret_temp_lockout_state:
New in version 2.0.6 (Plugin).
thermal_imaging_run_ffc_normalization
(ThermalImaging *thermal_imaging)¶Parameters: |
|
---|---|
Returns: |
|
Starts the Flat-Field Correction (FFC) normalization.
See FLIR document 110-0144-03 4.5.16 for more details.
New in version 2.0.6 (Plugin).
thermal_imaging_get_spitfp_error_count
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_set_status_led_config
(ThermalImaging *thermal_imaging, 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:
thermal_imaging_get_status_led_config
(ThermalImaging *thermal_imaging, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by thermal_imaging_set_status_led_config()
The following constants are available for this function:
For ret_config:
thermal_imaging_get_chip_temperature
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_reset
(ThermalImaging *thermal_imaging)¶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!
thermal_imaging_get_identity
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_register_callback
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_set_image_transfer_config
(ThermalImaging *thermal_imaging, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
The necessary bandwidth of this Bricklet is too high to use getter/callback or high contrast/temperature image at the same time. You have to configure the one you want to use, the Bricklet will optimize the internal configuration accordingly.
Corresponding functions:
thermal_imaging_get_high_contrast_image()
.thermal_imaging_get_temperature_image()
.THERMAL_IMAGING_CALLBACK_HIGH_CONTRAST_IMAGE
callback.THERMAL_IMAGING_CALLBACK_TEMPERATURE_IMAGE
callback.The following constants are available for this function:
For config:
thermal_imaging_get_image_transfer_config
(ThermalImaging *thermal_imaging, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the image transfer config, as set by thermal_imaging_set_image_transfer_config()
.
The following constants are available for this function:
For ret_config:
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the thermal_imaging_register_callback()
function:
void my_callback(int value, void *user_data) { printf("Value: %d\n", value); } thermal_imaging_register_callback(&thermal_imaging, THERMAL_IMAGING_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.
THERMAL_IMAGING_CALLBACK_HIGH_CONTRAST_IMAGE
¶void callback(uint8_t *image, uint16_t image_length, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered with every new high contrast image if the transfer image
config is configured for high contrast callback (see thermal_imaging_set_image_transfer_config()
).
The data is organized as a 8-bit value 80x60 pixel matrix linearized in a one-dimensional array. The data is arranged line by line from top left to bottom right.
Each 8-bit value represents one gray-scale image pixel that can directly be shown to a user on a display.
Note
If reconstructing the value fails, the callback is triggered with NULL for image.
THERMAL_IMAGING_CALLBACK_TEMPERATURE_IMAGE
¶void callback(uint16_t *image, uint16_t image_length, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered with every new temperature image if the transfer image
config is configured for temperature callback (see thermal_imaging_set_image_transfer_config()
).
The data is organized as a 16-bit value 80x60 pixel matrix linearized in a one-dimensional array. The data is arranged line by line from top left to bottom right.
Each 16-bit value represents one temperature measurement in either
Kelvin/10 or Kelvin/100 (depending on the resolution set with thermal_imaging_set_resolution()
).
Note
If reconstructing the value fails, the callback is triggered with NULL for image.
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.
thermal_imaging_get_api_version
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_get_response_expected
(ThermalImaging *thermal_imaging, 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
thermal_imaging_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:
thermal_imaging_set_response_expected
(ThermalImaging *thermal_imaging, 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:
thermal_imaging_set_response_expected_all
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_set_bootloader_mode
(ThermalImaging *thermal_imaging, 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:
thermal_imaging_get_bootloader_mode
(ThermalImaging *thermal_imaging, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current bootloader mode, see thermal_imaging_set_bootloader_mode()
.
The following constants are available for this function:
For ret_mode:
thermal_imaging_set_write_firmware_pointer
(ThermalImaging *thermal_imaging, uint32_t pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for thermal_imaging_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.
thermal_imaging_write_firmware
(ThermalImaging *thermal_imaging, uint8_t data[64], uint8_t *ret_status)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
thermal_imaging_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.
thermal_imaging_write_uid
(ThermalImaging *thermal_imaging, 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.
thermal_imaging_read_uid
(ThermalImaging *thermal_imaging, uint32_t *ret_uid)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
THERMAL_IMAGING_DEVICE_IDENTIFIER
¶This constant is used to identify a Thermal Imaging Bricklet.
The thermal_imaging_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.
THERMAL_IMAGING_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Thermal Imaging Bricklet.