dcmotor19

---

DC Motor 19 Click

DC Motor 19 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 : Oct 2021.
• Type : GPIO type

Software Support

Example Description

This example demonstrates the use of DC Motor 19 Click board by driving the motors in both direction in the span of 14 seconds.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.DCMotor19

Example Key Functions

• dcmotor19_cfg_setup Config Object Initialization function.

void dcmotor19_cfg_setup ( dcmotor19_cfg_t *cfg );

• dcmotor19_init Initialization function.

err_t dcmotor19_init ( dcmotor19_t *ctx, dcmotor19_cfg_t *cfg );

• dcmotor19_drive_motor This function drives the motor for a certian time specified by time_ms at the desired speed. The motor channel and mode must be previously selected using the dcmotor19_set_channel_mode function.

err_t dcmotor19_drive_motor ( dcmotor19_t *ctx, uint8_t speed, uint32_t time_ms );

• dcmotor19_set_channel_mode This function sets the active channel and mode which will be used by the dcmotor19_drive_motor function.

err_t dcmotor19_set_channel_mode ( dcmotor19_t *ctx, uint8_t channel, uint8_t mode );

• dcmotor19_disable_standby_mode This function disables the standby mode.

void dcmotor19_disable_standby_mode ( dcmotor19_t *ctx );

Application Init

Initializes the driver and enables the Click by disabling the standby mode.

void application_init ( void )
{
    log_cfg_t log_cfg;              /**< Logger config object. */
    dcmotor19_cfg_t dcmotor19_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.
    dcmotor19_cfg_setup( &dcmotor19_cfg );
    DCMOTOR19_MAP_MIKROBUS( dcmotor19_cfg, MIKROBUS_1 );
    if ( DIGITAL_OUT_UNSUPPORTED_PIN == dcmotor19_init( &dcmotor19, &dcmotor19_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    dcmotor19_disable_standby_mode ( &dcmotor19 );
    log_info( &logger, " Application Task " );
}

Application Task

Drives the motors in the forward direction for 5 seconds, then pulls brake for 2 seconds, and after that drives them in the reverse direction for 5 seconds, and finally, stops driving for 2 seconds which basically disconnects the motors. Each step will be logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    log_printf ( &logger, " Driving motors forward...\r\n" );
    dcmotor19_set_channel_mode ( &dcmotor19, DCMOTOR19_CHANNEL_1 | DCMOTOR19_CHANNEL_2, DCMOTOR19_MODE_FORWARD );
    dcmotor19_drive_motor ( &dcmotor19, DCMOTOR19_SPEED_DEFAULT, 5000 );
    log_printf ( &logger, " Pull brake!\r\n" );
    dcmotor19_set_channel_mode ( &dcmotor19, DCMOTOR19_CHANNEL_1 | DCMOTOR19_CHANNEL_2, DCMOTOR19_MODE_SHORT_BRAKE );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    log_printf ( &logger, " Driving motors in reverse...\r\n" );
    dcmotor19_set_channel_mode ( &dcmotor19, DCMOTOR19_CHANNEL_1 | DCMOTOR19_CHANNEL_2, DCMOTOR19_MODE_REVERSE );
    dcmotor19_drive_motor ( &dcmotor19, DCMOTOR19_SPEED_DEFAULT, 5000 );
    log_printf ( &logger, " Stop driving!\r\n\n" );
    dcmotor19_set_channel_mode ( &dcmotor19, DCMOTOR19_CHANNEL_1 | DCMOTOR19_CHANNEL_2, DCMOTOR19_MODE_STOP );
    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.

---