This is the description of the MQTT 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 MQTT API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
Download (example-callback.txt)
1 2 3 4 5 6 7 8 9 | # Change XYZ to the UID of your Thermal Imaging Bricklet
setup:
# Handle incoming high contrast image callbacks
subscribe to tinkerforge/callback/thermal_imaging_bricklet/XYZ/high_contrast_image
publish '{"register": true}' to tinkerforge/register/thermal_imaging_bricklet/XYZ/high_contrast_image # Register high_contrast_image callback
# Enable high contrast image transfer for callback
publish '{"config": "callback_high_contrast_image"}' to tinkerforge/request/thermal_imaging_bricklet/XYZ/set_image_transfer_config
|
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 member _ERROR
.
It is published on the corresponding response topic: .../response/...
for .../request/...
and .../callback/...
for .../register/...
.
request/
thermal_imaging_bricklet/
<UID>/
get_high_contrast_image
¶Request: |
|
---|---|
Response: |
|
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
request/thermal_imaging_bricklet/<UID>/set_image_transfer_config
.
request/
thermal_imaging_bricklet/
<UID>/
get_temperature_image
¶Request: |
|
---|---|
Response: |
|
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 request/thermal_imaging_bricklet/<UID>/set_resolution
).
Before you can use this function you have to enable it with
request/thermal_imaging_bricklet/<UID>/set_image_transfer_config
.
request/
thermal_imaging_bricklet/
<UID>/
get_statistics
¶Request: |
|
---|---|
Response: |
|
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 symbols are available for this function:
For resolution:
For ffc_status:
request/
thermal_imaging_bricklet/
<UID>/
set_resolution
¶Request: |
|
---|---|
Response: |
|
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 symbols are available for this function:
For resolution:
request/
thermal_imaging_bricklet/
<UID>/
get_resolution
¶Request: |
|
---|---|
Response: |
|
Returns the resolution as set by request/thermal_imaging_bricklet/<UID>/set_resolution
.
The following symbols are available for this function:
For resolution:
request/
thermal_imaging_bricklet/
<UID>/
set_spotmeter_config
¶Request: |
|
---|---|
Response: |
|
Sets the spotmeter region of interest. The 4 values are
The spotmeter statistics can be read out with request/thermal_imaging_bricklet/<UID>/get_statistics
.
request/
thermal_imaging_bricklet/
<UID>/
get_spotmeter_config
¶Request: |
|
---|---|
Response: |
|
Returns the spotmeter config as set by request/thermal_imaging_bricklet/<UID>/set_spotmeter_config
.
request/
thermal_imaging_bricklet/
<UID>/
set_high_contrast_config
¶Request: |
|
---|---|
Response: |
|
Sets the high contrast region of interest, dampening factor, clip limit and empty counts.
This config is only used in high contrast mode (see request/thermal_imaging_bricklet/<UID>/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.
request/
thermal_imaging_bricklet/
<UID>/
get_high_contrast_config
¶Request: |
|
---|---|
Response: |
|
Returns the high contrast config as set by request/thermal_imaging_bricklet/<UID>/set_high_contrast_config
.
request/
thermal_imaging_bricklet/
<UID>/
set_flux_linear_parameters
¶Request: |
|
---|---|
Response: |
|
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).
request/
thermal_imaging_bricklet/
<UID>/
get_flux_linear_parameters
¶Request: |
|
---|---|
Response: |
|
Returns the flux linear parameters, as set by request/thermal_imaging_bricklet/<UID>/set_flux_linear_parameters
.
New in version 2.0.5 (Plugin).
request/
thermal_imaging_bricklet/
<UID>/
set_ffc_shutter_mode
¶Request: |
|
---|---|
Response: |
|
Sets the FFC shutter mode parameters.
See FLIR document 110-0144-03 4.5.15 for more details.
The following symbols are available for this function:
For shutter_mode:
For temp_lockout_state:
New in version 2.0.6 (Plugin).
request/
thermal_imaging_bricklet/
<UID>/
get_ffc_shutter_mode
¶Request: |
|
---|---|
Response: |
|
Sets the FFC shutter mode parameters.
See FLIR document 110-0144-03 4.5.15 for more details.
The following symbols are available for this function:
For shutter_mode:
For temp_lockout_state:
New in version 2.0.6 (Plugin).
request/
thermal_imaging_bricklet/
<UID>/
run_ffc_normalization
¶Request: |
|
---|---|
Response: |
|
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).
request/
thermal_imaging_bricklet/
<UID>/
get_spitfp_error_count
¶Request: |
|
---|---|
Response: |
|
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.
request/
thermal_imaging_bricklet/
<UID>/
set_status_led_config
¶Request: |
|
---|---|
Response: |
|
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 symbols are available for this function:
For config:
request/
thermal_imaging_bricklet/
<UID>/
get_status_led_config
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/thermal_imaging_bricklet/<UID>/set_status_led_config
The following symbols are available for this function:
For config:
request/
thermal_imaging_bricklet/
<UID>/
get_chip_temperature
¶Request: |
|
---|---|
Response: |
|
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.
request/
thermal_imaging_bricklet/
<UID>/
reset
¶Request: |
|
---|---|
Response: |
|
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!
request/
thermal_imaging_bricklet/
<UID>/
get_identity
¶Request: |
|
---|---|
Response: |
|
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. 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 Thermal Imaging's name in a human readable form.
request/
thermal_imaging_bricklet/
<UID>/
set_image_transfer_config
¶Request: |
|
---|---|
Response: |
|
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:
request/thermal_imaging_bricklet/<UID>/get_high_contrast_image
.request/thermal_imaging_bricklet/<UID>/get_temperature_image
.register/thermal_imaging_bricklet/<UID>/high_contrast_image
callback.register/thermal_imaging_bricklet/<UID>/temperature_image
callback.The following symbols are available for this function:
For config:
request/
thermal_imaging_bricklet/
<UID>/
get_image_transfer_config
¶Request: |
|
---|---|
Response: |
|
Returns the image transfer config, as set by request/thermal_imaging_bricklet/<UID>/set_image_transfer_config
.
The following symbols are available for this function:
For config:
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/
thermal_imaging_bricklet/
<UID>/
high_contrast_image
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/thermal_imaging_bricklet/<UID>/high_contrast_image[/<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/thermal_imaging_bricklet/<UID>/high_contrast_image[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered with every new high contrast image if the transfer image
config is configured for high contrast callback (see request/thermal_imaging_bricklet/<UID>/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.
register/
thermal_imaging_bricklet/
<UID>/
temperature_image
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/thermal_imaging_bricklet/<UID>/temperature_image[/<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/thermal_imaging_bricklet/<UID>/temperature_image[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered with every new temperature image if the transfer image
config is configured for temperature callback (see request/thermal_imaging_bricklet/<UID>/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 request/thermal_imaging_bricklet/<UID>/set_resolution
).
Note
If reconstructing the value fails, the callback is triggered with null for image.
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.
request/
thermal_imaging_bricklet/
<UID>/
set_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
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 symbols are available for this function:
For mode:
For status:
request/
thermal_imaging_bricklet/
<UID>/
get_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
Returns the current bootloader mode, see request/thermal_imaging_bricklet/<UID>/set_bootloader_mode
.
The following symbols are available for this function:
For mode:
request/
thermal_imaging_bricklet/
<UID>/
set_write_firmware_pointer
¶Request: |
|
---|---|
Response: |
|
Sets the firmware pointer for request/thermal_imaging_bricklet/<UID>/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.
request/
thermal_imaging_bricklet/
<UID>/
write_firmware
¶Request: |
|
---|---|
Response: |
|
Writes 64 Bytes of firmware at the position as written by
request/thermal_imaging_bricklet/<UID>/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.
request/
thermal_imaging_bricklet/
<UID>/
write_uid
¶Request: |
|
---|---|
Response: |
|
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.
request/
thermal_imaging_bricklet/
<UID>/
read_uid
¶Request: |
|
---|---|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.