Convert analog to digital signals with AD7091R and MK22FN512VLH12 with additional electrical isolation between them
Isolate and digitize with precision
Published May 31, 2023
Click board™
ISO ADC 2 Click
Dev Board
Kinetis Clicker
Compiler
NECTO Studio
MCU
MK22FN512VLH12
Unleash the power of isolation with our cutting-edge A/D converter!
A
A
Hardware Overview
How does it work?
ISO ADC 2 Click is based on the AD7091R, a 12-bit successive-approximation analog-to-digital converter (ADC) with an isolated DC-DC converter from Analog Devices. This Click board™ allows single-supply operation and consists of active Analog Devices components: AD8616, a level shifting circuit; AD7091R, an ADC stage; and ADuM5401, an output isolation stage. The AD8616 is chosen for this application because of its low offset voltage, low bias current, and low noise. The output of the OpAmp is 0.1V to 2.4V, which matches the input range of the ADC (0V to 2.5V) with a 100mV safety margin to maintain linearity. A single-pole RC filter (R2/C9) follows the OpAmp output stage to reduce the out-of-band noise. The next part of the circuit is the AD7091R, ADC chosen because of its
ultralow power, which is significantly lower than any competitive A/D converter. It features a power-down option, implemented across the serial interface to save power between conversions, described in the Modes of Operation section in the datasheet. After a successful conversion, the ADC sends the data to the MCU through galvanic isolation provided by the ADuM5401 quad-channel digital isolator with an integrated DC-DC converter. The isolator has a secondary side controller architecture with isolated pulse-width modulation (PWM) feedback, and it works on the principle common to most switching power supplies. The ISO ADC 2 Click communicates with MCU using the 3-wire SPI serial interface that operates at clock rates up to 50MHz used for accessing data from the result register
and controlling the device's modes of operation. The CONVST signal of the AD7091R routed to the RST pin on the mikroBUS™ is used to initiate the conversion process, data acquisition, and select the operation mode. This ADC requires the user to initiate a software reset upon Power-Up, and it should be noted that failure to apply the correct software reset command may result in a device malfunction. 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. However, the 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
Kinetis 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 ARM Cortex-M4 microcontroller, the MK22FN512VLH12 from NXP Semiconductor, 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 Kinetis Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Kinetis Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for Kinetis programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB-MiniAB connection provides 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. Kinetis 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
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
NXP
Pin count
64
RAM (Bytes)
131072
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Kinetis Clicker as your development board.
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.
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™.
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.
Software Support
Library Description
This library contains API for ISO ADC 2 Click driver.
Key functions:
uint16_t isoadc2_read_adc ( void )Function for reading 12bit ADC datauint16_t isoadc2_get_mv ( uint16_t adc_data )Function for converting ADC to mV data
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 IsoAdc2 Click example
*
* # Description
* This is an example that demonstrates the use of the ISO ADC 2 Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of SPI module and additional GPIO pins.
*
* ## Application Task
* Every second reads ADC data and voltage in mV and logs result.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "isoadc2.h"
static isoadc2_t isoadc2;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
isoadc2_cfg_t isoadc2_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.
isoadc2_cfg_setup( &isoadc2_cfg );
ISOADC2_MAP_MIKROBUS( isoadc2_cfg, MIKROBUS_1 );
err_t init_flag = isoadc2_init( &isoadc2, &isoadc2_cfg );
if ( SPI_MASTER_ERROR == init_flag ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
uint16_t rx_data;
uint16_t mv_data;
isoadc2_read_adc( &isoadc2, &rx_data );
Delay_ms( 100 );
isoadc2_get_mv( &isoadc2, &mv_data );
log_printf( &logger, " ADC: %d \r\n", rx_data );
log_printf( &logger, " VIN: %d mV\r\n", mv_data );
log_printf( &logger, "---------------\r\n" );
Delay_ms( 1000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
