multisteppertb67s102

---

Multi Stepper TB67S102 Click

Multi Stepper TB67S102 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 2022.
• Type : I2C type

Software Support

Example Description

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

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.MultiStepperTB67S102

Example Key Functions

• multisteppertb67s102_cfg_setup Config Object Initialization function.

void multisteppertb67s102_cfg_setup ( multisteppertb67s102_cfg_t *cfg );

• multisteppertb67s102_init Initialization function.

err_t multisteppertb67s102_init ( multisteppertb67s102_t *ctx, multisteppertb67s102_cfg_t *cfg );

• multisteppertb67s102_default_cfg Click Default Configuration function.

err_t multisteppertb67s102_default_cfg ( multisteppertb67s102_t *ctx );

• multisteppertb67s102_set_step_mode This function sets the step mode resolution settings.

err_t multisteppertb67s102_set_step_mode ( multisteppertb67s102_t *ctx, uint8_t mode );

• multisteppertb67s102_drive_motor This function drives the motor for the specific number of steps at the selected speed.

void multisteppertb67s102_drive_motor ( multisteppertb67s102_t *ctx, uint32_t steps, uint8_t speed );

• multisteppertb67s102_set_direction This function sets the motor direction by setting the AN pin logic state.

void multisteppertb67s102_set_direction ( multisteppertb67s102_t *ctx, uint8_t dir );

Application Init

Initializes the driver and performs the Click default configuration.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    multisteppertb67s102_cfg_t multisteppertb67s102_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.
    multisteppertb67s102_cfg_setup( &multisteppertb67s102_cfg );
    MULTISTEPPERTB67S102_MAP_MIKROBUS( multisteppertb67s102_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == multisteppertb67s102_init( &multisteppertb67s102, &multisteppertb67s102_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( MULTISTEPPERTB67S102_ERROR == multisteppertb67s102_default_cfg ( &multisteppertb67s102 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

Drives the motor clockwise for 200 steps and then counter-clockiwse for 100 steps with 2 seconds delay before changing the direction. Each step will be logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    log_printf ( &logger, " Move 200 steps clockwise \r\n\n" );
    multisteppertb67s102_set_direction ( &multisteppertb67s102, MULTISTEPPERTB67S102_DIR_CW );
    multisteppertb67s102_drive_motor ( &multisteppertb67s102, 200, MULTISTEPPERTB67S102_SPEED_FAST );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    
    log_printf ( &logger, " Move 100 steps counter-clockwise \r\n\n" );
    multisteppertb67s102_set_direction ( &multisteppertb67s102, MULTISTEPPERTB67S102_DIR_CCW );
    multisteppertb67s102_drive_motor ( &multisteppertb67s102, 100, MULTISTEPPERTB67S102_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.

---