Monitor airflows in HVAC systems and ensure efficient ventilation and temperature control for enhanced comfort and energy savings
A
A
Hardware Overview
How does it work?
Air Velocity Click is based on the FS3000-1005, a high-performance surface-mount type air velocity module utilizing a MEMS thermopile-based sensor from Renesas. The FS3000-1005 measures the direct local air, which allows the system control to make adjustments quickly. It features a digital output with a 12-bit resolution with a wide operational range of 0-7.2 meters/second (0-16.2mph). By providing a closed-loop control, systems can reduce the energy cost of the system. The FS3000-1005 targets low-profile applications
and is designed to measure airflow around critical components such as analytic gas monitoring systems, data centers, and air quality systems to detect failures in the fan or blower, fan speed control, or filter clogging. The FS3000-1005 comprises a “solid” thermal isolation technology and silicon-carbide coating to protect it from abrasive wear and water condensation. This Click board™ communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting a Fast Mode
operation up to 400kHz. It continuously measures in operation, where the data is sent in byte packages. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive
mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI
GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
You complete me!
Accessories
Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for Air Velocity Click driver.
Key functions:
airvelocity_read_output
- This function reads the raw output counts by using I2C serial interfaceairvelocity_convert_counts_to_mps
- This function converts raw output counts to velocity in m/sec (0-7.23)
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief Air Velocity Click example
*
* # Description
* This example demonstrates the use of Air Velocity click board by reading
* and displaying the output counts and air velocity in m/sec.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Reads the output counts and converts it to air velocity in m/sec. Both values
* will be displayed on the USB UART approximately every 250ms.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "airvelocity.h"
static airvelocity_t airvelocity;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
airvelocity_cfg_t airvelocity_cfg; /**< Click config object. */
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
// Click initialization.
airvelocity_cfg_setup( &airvelocity_cfg );
AIRVELOCITY_MAP_MIKROBUS( airvelocity_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == airvelocity_init( &airvelocity, &airvelocity_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint16_t out_counts;
if ( AIRVELOCITY_OK == airvelocity_read_output ( &airvelocity, &out_counts ) )
{
log_printf ( &logger, " Out counts: %u\r\n", out_counts );
log_printf ( &logger, " Air velocity: %.2f m/s\r\n\n", airvelocity_convert_counts_to_mps ( out_counts ) );
Delay_ms ( 250 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END