Convert the countless reams of digital information into analog signals using DAC104S085 and PIC32MZ1024EFH064
From digits to signals
Published Aug 18, 2023
Click board™
DAC 6 Click
Dev. board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
As digital information converges into analog clarity, our solution fosters connectivity by enabling effective communication between systems, unlocking a realm of data transformation possibilities
A
A
Hardware Overview
How does it work?
DAC 6 Click is based on the DAC104S085, 10-bit resolution micro-power QUAD digital-to-analog converter with rail-to-rail output from Texas Instruments. The DAC104S085 is manufactured on a CMOS process with an architecture consisting of switches and resistor strings followed by an output buffer. The reference voltage is applied at the VREFIN pin and is shared by all four DAC outputs (A, B, C, and D). This string consists of 1024 equal-valued resistors with a switch at each junction of two resistors, plus a switch to the ground. The code loaded into the DAC register determines which switch is closed, connecting the proper node to the amplifier. The voltage reference pin of the DAC104S085 is not buffered, and because of that, it is recommended to drive the VREFIN pin by a voltage source with a low output impedance.
This is accomplished using the MCP1501, a low drift bandgap-based voltage reference from a Microchip capable of sinking and sourcing 20mA of current. The bandgap uses chopper-based amplifiers, effectively reducing the drift to zero. The reference voltage range which can be applied to the VREFIN pin is 1V to VCC (in this case, 2.048V), providing the widest possible output dynamic range with a maximum output current of 11mA per channel. The DAC 6 Click communicates with MCU using the 3-Wire SPI serial interface compatible with standard SPI, QSPI™, and MICROWIRE™ and operates at clock rates up to 40 MHz. To use the full dynamic range of the DAC104S085, it is possible to connect the VREFIN pin to the supply voltage VCC. Because of its low power consumption, a reference source may be
used as the reference input or the supply voltage, which results in accuracy and stability. The reference voltage level can be selected by positioning the SMD jumper labeled as VREF SEL to an appropriate position, selecting between a value of 2.048V and the supply voltage VCC. This Click Board™ uses the SPI communication interface with both 3.3V and 5V. The onboard SMD jumper labeled VCC SEL allows voltage selection for interfacing with 3.3V and 5V MCUs. More information about the DAC104S085’s functionality, electrical specifications, and typical performance can be found in the attached datasheet. However, the Click board™ comes equipped with a library that contains easy-to-use functions and a usage example that may be used as a reference for the development.
Features overview
Development board
PIC32MZ Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ 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.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the PIC32MZ clicker as your development board.
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 6 Click driver.
Key functions:
dac6_set_output- Function is used to set operation mode output channel and leveldac6_write_data- Sends 16-bit data to the device's input shift register.
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 Dac6 Click example
*
* # Description
* DAC 6 click carries 12-bit buffered Digital-to-Analog Converter. It converts digital value
* to the corresponding voltage level using external voltage reference.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes SPI driver.
*
* ## Application Task
* This example shows capabilities of DAC 6 click by changeing
* output values from 0 to the maximum output range on all four channels.
* Output voltage is calculated by using the equation :
* Vout = Vrefin * (set_out / 4095).
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "dac6.h"
// ------------------------------------------------------------------ VARIABLES
static dac6_t dac6;
static log_t logger;
static uint16_t n_cnt;
static float v_out;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
dac6_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.
dac6_cfg_setup( &cfg );
DAC6_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dac6_init( &dac6, &cfg );
}
void application_task ( void )
{
for ( n_cnt = 0; n_cnt < 4096; n_cnt += 315 )
{
dac6.chan = DAC6_CHANNEL_A;
dac6.op_mod = DAC6_WRITE_SPEC_UPDATE_OUTPUT;
dac6.v_ref = DAC6_V_REF_2048;
dac6.set_out = n_cnt;
v_out = dac6_set_output( &dac6 );
log_printf( &logger, " Channel A : VOUT ~ %.2f mV\r\n", v_out );
log_printf( &logger, "--------------------\r\n" );
Delay_ms( 5000 );
}
for ( n_cnt = 0; n_cnt < 4096; n_cnt += 315 )
{
dac6.chan = DAC6_CHANNEL_B;
dac6.op_mod = DAC6_WRITE_SPEC_UPDATE_OUTPUT;
dac6.v_ref = DAC6_V_REF_2048;
dac6.set_out = n_cnt;
v_out = dac6_set_output( &dac6 );
log_printf( &logger, " Channel B : VOUT ~ %.2f mV\r\n", v_out );
log_printf( &logger, "--------------------\r\n" );
Delay_ms( 5000 );
}
for ( n_cnt = 0; n_cnt < 4096; n_cnt += 315 )
{
dac6.chan = DAC6_CHANNEL_C;
dac6.op_mod = DAC6_WRITE_SPEC_UPDATE_OUTPUT;
dac6.v_ref = DAC6_V_REF_2048;
dac6.set_out = n_cnt;
v_out = dac6_set_output( &dac6 );
log_printf( &logger, " Channel C : VOUT ~ %.2f mV\r\n", v_out );
log_printf( &logger, "--------------------\r\n" );
Delay_ms( 5000 );
}
for ( n_cnt = 0; n_cnt < 4096; n_cnt += 315 )
{
dac6.chan = DAC6_CHANNEL_D;
dac6.op_mod = DAC6_WRITE_SPEC_UPDATE_OUTPUT;
dac6.v_ref = DAC6_V_REF_2048;
dac6.set_out = n_cnt;
v_out = dac6_set_output( &dac6 );
log_printf( &logger, " Channel D : VOUT ~ %.2f mV\r\n", v_out );
log_printf( &logger, "--------------------\r\n" );
Delay_ms( 5000 );
}
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
