Multi Stepper TB67S101 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.
- Author : Stefan Filipovic
- Date : Feb 2022.
- Type : I2C type
This example demonstrates the use of the Multi Stepper TB67S101 Click board by driving the motor in both directions for a desired number of steps.
- MikroSDK.Board
- MikroSDK.Log
- Click.MultiStepperTB67S101
multisteppertb67s101_cfg_setup
Config Object Initialization function.
void multisteppertb67s101_cfg_setup ( multisteppertb67s101_cfg_t *cfg );
multisteppertb67s101_init
Initialization function.
err_t multisteppertb67s101_init ( multisteppertb67s101_t *ctx, multisteppertb67s101_cfg_t *cfg );
multisteppertb67s101_default_cfg
Click Default Configuration function.
err_t multisteppertb67s101_default_cfg ( multisteppertb67s101_t *ctx );
multisteppertb67s101_set_step_mode
This function sets the step mode resolution settings in ctx->step_mode.
void multisteppertb67s101_set_step_mode ( multisteppertb67s101_t *ctx, uint8_t mode );
multisteppertb67s101_drive_motor
This function drives the motor for the specific number of steps at the selected speed.
err_t multisteppertb67s101_drive_motor ( multisteppertb67s101_t *ctx, uint32_t steps, uint8_t speed );
multisteppertb67s101_set_direction
This function sets the motor direction to clockwise or counter-clockwise in ctx->direction.
void multisteppertb67s101_set_direction ( multisteppertb67s101_t *ctx, uint8_t dir );
Initializes the driver and performs the Click default configuration.
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
multisteppertb67s101_cfg_t multisteppertb67s101_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.
multisteppertb67s101_cfg_setup( &multisteppertb67s101_cfg );
MULTISTEPPERTB67S101_MAP_MIKROBUS( multisteppertb67s101_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == multisteppertb67s101_init( &multisteppertb67s101, &multisteppertb67s101_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( MULTISTEPPERTB67S101_ERROR == multisteppertb67s101_default_cfg ( &multisteppertb67s101 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " 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 )
{
multisteppertb67s101_set_direction ( &multisteppertb67s101, MULTISTEPPERTB67S101_DIR_CW );
if ( MULTISTEPPERTB67S101_OK == multisteppertb67s101_drive_motor ( &multisteppertb67s101, 200,
MULTISTEPPERTB67S101_SPEED_FAST ) )
{
log_printf ( &logger, " Move 200 steps clockwise \r\n\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
multisteppertb67s101_set_direction ( &multisteppertb67s101, MULTISTEPPERTB67S101_DIR_CCW );
if ( MULTISTEPPERTB67S101_OK == multisteppertb67s101_drive_motor ( &multisteppertb67s101, 100,
MULTISTEPPERTB67S101_SPEED_FAST ) )
{
log_printf ( &logger, " Move 100 steps counter-clockwise \r\n\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
}
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.
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.