Create a smarter way to switch power sources with TPS2120 and PIC32MZ2048EFM100
Switch smarter, stay powered: Redefine reliability with our multiplexer
Published Oct 09, 2023
Click board™
Power MUX 2 Click
Dev Board
Curiosity PIC32 MZ EF
Compiler
NECTO Studio
MCU
PIC32MZ2048EFM100
Experience the future of uninterrupted power with our multiplexer, where each transition is executed seamlessly, keeping your systems running smoothly and eliminating downtime
A
A
Hardware Overview
How does it work?
Power MUX 2 Click is based on the TPS2120, a highly configurable power mux with an automatic switchover feature from Texas Instruments. This dual-input single-output power multiplexer prioritizes the main supply of 12V when present and quickly switches to an auxiliary supply of 5 V when the main supply drops. A priority voltage supervisor is used to select an input source. During switchover, the voltage drop is controlled to block reverse current before it happens and provide uninterrupted power to the load with minimal hold-up capacitance. If one of the input power supplies fails, the system must automatically switch to a backup power source without interrupting regular operation. When the
12V supply on IN1 drops below 7.6V, the device automatically switches to the 5V auxiliary supply on IN2. When the 12V supply returns, it will become the output supply again. Furthermore, the voltage drop on the output should be minimal, providing the output with uninterrupted redundant power. The Power MUX 2 Click communicates with MCU through the 3-Wire SPI serial interface using the TPL0501, an onboard 256-tap digital potentiometer from Texas Instruments. This way, the TPL0501 serves as a current limiter that adjusts the output current of the TPS2120 instead of an external resistor. Current limiting can be used during Startup and switchover to protect against overcurrent events and protect the device
during regular operation. As an additional feature, this Click board™ also has two red LED indicators labeled IN1 and IN2, which visually indicate to the user the fact which one of the two power supplies, IN1 or IN2, is located on the output more precisely on the output connector of the Click board, labeled as OUT. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the VCC SEL jumper. This allowed both 3.3V and 5V capable MCUs to use the SPI 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
Curiosity PIC32 MZ EF development board is a fully integrated 32-bit development platform featuring the high-performance PIC32MZ EF Series (PIC32MZ2048EFM) that has a 2MB Flash, 512KB RAM, integrated FPU, Crypto accelerator, and excellent connectivity options. It includes an integrated programmer and debugger, requiring no additional hardware. Users can expand
functionality through MIKROE mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY daughter board, add WiFi connectivity capability using the Microchip expansions boards, and add audio input and output capability with Microchip audio daughter boards. These boards are fully integrated into PIC32’s powerful software framework, MPLAB Harmony,
which provides a flexible and modular interface to application development a rich set of inter-operable software stacks (TCP-IP, USB), and easy-to-use features. The Curiosity PIC32 MZ EF development board offers expansion capabilities making it an excellent choice for a rapid prototyping board in Connectivity, IOT, and general-purpose applications.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Curiosity PIC32 MZ EF as your development board.
Track your results in real time
Application Output
This Click board can be interfaced and monitored in two ways:
Application Output- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for Power MUX 2 Click driver.
Key functions:
powermux2_generic_write- Power MUX 2 data writing functionpowermux2_set_resistance- Power MUX 2 set resistance function
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 PowerMux2 Click example
*
* # Description
* This library contains API for the Power MUX 2 Click driver.
* The Power MUX 2 operates in automatic switchover mode with a priority prioritizing supply 1
* when present and quickly switches to supply 2 when supply 1 drops below approximately 6V.
*
* The demo application is composed of two sections :
*
* ## Application Init
* The application init consist of initialization of SPI driver and logger.
*
* ## Application Task
* This is an example that demonstrates the use of the Power MUX 2 Click board™.
* In this example, we set the resistance of the 100kΩ
* for the output current limit of approximately 1.23A
* and lower the resistance to 50kΩ, which fits the current limit of 2.25 A.
* Results are sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "powermux2.h"
static powermux2_t powermux2;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
powermux2_cfg_t powermux2_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.
powermux2_cfg_setup( &powermux2_cfg );
POWERMUX2_MAP_MIKROBUS( powermux2_cfg, MIKROBUS_1 );
err_t init_flag = powermux2_init( &powermux2, &powermux2_cfg );
if ( init_flag == SPI_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " Resistance ~ 100 kOhm \r\n" );
log_printf( &logger, " Current Limit ~ 1.23 A \r\n" );
powermux2_set_resistance( &powermux2, 100 );
Delay_ms( 5000 );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " Resistance ~ 50 kOhm \r\n" );
log_printf( &logger, " Current Limit ~ 2.25 A \r\n" );
powermux2_set_resistance( &powermux2, 50 );
Delay_ms( 5000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
