Master motor speed control with Si8711CC and STM32F031K6
PWM precision meets motor control
Published Oct 01, 2024
Click board™
PWM driver Click
Dev. board
Nucleo 32 with STM32F031K6 MCU
Compiler
NECTO Studio
MCU
STM32F031K6
Unlock speed control possibilities with our PWM-controlled DC motor solution
A
A
Hardware Overview
How does it work?
PWM driver Click is based on the Si8711CC, a 5kV LED emulator input, open collector output isolator from Skyworks. Compared to the optocouplers, the Si8711CC is more resistant to temperature, age, and forward current effects. It has a longer service life, higher common-mode transient immunity, and more. The Si8711CC is based on proprietary CMOS isolation technology for low-power, high-speed operation and is resistant to wear-out effects that, in the case of optocouplers, degrade the performance. The Si8711CC features up to 5000VRMS isolation and 10kV surge protection, making it a perfect isolator. For controlling the devices, it is capable of data rates DC of up to 15Mbps, with a propagation delay of 30ns. The Si8711CC controls the loads over the DMP3010LK3,
a P-channel enhancement mode MOSFET from Diodes Incorporated. This fast-switching diode has ESD protected gate, low input capacitance, and low on-resistance, designed to maintain superior switching performance, making it ideal for high-efficiency power management applications. The PWM Driver Click comes with the screw terminals labeled LOAD (+END, -END) to connect the load, which the Si7811CC controls over the DMP3010LK3 diode, and EXT for external power supply. It is not recommended to use this Click board™ with loads over 50W as the MOSFET can get overheated; this, however, does not apply if the Click board™ is used as an ON/OFF switch. The PWM Driver Click is controlled by the host MCU by PWM pulses over the PWM pin of the mikroBUS™ socket. The PWM
pin does not have direct control over the Si8711CC but rather through the DMG3420U, an N-channel enhancement mode MOSFET from Diodes Incorporated. This diode shares many features with the one mentioned above, such as low on-resistance, low input capacitance, fast switching speed, and more. This Click board™ can be operated only with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ 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
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
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 32 with STM32F031K6 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 PWM driver Click driver.
Key functions:
pwmdriver_set_duty_cycle- Generic sets PWM duty cyclepwmdriver_pwm_stop- Stop PWM modulepwmdriver_pwm_start- Start PWM module
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
* @brief PwmDriver Click example
*
* # Description
* This application is controls the speed DC motors.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables - GPIO, PWM initialization set PWM duty cycle and PWM frequency,
* start PWM, enable the engine, and start to write log.
*
* ## Application Task
* This is an example that demonstrates the use of the PWM driver Click board.
* This example shows the automatic control of PWM,
* the first increases duty cycle and then the duty cycle is falling.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* *note:*
* EXT PWR 3-30VDC
*
* @author Nikola Peric
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "pwmdriver.h"
// ------------------------------------------------------------------ VARIABLES
static pwmdriver_t pwmdriver;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
pwmdriver_cfg_t cfg;
/**
* 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.
pwmdriver_cfg_setup( &cfg );
PWMDRIVER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
pwmdriver_init( &pwmdriver, &cfg );
Delay_ms( 100 );
log_printf( &logger, " Initialization PWM \r\n " );
pwmdriver_set_duty_cycle( &pwmdriver, 0.0 );
pwmdriver_pwm_start( &pwmdriver );
Delay_ms( 1000 );
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;
pwmdriver_set_duty_cycle ( &pwmdriver, duty );
log_printf( &logger, "Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
Delay_ms( 500 );
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
}
duty_cnt += duty_inc;
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
