Gain insights into energy consumption patterns with PAC1720 and STM32F410RB
Energize your savings: DC power monitoring made simple
Published Oct 08, 2024
Click board™
PAC1720 Click
Dev Board
Nucleo 64 with STM32F410RB MCU
Compiler
NECTO Studio
MCU
STM32F410RB
Achieve your energy efficiency goals effortlessly with our DC energy monitor, tailored to meet your unique needs
A
A
Hardware Overview
How does it work?
PAC1720 Click is based on the PAC1720, a dual bidirectional high-side current-sensing device with precision voltage measurement capabilities from Microchip Technology. It measures the voltage developed across external sense resistors to represent the high-side current of a battery or voltage regulator, then digitizes it with a variable resolution Sigma-Delta ADC and transmits it over the I2C protocol. The PAC1720 also measures the SENSE+ pin voltages and calculates average power over the integration period. The PAC1720 has three states of operation: Active, Standby, and One-Shot Mode. In Active mode, the PAC1720 initiates conversion cycles for the programmed conversion rate. The Standby mode represents the lowest
power state, with no conversion cycles. Most circuitry is powered down to reduce supply current to a minimum. While the device is in the Standby state, the host can initiate a conversion cycle on-demand using One-Shot mode. After the conversion cycle is complete, the device will return to the Standby state. PAC1720 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting operation with a clock frequency up to 400kHz. Besides, it also allows the choice of its I2C slave address by positioning the SMD resistor of the appropriate value labeled as R2, allowing the user to select one of eight possible slave addresses. The current range allows for significant variations in
measured current with high accuracy and low voltage drop across the resistor. The PAC1720 has programmable high and low limits for current sense and bus voltage with a maskable alert signal labeled INT, routed to the RST pin of the mikroBUS™ socket to the host when an out-of-limit measurement occurs. 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 STM32F410RB 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-M4
MCU Memory (KB)
128
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
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32F410RB MCU as your development board.
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 PAC1720 Click driver.
Key functions:
pac1720_set_vsource_config- This function sets the Voltage Source configuration (sample time and average samples) for the selected channelpac1720_set_vsense_config- This function sets the Voltage Sense configuration (sample time, average samples, and sampling range) for the selected channelpac1720_get_measurements- This function reads voltage, current, and power from the selected channel
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 PAC1720 Click example
*
* # Description
* This example demonstrates the use of PAC1720 click board by reading the voltage,
* current, and power from both available channels.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Reads the voltage, current, and power from both channels and displays
* the results on the USB UART approximately once per second.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "pac1720.h"
static pac1720_t pac1720;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
pac1720_cfg_t pac1720_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.
pac1720_cfg_setup( &pac1720_cfg );
PAC1720_MAP_MIKROBUS( pac1720_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == pac1720_init( &pac1720, &pac1720_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( PAC1720_ERROR == pac1720_default_cfg ( &pac1720 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float voltage = 0, current = 0, power = 0;
if ( PAC1720_OK == pac1720_get_measurements ( &pac1720, PAC1720_CHANNEL_1, &voltage, ¤t, &power ) )
{
log_printf( &logger, " Channel 1:\r\n" );
log_printf( &logger, " U: %.3fV, I: %.3fA, P: %.3fW\r\n", voltage, current, power );
}
if ( PAC1720_OK == pac1720_get_measurements ( &pac1720, PAC1720_CHANNEL_2, &voltage, ¤t, &power ) )
{
log_printf( &logger, " Channel 2:\r\n" );
log_printf( &logger, " U: %.3fV, I: %.3fA, P: %.3fW\r\n\n", voltage, current, power );
}
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
