This is the description of the C/C++ for Microcontrollers API bindings for the Industrial Dual 0-20mA Bricklet 2.0. General information and technical specifications for the Industrial Dual 0-20mA 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 29 | // 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_industrial_dual_0_20ma_v2.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
static TF_IndustrialDual020mAV2 id020;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_industrial_dual_0_20ma_v2_create(&id020, NULL, hal), "create device object");
// Get current current from channel 0
int32_t current;
check(tf_industrial_dual_0_20ma_v2_get_current(&id020, 0,
¤t), "get current from channel 0");
tf_hal_printf("Current (Channel 0): %d 1/%d mA\n", current, 1000000);
}
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 38 39 40 | // 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_industrial_dual_0_20ma_v2.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
// Callback function for current callback
static void current_handler(TF_IndustrialDual020mAV2 *device, uint8_t channel,
int32_t current, void *user_data) {
(void)device; (void)user_data; // avoid unused parameter warning
tf_hal_printf("Channel: %I8u\n", channel);
tf_hal_printf("Current: %d 1/%d mA\n", current, 1000000);
tf_hal_printf("\n");
}
static TF_IndustrialDual020mAV2 id020;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_industrial_dual_0_20ma_v2_create(&id020, NULL, hal), "create device object");
// Register current callback to function current_handler
tf_industrial_dual_0_20ma_v2_register_current_callback(&id020,
current_handler,
NULL);
// Set period for current (channel 0) callback to 1s (1000ms) without a threshold
tf_industrial_dual_0_20ma_v2_set_current_callback_configuration(&id020, 0, 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 39 40 41 | // 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_industrial_dual_0_20ma_v2.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
// Callback function for current callback
static void current_handler(TF_IndustrialDual020mAV2 *device, uint8_t channel,
int32_t current, void *user_data) {
(void)device; (void)user_data; // avoid unused parameter warning
tf_hal_printf("Channel: %I8u\n", channel);
tf_hal_printf("Current: %d 1/%d mA\n", current, 1000000);
tf_hal_printf("\n");
}
static TF_IndustrialDual020mAV2 id020;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_industrial_dual_0_20ma_v2_create(&id020, NULL, hal), "create device object");
// Register current callback to function current_handler
tf_industrial_dual_0_20ma_v2_register_current_callback(&id020,
current_handler,
NULL);
// Configure threshold for current (channel 0) "greater than 10 mA"
// with a debounce period of 10s (10000ms)
tf_industrial_dual_0_20ma_v2_set_current_callback_configuration(&id020, 0, 10000, false, '>', 10*1000000, 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_industrial_dual_0_20ma_v2_create
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, const char *uid_or_port_name, TF_HAL *hal)¶Parameters: |
|
---|---|
Returns: |
|
Creates the device object industrial_dual_0_20ma_v2
with the optional unique device ID or port name
uid_or_port_name
and adds it to the HAL hal
:
TF_IndustrialDual020mAV2 industrial_dual_0_20ma_v2;
tf_industrial_dual_0_20ma_v2_create(&industrial_dual_0_20ma_v2, NULL, &hal);
Normally uid_or_port_name
can stay NULL
. For more details about this
see section UID or Port Name.
tf_industrial_dual_0_20ma_v2_destroy
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2)¶Parameters: |
|
---|---|
Returns: |
|
Removes the device object industrial_dual_0_20ma_v2
from its HAL and destroys it.
The device object cannot be used anymore afterwards.
tf_industrial_dual_0_20ma_v2_get_current
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, int32_t *ret_current)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current of the specified channel.
It is possible to detect if an IEC 60381-1 compatible sensor is connected and if it works probably.
If the returned current is below 4mA, there is likely no sensor connected or the connected sensor is defective. If the returned current is over 20mA, there might be a short circuit or the sensor is defective.
If you want to get the value periodically, it is recommended to use the
Current
callback. You can set the callback configuration
with tf_industrial_dual_0_20ma_v2_set_current_callback_configuration()
.
tf_industrial_dual_0_20ma_v2_set_channel_led_config
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Each channel has a corresponding LED. You can turn the LED off, on or show a heartbeat. You can also set the LED to "Channel Status". In this mode the LED can either be turned on with a pre-defined threshold or the intensity of the LED can change with the measured value.
You can configure the channel status behavior with tf_industrial_dual_0_20ma_v2_set_channel_led_status_config()
.
The following constants are available for this function:
For config:
tf_industrial_dual_0_20ma_v2_get_channel_led_config
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the channel LED configuration as set by tf_industrial_dual_0_20ma_v2_set_channel_led_config()
The following constants are available for this function:
For ret_config:
tf_industrial_dual_0_20ma_v2_set_channel_led_status_config
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, int32_t min, int32_t max, uint8_t config)¶Parameters: |
|
---|---|
Returns: |
|
Sets the channel LED status config. This config is used if the channel LED is
configured as "Channel Status", see tf_industrial_dual_0_20ma_v2_set_channel_led_config()
.
For each channel you can choose between threshold and intensity mode.
In threshold mode you can define a positive or a negative threshold. For a positive threshold set the "min" parameter to the threshold value in nA above which the LED should turn on and set the "max" parameter to 0. Example: If you set a positive threshold of 10mA, the LED will turn on as soon as the current exceeds 10mA and turn off again if it goes below 10mA. For a negative threshold set the "max" parameter to the threshold value in nA below which the LED should turn on and set the "min" parameter to 0. Example: If you set a negative threshold of 10mA, the LED will turn on as soon as the current goes below 10mA and the LED will turn off when the current exceeds 10mA.
In intensity mode you can define a range in nA that is used to scale the brightness of the LED. Example with min=4mA and max=20mA: The LED is off at 4mA and below, on at 20mA and above and the brightness is linearly scaled between the values 4mA and 20mA. If the min value is greater than the max value, the LED brightness is scaled the other way around.
The following constants are available for this function:
For config:
tf_industrial_dual_0_20ma_v2_get_channel_led_status_config
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, int32_t *ret_min, int32_t *ret_max, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the channel LED status configuration as set by
tf_industrial_dual_0_20ma_v2_set_channel_led_status_config()
.
The following constants are available for this function:
For ret_config:
tf_industrial_dual_0_20ma_v2_set_sample_rate
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t rate)¶Parameters: |
|
---|---|
Returns: |
|
Sets the sample rate to either 240, 60, 15 or 4 samples per second. The resolution for the rates is 12, 14, 16 and 18 bit respectively.
Value | Description |
---|---|
0 | 240 samples per second, 12 bit resolution |
1 | 60 samples per second, 14 bit resolution |
2 | 15 samples per second, 16 bit resolution |
3 | 4 samples per second, 18 bit resolution |
The following constants are available for this function:
For rate:
tf_industrial_dual_0_20ma_v2_get_sample_rate
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t *ret_rate)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the sample rate as set by tf_industrial_dual_0_20ma_v2_set_sample_rate()
.
The following constants are available for this function:
For ret_rate:
tf_industrial_dual_0_20ma_v2_set_gain
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t gain)¶Parameters: |
|
---|---|
Returns: |
|
Sets a gain between 1x and 8x. If you want to measure a very small current, you can increase the gain to get some more resolution.
Example: If you measure 0.5mA with a gain of 8x the return value will be 4mA.
The following constants are available for this function:
For gain:
tf_industrial_dual_0_20ma_v2_get_gain
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t *ret_gain)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the gain as set by tf_industrial_dual_0_20ma_v2_set_gain()
.
The following constants are available for this function:
For ret_gain:
tf_industrial_dual_0_20ma_v2_get_spitfp_error_count
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_set_status_led_config
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_get_status_led_config
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by tf_industrial_dual_0_20ma_v2_set_status_led_config()
The following constants are available for this function:
For ret_config:
tf_industrial_dual_0_20ma_v2_get_chip_temperature
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_reset
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_get_identity
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_set_current_callback_configuration
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, 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 Current
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 Current
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_industrial_dual_0_20ma_v2_get_current_callback_configuration
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, 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_industrial_dual_0_20ma_v2_set_current_callback_configuration()
.
The following constants are available for this function:
For ret_option:
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the corresponding tf_industrial_dual_0_20ma_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_industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_register_current_callback
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, TF_IndustrialDual020mAV2_CurrentHandler handler, void *user_data)¶void handler(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t channel, int32_t current, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
tf_industrial_dual_0_20ma_v2_set_current_callback_configuration()
.
The parameter is the same as tf_industrial_dual_0_20ma_v2_get_current()
.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object.
tf_industrial_dual_0_20ma_v2_get_response_expected
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_set_response_expected
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_set_response_expected_all
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_set_bootloader_mode
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_get_bootloader_mode
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current bootloader mode, see tf_industrial_dual_0_20ma_v2_set_bootloader_mode()
.
The following constants are available for this function:
For ret_mode:
tf_industrial_dual_0_20ma_v2_set_write_firmware_pointer
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_v2, uint32_t pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for tf_industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_write_firmware
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_write_uid
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_industrial_dual_0_20ma_v2_read_uid
(TF_IndustrialDual020mAV2 *industrial_dual_0_20ma_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_INDUSTRIAL_DUAL_0_20MA_V2_DEVICE_IDENTIFIER
¶This constant is used to identify a Industrial Dual 0-20mA Bricklet 2.0.
The functions tf_industrial_dual_0_20ma_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_INDUSTRIAL_DUAL_0_20MA_V2_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Industrial Dual 0-20mA Bricklet 2.0.