Intermediate
30 min
0

Convert digital signals into tangible analog outputs using DAC53401 and PIC18F57Q43

Redefine data with our DAC symphony!

DAC 10 Click with UNI Clicker

Published Aug 19, 2023

Click board™

DAC 10 Click

Development board

UNI Clicker

Compiler

NECTO Studio

MCU

PIC18F57Q43

Our DAC solution empowers data to transcend the digital realm, converting it into actionable analog outputs and fostering effective communication and control across many applications

A

A

Hardware Overview

How does it work?

DAC 10 Click is based on the DAC53401, a 10-bit voltage-output smart digital-to-analog converter from Texas Instruments. This device consumes extremely low power and has a nonvolatile memory (NVM), an internal reference, and an I2C serial interface. It also has a power-on-reset circuit that ensures all the registers start with default or user-programmed settings using NVM. It operates with either an internal reference or the power supply as a reference and provides full-scale output from 0V to 5.5V. The DAC53401 includes digital slew rate control and supports basic signal generation such as square, ramp, and sawtooth waveforms. It also can generate pulse-width modulation (PWM) output with the

combination of the triangular or sawtooth waveform and the VFB terminal. The DAC53401 is also called a smart DAC device because of its advanced integrated features. This smart DAC's force-sense output, PWM output, and NVM capabilities enable system performance and control without using the software. These features allow DAC53401 to go beyond a conventional DAC's limitations that depend on a processor to function. DAC 10 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting Standard Mode operation with a clock frequency up to 100kHz, Fast Mode up to 400kHz, and Fast Mode Plus up to 1MHz. Besides, it also allows the

choice of the three least significant bits of its I2C slave address by positioning the SMD jumper labeled as ADDR SEL to an appropriate position marked as 0, 1, SCL, and SDA, providing the user with a choice of 4 I2C Slave addresses. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.

DAC 10 Click hardware overview image

Features overview

Development board

UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build

gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li

Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

UNI clicker double image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

PIC

MCU Memory (KB)

128

Silicon Vendor

Microchip

Pin count

48

RAM (Bytes)

8196

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB1
SCL
I2C Data
PB2
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

DAC 10 Click Schematic schematic

Step by step

Project assembly

UNI Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.

UNI Clicker front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for STM32F745VG front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
UNI Clicker Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for DAC 10 Click driver.

Key functions:

  • dac10_check_device_id - This function checks the communication by reading and verifying the device ID

  • dac10_enable_dac - This function enables the DAC output

  • dac10_set_output_voltage - This function sets the output voltage depending on the vref value

Open Source

Code example

This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.

/*!
 * @file main.c
 * @brief DAC10 Click example
 *
 * # Description
 * This example demonstrates the use of DAC 10 click board.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initializes the driver, checks the communication by reading and verifying the device ID,
 * and enables the DAC output.
 *
 * ## 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 taking into account the number of steps 
 * which is defined below.
 *
 * @note
 * Measure the voltage at VCC_SEL jumper and adjust the reference voltage value below for better accuracy.
 *
 * @author Stefan Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "dac10.h"

#define REFERENCE_VOLTAGE  3.3 // The reference voltage defined by the VCC_SEL on-board jumper. 
#define NUMBER_OF_STEPS    20  // The number of steps by which we will divide the entire voltage range. 

static dac10_t dac10;
static log_t logger;

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    dac10_cfg_t dac10_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 );
    Delay_ms( 100 );
    log_info( &logger, " Application Init " );

    // Click initialization.
    dac10_cfg_setup( &dac10_cfg );
    DAC10_MAP_MIKROBUS( dac10_cfg, MIKROBUS_1 );
    err_t init_flag = dac10_init( &dac10, &dac10_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) 
    {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    if ( DAC10_ERROR == dac10_check_device_id ( &dac10 ) ) 
    {
        log_error( &logger, " Check Device ID Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }
    
    dac10_enable_dac( &dac10 );
    Delay_ms( 100 );
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    float step = REFERENCE_VOLTAGE / NUMBER_OF_STEPS;
    float output_voltage = step;
    uint8_t cnt = 0;
    while ( cnt < NUMBER_OF_STEPS )
    {
        dac10_set_output_voltage ( &dac10, REFERENCE_VOLTAGE, output_voltage );
        log_printf( &logger, " DAC output voltage set to %.2f V\r\n", output_voltage );
        output_voltage += step;
        cnt++;
        Delay_ms( 2000 );
    }
}

void main ( void ) 
{
    application_init( );

    for ( ; ; ) 
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources