Skip to content

Latest commit

 

History

History

brushless10

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

Brushless 10 Click

Brushless 10 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.


Click Library

  • Author : Stefan Filipovic
  • Date : Mar 2024.
  • Type : PWM type

Software Support

Example Description

This example demonstrates the use of the Brushless 10 Click board by driving the motor at different speeds.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Brushless10

Example Key Functions

  • brushless10_cfg_setup Config Object Initialization function.
void brushless10_cfg_setup ( brushless10_cfg_t *cfg );
  • brushless10_init Initialization function.
err_t brushless10_init ( brushless10_t *ctx, brushless10_cfg_t *cfg );
  • brushless10_default_cfg Click Default Configuration function.
err_t brushless10_default_cfg ( brushless10_t *ctx );
  • brushless10_set_duty_cycle This function sets the PWM duty cycle in percentages ( Range[ 0..1 ] ).
err_t brushless10_set_duty_cycle ( brushless10_t *ctx, float duty_cycle );
  • brushless10_pull_brake This function pulls brake by setting the BRAKE pin to high logic state.
void brushless10_pull_brake ( brushless10_t *ctx );
  • brushless10_release_brake This function releases brake by setting the BRAKE pin to low logic state.
void brushless10_release_brake ( brushless10_t *ctx );

Application Init

Initializes the driver and performs the Click default configuration.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    brushless10_cfg_t brushless10_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.
    brushless10_cfg_setup( &brushless10_cfg );
    BRUSHLESS10_MAP_MIKROBUS( brushless10_cfg, MIKROBUS_1 );
    if ( BRUSHLESS10_OK != brushless10_init( &brushless10, &brushless10_cfg ) )
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( BRUSHLESS10_OK != brushless10_default_cfg ( &brushless10 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

Controls the motor speed by changing the PWM duty cycle every 2 seconds. The duty cycle ranges from 20% to 100%. Each step will be logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    static int8_t duty_cnt = 2;
    static int8_t duty_inc = 1;
    float duty = duty_cnt / 10.0;
    
    brushless10_set_duty_cycle ( &brushless10, duty );
    log_printf( &logger, "> Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
    
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );

    duty_cnt += duty_inc;
    if ( duty_cnt > 10 ) 
    {        
        duty_cnt = 9;
        duty_inc = -1;
    }
    else if ( duty_cnt < 2 ) 
    {
        duty_cnt = 2;
        duty_inc = 1;
        log_printf( &logger, " Pull brake\r\n" );
        brushless10_pull_brake ( &brushless10 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        log_printf( &logger, " Release brake\r\n" );
        brushless10_release_brake ( &brushless10 );
        Delay_ms ( 1000 );
    }
}

Application Output

This Click board can be interfaced and monitored in two ways:

  • Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
  • UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.

Additional Notes and Information

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.