This is the description of the C/C++ API bindings for the Thermocouple Bricklet. General information and technical specifications for the Thermocouple 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 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_thermocouple.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Thermocouple Bricklet
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
Thermocouple t;
thermocouple_create(&t, 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
// Get current temperature
int32_t temperature;
if(thermocouple_get_temperature(&t, &temperature) < 0) {
fprintf(stderr, "Could not get temperature, probably timeout\n");
return 1;
}
printf("Temperature: %f °C\n", temperature/100.0);
printf("Press key to exit\n");
getchar();
thermocouple_destroy(&t);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 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 49 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_thermocouple.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Thermocouple Bricklet
// Callback function for temperature callback
void cb_temperature(int32_t temperature, void *user_data) {
(void)user_data; // avoid unused parameter warning
printf("Temperature: %f °C\n", temperature/100.0);
}
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
Thermocouple t;
thermocouple_create(&t, 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 temperature callback to function cb_temperature
thermocouple_register_callback(&t,
THERMOCOUPLE_CALLBACK_TEMPERATURE,
(void (*)(void))cb_temperature,
NULL);
// Set period for temperature callback to 1s (1000ms)
// Note: The temperature callback is only called every second
// if the temperature has changed since the last call!
thermocouple_set_temperature_callback_period(&t, 1000);
printf("Press key to exit\n");
getchar();
thermocouple_destroy(&t);
ipcon_destroy(&ipcon); // Calls ipcon_disconnect internally
return 0;
}
|
Download (example_threshold.c)
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 | #include <stdio.h>
#include "ip_connection.h"
#include "bricklet_thermocouple.h"
#define HOST "localhost"
#define PORT 4223
#define UID "XYZ" // Change XYZ to the UID of your Thermocouple Bricklet
// Callback function for temperature reached callback
void cb_temperature_reached(int32_t temperature, void *user_data) {
(void)user_data; // avoid unused parameter warning
printf("Temperature: %f °C\n", temperature/100.0);
}
int main(void) {
// Create IP connection
IPConnection ipcon;
ipcon_create(&ipcon);
// Create device object
Thermocouple t;
thermocouple_create(&t, 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
// Get threshold callbacks with a debounce time of 10 seconds (10000ms)
thermocouple_set_debounce_period(&t, 10000);
// Register temperature reached callback to function cb_temperature_reached
thermocouple_register_callback(&t,
THERMOCOUPLE_CALLBACK_TEMPERATURE_REACHED,
(void (*)(void))cb_temperature_reached,
NULL);
// Configure threshold for temperature "greater than 30 °C"
thermocouple_set_temperature_callback_threshold(&t, '>', 30*100, 0);
printf("Press key to exit\n");
getchar();
thermocouple_destroy(&t);
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.
thermocouple_create
(Thermocouple *thermocouple, const char *uid, IPConnection *ipcon)¶Parameters: |
|
---|
Creates the device object thermocouple
with the unique device ID uid
and adds
it to the IPConnection ipcon
:
Thermocouple thermocouple;
thermocouple_create(&thermocouple, "YOUR_DEVICE_UID", &ipcon);
This device object can be used after the IP connection has been connected.
thermocouple_destroy
(Thermocouple *thermocouple)¶Parameters: |
|
---|
Removes the device object thermocouple
from its IPConnection and destroys it.
The device object cannot be used anymore afterwards.
thermocouple_get_temperature
(Thermocouple *thermocouple, int32_t *ret_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the temperature of the thermocouple.
If you want to get the temperature periodically, it is recommended
to use the THERMOCOUPLE_CALLBACK_TEMPERATURE
callback and set the period with
thermocouple_set_temperature_callback_period()
.
thermocouple_set_configuration
(Thermocouple *thermocouple, uint8_t averaging, uint8_t thermocouple_type, uint8_t filter)¶Parameters: |
|
---|---|
Returns: |
|
You can configure averaging size, thermocouple type and frequency filtering.
Available averaging sizes are 1, 2, 4, 8 and 16 samples.
As thermocouple type you can use B, E, J, K, N, R, S and T. If you have a different thermocouple or a custom thermocouple you can also use G8 and G32. With these types the returned value will not be in °C/100, it will be calculated by the following formulas:
value = 8 * 1.6 * 2^17 * Vin
value = 32 * 1.6 * 2^17 * Vin
where Vin is the thermocouple input voltage.
The frequency filter can be either configured to 50Hz or to 60Hz. You should configure it according to your utility frequency.
The conversion time depends on the averaging and filter configuration, it can be calculated as follows:
time = 82 + (samples - 1) * 16.67
time = 98 + (samples - 1) * 20
The following constants are available for this function:
For averaging:
For thermocouple_type:
For filter:
thermocouple_get_configuration
(Thermocouple *thermocouple, uint8_t *ret_averaging, uint8_t *ret_thermocouple_type, uint8_t *ret_filter)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by thermocouple_set_configuration()
.
The following constants are available for this function:
For ret_averaging:
For ret_thermocouple_type:
For ret_filter:
thermocouple_get_error_state
(Thermocouple *thermocouple, bool *ret_over_under, bool *ret_open_circuit)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current error state. There are two possible errors:
Over/Under Voltage happens for voltages below 0V or above 3.3V. In this case it is very likely that your thermocouple is defective. An Open Circuit error indicates that there is no thermocouple connected.
You can use the THERMOCOUPLE_CALLBACK_ERROR_STATE
callback to automatically get triggered
when the error state changes.
thermocouple_get_identity
(Thermocouple *thermocouple, 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.
thermocouple_register_callback
(Thermocouple *thermocouple, 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.
thermocouple_set_temperature_callback_period
(Thermocouple *thermocouple, uint32_t period)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the THERMOCOUPLE_CALLBACK_TEMPERATURE
callback is triggered
periodically. A value of 0 turns the callback off.
The THERMOCOUPLE_CALLBACK_TEMPERATURE
callback is only triggered if the temperature has changed
since the last triggering.
thermocouple_get_temperature_callback_period
(Thermocouple *thermocouple, uint32_t *ret_period)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the period as set by thermocouple_set_temperature_callback_period()
.
thermocouple_set_temperature_callback_threshold
(Thermocouple *thermocouple, char option, int32_t min, int32_t max)¶Parameters: |
|
---|---|
Returns: |
|
Sets the thresholds for the THERMOCOUPLE_CALLBACK_TEMPERATURE_REACHED
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the temperature is outside the min and max values |
'i' | Callback is triggered when the temperature is inside the min and max values |
'<' | Callback is triggered when the temperature is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the temperature is greater than the min value (max is ignored) |
The following constants are available for this function:
For option:
thermocouple_get_temperature_callback_threshold
(Thermocouple *thermocouple, char *ret_option, int32_t *ret_min, int32_t *ret_max)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the threshold as set by thermocouple_set_temperature_callback_threshold()
.
The following constants are available for this function:
For ret_option:
thermocouple_set_debounce_period
(Thermocouple *thermocouple, uint32_t debounce)¶Parameters: |
|
---|---|
Returns: |
|
Sets the period with which the threshold callback
is triggered, if the threshold
keeps being reached.
thermocouple_get_debounce_period
(Thermocouple *thermocouple, uint32_t *ret_debounce)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the debounce period as set by thermocouple_set_debounce_period()
.
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the thermocouple_register_callback()
function:
void my_callback(int value, void *user_data) { printf("Value: %d\n", value); } thermocouple_register_callback(&thermocouple, THERMOCOUPLE_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.
THERMOCOUPLE_CALLBACK_TEMPERATURE
¶void callback(int32_t temperature, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically with the period that is set by
thermocouple_set_temperature_callback_period()
. The parameter is the
temperature of the thermocouple.
The THERMOCOUPLE_CALLBACK_TEMPERATURE
callback is only triggered if the temperature has
changed since the last triggering.
THERMOCOUPLE_CALLBACK_TEMPERATURE_REACHED
¶void callback(int32_t temperature, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered when the threshold as set by
thermocouple_set_temperature_callback_threshold()
is reached.
The parameter is the temperature of the thermocouple.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by thermocouple_set_debounce_period()
.
THERMOCOUPLE_CALLBACK_ERROR_STATE
¶void callback(bool over_under, bool open_circuit, void *user_data)
Callback Parameters: |
|
---|
This Callback is triggered every time the error state changes
(see thermocouple_get_error_state()
).
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.
thermocouple_get_api_version
(Thermocouple *thermocouple, 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.
thermocouple_get_response_expected
(Thermocouple *thermocouple, 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
thermocouple_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:
thermocouple_set_response_expected
(Thermocouple *thermocouple, 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:
thermocouple_set_response_expected_all
(Thermocouple *thermocouple, bool response_expected)¶Parameters: |
|
---|---|
Returns: |
|
Changes the response expected flag for all setter and callback configuration functions of this device at once.
THERMOCOUPLE_DEVICE_IDENTIFIER
¶This constant is used to identify a Thermocouple Bricklet.
The thermocouple_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.
THERMOCOUPLE_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Thermocouple Bricklet.