Monitor indoor air velocity with FS3000-1005 and MK64FN1M0VDC12 to improve indoor air quality
Feel the breeze of innovation
Published Aug 25, 2023
Click board™
Air Velocity Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
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
