oneshot

---

One Shot Click

One Shot 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 : MikroE Team
• Date : Feb 2020.
• Type : I2C type

Software Support

Example Description

This example shows the user how to configure and use the One Shot Click. The Click has a monostable monovibrator which cam generate a pulse of width between 1μs and 33.6 seconds.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.OneShot

Example Key Functions

• oneshot_cfg_setup Config Object Initialization function.

void oneshot_cfg_setup ( oneshot_cfg_t *cfg );

• oneshot_init Initialization function.

err_t oneshot_init ( oneshot_t *ctx, oneshot_cfg_t *cfg );

• oneshot_default_cfg Click Default Configuration function.

void oneshot_default_cfg ( oneshot_t *ctx );

• oneshot_get_resistance This function reads the resistance data from the AD5241 chip.

float oneshot_get_resistance ( oneshot_t *ctx );

• oneshot_digital_read_rst This function reads the digital signal from the RST pin.

uint8_t oneshot_digital_read_rst ( oneshot_t *ctx );

• oneshot_digital_write_cs This function writes the specified digital signal to the CS pin.

void oneshot_digital_write_cs ( oneshot_t *ctx, uint8_t signal );

Application Init

This function initializes and configures the logger and Click modules. Resistance data, acquired from the AD5241, is displayed at the end of the initialization process.

void application_init ( )
{
    log_cfg_t log_cfg;
    oneshot_cfg_t cfg;

    /** 
     * 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.

    oneshot_cfg_setup( &cfg );
    ONESHOT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    oneshot_init( &oneshot, &cfg );
    Delay_100ms( );
    oneshot_default_cfg( &oneshot );
    Delay_100ms( );
    log_printf( &logger, " * Resistance: %.1f Ohm\r\n", oneshot_get_resistance( &oneshot ) );
}

Application Task

This function triggers one shot every 8 seconds.

void application_task ( )
{
    oneshot_digital_write_cs( &oneshot, 1 );
    Delay_ms ( 1 );
    oneshot_digital_write_cs( &oneshot, 0 );
    log_printf( &logger, " * One shot triggered \r\n" );
    log_printf( &logger, " --------------------------- \r\n" );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    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.

---