30 min

Create a highly compact, high-performance DAQ solution with ADAQ7768-1 and STM32L073RZ

Streamline data collection - save time and effort

DAQ Click with Fusion for STM32 v8

Published Jun 01, 2023

Click board™

DAQ Click

Development board

Fusion for STM32 v8


NECTO Studio



Simplify complex data acquisition challenges with our user-friendly solution



Hardware Overview

How does it work?

DAQ Click is based on the ADAQ7768-1, a 24-bit precision data acquisition μModule system that encapsulates signal conditioning, conversion, and processing blocks into one SiP from Analog Devices, enabling rapid development of highly compact, high-performance precision DAQ systems. The ADAQ7768-1 consists of low noise, high bandwidth programmable gain instrumentation amplifier (PGIA) capable of amplifying and attenuating while maintaining high input impedance. Also, it has a linear phase anti-aliasing filter, a high-performance 24-bit sigma-delta ADC with a programmable digital filter, a low dropout linear regulator, reference buffers, and critical passive components required for the signal chain. The wide common-mode input range of the ADAQ7768-1 allows it to accept a wide variety of signal swings. It supports a fully differential input signal connection with a maximum voltage range of ±12V with an excellent common-mode rejection ratio. The input signal is fully buffered with a low input bias current, enabling the ADAQ7768-1 to directly interface to sensors with high output impedance. The ADAQ7768-1‘s PGA requires a voltage of ±15V to supply the frontend amplifiers. Therefore, a dual-channel low-noise bias generator, the LT3095 from Analog Devices, provides a +15V out of 3V3 mikroBUS™ rail.

A -15V supply is obtained by combining a step-down regulator ADP2300 and a small low-noise LDO ADP7182, both from Analog Devices, also out of 3V3 mikroBUS™ rail. The PGIA has six gain settings capable of varying input ranges from ±0.197V to ±12.603V fully differential input signal, which can be configured with GAIN pins controlled by three multifunction GPIO pins of the ADAQ7768-1 (MODE1-3). An integrated 4th-order low-pass analog filter combined with the user-programmable digital filter ensures the signal chain is fully protected against the high-frequency noise and out-of-band tones presented at the input node. This filter is designed to achieve high phase linearity and maximum in-band magnitude response flatness. Inside the ADAQ7768-1 is a high-performance, 24-bit precision, single-channel Sigma-Delta converter with excellent AC performance and DC precision and throughput rate of 256kSPS from a 16.384MHz onboard crystal (clock source). In addition to the internal clock source, the user can use an external clock brought to the connector labeled as EXT CLK. The clock source is selected by positioning a jumper marked as INT/EXT. Since the LT3095 generates two independent supplies, in addition to -15V, this regulator also provides the 5.3V voltage required to power the internal LDO of the ADAQ7768-1, whose output

supplies an onboard voltage reference - the ADR4540This Click board™ also allows the user to filter the reference voltage itself, with the optional use of a reference buffer implemented using OpAmp, ADA4807-1, which provides high-speed performance with DC precision, low noise distortion, and power to maintain the accuracy of the reference. This Click board™ communicates with MCU through a standard SPI interface to program the internal registers for complete control of the ADAQ7768-1. In addition, it uses several GPIO pins, such as the reset pin routed to the RST pin on the mikroBUS™ socket, which with a low logic level puts the module into a Reset state, an additional data-ready signal, routed on the INT pin of the mikroBUS™ socket labeled as RDY, indicating that new data is ready for the host, and one extra user-configurable general-purpose I/O pin labeled as IO3 routed to the PWM pin on the mikroBUS™ socket. This Click board™ can only be operated with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.


Features overview

Development board

Fusion for STM32 v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from STMicroelectronics, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for STM32 v8 provides a fluid and immersive working experience, allowing

access anywhere and under any circumstances at any time. Each part of the Fusion for STM32 v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.

Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for STM32 v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

Fusion for STM32 v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation


ARM Cortex-M0

MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

SPI Chip Select
SPI Clock
Power Supply
General-Purpose I/O
Data Ready

Take a closer look


DAQ Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Fusion for STM32 v8 as your development board.

Fusion for PIC v8 front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
v8 SiBRAIN 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 Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

Software Support

Library Description

This library contains API for DAQ Click driver.

Key functions:

  • daq_set_gain Set gain range.

  • daq_read_data Reading adc data.

  • daq_calculate_voltage Convert data from raw ADC to voltage.

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 DAQ Click example
 * # Description
 * This example showcases ability of the device to read ADC 
 * data and calculate voltage for set configuration.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initialization of communication modules (SPI, UART) and
 * additional pins for controling device. Resets device and
 * then configures default configuration and sets read range
 * by setting gain to +-12V. In the end reads vendor and 
 * device ID to confirm communication.
 * ## Application Task
 * Reads ADC data and calculates voltage from it, every 0.3 seconds.
 * @author Luka Filipovic

#include "board.h"
#include "log.h"
#include "daq.h"

static daq_t daq;
static log_t logger;

void application_init ( void ) 
    log_cfg_t log_cfg;  /**< Logger config object. */
    daq_cfg_t daq_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.
    daq_cfg_setup( &daq_cfg );
    DAQ_MAP_MIKROBUS( daq_cfg, MIKROBUS_1 );
    err_t init_flag  = daq_init( &daq, &daq_cfg );
    if ( SPI_MASTER_ERROR == init_flag ) 
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    if ( daq_default_cfg ( &daq ) ) 
        log_error( &logger, " Default configuration. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    uint8_t id = 0;
    daq_generic_read( &daq, DAQ_REG_VENDOR_H, &id, 1 );
    log_printf( &logger, " > Vendor: \t0x%.2X", ( uint16_t )id );
    daq_generic_read( &daq, DAQ_REG_VENDOR_L, &id, 1 );
    log_printf( &logger, "%.2X\r\n", ( uint16_t )id );
    daq_generic_read( &daq, DAQ_REG_PRODUCT_ID_H, &id, 1 );
    log_printf( &logger, " > ID: \t\t0x%.2X", ( uint16_t )id );
    daq_generic_read( &daq, DAQ_REG_PRODUCT_ID_L, &id, 1 );
    log_printf( &logger, "%.2X\r\n", ( uint16_t )id );
    Delay_ms( 1000 );
    log_info( &logger, " Application Task " );

void application_task ( void ) 
    int32_t adc_data = 0;
    float voltage = 0.0;
    daq_read_data( &daq, &adc_data );
    daq_calculate_voltage( &daq, adc_data, &voltage );
    log_printf( &logger, " > Data: %ld\r\n", adc_data );
    log_printf( &logger, " > Voltage: %.2f\r\n", voltage );
    log_printf( &logger, "***********************************\r\n" );
    Delay_ms( 300 );  

void main ( void ) 
    application_init( );

    for ( ; ; ) 
        application_task( );

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

Additional Support