Gain a clear view of AC or DC current profiles using TMCS1108A2U and STM32F407ZG
Efficiency amplified through advanced current sensing
Published Aug 12, 2023
Click board™
Hall Current 11 Click
Dev Board
Fusion for STM32 v8
Compiler
NECTO Studio
MCU
STM32F407ZG
Elevate your engineering projects with our Hall-effect current sensing solution, delivering accurate and actionable current data for effective system design, optimization, and maintenance
A
A
Hardware Overview
How does it work?
Hall Current 11 Click is based on the TMCS1108A2U, a precision Hall-effect current sensor featuring a 100V functional isolation working voltage, <3% full-scale error across temperature, and both unidirectional and bidirectional current sensing from Texas Instruments. The input current flows through a 1.8mΩ resistance conductor between the isolated input current pins, minimizing power loss and thermal dissipation. The magnetic field generated by the input current is sensed by a Hall sensor and amplified by a precision integrated signal chain. The TMCS1108A2U can be used for both AC and DC current measurements with a bandwidth of 80kHz. The TMCS1108A2U is optimized for high accuracy and temperature stability, with both offset and sensitivity compensated across the entire operating
temperature range. Based on the selected logic voltage VCC, the TMCS1108A2U allows the user to measure current in two appropriate ranges, where after that, can process the output signal in analog or digital form. With the selected logic voltage of 3.3V, it is possible to measure the current from -2.8A to 27.7A, while with the chosen 5V, it is possible to measure it in the range from -4.5A to 43A. The analog output signal of the TMCS1108A2U 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.
The MCP3221 provides one single-ended input with low power consumption, a low maximum conversion current, and a Standby current of 250μA and 1μA, respectively. Data can be transferred at 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 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
Fusion for STM32 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 32-bit ARM® Cortex®-M based MCUs from STMicroelectronics, 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 STM32 v8 provides a fluid and immersive working experience, allowing
access anywhere and under any circumstances at any time. Each part of the Fusion for STM32 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. Fusion for STM32 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
STMicroelectronics
Pin count
144
RAM (Bytes)
196608
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 Fusion for STM32 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 11 Click driver.
Key functions:
hallcurrent11_get_adc- Hall Current 11 ADC reading functionhallcurrent11_get_adc_voltage- Hall Current 11 get ADC voltage functionhallcurrent11_get_current- Hall Current 11 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 HallCurrent11 Click example
*
* # Description
* This library contains API for Hall Current 11 Click driver.
* The demo application reads ADC value and current ( A ).
*
* 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 11 Click board™.
* In this example, we read and display the ADC values and current ( A ) 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 "hallcurrent11.h"
static hallcurrent11_t hallcurrent11;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
hallcurrent11_cfg_t hallcurrent11_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.
hallcurrent11_cfg_setup( &hallcurrent11_cfg );
HALLCURRENT11_MAP_MIKROBUS( hallcurrent11_cfg, MIKROBUS_1 );
err_t init_flag = hallcurrent11_init( &hallcurrent11, &hallcurrent11_cfg );
if ( I2C_MASTER_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
hallcurrent11_default_cfg ( &hallcurrent11 );
log_info( &logger, " Application Task " );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 100 );
}
void application_task ( void )
{
static uint16_t adc_data;
static float current;
hallcurrent11_get_adc( &hallcurrent11, &adc_data );
log_printf( &logger, " ADC Value : %d \r\n", adc_data );
log_printf( &logger, "- - - - - - - - - - - - -\r\n" );
Delay_ms( 100 );
hallcurrent11_get_current ( &hallcurrent11, ¤t );
log_printf( &logger, " Current : %.3f A \r\n", current );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
