Improve your motor control experience with our brushless driver, offering unparalleled smoothness, intelligent features, and superior performance for your every need.
A
A
Hardware Overview
How does it work?
Brushless 25 Click is based on the MCT8316A, a high-speed sensorless trapezoidal control integrated FET BLDC driver from Texas Instruments. It is the ideal solution for applications requiring the high-speed operation of up to 3kHz of electrical speed, a very fast startup time of under 50ms for 12V to 24V BLDC motors, and fast deceleration of under 150ms. The driver's control is highly configurable through register settings stored in an onboard non-volatile EEPROM. This feature allows the device to operate as a stand-alone device once it has been configured. In addition, the MCT8316A allows a high level of monitoring, where any variable in the algorithm can be observed as an analog output via two 12-bit DACs. Brushless 25 Click uses a standard I2C 2-Wire interface that allows the host MCU to configure EEPROM settings and read detailed fault and motor state information. If a fault condition occurs, the MCT8316A will pull the FLT pin to a low logic state, with a FAULT LED as a visual presentation. The FG pin is used as a motor speed indicator and provides pulses proportional to motor speed. For connecting the
three-phase BLDC motor, this Click board™ features the half-bridge output CBA screw terminal and a VM terminal for an external motor power supply. The RST pin can set the motor driver to sleep mode by turning all MOSFETs OFF. There are three switches to control the connected motor manually. The speed can be controlled by a PWM or analog value, which can be selected via the SPEED CTRL switch. The PWM signal can be set over the corresponding pin of the mikroBUS™ socket, while the analog value can be set over the MCP4161, an 8-bit, single SPI digital potentiometer with non-volatile memory from Microchip. The motor driver expects up to 95KHz of PWM frequency or an analog voltage in 732μV resolution. In addition, this is also a way to wake up the motor driver from sleep mode. The DIR switch changes the direction of the motor spinning with 0 and 1 positions. The low position (0) sets the phase driving sequence as ABC, while the high position (1) sets the ACB sequence. The I2C interface can overwrite this input. The Brake switch also has two states, with high entering the brake state. The MCT8316A will decrease the
output speed to the threshold value and stay in the brake state as long as this switch is in a high position. This input also can be overwritten by the I2C interface. In addition, the Brushless 25 Click comes with two headers above the mikroBUS™ socket for some optional feature additions. The VBK pin on the right-side unpopulated header is an output voltage pin from the internal buck regulator for some external loads. Other pins on this header are for monitoring algorithm variables and phase current feedback through DAC and SOX pins (the SOX pin can also be configured as one of the DAC pins). On the left is an unpopulated header with E_WD and E_CLK signals acting as the external clock reference and watchdog input pins. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
PIC32MZ Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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

Architecture
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
You complete me!
Accessories
Brushless DC (BLDC) Motor with a Hall sensor represents a high-performance motor from the 42BLF motor series. This motor, wired in a star configuration, boasts a Hall Effect angle of 120°, ensuring precise and reliable performance. With a compact motor length of 47mm and a lightweight design tipping the scales at just 0.29kg, this BLDC motor is engineered to meet your needs. Operating flawlessly at a voltage rating of 24VDC and a speed range of 4000 ± 10% RPM, this motor offers consistent and dependable power. It excels in a normal operational temperature range from -20 to +50°C, maintaining efficiency with a rated current of 1.9A. Also, this product seamlessly integrates with all Brushless Click boards™ and those that require BLDC motors with Hall sensors.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
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 25 Click driver.
Key functions:
brushless25_register_write
- Brushless 25 data writing function.brushless25_register_read
- Brushless 25 data reading function.brushless25_set_speed_value
- Brushless 25 set speed 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 Brushless 25 Click example
*
* # Description
* Application example shows the device's capability of controlling
* the brushless motor speed and state of the driver.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver, sets the device into slow start mode
* and sets the speed of the motor to 30%.
*
* ## Application Task
* This example is taking track of the state of the driver and motor, as well as its
* voltage and speed which is changing from 30% to 100%, and logging it onto the USB UART terminal.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "brushless25.h"
static brushless25_t brushless25;
static log_t logger;
uint8_t sw_data = 0;
uint8_t speed_val = 3;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
brushless25_cfg_t brushless25_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.
brushless25_cfg_setup( &brushless25_cfg );
BRUSHLESS25_MAP_MIKROBUS( brushless25_cfg, MIKROBUS_1 );
err_t init_flag = brushless25_init( &brushless25, &brushless25_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( BRUSHLESS25_ERROR == brushless25_default_cfg ( &brushless25 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
brushless25_set_speed_value( &brushless25, ( speed_val * 10 ) );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint32_t tmp_data = 0;
uint16_t spd_data = 0;
uint16_t voltage_data = 0;
brushless25_register_read( &brushless25, BRUSHLESS25_REG_SYS_STATUS2, &tmp_data );
tmp_data &= BRUSHLESS25_STATE_MASK;
switch ( tmp_data )
{
case BRUSHLESS25_STATE_SYSTEM_IDLE:
{
log_info( &logger, " System is idle " );
break;
}
case BRUSHLESS25_STATE_MOTOR_START:
{
log_info( &logger, " Motor is starting " );
break;
}
case BRUSHLESS25_STATE_MOTOR_RUN:
{
log_info( &logger, " Motor is running" );
if ( ( speed_val < 10 ) && ( sw_data == 0 ) )
{
speed_val++;
if ( speed_val == 10 )
{
sw_data = 1;
}
}
else if ( ( speed_val > 3 ) && ( sw_data == 1 ) )
{
speed_val--;
if ( speed_val == 3 )
{
sw_data = 0;
}
}
break;
}
case BRUSHLESS25_STATE_MOTOR_ALIGN:
{
log_info( &logger, " Motor is aligning " );
break;
}
case BRUSHLESS25_STATE_MOTOR_IDLE:
{
log_info( &logger, " Motor is in idle mode " );
break;
}
case BRUSHLESS25_STATE_MOTOR_STOP:
{
log_info( &logger, " Motor is stoped " );
brushless25_set_brake_state( &brushless25, BRUSHLESS25_BRAKE_ON );
break;
}
case BRUSHLESS25_STATE_FAULT:
{
log_error( &logger, " Fault accured " );
brushless25_set_brake_state( &brushless25, BRUSHLESS25_BRAKE_ON );
for ( ; ; );
}
case BRUSHLESS25_STATE_MOTOR_BRAKE:
{
log_info( &logger, " Motor brake is on " );
brushless25_set_brake_state( &brushless25, BRUSHLESS25_BRAKE_OFF );
break;
}
default:
{
break;
}
}
brushless25_set_speed_value( &brushless25, ( speed_val * 10 ) );
Delay_ms ( 1000 );
brushless25_register_read( &brushless25, BRUSHLESS25_REG_SYS_STATUS2, &tmp_data );
spd_data = ( uint16_t ) tmp_data / 10;
brushless25_register_read( &brushless25, BRUSHLESS25_REG_SYS_STATUS1, &tmp_data );
voltage_data = ( ( uint16_t ) ( tmp_data >> 16 ) / 10 );
log_printf( &logger, " Motor speed: %d Hz \r\n", spd_data );
log_printf( &logger, " Motor voltage: %d V \r\n", voltage_data );
log_printf( &logger, " --------------------- \r\n" );
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