This is the description of the C/C++ for Microcontrollers API bindings for the Particulate Matter Bricklet. General information and technical specifications for the Particulate Matter Bricklet 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 30 31 | // 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_particulate_matter.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
static TF_ParticulateMatter pm;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_particulate_matter_create(&pm, NULL, hal), "create device object");
// Get current PM concentration
uint16_t pm10, pm25, pm100;
check(tf_particulate_matter_get_pm_concentration(&pm, &pm10, &pm25,
&pm100), "get PM concentration");
tf_hal_printf("PM 1.0: %I16u µg/m³\n", pm10);
tf_hal_printf("PM 2.5: %I16u µg/m³\n", pm25);
tf_hal_printf("PM 10.0: %I16u µg/m³\n", pm100);
}
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 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_particulate_matter.h"
void check(int rc, const char *msg);
void example_setup(TF_HAL *hal);
void example_loop(TF_HAL *hal);
// Callback function for PM concentration callback
static void pm_concentration_handler(TF_ParticulateMatter *device, uint16_t pm10,
uint16_t pm25, uint16_t pm100, void *user_data) {
(void)device; (void)user_data; // avoid unused parameter warning
tf_hal_printf("PM 1.0: %I16u µg/m³\n", pm10);
tf_hal_printf("PM 2.5: %I16u µg/m³\n", pm25);
tf_hal_printf("PM 10.0: %I16u µg/m³\n", pm100);
tf_hal_printf("\n");
}
static TF_ParticulateMatter pm;
void example_setup(TF_HAL *hal) {
// Create device object
check(tf_particulate_matter_create(&pm, NULL, hal), "create device object");
// Register PM concentration callback to function pm_concentration_handler
tf_particulate_matter_register_pm_concentration_callback(&pm,
pm_concentration_handler,
NULL);
// Set period for PM concentration callback to 1s (1000ms)
tf_particulate_matter_set_pm_concentration_callback_configuration(&pm, 1000, false);
}
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_particulate_matter_create
(TF_ParticulateMatter *particulate_matter, const char *uid_or_port_name, TF_HAL *hal)¶Parameters: |
|
---|---|
Returns: |
|
Creates the device object particulate_matter
with the optional unique device ID or port name
uid_or_port_name
and adds it to the HAL hal
:
TF_ParticulateMatter particulate_matter;
tf_particulate_matter_create(&particulate_matter, NULL, &hal);
Normally uid_or_port_name
can stay NULL
. For more details about this
see section UID or Port Name.
tf_particulate_matter_destroy
(TF_ParticulateMatter *particulate_matter)¶Parameters: |
|
---|---|
Returns: |
|
Removes the device object particulate_matter
from its HAL and destroys it.
The device object cannot be used anymore afterwards.
tf_particulate_matter_get_pm_concentration
(TF_ParticulateMatter *particulate_matter, uint16_t *ret_pm10, uint16_t *ret_pm25, uint16_t *ret_pm100)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the particulate matter concentration, broken down as:
If the sensor is disabled (see tf_particulate_matter_set_enable()
) then the last known good
values from the sensor are returned.
If you want to get the values periodically, it is recommended to use the
PM Concentration
callback. You can set the callback configuration
with tf_particulate_matter_set_pm_concentration_callback_configuration()
.
tf_particulate_matter_get_pm_count
(TF_ParticulateMatter *particulate_matter, uint16_t *ret_greater03um, uint16_t *ret_greater05um, uint16_t *ret_greater10um, uint16_t *ret_greater25um, uint16_t *ret_greater50um, uint16_t *ret_greater100um)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the number of particulates in 100 ml of air, broken down by their diameter:
If the sensor is disabled (see tf_particulate_matter_set_enable()
) then the last known good
value from the sensor is returned.
If you want to get the values periodically, it is recommended to use the
PM Count
callback. You can set the callback configuration
with tf_particulate_matter_set_pm_count_callback_configuration()
.
tf_particulate_matter_set_enable
(TF_ParticulateMatter *particulate_matter, bool enable)¶Parameters: |
|
---|---|
Returns: |
|
Enables/Disables the fan and the laser diode of the sensors.
The sensor takes about 30 seconds after it is enabled to settle and produce stable values.
The laser diode has a lifetime of about 8000 hours. If you want to measure in an interval with a long idle time (e.g. hourly) you should turn the laser diode off between the measurements.
tf_particulate_matter_get_enable
(TF_ParticulateMatter *particulate_matter, bool *ret_enable)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the state of the sensor as set by tf_particulate_matter_set_enable()
.
tf_particulate_matter_get_sensor_info
(TF_ParticulateMatter *particulate_matter, uint8_t *ret_sensor_version, uint8_t *ret_last_error_code, uint8_t *ret_framing_error_count, uint8_t *ret_checksum_error_count)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns information about the sensor:
tf_particulate_matter_get_spitfp_error_count
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_set_status_led_config
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_get_status_led_config
(TF_ParticulateMatter *particulate_matter, uint8_t *ret_config)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the configuration as set by tf_particulate_matter_set_status_led_config()
The following constants are available for this function:
For ret_config:
tf_particulate_matter_get_chip_temperature
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_reset
(TF_ParticulateMatter *particulate_matter)¶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_particulate_matter_get_identity
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_set_pm_concentration_callback_configuration
(TF_ParticulateMatter *particulate_matter, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the PM Concentration
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.
tf_particulate_matter_get_pm_concentration_callback_configuration
(TF_ParticulateMatter *particulate_matter, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by
tf_particulate_matter_set_pm_concentration_callback_configuration()
.
tf_particulate_matter_set_pm_count_callback_configuration
(TF_ParticulateMatter *particulate_matter, uint32_t period, bool value_has_to_change)¶Parameters: |
|
---|---|
Returns: |
|
The period is the period with which the PM Count
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.
tf_particulate_matter_get_pm_count_callback_configuration
(TF_ParticulateMatter *particulate_matter, uint32_t *ret_period, bool *ret_value_has_to_change)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the callback configuration as set by
tf_particulate_matter_set_pm_count_callback_configuration()
.
Callbacks can be registered to receive time critical or recurring data from the
device. The registration is done with the corresponding tf_particulate_matter_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_particulate_matter_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_particulate_matter_register_pm_concentration_callback
(TF_ParticulateMatter *particulate_matter, TF_ParticulateMatter_PMConcentrationHandler handler, void *user_data)¶void handler(TF_ParticulateMatter *particulate_matter, uint16_t pm10, uint16_t pm25, uint16_t pm100, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
tf_particulate_matter_set_pm_concentration_callback_configuration()
.
The parameters are the same as tf_particulate_matter_get_pm_concentration()
.
tf_particulate_matter_register_pm_count_callback
(TF_ParticulateMatter *particulate_matter, TF_ParticulateMatter_PMCountHandler handler, void *user_data)¶void handler(TF_ParticulateMatter *particulate_matter, uint16_t greater03um, uint16_t greater05um, uint16_t greater10um, uint16_t greater25um, uint16_t greater50um, uint16_t greater100um, void *user_data)
Callback Parameters: |
|
---|
This callback is triggered periodically according to the configuration set by
tf_particulate_matter_set_pm_count_callback_configuration()
.
The parameters are the same as tf_particulate_matter_get_pm_count()
.
Virtual functions don't communicate with the device itself, but operate only on the API bindings device object.
tf_particulate_matter_get_response_expected
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_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_particulate_matter_set_response_expected
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_set_response_expected_all
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_set_bootloader_mode
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_get_bootloader_mode
(TF_ParticulateMatter *particulate_matter, uint8_t *ret_mode)¶Parameters: |
|
---|---|
Output Parameters: |
|
Returns: |
|
Returns the current bootloader mode, see tf_particulate_matter_set_bootloader_mode()
.
The following constants are available for this function:
For ret_mode:
tf_particulate_matter_set_write_firmware_pointer
(TF_ParticulateMatter *particulate_matter, uint32_t pointer)¶Parameters: |
|
---|---|
Returns: |
|
Sets the firmware pointer for tf_particulate_matter_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_particulate_matter_write_firmware
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_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_particulate_matter_write_uid
(TF_ParticulateMatter *particulate_matter, 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_particulate_matter_read_uid
(TF_ParticulateMatter *particulate_matter, 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_PARTICULATE_MATTER_DEVICE_IDENTIFIER
¶This constant is used to identify a Particulate Matter Bricklet.
The functions tf_particulate_matter_get_identity()
and tf_hal_get_device_info()
have a device_identifier
output parameter to specify
the Brick's or Bricklet's type.
TF_PARTICULATE_MATTER_DEVICE_DISPLAY_NAME
¶This constant represents the human readable name of a Particulate Matter Bricklet.