This is the description of the C/C++ for Microcontrollers API bindings for the PTC Bricklet 2.0. General information and technical specifications for the PTC Bricklet 2.0 are summarized in its hardware description.
An installation guide for the C/C++ for Microcontrollers 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 | // This example is not self-contained.
// It requires usage of the example driver specific to your platform.
// See the HAL documentation.
#include "src/bindings/hal_common.h"
#include "src/bindings/bricklet_ptc_v2.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
static TF_PTCV2 ptc;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_ptc_v2_create(&ptc, NULL, hal), "create device object");
// Get current temperature
int32_t temperature;
check(tf_ptc_v2_get_temperature(&ptc, &temperature), "get temperature");
tf_hal_printf("Temperature: %d 1/%d °C\n", temperature, 100);
}
void example_loop(TF_HAL *hal) {
// Poll for callbacks
tf_hal_callback_tick(hal, 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 | // This example is not self-contained.
// It requires usage of the example driver specific to your platform.
// See the HAL documentation.
#include "src/bindings/hal_common.h"
#include "src/bindings/bricklet_ptc_v2.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
// Callback function for temperature callback
static void temperature_handler(TF_PTCV2 *device, int32_t temperature, void *user_data) {
(void)device; (void)user_data; // avoid unused parameter warning
tf_hal_printf("Temperature: %d 1/%d °C\n", temperature, 100);
}
static TF_PTCV2 ptc;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_ptc_v2_create(&ptc, NULL, hal), "create device object");
// Register temperature callback to function temperature_handler
tf_ptc_v2_register_temperature_callback(&ptc,
temperature_handler,
NULL);
// Set period for temperature callback to 1s (1000ms) without a threshold
tf_ptc_v2_set_temperature_callback_configuration(&ptc, 1000, false, 'x', 0, 0);
}
void example_loop(TF_HAL *hal) {
// Poll for callbacks
tf_hal_callback_tick(hal, 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 | // This example is not self-contained.
// It requires usage of the example driver specific to your platform.
// See the HAL documentation.
#include "src/bindings/hal_common.h"
#include "src/bindings/bricklet_ptc_v2.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
// Callback function for temperature callback
static void temperature_handler(TF_PTCV2 *device, int32_t temperature, void *user_data) {
(void)device; (void)user_data; // avoid unused parameter warning
tf_hal_printf("Temperature: %d 1/%d °C\n", temperature, 100);
}
static TF_PTCV2 ptc;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_ptc_v2_create(&ptc, NULL, hal), "create device object");
// Register temperature callback to function temperature_handler
tf_ptc_v2_register_temperature_callback(&ptc,
temperature_handler,
NULL);
// Configure threshold for temperature "greater than 30 °C"
// with a debounce period of 1s (1000ms)
tf_ptc_v2_set_temperature_callback_configuration(&ptc, 1000, false, '>', 30*100, 0);
}
void example_loop(TF_HAL *hal) {
// Poll for callbacks
tf_hal_callback_tick(hal, 0);
}
|
Most functions of the C/C++ bindings for microcontrollers return an error code
(e_code
).
Possible error codes are:
(as defined in errors.h
) as well as the errors returned from
the hardware abstraction layer (HAL) that is used.
Use :cpp:func`tf_hal_strerror` (defined in the HAL's header file) to get an error string for an error code.
Data returned from the device, when a getter is called,
is handled via output parameters. These parameters are labeled with the
ret_
prefix. The bindings will not write to an output parameter if NULL or nullptr
is passed. This can be used to ignore outputs that you are not interested in.
None of the functions listed below are thread-safe. See the API bindings description for details.
tf_ptc_v2_create
(TF_PTCV2 *ptc_v2, const char *uid_or_port_name, TF_HAL *hal)¶Parameters: |
|
---|---|
Returns: |
|
Creates the device object ptc_v2
with the optional unique device ID or port name
uid_or_port_name
and adds it to the HAL hal
:
TF_PTCV2 ptc_v2;
tf_ptc_v2_create(&ptc_v2, NULL, &hal);
Normally uid_or_port_name
can stay NULL
. For more details about this
see section UID or Port Name.
tf_ptc_v2_destroy
(TF_PTCV2 *ptc_v2)¶Parameters: |
|
---|---|
Returns: |
|
Removes the device object ptc_v2
from its HAL and destroys it.
The device object cannot be used anymore afterwards.
tf_ptc_v2_get_temperature
(TF_PTCV2 *ptc_v2, int32_t *ret_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the temperature of the connected sensor.
If you want to get the value periodically, it is recommended to use the
Temperature
callback. You can set the callback configuration
with tf_ptc_v2_set_temperature_callback_configuration()
.
tf_ptc_v2_get_resistance
(TF_PTCV2 *ptc_v2, int32_t *ret_resistance)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the value as measured by the MAX31865 precision delta-sigma ADC.
The value can be converted with the following formulas:
If you want to get the value periodically, it is recommended to use the
Resistance
callback. You can set the callback configuration
with tf_ptc_v2_set_resistance_callback_configuration()
.
tf_ptc_v2_is_sensor_connected
(TF_PTCV2 *ptc_v2, bool *ret_connected)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns true if the sensor is connected correctly.
If this function returns false, there is either no Pt100 or Pt1000 sensor connected, the sensor is connected incorrectly or the sensor itself is faulty.
If you want to get the status automatically, it is recommended to use the
Sensor Connected
callback. You can set the callback configuration
with tf_ptc_v2_set_sensor_connected_callback_configuration()
.
tf_ptc_v2_set_wire_mode
(TF_PTCV2 *ptc_v2, uint8_t mode)¶Parameters: |
|
---|---|
Returns: |
|
Sets the wire mode of the sensor. Possible values are 2, 3 and 4 which correspond to 2-, 3- and 4-wire sensors. The value has to match the jumper configuration on the Bricklet.
The following constants are available for this function:
For mode:
tf_ptc_v2_get_wire_mode
(TF_PTCV2 *ptc_v2, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the wire mode as set by tf_ptc_v2_set_wire_mode()
The following constants are available for this function:
For ret_mode:
tf_ptc_v2_set_moving_average_configuration
(TF_PTCV2 *ptc_v2, uint16_t moving_average_length_resistance, uint16_t moving_average_length_temperature)¶Parameters: |
|
---|---|
Returns: |
|
Sets the length of a moving averaging for the resistance and temperature.
Setting the length to 1 will turn the averaging off. With less averaging, there is more noise on the data.
New data is gathered every 20ms. With a moving average of length 1000 the resulting averaging window has a length of 20s. If you want to do long term measurements the longest moving average will give the cleanest results.
The default values match the non-changeable averaging settings of the old PTC Bricklet 1.0
tf_ptc_v2_get_moving_average_configuration
(TF_PTCV2 *ptc_v2, uint16_t *ret_moving_average_length_resistance, uint16_t *ret_moving_average_length_temperature)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the moving average configuration as set by tf_ptc_v2_set_moving_average_configuration()
.
tf_ptc_v2_set_noise_rejection_filter
(TF_PTCV2 *ptc_v2, uint8_t filter)¶Parameters: |
|
---|---|
Returns: |
|
Sets the noise rejection filter to either 50Hz (0) or 60Hz (1). Noise from 50Hz or 60Hz power sources (including harmonics of the AC power's fundamental frequency) is attenuated by 82dB.
The following constants are available for this function:
For filter:
tf_ptc_v2_get_noise_rejection_filter
(TF_PTCV2 *ptc_v2, uint8_t *ret_filter)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the noise rejection filter option as set by
tf_ptc_v2_set_noise_rejection_filter()
The following constants are available for this function:
For ret_filter:
tf_ptc_v2_get_spitfp_error_count
(TF_PTCV2 *ptc_v2, 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.
tf_ptc_v2_set_status_led_config
(TF_PTCV2 *ptc_v2, 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:
tf_ptc_v2_get_status_led_config
(TF_PTCV2 *ptc_v2, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by tf_ptc_v2_set_status_led_config()
The following constants are available for this function:
For ret_config:
tf_ptc_v2_get_chip_temperature
(TF_PTCV2 *ptc_v2, 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.
tf_ptc_v2_reset
(TF_PTCV2 *ptc_v2)¶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!
tf_ptc_v2_get_identity
(TF_PTCV2 *ptc_v2, 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.
tf_ptc_v2_set_temperature_callback_configuration
(TF_PTCV2 *ptc_v2, uint32_t period, bool value_has_to_change, char option, int32_t min, int32_t max)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the Temperature
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 Temperature
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:
tf_ptc_v2_get_temperature_callback_configuration
(TF_PTCV2 *ptc_v2, uint32_t *ret_period, bool *ret_value_has_to_change, char *ret_option, int32_t *ret_min, int32_t *ret_max)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by tf_ptc_v2_set_temperature_callback_configuration()
.
The following constants are available for this function:
For ret_option:
tf_ptc_v2_set_resistance_callback_configuration
(TF_PTCV2 *ptc_v2, uint32_t period, bool value_has_to_change, char option, int32_t min, int32_t max)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the Resistance
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 Resistance
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:
tf_ptc_v2_get_resistance_callback_configuration
(TF_PTCV2 *ptc_v2, uint32_t *ret_period, bool *ret_value_has_to_change, char *ret_option, int32_t *ret_min, int32_t *ret_max)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by tf_ptc_v2_set_resistance_callback_configuration()
.
The following constants are available for this function:
For ret_option:
tf_ptc_v2_set_sensor_connected_callback_configuration
(TF_PTCV2 *ptc_v2, bool enabled)¶Parameters: |
|
---|---|
Returns: |
|
If you enable this callback, the Sensor Connected
callback is triggered
every time a Pt sensor is connected/disconnected.
tf_ptc_v2_get_sensor_connected_callback_configuration
(TF_PTCV2 *ptc_v2, bool *ret_enabled)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by tf_ptc_v2_set_sensor_connected_callback_configuration()
.
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the corresponding tf_ptc_v2_register_*_callback
function.
The user_data
passed to the registration function as well as the device that triggered the callback are
passed to the registered callback handler.
Only one handler can be registered to a callback at the same time.
To deregister a callback, call the tf_ptc_v2_register_*_callback
function
with NULL as handler.
Note
Using callbacks for recurring events is preferred compared to using getters. Polling for a callback requires writing one byte only. See here Optimizing Performance.
Warning
Calling bindings function from inside a callback handler is not allowed. See here Thread safety.
tf_ptc_v2_register_temperature_callback
(TF_PTCV2 *ptc_v2, TF_PTCV2_TemperatureHandler handler, void *user_data)¶void handler(TF_PTCV2 *ptc_v2, int32_t temperature, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
tf_ptc_v2_set_temperature_callback_configuration()
.
The parameter is the same as tf_ptc_v2_get_temperature()
.
tf_ptc_v2_register_resistance_callback
(TF_PTCV2 *ptc_v2, TF_PTCV2_ResistanceHandler handler, void *user_data)¶void handler(TF_PTCV2 *ptc_v2, int32_t resistance, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
tf_ptc_v2_set_resistance_callback_configuration()
.
The parameter is the same as tf_ptc_v2_get_resistance()
.
tf_ptc_v2_register_sensor_connected_callback
(TF_PTCV2 *ptc_v2, TF_PTCV2_SensorConnectedHandler handler, void *user_data)¶void handler(TF_PTCV2 *ptc_v2, bool connected, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
tf_ptc_v2_set_sensor_connected_callback_configuration()
.
The parameter is the same as tf_ptc_v2_is_sensor_connected()
.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object.
tf_ptc_v2_get_response_expected
(TF_PTCV2 *ptc_v2, 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
tf_ptc_v2_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:
tf_ptc_v2_set_response_expected
(TF_PTCV2 *ptc_v2, 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:
tf_ptc_v2_set_response_expected_all
(TF_PTCV2 *ptc_v2, 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.
tf_ptc_v2_set_bootloader_mode
(TF_PTCV2 *ptc_v2, 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:
tf_ptc_v2_get_bootloader_mode
(TF_PTCV2 *ptc_v2, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current bootloader mode, see tf_ptc_v2_set_bootloader_mode()
.
The following constants are available for this function:
For ret_mode:
tf_ptc_v2_set_write_firmware_pointer
(TF_PTCV2 *ptc_v2, uint32_t pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for tf_ptc_v2_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.
tf_ptc_v2_write_firmware
(TF_PTCV2 *ptc_v2, const uint8_t data[64], uint8_t *ret_status)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Writes 64 Bytes of firmware at the position as written by
tf_ptc_v2_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.
tf_ptc_v2_write_uid
(TF_PTCV2 *ptc_v2, 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.
tf_ptc_v2_read_uid
(TF_PTCV2 *ptc_v2, uint32_t *ret_uid)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.
TF_PTC_V2_DEVICE_IDENTIFIER
¶This constant is used to identify a PTC Bricklet 2.0.
The functions tf_ptc_v2_get_identity()
and tf_hal_get_device_info()
have a device_identifier
output parameter to specify
the Brick's or Bricklet's type.
TF_PTC_V2_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a PTC Bricklet 2.0.