Skip to content

Latest commit

 

History

History
150 lines (115 loc) · 4.74 KB

README.md

File metadata and controls

150 lines (115 loc) · 4.74 KB

DAC 19 Click

DAC 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 : Sep 2024.
  • Type : I2C type

Software Support

Example Description

This example demonstrates the use of DAC 19 Click board by changing the output voltage level.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.DAC19

Example Key Functions

  • dac19_cfg_setup Config Object Initialization function.
void dac19_cfg_setup ( dac19_cfg_t *cfg );
  • dac19_init Initialization function.
err_t dac19_init ( dac19_t *ctx, dac19_cfg_t *cfg );
  • dac19_default_cfg Click Default Configuration function.
err_t dac19_default_cfg ( dac19_t *ctx );
  • dac19_set_voltage This function sets the output voltage depending on the vref value defined by the VCC SEL on-board jumper. VREF and Voltage values can be either in Volts or Milivolts.
err_t dac19_set_voltage ( dac19_t *ctx, uint16_t vref_mv, uint16_t voltage_mv );
  • dac19_set_value This function sets the DAC DATA register to a desired value.
err_t dac19_set_value ( dac19_t *ctx, uint16_t data_in );
  • dac19_set_voltage_int_vref This function sets the output voltage with the internal reference enabled.
err_t dac19_set_voltage_int_vref ( dac19_t *ctx, uint16_t voltage_mv );

Application Init

Initializes the driver, checks the communication by reading and verifying the device ID, and enables the DAC output.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    dac19_cfg_t dac19_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.
    dac19_cfg_setup( &dac19_cfg );
    DAC19_MAP_MIKROBUS( dac19_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == dac19_init( &dac19, &dac19_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( DAC19_ERROR == dac19_default_cfg ( &dac19 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

Changes the output voltage every 2 seconds and logs the voltage value on the USB UART. It will go through the entire voltage range for the step number defined below.

void application_task ( void )
{
    uint16_t step = REFERENCE_VOLTAGE_MV / NUMBER_OF_STEPS;
    uint16_t output_voltage = step;
    for ( uint8_t cnt = 0; cnt < NUMBER_OF_STEPS; cnt++ )
    {
        if ( DAC19_OK == dac19_set_voltage ( &dac19, REFERENCE_VOLTAGE_MV, output_voltage ) )
        {
            log_printf( &logger, " VOUT: %u mV\r\n", output_voltage );
        }
        output_voltage += step;
        Delay_ms ( 1000 ); 
        Delay_ms ( 1000 );
    }
}

Note

Measure the voltage at VCC_SEL jumper and adjust the reference voltage value below for better accuracy.

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.