Integrate sensorless BLDC motor driver into your designs easily with STM32F091RC
Say goodbye to tangled wires
Published Feb 26, 2024
Click board™
Brushless 21 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
The perfect choice for enhancing the performance of home appliances such as fans and pumps, offering flexibility and versatility to optimize their operation
A
A
Hardware Overview
How does it work?
Brushless 21 Click is based on the AMT49400, a three-phase BLDC controller with integrated MOSFETs from Allegro Microsystems. The integrated field-oriented control (FOC) algorithm achieves the best efficiency and dynamic response and minimizes acoustic noise. Also, Allegro's proprietary non-reverse startup algorithm improves startup performance. The BLDC motor, connected to the terminals labeled U, V, and W, will start towards the target direction after power-up without reverse shaking or vibration. The Soft-On Soft-Off (SOSO) feature gradually increases the current to the motor at the ON command (windmill condition). It gradually reduces the current from the motor at the OFF command, further reducing the acoustic noise and operating the motor smoothly. This Click board™ allows interface selection to communicate with MCU. The selection between PWM and I2C interface can be
made by positioning SMD jumpers labeled as COMM SEL in an appropriate position. Note that all the jumpers' positions must be on the same side, or the Click board™ may become unresponsive. While the I2C interface is selected, setting motor-rated voltage, rated current, rated speed, resistance, and startup profiles are allowed via the EEPROM programmability. On the other side, the motor speed is controlled by applying a duty cycle command to the PWM input pin of the AMT49400. Alongside the PWM pin from the mikroBUS™ socket, this Click board™ also has the Enable pin labeled as EN and routed to the CS pin of the mikroBUS™ socket to optimize power consumption used for power ON/OFF purposes. The FG pin routed on the default INT pin of the mikroBUS™ socket provides motor speed information to the system, such as motor lock detection.
This feature monitors the motor position to determine if the motor is running as expected. If a lock condition is detected, the motor drive will be disabled for 5 seconds before an attempted auto-restart. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VIO SEL jumper. It allows both 3.3V and 5V capable MCUs to use the communication lines properly. Additionally, there is a possibility for the AMT49400 power supply selection via jumper labeled as VBB SEL to supply the AMT49400 from an external power supply terminal in the range from 4V to 16V or with 5V from mikroBUS™ power rail. 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
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
2207V-2500kV BLDC Motor is an outrunner brushless DC motor with a kV rating of 2500 and an M5 shaft diameter. It is an excellent solution for fulfilling many functions initially performed by brushed DC motors or in RC drones, racing cars, and much more.
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 Nucleo-64 with STM32F091RC MCU 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 Brushless 21 Click driver.
Key functions:
brushless21_set_duty_cycleThis function sets the duty cycle in percentages ( Range[ 0..1 ] ).brushless21_get_motor_speedThis function reads the motor speed in Hz.brushless21_switch_directionThis function switches the motor direction by toggling the DIR bit.
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 Brushless21 Click example
*
* # Description
* This example demonstrates the use of the Brushless 21 click board by driving the
* motor at different speeds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration which sets the GPIO
* as a default communication and enables the PWM.
*
* ## Application Task
* Controls the motor speed by changing the PWM duty cycle once per second. The duty cycle ranges from 0% to 100%.
* When the click board is configured in I2C mode the motor switches the direction at a minimal speed.
* Also, the chip internal temperature, VBB voltage and the motor speed readings are supported in I2C mode.
* Each step will be logged on the USB UART where you can track the program flow.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "brushless21.h"
static brushless21_t brushless21;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
brushless21_cfg_t brushless21_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.
brushless21_cfg_setup( &brushless21_cfg );
BRUSHLESS21_MAP_MIKROBUS( brushless21_cfg, MIKROBUS_1 );
err_t init_flag = brushless21_init( &brushless21, &brushless21_cfg );
if ( ( PWM_ERROR == init_flag ) || ( I2C_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( BRUSHLESS21_ERROR == brushless21_default_cfg ( &brushless21 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float duty = duty_cnt / 10.0;
if ( BRUSHLESS21_OK == brushless21_set_duty_cycle ( &brushless21, duty ) )
{
log_printf( &logger, "\r\n Duty Cycle : %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
}
if ( BRUSHLESS21_DRV_SEL_I2C == brushless21.drv_sel )
{
int8_t temperature = 0;
float motor_speed = 0;
float vbb_voltage = 0;
if ( BRUSHLESS21_OK == brushless21_get_temperature ( &brushless21, &temperature ) )
{
log_printf( &logger, " Temperature: %d C\r\n", ( int16_t ) temperature );
}
if ( BRUSHLESS21_OK == brushless21_get_motor_speed ( &brushless21, &motor_speed ) )
{
log_printf( &logger, " Motor Speed: %.2f Hz\r\n", motor_speed );
}
if ( BRUSHLESS21_OK == brushless21_get_vbb_voltage ( &brushless21, &vbb_voltage ) )
{
log_printf( &logger, " VBB Voltage: %.2f V\r\n", vbb_voltage );
}
if ( 0 == duty_cnt )
{
duty_inc = 1;
if ( BRUSHLESS21_OK == brushless21_switch_direction ( &brushless21 ) )
{
log_printf( &logger, " Switch direction\r\n" );
}
}
}
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
}
duty_cnt += duty_inc;
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
