Accurately monitor and control indoor climate conditions using BME280 and MK64FN1M0VDC12
Tri-Meteo Nexus
Published Aug 24, 2023
Click board™
Weather Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Enhance weather forecasting and environmental research with our integrated sensor solution, providing valuable data for meteorologists and scientists to analyze climate patterns and trends
A
A
Hardware Overview
How does it work?
Weather Click is based on the BME280, a combined humidity and pressure sensor from Bosch Sensortec. The BME280 itself contains sensors from each of the environmental measurements. The humidity sensor has high overall accuracy and an extremely fast response time. The pressure sensor has extremely high accuracy and resolution as an absolute barometric sensor. The temperature sensor is basically used for temperature compensation, thus for accurate readings. Nevertheless, it has low noise and high resolution and can be used for ambient temperature readings. The Weather Click can work in one of three power modes. Sleep mode is the first mode the sensor enters after the Power-On reset, when no measurements are performed with
its power consumption at the minimum. In Forced mode, the sensor performs a single measurement and returns to Sleep mode. For the next measurement, the Forced mode must be selected again. The Normal mode means the sensor will take measurements in automated perpetual cycling between measurement and inactive periods. The sensors inside the BME280 have different output resolutions, with 16-bit ADC for humidity and up to 20-bit for pressure readings. An internal IIR filter helps suppress the disturbance of many shorter changes, such as a wind blowing into the sensor, slamming a door, and such. To achieve a high resolution and low noise of readings, the IIR filter must be enabled. Weather Click can use a standard 2-Wire I2C
interface supporting standard, fast, and high speeds or an SPI serial interface to communicate with the host MCU. The communication interface can be selected via SPI I2C 4-jumper sets, with the I2C interface selected by default. All four jumpers must be in place for the Weather Click to work properly. The I2C address can be selected via the ADDR jumper, with 0 set by default. 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
Click board™ 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
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Weather Click driver.
Key functions:
weather_get_ambient_data- Use this function to read the temperature, pressure and humidity dataweather_get_device_id- You can use this function as a check on click communication with your MCUweather_measurement_cfg- Use this function to set up new settings
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file
* @brief Weather Click example
*
* # Description
* This demo-app shows the temperature, pressure and humidity measurement using Weather Click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Configuring Clicks and log objects.
* Setting the Click in the default configuration to start the measurement.
*
* ## Application Task
* Reads Temperature data, Relative Humidity data and Pressure data,
* and displays them on USB UART every 1500ms.
*
* @author MikroE Team
*
*/
#include "board.h"
#include "log.h"
#include "weather.h"
static weather_t weather;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg;
weather_cfg_t weather_cfg;
/**
* 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.
weather_cfg_setup( &weather_cfg );
WEATHER_MAP_MIKROBUS( weather_cfg, MIKROBUS_1 );
if ( WEATHER_OK != weather_init( &weather, &weather_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( WEATHER_OK != weather_default_cfg ( &weather ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
weather_data_t weather_data;
if ( WEATHER_OK == weather_get_ambient_data( &weather, &weather_data ) )
{
log_printf( &logger, " \r\n ---- Weather data ----- \r\n" );
log_printf( &logger, "[PRESSURE]: %.2f mBar.\n\r", weather_data.pressure );
log_printf( &logger, "[TEMPERATURE]: %.2f C.\n\r", weather_data.temperature );
log_printf( &logger, "[HUMIDITY]: %.2f %%.\n\r", weather_data.humidity );
Delay_ms ( 1000 );
Delay_ms ( 500 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
