Stop compromising between safety and efficiency - choose our I2C isolator to optimize your system's potential and safeguard your data.
A
A
Hardware Overview
How does it work?
I2C Isolator 5 Click is based on the ISO1644, a hot-swappable bidirectional I2C isolator with enhanced EMC and GPIOs from Texas Instruments. The ISO1644 bidirectionally buffers the two I2C signals across the isolation barrier while providing 5kVRMS of galvanic isolation. The isolation barrier consists of a double capacitive silicon dioxide and includes basic and reinforced insulation devices. In addition, the ISO1644 also integrates three unidirectional CMOS isolation channels with up to 50Mbps speed, which can be used for static GPIO signal isolation. It also integrates the logic required to support
bidirectional channels. The ISO1644 supports I2C 2-Wire bidirectional data transfer between a host device and several peripheral devices, where the host MCU controls the bus, specifically the serial clock (SCL) line. The data transfer can be made in standard, fast, fast-mode plus, and high-speed mode with speeds up to 3.4Mbps. As for three GPIO lines, the ISO1644 consists of two lines in one direction and one in the opposite direction. It could be used for any GPIO purpose. This Click board™ poses a terminal with isolated SCL and SDA lines. Besides, the terminal consists of VCC and GND lines and OUTA, OUTB, and INA, labeling
the direction of the lines. Those GPIO lines are connected to the mikroBUS™ socket, thus the host MCU, via OTA, OTB, and INA pins. If that suits your needs, you can pull up the isolated I2C lines via unpopulated R6 and R7 jumpers. 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. Also, this 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
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
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 I2C Isolator 5 Click driver.
Key functions:
i2cisolator5_set_slave_address
- I2C Isolator 5 set I2C Slave address function.i2cisolator5_set_outa_state
- I2C Isolator 5 set output A state function.i2cisolator5_get_ina_state
- I2C Isolator 5 get input A state function.
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 main.c
* @brief I2C Isolator 5 Click example
*
* # Description
* This library contains API for the I2C Isolator 5 click driver.
* This demo application shows an example of an I2C Isolator 5 click
* wired to the VAV Press click for reading
* differential pressure and temperature measurement.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of I2C module and log UART.
* After driver initialization and default settings,
* the app set VAV Press click I2C slave address ( 0x5C )
* and enable device.
*
* ## Application Task
* This is an example that shows the use of an I2C Isolator 5 click board™.
* Logs pressure difference [ Pa ] and temperature [ degree Celsius ] values
* of the VAV Press click written to the I2C Isolator 5 click board™.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "i2cisolator5.h"
#define I2CISOLATOR5_VAV_PRESS_DEV_ADDR 0x5C
#define I2CISOLATOR5_VAV_PRESS_CMD_START_PRESSURE_CONVERSION 0x21
#define I2CISOLATOR5_VAV_PRESS_PRESS_SCALE_FACTOR 1200
#define I2CISOLATOR5_VAV_PRESS_TEMP_SCALE_FACTOR 72
#define I2CISOLATOR5_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE 105
#define I2CISOLATOR5_VAV_PRESS_KNOWN_TEMPERATURE_C 23.1
static i2cisolator5_t i2cisolator5;
static log_t logger;
static float diff_press;
static float temperature;
/**
* @brief I2C Isolator 5 get pressure difference and temperature function.
* @details This function reads pressure difference and temperature from the VAV Press Click.
* @return @li @c 0 - Success,
* @li @c -1 - Error.
* See #err_t definition for detailed explanation.
* @note None.
*/
err_t i2cisolator5_get_press_and_temp ( void );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
i2cisolator5_cfg_t i2cisolator5_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.
i2cisolator5_cfg_setup( &i2cisolator5_cfg );
I2CISOLATOR5_MAP_MIKROBUS( i2cisolator5_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == i2cisolator5_init( &i2cisolator5, &i2cisolator5_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_printf( &logger, " Set VAV Press Click I2C Slave Address \r\n" );
i2cisolator5_set_slave_address ( &i2cisolator5, I2CISOLATOR5_VAV_PRESS_DEV_ADDR );
Delay_ms( 100 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
if ( I2CISOLATOR5_OK == i2cisolator5_get_press_and_temp( ) )
{
log_printf( &logger, " Diff. Pressure : %.4f Pa \r\n", diff_press );
log_printf( &logger, " Temperature : %.2f C \r\n", temperature );
log_printf( &logger, "--------------------------------\r\n" );
}
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
err_t i2cisolator5_get_press_and_temp ( void )
{
err_t error_flag = I2CISOLATOR5_OK;
uint8_t rx_buf[ 4 ] = { 0 };
uint8_t tx_cmd = I2CISOLATOR5_VAV_PRESS_CMD_START_PRESSURE_CONVERSION;
int16_t readout_data;
error_flag |= i2cisolator5_write_then_read( &i2cisolator5, &tx_cmd, 1, rx_buf, 4 );
if ( I2CISOLATOR5_OK == error_flag )
{
readout_data = rx_buf[ 1 ];
readout_data <<= 8;
readout_data |= rx_buf[ 0 ];
readout_data <<= 1;
readout_data >>= 1;
diff_press = ( float ) readout_data;
diff_press /= I2CISOLATOR5_VAV_PRESS_PRESS_SCALE_FACTOR;
readout_data = rx_buf[ 3 ];
readout_data <<= 8;
readout_data |= rx_buf[ 2 ];
temperature = ( float ) readout_data;
temperature -= I2CISOLATOR5_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE;
temperature /= I2CISOLATOR5_VAV_PRESS_TEMP_SCALE_FACTOR;
temperature += I2CISOLATOR5_VAV_PRESS_KNOWN_TEMPERATURE_C;
}
return error_flag;
}
// ------------------------------------------------------------------------ END