Optimize efficiency through digital VCP monitoring based on the INA260 and STM32F091RC
Your digital guide to current and power excellence!
Published Feb 26, 2024
Click board™
VCP Monitor Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
From real-time diagnostics to performance optimization, the possibilities are endless
A
A
Hardware Overview
How does it work?
VCP Monitor Click is based on the INA260, a power monitor solution from Texas Instruments, which includes precision measurement of current, voltage, and power with low drift. The current-sensing resistor is designed as a 4-wire connected resistor that enables accurate measurements through a force-sense connection. The INA260 is internally calibrated to ensure the current-sensing resistor and amplifier are precisely matched. The INA260 device performs two measurements on the power supply bus. The current measurement on the LOAD connector is internally calculated by measuring the voltage developed across a known internal shunt resistor. The feature is a physical shunt resistance that can withstand current levels higher than the continuous handling limit of 15A without sustaining damage to the current-sensing resistor or the current-sensing amplifier if the excursions are brief. The voltage measurement on
the SUPPLY connector is calculated by measuring the voltage from the external VBUS pin to the ground. The voltage monitored ranges from 0V to 36V. The INA260 device performs two measurements on the power supply bus. The current measurement on the LOAD connector is internally calculated by measuring the voltage developed across a known internal shunt resistor, and the voltage measurement on the SUPPLY connector is calculated by measuring the voltage from the external VBUS pin to the ground. The VCP Monitor click is compatible with the I2C communication protocol. The INA260 has two slave address selection pins, A0 and A1. For I2C slave address selection, the VCP Monitor click has two cross-shape jumpers, first for set pin A0 and second for set A1 pin. One cross-shape jumper has four positions for the select address pins, which can be selected with an SMD 0 ohm resistor; the
address pin can be connected to GND, VS, SCL, or SDA pins. The VCP Monitor Clicks with the two separate jumpers on the Click board™ user can set the desired address. The INA260AIPWR provides the opportunity of the 16 possible different I2C addresses. The INA260AIPWR is supported with an ALERT pin connected to the INT pin on mikroBUS™ to interrupt the ongoing MCU routine in case of the alert condition. INT pin can be programmed to respond to a user-defined event or a conversion-ready notification. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 Nucleo-64 with STM32F091RC MCU 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 VCP Monitor Click driver.
Key functions:
vcpmonitor_get_current- This function reads current data in mAvcpmonitor_get_power- This function reads power data in mWvcpmonitor_get_voltage- This function reads voltage data in mV.
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 VCPmonitor Click example
*
* # Description
* The VCP Monitor Click is add-on board power monitor system. This Click board is
* based on precision digital current and power monitor with low-drift, integrated
* precision shunt resistor.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initiaizes the driver, and checks the communication by reading the device and manufacture IDs.
* After that, performs the device default configuration.
*
* ## Application Task
* Displays the voltage, current, and power measured by the sensor on the USB UART every 2 seconds.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "vcpmonitor.h"
// ------------------------------------------------------------------ VARIABLES
static vcpmonitor_t vcpmonitor;
static log_t logger;
static uint16_t manufacture_id;
static uint16_t did_id;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
vcpmonitor_cfg_t 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 ----" );
vcpmonitor_cfg_setup( &cfg );
VCPMONITOR_MAP_MIKROBUS( cfg, MIKROBUS_1 );
vcpmonitor_init( &vcpmonitor, &cfg );
if ( VCPMONITOR_OK == vcpmonitor_get_id_value( &vcpmonitor, &manufacture_id, &did_id ) )
{
log_printf( &logger, ">> Manufacture ID: 0x%.4X\r\n", manufacture_id );
log_printf( &logger, ">> Device ID: 0x%.4X\r\n", did_id );
}
else
{
log_error( &logger, " WRONG ID READ! " );
log_printf( &logger, "Please restart your system.\r\n" );
for ( ; ; );
}
vcpmonitor_default_cfg(&vcpmonitor );
Delay_ms( 500 );
}
void application_task ( void )
{
float current_data;
float voltage_data;
float power_data;
current_data = vcpmonitor_get_current( &vcpmonitor );
log_printf( &logger, ">> Current : %.2f mA\r\n", current_data );
voltage_data = vcpmonitor_get_voltage( &vcpmonitor );
log_printf( &logger, ">> Voltage : %.2f mV\r\n", voltage_data );
power_data = vcpmonitor_get_power( &vcpmonitor );
log_printf( &logger, ">> Power : %.2f mW\r\n", power_data );
log_printf( &logger, "-------------------------------\r\n" );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
