Drive single-coil reversible DC fans and motors with ZXBM5210 and STM32F091RC
Unleash smooth and precise motion
Published Feb 26, 2024
Click board™
DC Motor 16 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Do you want to control handheld power tools easily? Add this brushed motor control solution and transform your project!
A
A
Hardware Overview
How does it work?
DC Motor 16 Click is based on the ZXBM5210, a single-chip solution for driving single-coil reversible direct current (DC) fans and motors from Diodes Incorporated. The driver output stage is designed to minimize audible switching noise and electromagnetic interference (EMI), ensuring a low-noise solution. The device has four motor operation modes: Standby, Forward, Reverse, and Brake Mode. These four modes are controlled by the FWD and REV pins routed to the RST and PWM pins of the mikroBUS™ used for controlling the motor rotation directions. All the internal circuits are turned off in the Standby mode to minimize power consumption, while the Brake mode allows the motor to stop quickly. The power consumption in the Standby mode is less than in the Brake mode. The signal change should be completed within 125μs to prevent the ZXBM5210 from entering the Standby mode during mode changes. The ZXBM5210 also possesses three modes of motor speed
control: VREF speed control mode, PWM speed control mode, and motor speed control by adjusting the supply voltage. Motor speed can be controlled by adjusting the duty cycle of the PWM signal while keeping the supply voltage pin at the nominal motor voltage or can be controlled by varying the supply voltage while the FWD and REV pins are set to either a logic high or low depending on needed motor direction. In PWM Mode, the input voltage on the Vref pin of the ZXBM5210 must be greater than or equal to the supply voltage value. The motor speed of the ZXBM5210 can be controlled by adjusting the DC voltage on the Vref pin. For this purpose, the DC Motor 16 click employs the MCP4161 digital potentiometer from Microchip, which allows setting the corresponding voltage value via the SPI serial interface. The potentiometer terminal B is fixed to the Zero-Scale wiper value (which corresponds to a wiper value of 0x00 for both 7-bit and 8-bit devices), while the
potentiometer terminal A is fixed connected to the Full-Scale wiper value (which corresponds to a wiper value of 0x100 for 8-bit devices or 0x80 for 7-bit devices). For this reason, it was chosen that when the user selects 0x100 as the desired value, the value on the Vref pin takes the value of supply voltage from the mikroBUS™ (VCC), while in the case of selecting 0x00 on the Vref pin value is equal to the 0.2*VCC. In this mode, FWD and REV pins are only used for direction control, and therefore high-frequency PWM control signal should not be applied to those pins. 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. 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.
DC Gear Motor - 430RPM (3-6V) represents an all-in-one combination of a motor and gearbox, where the addition of gear leads to a reduction of motor speed while increasing the torque output. This gear motor has a spur gearbox, making it a highly reliable solution for applications with lower torque and speed requirements. The most critical parameters for gear motors are speed, torque, and efficiency, which are, in this case, 520RPM with no load and 430RPM at maximum efficiency, alongside a current of 60mA and a torque of 50g.cm. Rated for a 3-6V operational voltage range and clockwise/counterclockwise rotation direction, this motor represents an excellent solution for many functions initially performed by brushed DC motors in robotics, medical equipment, electric door locks, 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 DC Motor 16 Click driver.
Key functions:
void dcmotor16_set_direction( uint8_t dir )- Set motor directionvoid dcmotor16_ctrl_vref( uint16_t value )- Control motor VRef (speed)void dcmotor16_stop( void )- Motor stop
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 DCMotor16 Click example
*
* # Description
* This example shows the capabilities of the DC Motor 16 click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver init.
*
* ## Application Task
* Start motor example with change in motor direction and speed.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "dcmotor16.h"
static dcmotor16_t dcmotor16;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor16_cfg_t dcmotor16_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.
dcmotor16_cfg_setup( &dcmotor16_cfg );
DCMOTOR16_MAP_MIKROBUS( dcmotor16_cfg, MIKROBUS_1 );
err_t init_flag = dcmotor16_init( &dcmotor16, &dcmotor16_cfg );
if ( SPI_MASTER_ERROR == init_flag ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
uint16_t cnt;
log_printf( &logger, ">> Motor start with direction [FORWARD] <<\r\n" );
dcmotor16_set_direction( &dcmotor16, DCMOTOR16_DIR_FORWARD );
for( cnt = 0; cnt <= 0x0100; cnt+= 25 ) {
dcmotor16_ctrl_vref( &dcmotor16, cnt );
Delay_ms( 250 );
}
Delay_ms( 2000 );
log_printf( &logger, ">> Motor stop \r\n" );
dcmotor16_stop( &dcmotor16 );
Delay_ms( 1000 );
log_printf( &logger, ">> Motor start with direction [BACKWARD] <<\r\n" );
dcmotor16_set_direction( &dcmotor16, DCMOTOR16_DIR_BACKWARD );
for( cnt = 0; cnt <= 0x0100; cnt+= 25 ) {
dcmotor16_ctrl_vref( &dcmotor16, cnt );
Delay_ms( 250 );
}
Delay_ms( 2000 );
log_printf( &logger, ">> Motor stop \r\n" );
dcmotor16_stop( &dcmotor16 );
Delay_ms( 1000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
