Skip to content

Latest commit

 

History

History

stepper

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

Stepper Click

Stepper 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 : GPIO type

Software Support

Example Description

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

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Stepper

Example Key Functions

  • stepper_cfg_setup Config Object Initialization function.
void stepper_cfg_setup ( stepper_cfg_t *cfg );
  • stepper_init Initialization function.
err_t stepper_init ( stepper_t *ctx, stepper_cfg_t *cfg );
  • stepper_default_cfg Click Default Configuration function.
void stepper_default_cfg ( stepper_t *ctx );
  • stepper_set_step_mode This function sets the step mode resolution settings.
void stepper_set_step_mode ( stepper_t *ctx, uint8_t mode );
  • stepper_set_direction This function sets the motor direction by setting the DIR pin logic state.
void stepper_set_direction ( stepper_t *ctx, uint8_t dir );
  • stepper_drive_motor This function drives the motor for the specific number of steps at the selected speed.
void stepper_drive_motor ( stepper_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. */
    stepper_cfg_t stepper_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.
    stepper_cfg_setup( &stepper_cfg );
    STEPPER_MAP_MIKROBUS( stepper_cfg, MIKROBUS_1 );
    if ( DIGITAL_OUT_UNSUPPORTED_PIN == stepper_init( &stepper, &stepper_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }

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

Application Task

Drives the motor clockwise for 64 full steps and then counter-clockiwse for 128 half steps with 2 seconds delay before changing the direction. All data is being logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    log_printf ( &logger, " Move 64 full steps clockwise \r\n\n" );
    stepper_set_step_mode ( &stepper, STEPPER_MODE_FULL_STEP );
    stepper_set_direction ( &stepper, STEPPER_DIR_CW );
    stepper_drive_motor ( &stepper, 64, STEPPER_SPEED_FAST );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );

    log_printf ( &logger, " Move 128 half steps counter-clockwise \r\n\n" );
    stepper_set_step_mode ( &stepper, STEPPER_MODE_HALF_STEP );
    stepper_set_direction ( &stepper, STEPPER_DIR_CCW );
    stepper_drive_motor ( &stepper, 128, STEPPER_SPEED_VERY_FAST );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

Note

Step Motor 5v [MIKROE-1530] is a fully compatible stepper motor for this Click board: https://www.mikroe.com/step-motor-5v

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.