Skip to content

Latest commit

 

History

History
125 lines (94 loc) · 3.77 KB

README.md

File metadata and controls

125 lines (94 loc) · 3.77 KB

Digi Pot 4 Click

Digi Pot 4 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 : dec 2019.
  • Type : SPI type

Software Support

Example Description

This application is a digitally controlled dual potentiometer.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.DigiPot4

Example Key Functions

  • digipot4_cfg_setup Config Object Initialization function.
void digipot4_cfg_setup ( digipot4_cfg_t *cfg );
  • digipot4_init Initialization function.
err_t digipot4_init ( digipot4_t *ctx, digipot4_cfg_t *cfg );
  • digipot4_default_cfg Click Default Configuration function.
void digipot4_default_cfg ( digipot4_t *ctx );
  • digipot4_write_reg This function writes data in wiper register and NV register.
void digipot4_write_reg ( digipot4_t *ctx, uint8_t reg,          uint16_t value );
  • digipot4_copy_reg This function is used to copy the data from the wipers to the NV memory and from the NV memory it wipers.
void digipot4_copy_reg ( digipot4_t *ctx, uint8_t reg );

Application Init

Driver intialization

void application_init ( void )
{
    log_cfg_t log_cfg;
    digipot4_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 ----" );

    digipot4_cfg_setup( &cfg );
    DIGIPOT4_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    digipot4_init( &digipot4, &cfg );
}

Application Task

Set the wiper position.

void application_task ( void )
{

    digipot4_write_reg( &digipot4, DIGIPOT4_WIPER_REG_1, 0 );
    digipot4_write_reg( &digipot4, DIGIPOT4_WIPER_REG_2, 0 );
    Delay_1sec( );
    digipot4_write_reg( &digipot4, DIGIPOT4_WIPER_REG_1, 512 );
    digipot4_write_reg( &digipot4, DIGIPOT4_WIPER_REG_2, 512 );
    Delay_1sec( );
    digipot4_write_reg( &digipot4, DIGIPOT4_WIPER_REG_1, 1023 );
    digipot4_write_reg( &digipot4, DIGIPOT4_WIPER_REG_2, 1023 );
    Delay_1sec( );
}

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.