Achieve continuous insights into current fluctuations using ACHS-7194 and TM4C129LNCZAD
Amp Up Accuracy
Published 8月 12, 2023
Click board™
Hall Current 10 Click
Dev Board
UNI-DS v8
Compiler
NECTO Studio
MCU
TM4C129LNCZAD
Maximize the lifespan of your equipment by utilizing our Hall-effect current sensing solution, which assists in identifying overload conditions and preventing potential damage
A
A
Hardware Overview
How does it work?
Hall Current 10 Click is based on the ACHS-7194, a Hall-effect current sensor from Broadcom Limited that sends an analog voltage proportional to the magnetic field intensity caused by the current flowing through the primary input conductor. Without a magnetic field, the output voltage is half of the supply voltage. The ACHS-7194 can detect both DC and AC, designed for the current range of ±40A. Device accuracy is optimized across the operating ambient temperature through the close proximity of the magnetic signal to the Hall sensors. The copper conductor's thickness allows the device's survival at high overcurrent conditions. The terminals of the conductive path are electrically
isolated from the signal leads. This feature enables the ACHS-7194 to be used in applications requiring electrical isolation without optoisolators or other costly isolation techniques. The ACHS-7194 also has a ratiometric output, which changes proportionally to the supply voltage. Just like that, the output voltage, analog signal, can be converted to a digital value using MCP3221, a successive approximation A/D converter with a 12-bit resolution from Microchip, using a 2-wire I2C compatible interface, or can be sent directly to an analog pin of the mikroBUS™ socket labeled as AN. Selection can be performed by onboard SMD jumper labeled ADC SEL to an appropriate position
marked as AN and I2C. With the MCP3221, data transfers at rates of up to 100kbit/s in the Standard and 400kbit/s in the Fast Mode. Also, maximum sample rates of 22.3kSPS with the MCP3221 are possible in a Continuous-Conversion Mode with a clock rate of 400kHz. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VIO 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
UNI-DS 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 STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR 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, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it 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 is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
212
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.
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.
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.
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".
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.
Software Support
Library Description
This library contains API for Hall Current 10 Click driver.
Key functions:
hallcurrent10_read_adc- Hall Current 10 I2C ADC reading functionhallcurrent10_get_adc_volatge- Hall Current 10 get ADC voltage functionhallcurrent10_get_current- Hall Current 10 get current function
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 main.c
* @brief HallCurrent10 Click example
*
* # Description
* This library contains API for Hall Current 10 Click driver.
* The demo application reads ADC value, ADC voltage and current value.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes I2C driver and log UART.
* After driver initialization the app set default settings.
*
* ## Application Task
* This is an example that demonstrates the use of the Hall Current 10 Click board™.
* In this example, we read and display the ADC values and current ( mA ) data.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "hallcurrent10.h"
static hallcurrent10_t hallcurrent10;
static log_t logger;
static uint16_t adc_data;
static float current;
static float adc_voltage;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
hallcurrent10_cfg_t hallcurrent10_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.
hallcurrent10_cfg_setup( &hallcurrent10_cfg );
HALLCURRENT10_MAP_MIKROBUS( hallcurrent10_cfg, MIKROBUS_1 );
err_t init_flag = hallcurrent10_init( &hallcurrent10, &hallcurrent10_cfg );
if ( I2C_MASTER_ERROR == init_flag )
{
log_info( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
hallcurrent10_default_cfg ( &hallcurrent10 );
log_info( &logger, " Application Task " );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 100 );
}
void application_task ( void )
{
hallcurrent10_read_adc( &hallcurrent10, &adc_data );
log_printf( &logger, " ADC Value : %d \r\n", adc_data );
Delay_ms( 100 );
hallcurrent10_get_adc_volatge( &hallcurrent10, &adc_voltage );
log_printf( &logger, " ADC Voltage : %.2f mV \r\n", adc_voltage );
log_printf( &logger, "- - - - - - - - - - - - -\r\n" );
Delay_ms( 100 );
hallcurrent10_get_current ( &hallcurrent10, ¤t );
log_printf( &logger, " Current : %.2f mA \r\n", current );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
