With high accuracy at its core, our solution bridges the gap between digital data and analog interpretation, enhancing your ability to derive meaning and make informed decisions
A
A
Hardware Overview
How does it work?
DAC 2 Click is based on the LTC2601, a single 16-bit rail-to-rail voltage output digital-to-analog converter from Analog Devices with built-in high-performance output buffers. The DAC output (VOUT terminal) can directly drive capacitive loads up to 1000pF or current loads up to 15mA and maintains good linearity to within millivolts of both supply rails. The LTC2601's guaranteed monotonic performance is ideal for digital calibration, trim/adjust, and level setting applications in various applications. This Click board™ communicates with MCU through a 3-Wire SPI interface (write-only) with a maximum
frequency of 50MHz. The LTC2601 also provides an asynchronous clear pin routed to the RST pin of the mikroBUS™ socket, which is required in many servo and control applications. A low-level logic at this level-triggered pin clears all registers and causes the DAC voltage outputs to drop to 0V. It also sets all registers to midscale code and causes the DAC voltage outputs to go to midscale. Like any DAC, the MCP3551 uses a reference voltage as the differential voltage range. The reference voltage level selection is performed by positioning the SMD jumper labeled REF SEL to an appropriate position, choosing between 3.3V or 5V
provided by the mikroBUS™ power rails or 4.096V provided by MCP1541. Those voltages may be used as the reference input that results in accuracy and stability. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the PWR 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.
Features overview
Development board
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for DAC 2 Click driver.
Key functions:
dac2_default_cfg
- This function executes default configuration for LTC2601dac2_write_output_voltage_procentage
- This function required percentage value ( from 0% to 100% ) convert to digital input and transforms it to the output voltage from 0 to Vref [mV]
Open Source
Code example
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.
/*!
* \file
* \brief Dac2 Click example
*
* # Description
* DAC 2 click represents a 16-bit digital-to-analog converter.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Application Init performs Logger and Click initialization.
*
* ## Application Task
* This example of the DAC 2 communicates with MCU through the SPI communication,
* send digital input ( form 0 to 100 with step 1 ) and transforms it
* to the output voltage, ranging from 0 to Vref [mV].
*
* \author Mihajlo Djordjevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "dac2.h"
// ------------------------------------------------------------------ VARIABLES
static dac2_t dac2;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
dac2_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 ----" );
Delay_ms ( 1000 );
// Click initialization.
dac2_cfg_setup( &cfg );
DAC2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dac2_init( &dac2, &cfg );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " ----- DAC 2 Click ----- \r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
dac2_default_cfg( &dac2 );
Delay_ms ( 1000 );
log_printf( &logger, " -- Initialization done --\r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
}
void application_task ( void )
{
uint16_t voltage_out;
uint8_t value_pct;
for ( value_pct = 0; value_pct <= 100; value_pct += 10 )
{
dac2_write_output_voltage_procentage( &dac2, value_pct );
voltage_out = value_pct * 50;
log_printf( &logger, "Voltage Output: %d mV\r\n", voltage_out );
voltage_out = value_pct;
log_printf( &logger, "Percentage Output: %d %%\r\n", voltage_out );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 5000 );
}
log_printf( &logger, "###############################\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END