Skip to content

Latest commit

 

History

History
155 lines (120 loc) · 5.19 KB

README.md

File metadata and controls

155 lines (120 loc) · 5.19 KB

Stepper 5 Click

Stepper 5 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 : Feb 2024.
  • Type : UART type

Software Support

Example Description

This example demonstrates the use of the Stepper 5 Click board by driving the motor in both directions for a desired number of steps.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Stepper5

Example Key Functions

  • stepper5_cfg_setup Config Object Initialization function.
void stepper5_cfg_setup ( stepper5_cfg_t *cfg );
  • stepper5_init Initialization function.
err_t stepper5_init ( stepper5_t *ctx, stepper5_cfg_t *cfg );
  • stepper5_default_cfg Click Default Configuration function.
err_t stepper5_default_cfg ( stepper5_t *ctx );
  • stepper5_set_direction This function sets the motor direction by setting the DIR pin logic state.
void stepper5_set_direction ( stepper5_t *ctx, uint8_t dir );
  • stepper5_set_step_res This function sets the microstep resolution bits in CHOPCONF register.
err_t stepper5_set_step_res ( stepper5_t *ctx, uint8_t mres );
  • stepper5_drive_motor This function drives the motor for the specific number of steps at the selected speed.
void stepper5_drive_motor ( stepper5_t *ctx, uint32_t steps, uint8_t speed );

Application Init

Initializes the driver and performs the Click default configuration.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    stepper5_cfg_t stepper5_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.
    stepper5_cfg_setup( &stepper5_cfg );
    STEPPER5_MAP_MIKROBUS( stepper5_cfg, MIKROBUS_1 );
    if ( UART_ERROR == stepper5_init( &stepper5, &stepper5_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( STEPPER5_ERROR == stepper5_default_cfg ( &stepper5 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

Drives the motor clockwise for 200 full steps and then counter-clockiwse for 200 half steps and 400 quarter steps with 2 seconds delay on driving mode change. All data is being logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    log_printf ( &logger, " Move 200 full steps clockwise, speed: slow\r\n\n" );
    stepper5_set_direction ( &stepper5, STEPPER5_DIR_CW );
    stepper5_set_step_res ( &stepper5, STEPPER5_MRES_FULLSTEP );
    stepper5_drive_motor ( &stepper5, 200, STEPPER5_SPEED_SLOW );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );

    log_printf ( &logger, " Move 200 half steps counter-clockwise, speed: medium\r\n\n" );
    stepper5_set_direction ( &stepper5, STEPPER5_DIR_CCW );
    stepper5_set_step_res ( &stepper5, STEPPER5_MRES_2 );
    stepper5_drive_motor ( &stepper5, 200, STEPPER5_SPEED_MEDIUM );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );

    log_printf ( &logger, " Move 400 quarter steps counter-clockwise, speed: fast\r\n\n" );
    stepper5_set_direction ( &stepper5, STEPPER5_DIR_CCW );
    stepper5_set_step_res ( &stepper5, STEPPER5_MRES_4 );
    stepper5_drive_motor ( &stepper5, 400, STEPPER5_SPEED_FAST );
    Delay_ms ( 1000 );
    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.