Add a boost converter to your solution today and enjoy seamless power management
A
A
Hardware Overview
How does it work?
Boost 3 Click is based on the TPS61391, a 700-kHz pulse-width modulating (PWM) Step-Up converter with a 70V switch FET from Texas Instruments. It supports an input voltage of up to 5.5V and operates at a 700 kHz pulse-width modulation (PWM), crossing the whole load range. There are two ratio options for the current proportional to the APD current: MON1 (4:5) and MON2 (1:5). By connecting an additional RC filter for low ripple applications from the mirror output pins to the GND, the current flowing through the APD is converted into the voltage crossing the resistor from MON1/MON2 pins to GND. Additionally, high-power optical protection, with a response time typically of 0.5 μs, is integrated by clamping the pre-set current limit (programmed by the R6 resistor) and could recover automatically when the high optical power is removed. The output voltage of the TPS61391 is externally adjustable using a resistor divider network. The equation gives the relationship between the output voltage and the resistor divider: VOUT = ( VREF + 0.1V ) * ( 1 + ( VR1 + R8 ) / R9 ) [V], where VREF has a typical
value of 1.2V.When the potentiometer has a 0V value, the output voltage has its minimum value of 20V. Increasing the resistance of a potentiometer and reaching its maximum value of 500kΩ, the output voltage reaches its maximum value of 70V. The potentiometer featured on the Boost 3 Click can change the feedback, thus influencing a change in the output voltage. This feature makes the Click board™ extremely practical because you can get a wide voltage range with a simple potentiometer turn. Boost 3 Click communicates with MCU using only one GPIO pin routed on the CS pin of the mikroBUS™ socket labeled as EN. An under-voltage lockout (UVLO) circuit stops the operation of the converter when the input voltage drops below the typical UVLO threshold of 2.5 V. When the input voltage is above the maximal UVLO rising threshold of 2.5 V, and the EN pin is pulled above the high threshold (1.2V minimum), the TPS61391 is enabled. When the EN pin is pulled below the low threshold (0.4 maximum), the device goes into Shutdown Mode.
It also possesses the output terminal labeled APD used for biasing and monitoring the avalanche photodiodes (APD) and high optical power protection. This line has an additional FET in a series of power-path connecting with the APD output terminal. When the current flowing through the external APD exceeds the short protection threshold, set by connecting the resistor from R6 to the ground, the on-resistance of the internal FET becomes larger to clamp the current within the protection threshold by lowering the APD bias voltage. It typically takes 0.5μs for the FET to respond in case of high optical power occurring. When the high optical power condition is released, the TPS61391 recovers automatically back to Normal Operation Mode. 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. However, the 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
Fusion for PIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different PIC, dsPIC, PIC24, and PIC32 MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for PIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the Fusion for PIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB
HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet are also included, including the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options (graphical and character-based LCD). Fusion for PIC v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
![default](https://cdn.mikroe.com/rent-a-product/request-setup/mcu-cards/mcu-card-11-for-pic-pic18f57q43.png)
Type
8th Generation
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Boost 3 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790b4-09f3-6648-8a08-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for Boost 3 Click driver.
Key functions:
void boost3_dev_enable ( uint8_t state );
- Function is used to enable or disable the device.
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
* \brief Boost 3 Click example
*
* # Description
* Boost 3 click provides an adjustable output voltage through the onboard
* potentiometer. The chip is a 700-kHz pulse-width modulating (PWM) step-up
* converter with an 85-V switch FET with an input ranging from 2.5 V to 5.5 V.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes GPIO and LOG structures, and set CS pin as output.
*
* ## Application Task
* Turns ON the device for 10 seconds and then turns it OFF for 3 seconds.
* It also displays appropriate messages on the USB UART.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "boost3.h"
// ------------------------------------------------------------------ VARIABLES
static boost3_t boost3;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
boost3_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.
boost3_cfg_setup( &cfg );
BOOST3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
boost3_init( &boost3, &cfg );
}
void application_task ( void )
{
boost3_dev_enable( &boost3, BOOST3_ENABLE );
log_printf( &logger, "The click board is enabled!\r\n" );
log_printf( &logger, "Please use the on-board potentiometer" );
log_printf( &logger, " to adjust the voltage output.\r\n" );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms ( 10000 );
boost3_dev_enable( &boost3, BOOST3_DISABLE );
log_printf( &logger, "The click board is turned OFF!\r\n" );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms ( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END