Connect and control various types of sensors and actuators with AD74115H, ADP1034 and STM32F091RC
From analog signals to digital commands: AD-SWIO shapes your control
Published Feb 26, 2024
Click board™
AD-SWIO 3 Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Manage and control different devices in industrial and automation setups, ensuring safety and flexibility in the process
A
A
Hardware Overview
How does it work?
AD-SWIO 3 Click is based on the AD74115H, a single-channel, software-configurable input and output with HART mode, and ADP1034, a 3-channel isolated micropower management unit with seven digital isolators and programmable power control both from Analog Devices. The AD74115H has a single-channel input and output, which can be configured as voltage input, current input, voltage output, current output, digital input, digital output, 2/3/4-wire RTD measurement, or thermocouple measurement input. It features a 16-bit, Σ-Δ analog-to-digital converter (ADC) and a 14-bit digital-to-analog converter (DAC), with a high accuracy 2.5V on-chip reference that can be used both for ADC and DAC. You can connect the desired load to terminals labeled I/OP and I/ON for analog output, analog input, and digital input functions. To apply a stimulus to the two auxiliary high-voltage sense pins, use I/O EXT1 and I/O
EXT2 terminals. The resistance measurements can be made between those four terminals, depending on the number of wires RTD. For instance, take 2-wire resistance measurements between the I/OP and I/ON terminals. The integrated HART modem can transmit and receive signals to and from the I/OP terminal. For more info, check the datasheet. Four LEDs (GPIOA, GPIOB, GPIOC, GPIOD) can be configured in several ways to represent digital input, digital output, external or internal conditions, and more. An onboard thermistor is connected to the AD74115H, which can measure the board's temperature. The ADP1034 provides power and isolation to the AD74115H. A flyback regulator supply voltage of 24V can be applied over the VINP terminal. You can control the flyback regulator slew rate over the SLEW jumper between the slowest and normal as default. You can also choose the highest by leaving the SLEW pin open. The
ZA9644-AED, a flyback transformer from Coilcraft, is used for flyback regulator operation. AD-SWIO 3 Click uses a standard 4-wire SPI serial interface of the AD74115H through the isolation that provides the ADP1034 to communicate with the host MCU. You can reset the AD74115H over the RST pin. When a new sequence of ADC conversion is ready to be read, the RDY will be asserted. Also, the alert ALR pin will be asserted when the alert condition is met. All those lines pass through an isolation barrier of the ADP1034 on its way to the host MCU. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used for further development.
Features overview
Development board
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 Nucleo-64 with STM32F091RC MCU as your development board.
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for AD-SWIO 3 Click driver.
Key functions:
adswio3_get_voltage_input- This function reads the raw ADC value and converts them to a proportional voltage level measured by the voltage between the I/OP and I/ON screw terminals.adswio3_get_diag_res- This function is used to read the desired diagnostic conversion results.adswio3_set_adc_cnv- This function is used to control the ADC conversions that must be performed.
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 AD-SWIO 3 Click example
*
* # Description
* This library contains API for the AD-SWIO 3 Click driver
* for measurements of the analog output, analog input, digital input,
* resistance temperature detector (RTD), and thermocouple measurements.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of SPI and log UART.
* After driver initialization, the app executes a default configuration
* that enables and sets it to measure IOP/ION voltage input from 0V to 12V,
* with 4.8k SPS and enabled four diagnostics measurements (AVDD, VASS, VACC and LVIN).
*
* ## Application Task
* This example demonstrates the use of the AD-SWIO 3 Click board.
* The demo application reads and displays the voltage level input,
* measured by the voltage between the I/OP and I/ON screw terminals
* and NTC thermistor temperature in degrees Celsius.
* Results are being sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "adswio3.h"
static adswio3_t adswio3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
adswio3_cfg_t adswio3_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.
adswio3_cfg_setup( &adswio3_cfg );
ADSWIO3_MAP_MIKROBUS( adswio3_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == adswio3_init( &adswio3, &adswio3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( ADSWIO3_ERROR == adswio3_default_cfg ( &adswio3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
Delay_ms( 100 );
for ( uint8_t n_cnt = ADSWIO3_GPIO_CONFIG_SEL_A; n_cnt <= ADSWIO3_GPIO_CONFIG_SEL_D; n_cnt ++ )
{
if ( ADSWIO3_ERROR == adswio3_set_gpio_config( &adswio3, n_cnt,
ADSWIO3_GPIO_CONFIG_GPO_DATA_HIGH,
ADSWIO3_GPIO_CONFIG_GP_WK_PD_DIS,
ADSWIO3_GPIO_CONFIG_MODE_OUT ) )
{
log_error( &logger, " Set GPIO configuration" );
for ( ; ; );
}
Delay_ms( 100 );
}
float diag_vtg = 0;
log_printf( &logger, "_________________________\r\n" );
log_printf( &logger, " > Diagnostic Voltages <\r\n" );
if ( ADSWIO3_OK == adswio3_get_diag_vtg( &adswio3, ADSWIO3_DIAG_RESULT_SEL_0, &diag_vtg ) )
{
log_printf( &logger, " AVDD: %.2f V\r\n", diag_vtg );
Delay_ms( 100 );
}
if ( ADSWIO3_OK == adswio3_get_diag_vtg( &adswio3, ADSWIO3_DIAG_RESULT_SEL_1, &diag_vtg ) )
{
log_printf( &logger, " VASS: %.2f V\r\n", diag_vtg );
Delay_ms( 100 );
}
if ( ADSWIO3_OK == adswio3_get_diag_vtg( &adswio3, ADSWIO3_DIAG_RESULT_SEL_2, &diag_vtg ) )
{
log_printf( &logger, " VACC: %.2f V\r\n", diag_vtg );
Delay_ms( 100 );
}
if ( ADSWIO3_OK == adswio3_get_diag_vtg( &adswio3, ADSWIO3_DIAG_RESULT_SEL_3, &diag_vtg ) )
{
log_printf( &logger, " LVIN: %.2f V\r\n", diag_vtg );
Delay_ms( 100 );
}
log_printf( &logger, "_________________________\r\n" );
Delay_ms( 1000 );
}
void application_task ( void )
{
float ntc_temp = 0, iop_ion_vtg = 0;
if ( ADSWIO3_OK == adswio3_get_ntc_temp( &adswio3, ADSWIO3_DIAG_RESULT_SEL_3, &ntc_temp ) )
{
log_printf( &logger, " NTC Temperature: %.2f degC\r\n", ntc_temp );
Delay_ms( 100 );
}
if ( ADSWIO3_OK == adswio3_get_voltage_input( &adswio3, 0, &iop_ion_vtg ) )
{
log_printf( &logger, "IOP/ION Voltage: %.3f V\r\n", iop_ion_vtg );
Delay_ms( 100 );
}
log_printf( &logger, "_________________________\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
