vibromotor2

---

Vibro Motor 2 Click

Vibro Motor 2 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 Ilic
• Date : Jun 2021.
• Type : PWM type

Software Support

Example Description

This application contorl the speed of vibro motor.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.VibroMotor2

Example Key Functions

• vibromotor2_cfg_setup Config Object Initialization function.

void vibromotor2_cfg_setup ( vibromotor2_cfg_t *cfg );

• vibromotor2_init Initialization function.

err_t vibromotor2_init ( vibromotor2_t *ctx, vibromotor2_cfg_t *cfg );

• vibromotor2_set_duty_cycle This function sets the PWM duty cycle in percentages ( Range[ 0..1 ] ).

err_t vibromotor2_set_duty_cycle ( vibromotor2_t *ctx, float duty_cycle );

• vibromotor2_pwm_stop This function stops the PWM moudle output.

err_t vibromotor2_pwm_stop ( vibromotor2_t *ctx );

• vibromotor2_pwm_start This function starts the PWM moudle output.

err_t vibromotor2_pwm_start ( vibromotor2_t *ctx );

Application Init

Initializes GPIO driver and PWM. Configures PWM to 5kHz frequency, calculates maximum duty ratio and starts PWM with duty ratio value 0.

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    vibromotor2_cfg_t vibromotor2_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.

    vibromotor2_cfg_setup( &vibromotor2_cfg );
    VIBROMOTOR2_MAP_MIKROBUS( vibromotor2_cfg, MIKROBUS_POSITION_VIBROMOTOR2 );
    err_t init_flag  = vibromotor2_init( &vibromotor2, &vibromotor2_cfg );
    if ( PWM_ERROR == init_flag ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    vibromotor2_set_duty_cycle ( &vibromotor2, 0.0 );
    vibromotor2_pwm_start( &vibromotor2 );

    log_info( &logger, " Application Task " );
}

Application Task

Allows user to enter desired command to control Vibro Motor Click board.

void application_task ( void ) 
{
    static int8_t duty_cnt = 1;
    static int8_t duty_inc = 1;
    float duty = duty_cnt / 10.0;
    
    vibromotor2_set_duty_cycle ( &vibromotor2, 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;
}

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.

---