Ensure your devices perform at their peak with NIS6150 and ATmega1284
eFuse: Unlock reliability, enhance efficiency
Published Jul 09, 2024
Click board™
eFuse 3 Click
Dev. board
EasyAVR v8
Compiler
NECTO Studio
MCU
ATmega1284
Experience enhanced reliability and efficiency with our cutting-edge eFuse device, where voltage and current are managed effortlessly to safeguard your devices and elevate their performance
A
A
Hardware Overview
How does it work?
eFuse 3 Click is based on the NIS6150, a self-protected, resettable electronic fuse from ON Semiconductor that contains circuits to monitor the input voltage, output voltage, output current, and die temperature. It has an ENABLE feature with a separate ‘flag’ for fault identification, adjustable output current-limit protection with a thermal shutdown, and a current monitoring pin. The NIS6150 also includes an internal temperature sensing circuit that senses the temperature on the die of the power FET. If the temperature reaches 175°C, the device will shut down and remove power from the load. This Click board™ communicates with MCU through the 3-Wire SPI serial interface using the MCP3551, a 22-bit sigma-delta ADC from Microchip. The MCP3551 is used for current monitoring purposes by converting the output current from the NIS6150 IMON pin with a very high resolution of 22 bits and low noise to digital data, which can be obtained via the SPI interface of the Click board™. This ADC uses the
reference voltage, the 4.096V reference voltage level provided by the MCP1541 from Microchip powered from the +5V mikroBUS™ power rail, resulting in high accuracy and stability. A resistor that connects to the middle connector on this Click board™, labeled as Rlim, sets the overload and short circuit current limit levels. The VSL pin routed to the RST pin on the mikroBUS™ socket allows the overvoltage clamp to be set at a 5.7V or 6.5V minimum by pulling this pin to a low logic state. It monitors the output voltage, and if the input exceeds the output voltage, the gate drive of the main FET is reduced to limit the output. This is intended to allow operation through transients while protecting the load. If an overvoltage condition exists for many seconds, the device may overheat due to the voltage drop across the FET combined with the load current. In this event, the thermal protection circuit would shut down the device. The eFuse 3 Click also has two active additional pins of the mikroBUS™ socket, the INT
and PWM pins labeled as FLG and EN. The Enable feature, routed to the PWM pin on the mikroBUS™ socket, provides a digital interface to control the output of the eFuse. That’s why when this pin is pulled to a low logic state - the eFuse is turned OFF. On the other hand, the ‘flag’ pin routed to the INT pin on the mikroBUS™ socket sends information to the MCU regarding the state of the chip. If a thermal fault occurs, the voltage on this pin will go to a low state to signal a monitoring circuit that the device is in thermal shutdown. 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. 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
EasyAVR v8 is a development board designed to rapidly develop embedded applications based on 8-bit AVR microcontrollers (MCUs). Redesigned from the ground up, EasyAVR v8 offers a familiar set of standard features, as well as some new and unique features standard for the 8th generation of development boards: programming and debugging over the WiFi network, connectivity provided by USB-C connectors, support for a wide range of different MCUs, and more. The development board is designed so that the developer has everything that might be needed for the application development, following the Swiss Army knife concept: a highly advanced programmer/debugger module, a reliable power supply module, and a USB-UART connectivity option. EasyAVR v8 board offers several different DIP sockets, covering a wide range of 8-bit AVR MCUs, from the smallest
AVR MCU devices with only eight pins, all the way up to 40-pin "giants". The development board supports the well-established mikroBUS™ connectivity standard, offering five mikroBUS™ sockets, allowing access to a huge base of Click boards™. EasyAVR v8 offers two display options, allowing even the basic 8-bit AVR MCU devices to utilize them and display graphical or textual content. One of them is the 1x20 graphical display connector, compatible with the familiar Graphical Liquid Crystal Display (GLCD) based on the KS108 (or compatible) display driver, and EasyTFT board that contains TFT Color Display MI0283QT-9A, which is driven by ILI9341 display controller, capable of showing advanced graphical content. The other option is the 2x16 character LCD module, a four-bit display module with an embedded character-based display controller. It
requires minimal processing power from the host MCU for its operation. There is a wide range of useful interactive options at the disposal: high-quality buttons with selectable press levels, LEDs, pull-up/pulldown DIP switches, and more. All these features are packed on a single development board, which uses innovative manufacturing technologies, delivering a fluid and immersive working experience. The EasyAVR v8 development board is also integral to the MIKROE rapid development ecosystem. Natively supported by the MIKROE Software toolchain, backed up by hundreds of different Click board™ designs with their number growing daily, it covers many different prototyping and development aspects, thus saving precious development time.
Microcontroller Overview
MCU Card / MCU
Architecture
AVR
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
16384
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 EasyAVR v8 as your development board.
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 eFuse 3 Click driver.
Key functions:
efuse3_get_current- eFuse 3 get current functionefuse3_get_flag- eFuse 3 get flag functionefuse3_reset- eFuse 3 reset 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 eFuse3 Click example
*
* # Description
* This library contains API for the eFuse 3 Click driver.
* The library contains drivers to enable/disable the device,
* for reading ADC voltage, overflow status, output and current value [ A ].
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI driver and set default configuration.
*
* ## Application Task
* This is an example that demonstrates the use of the eFuse 3 Click board.
* Read and display device status information and current value [ A ].
* The eFuse 3 includes an overvoltage clamp the circuit that limits the output voltage
* during transients but does not shut the unit down,
* thereby allowing the load circuit to continue its operation.
* The Electronic Fuse is to limit current and current limit
* Current limit ( 0.1 A - 1.8 A ) depends on the choice of resistor wired
* on the Rlimit ( 1 Ohm - 15 Ohm ) connector.
* For example, for Rlimit resistance of 1 Ohm, current limit is 1 A
* ( 3.5 Ohm - 0.5 A, 7 Ohm - 0.25 A ).
* Read details from the ON Semiconductor NIS6150 datasheets.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "efuse3.h"
static efuse3_t efuse3;
static log_t logger;
static float voltage;
static float current;
static uint8_t overflow_status;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
efuse3_cfg_t efuse3_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.
efuse3_cfg_setup( &efuse3_cfg );
EFUSE3_MAP_MIKROBUS( efuse3_cfg, MIKROBUS_1 );
err_t init_flag = efuse3_init( &efuse3, &efuse3_cfg );
if ( init_flag == SPI_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
efuse3_default_cfg ( &efuse3 );
log_info( &logger, " Application Task " );
log_printf( &logger, "---------------------------\r\n" );
Delay_ms ( 100 );
}
void application_task ( void ) {
log_printf( &logger, " Status :" );
if ( efuse3_get_flag( &efuse3 ) == EFUSE3_FLAG_NORMAL_OPERATION ) {
log_printf( &logger, " Normal operation \r\n" );
} else {
log_printf( &logger, " Device OFF \r\n" );
if ( overflow_status == EFUSE3_OVERFLOW_HIGH ) {
log_printf( &logger, " Overflow high in the analog input voltage.\r\n" );
} else if ( overflow_status == EFUSE3_OVERFLOW_LOW ) {
log_printf( &logger, " Overflow low in the analog input voltage.\r\n" );
}
efuse3_reset( &efuse3 );
Delay_ms ( 1000 );
}
log_printf( &logger, "- - - - - - - - - - - - - - \r\n" );
efuse3_get_current( &efuse3, ¤t );
log_printf( &logger, " Current : %.5f A\r\n", current );
log_printf( &logger, "---------------------------\r\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
