DC Motor 16 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 Ilic
- Date : Aug 2021.
- Type : SPI type
This example shows the capabilities of the DC Motor 16 Click board.
- MikroSDK.Board
- MikroSDK.Log
- Click.DCMotor16
dcmotor16_cfg_setupConfig Object Initialization function.
void dcmotor16_cfg_setup ( dcmotor16_cfg_t *cfg );dcmotor16_initInitialization function.
err_t dcmotor16_init ( dcmotor16_t *ctx, dcmotor16_cfg_t *cfg );dcmotor16_set_directionSet motor direction.
void dcmotor16_set_direction( dcmotor16_t *ctx, uint8_t dir );dcmotor16_ctrl_vrefControl motor VRef (speed).
void dcmotor16_ctrl_vref( dcmotor16_t *ctx, uint16_t value );dcmotor16_stopMotor stop.
void dcmotor16_stop( dcmotor16_t *ctx );Initialization driver init.
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
dcmotor16_cfg_t dcmotor16_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.
dcmotor16_cfg_setup( &dcmotor16_cfg );
DCMOTOR16_MAP_MIKROBUS( dcmotor16_cfg, MIKROBUS_1 );
err_t init_flag = dcmotor16_init( &dcmotor16, &dcmotor16_cfg );
if ( SPI_MASTER_ERROR == init_flag ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}Start motor example with change in motor direction and speed.
void application_task ( void )
{
uint16_t cnt;
log_printf( &logger, ">> Motor start with direction [FORWARD] <<\r\n" );
dcmotor16_set_direction( &dcmotor16, DCMOTOR16_DIR_FORWARD );
for( cnt = 0; cnt <= 0x0100; cnt+= 25 ) {
dcmotor16_ctrl_vref( &dcmotor16, cnt );
Delay_ms ( 250 );
}
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, ">> Motor stop \r\n" );
dcmotor16_stop( &dcmotor16 );
Delay_ms ( 1000 );
log_printf( &logger, ">> Motor start with direction [BACKWARD] <<\r\n" );
dcmotor16_set_direction( &dcmotor16, DCMOTOR16_DIR_BACKWARD );
for( cnt = 0; cnt <= 0x0100; cnt+= 25 ) {
dcmotor16_ctrl_vref( &dcmotor16, cnt );
Delay_ms ( 250 );
}
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, ">> Motor stop \r\n" );
dcmotor16_stop( &dcmotor16 );
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.