Our solution is designed to accurately measure voltage and current through your connected load, providing critical insights into electrical performance
A
A
Hardware Overview
How does it work?
PWR Meter 3 Click is based on the ACS37800, a simple solution for voltage, current, and power monitoring from Allegro MicroSystems, which simplifies the addition of power monitoring in 60Hz to many AC/DC applications. The ACS37800 includes a copper conduction path that generates a magnetic field proportional to the applied current, sensed differentially to reject errors introduced by common mode fields. It is particularly well suited for high isolation, achieving reinforced isolation ratings of 4800 VRMS and a reliable ±90A bidirectional current sensing range. With high configurability and integrated features, this Click board™ can fit most power monitoring applications. The ACS37800 measures the voltage applied to the REF terminal, in the range from 9.5 to 27V, by resistor dividing it down to fit the input range of the onboard voltage sense amplifier and
add isolation. On the other hand, the current applied to the current sensing terminals is measured using the integrated current loop and galvanically isolated Hall sensor. Both analog signals are then sampled using integrated high-accuracy ADCs before entering the digital system. The metrology engine later determines the frequency, calculates RMS values of current, voltage, and power, and provides a range of averaging and configuration options. PWR Meter 3 Click communicates with an MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting Standard Mode operation with a clock frequency of 100kHz and Fast Mode up to 400kHz. The ACS37800 can be turned on, or off through the EN pin routed to the RST pin of the mikroBUS™ socket, hence offering a switch operation to turn ON/OFF power delivery
to the ACS37800 via TPS2041B. Along with the ability to measure current and voltage, it also has two LED indicators, DIO0 and DIO1, for the realization of visual detection of some anomalies in operation, such as undervoltage and overvoltage reporting, and fast overcurrent fault detection. The DIO0 LED default state application is for zero crossing, while DIO1 stands for overcurrent detection. In addition to the LEDs, this information can be detected through the INT and AN pins of the mikroBUS™ socket, marked as D0 and D1. 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
Click board™ Schematic

Step by step
Project assembly
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 PWR Meter 3 Click driver.
Key functions:
pwrmeter3_get_dio0_pin
- This function returns the DIO0 pin logic statepwrmeter3_get_dio1_pin
- This function returns the DIO1 pin logic statepwrmeter3_read_average_rms
- This function reads the voltage and current RMS measurements averaged from a specified number of samples
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 main.c
* @brief PWR Meter 3 Click example
*
* # Description
* This example demonstrates the use of PWR Meter 3 click board by reading and displaying
* the voltage, current, and power RMS measurements.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration which sets the DC measurement
* and VRMS thresholds to about 28V for overvoltage and about 9.3V for undervoltage flag.
*
* ## Application Task
* Reads the voltage and current RMS values averaged from 500 samples, then calculates the power from it
* and displays the results on the USB UART. Also if an UV or OV flag is detected it will be logged accordingly.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "pwrmeter3.h"
static pwrmeter3_t pwrmeter3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
pwrmeter3_cfg_t pwrmeter3_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.
pwrmeter3_cfg_setup( &pwrmeter3_cfg );
PWRMETER3_MAP_MIKROBUS( pwrmeter3_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == pwrmeter3_init( &pwrmeter3, &pwrmeter3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( PWRMETER3_ERROR == pwrmeter3_default_cfg ( &pwrmeter3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float v_rms, i_rms;
if ( PWRMETER3_OK == pwrmeter3_read_average_rms ( &pwrmeter3, &v_rms, &i_rms, PWRMETER3_DEF_AVG_SAMPLES ) )
{
if ( !pwrmeter3_get_dio0_pin ( &pwrmeter3 ) )
{
log_printf ( &logger, " Over-voltage detected!\r\n" );
}
if ( !pwrmeter3_get_dio1_pin ( &pwrmeter3 ) )
{
log_printf ( &logger, " Under-voltage detected!\r\n" );
}
log_printf ( &logger, " Voltage: %.2f V\r\n", v_rms );
log_printf ( &logger, " Current: %.2f A\r\n", i_rms );
log_printf ( &logger, " Power: %.2f W\r\n\n", i_rms * v_rms );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:Measurements