Enhance the performance of your designs with the power of our Analog-To-Digital converter
A
A
Hardware Overview
How does it work?
ADC 7 Click is based on the LTC2500-32, a 32-bit oversampling ADC with a configurable digital filter from Analog Devices. The integrated configurable filter is used to process the data from the 32-bit successive approximation register (SAR) core, providing a very low noise on the output, with a high dynamic range of up to 148dB. It also simplifies the design, as it relaxes anti-aliasing filter requirements for the input signal. The LTC2500-32 ADC also allows external reference voltage; therefore, the Click board™ uses 4.096V from a tiny fixed reference voltage IC from Microchip, the MCP1541. There is a two-pole screw terminal on the Click board™, with its inputs routed to the +IN and -IN pins of the ADC IC. The input signal can be bipolar, unipolar, or differential, swinging from 0 to VREF. Inputs are buffered with two LTC2057 operational amplifiers. These low-noise op-amps adjust the input impedance, as the LTC2500-32 ADC performs optimally when driven with low-impedance sources. The inputs are DC coupled - no decoupling capacitors are used on the input signal path. The LTC2500-32 has two SDO pins available (dual SPI interface), yet only SDOA pin is used on this Click board™, offering conversion data from the programmable digital filter. The RDLA pin should be set to a LOW logic level to initiate the SPI communication. It is routed to the CS pin of the mikroBUS™, while the SDOA pin is routed to the MISO pin of the mikroBUS™, labeled as SDO. Configured like this, it is possible to use the standard
four-pin SPI interface of the mikroBUS™ to communicate with the Click board™. The digital filter can be programmed via the SPI interface (SDI pin of the mikroBUS™), or it can use the PRE pin of the ADC IC. When the PRE pin is set to a HIGH logic level, a logic state on the SDI pin will be used to select one of two filters presets. Otherwise, the filter can be configured via the SPI interface when the PRE pin is set to a LOW logic level. PRE pin is routed to the RST pin of the mikroBUS™ and labeled as PRE. This IC uses an external signal to initiate the conversion process. The internal conversion process starts when a rising edge appears on the MCLK pin. For optimal performance, the manufacturer recommends that the external signal pulse duration should be 40nS. The MCLK pin is routed to the PWM pin of the mikroBUS™ and is labeled as MCK. After a rising edge on the MCLK pin, the ADC starts sampling by comparing the input voltage with the binary-weighted fractions of the reference voltage. The sampled input is then passed through the successive approximation algorithm (SAR ADC type). The conversion data comprises 24 bits for the differential voltage, 7 bits for the common mode voltage, and one flag bit used as a signal overflow indicator (VIN > VREF). This data is then passed to the filter section, which stores a 32-bit processed value on the output register. The ADC IC compares the differential input voltage with the 2 × VREF, divided into 232 levels, resulting in a 1.9mV resolution (using 4.096V as a reference).
The wide common-mode input range (from 0V up to VREF), coupled with the high common-mode rejection rate, allows all types of signals to be sampled by the device: pseudo-differential unipolar, pseudo-differential bipolar, and fully differential. It is a unique feature of the LTC2500-32 ADC device. During the conversion phase, the BUSY pin is kept at the HIGH logic level (Hi-Z). This pin is driven to a LOW logic level when the conversion ends. The BUSY pin indicates the conversion-in-progress state and is routed to the mikroBUS™ INT pin, labeled as BSY. Another pin of the LTC2500-32 ADC with a similar function indicates that data is ready to be read at the output register. This pin is labeled as DRL and routed to the mikroBUS™ AN pin. By using these pins as the interrupt sources, the host MCU can achieve optimized data acquisition timing, not having to poll the ADC until it gets ready. The Click board™ uses both 3.3V and 5V rails of the mikroBUS™.The 3.3V rail provides the operating voltage for the ADC IC, which is 2.5V. Therefore, a small LDO is used to obtain this voltage. The 5V rail of the mikroBUS™ is used as the input voltage for the MCP1541 reference voltage source. Since the logic section of the LTC2500-32 ADC can operate with voltages from 1.8V up to 5V, no additional communication level shifting ICs are required, and the Click board™ can operate with both 3.3V and 5V MCUs.
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 ADC 7 Click driver.
Key functions:
adc7_set_config
Function performs the device configuration by sending configuration dataadc7_start_conv_cycle
Function generates clock signal on MCK pin and on that way starts conversionadc7_read_results
Function reads voltage value from AD converter and calculates this value to 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 ADC7 Click example
*
* # Description
* This application collects data from the analog signal, calculates and logs the
* converted voltage value.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver and performs configuration for conversion cycles.
*
* ## Application Task
* Performs the determined number of conversion cycles which are necessary for averaging.
* When all conversion cycles are done, it reads the converted voltage value.
* Results will be logged on UART terminal every second.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "adc7.h"
// ------------------------------------------------------------------ VARIABLES
static adc7_t adc7;
static log_t logger;
static float voltage_data;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
adc7_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 ( 100 );
// Click initialization.
adc7_cfg_setup( &cfg );
ADC7_MAP_MIKROBUS( cfg, MIKROBUS_1 );
adc7_init( &adc7, &cfg );
adc7_default_cfg( &adc7 );
}
void application_task ( void )
{
adc7_start_conv_cycle( &adc7 );
adc7_read_results( &adc7, &voltage_data );
log_printf( &logger, "Voltage: %.2f mV\r\n", voltage_data );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:ADC