We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.17
mikroSDK Library: 2.0.0.0
Category: Boost
Downloaded: 183 times
Not followed.
License: MIT license
Nano Power Click is a boost (step-up) DC-DC converter Click with extremely high efficiency and very low input voltage, aimed at the low power IoT market and battery-powered sensors and other devices.
Do you want to subscribe in order to receive notifications regarding "Nano Power Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "Nano Power Click" changes.
Do you want to report abuse regarding "Nano Power Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3623_nano_power_click.zip [433.82KB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for AVR mikroC AI for dsPIC XC16 |
|
Nano Power Click is a boost (step-up) DC-DC converter Click with extremely high efficiency and very low input voltage, aimed at the low power IoT market and battery-powered sensors and other devices.
We provide a library for the NanoPower 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.
This library contains API for NanoPower Click driver.
Config Object Initialization function.
void nanopower_cfg_setup ( nanopower_cfg_t *cfg );
Initialization function.
NANOPOWER_RETVAL nanopower_init ( nanopower_t ctx, nanopower_cfg_t cfg );
Click Default Configuration function.
void nanopower_default_cfg ( nanopower_t *ctx );
void nanopw_enable_device( nanopower_t *ctx, const uint8_t state )
This example enables the device.
The demo application is composed of two sections :
Initializes GPIO driver.
void application_init ( void )
{
log_cfg_t log_cfg;
nanopower_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 ----");
// Click initialization.
nanopower_cfg_setup( &cfg );
NANOPOWER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
nanopower_init( &nanopower, &cfg );
}
Turns device on for 5 seconds and than turns device off for 10 seconds,then the output voltage starts to fall.
void application_task ( void )
{
log_printf(&logger,"Device enabled\r\n");
nanopw_enable_device( &nanopower, NANOPW_ENABLE_DEVICE );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf(&logger,"Device disabled\r\n");
nanopw_enable_device( &nanopower, NANOPW_DISABLE_DEVICE );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
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:
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.