VCP Monitor Click

The VCP Monitor Click is add-on board power monitor system. This Click board™ is based on INA260AIPWR - precision digital current and power monitor with low-drift, integrated precision shunt resistor, from Texas Instruments. Therefore, using VCP Monitor Click, current, voltage and power can be monitored.

Click Product page

Click library

• Author : MikroE Team
• Date : Feb 2020.
• Type : I2C type

Software Support

We provide a library for the VCPmonitor Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for VCPmonitor Click driver.

Standard key functions :

• Config Object Initialization function.

  void vcpmonitor_cfg_setup ( vcpmonitor_cfg_t *cfg );

• Initialization function.

  VCPMONITOR_RETVAL vcpmonitor_init ( vcpmonitor_t ctx, vcpmonitor_cfg_t cfg );

• Click Default Configuration function.

  void vcpmonitor_default_cfg ( vcpmonitor_t *ctx );

Example key functions :

• This function reads current data in mA.

  float vcpmonitor_get_current ( vcpmonitor_t *ctx );

• This function reads power data in mW.

  float vcpmonitor_get_power ( vcpmonitor_t *ctx );

• This function reads voltage data in mV.

  float vcpmonitor_get_voltage ( vcpmonitor_t *ctx );

Examples 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.

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 );
}

Application Task

Displays the voltage, current, and power measured by the sensor on the USB UART every 2 seconds.

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 ( 1000 );
    Delay_ms ( 1000 );
} 

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

• MikroSDK.Board
• MikroSDK.Log
• Click.VCPmonitor

Additional notes and informations

Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.