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
Arduino UNO is a versatile microcontroller board built around the ATmega328P chip. It offers extensive connectivity options for various projects, featuring 14 digital input/output pins, six of which are PWM-capable, along with six analog inputs. Its core components include a 16MHz ceramic resonator, a USB connection, a power jack, an
ICSP header, and a reset button, providing everything necessary to power and program the board. The Uno is ready to go, whether connected to a computer via USB or powered by an AC-to-DC adapter or battery. As the first USB Arduino board, it serves as the benchmark for the Arduino platform, with "Uno" symbolizing its status as the
first in a series. This name choice, meaning "one" in Italian, commemorates the launch of Arduino Software (IDE) 1.0. Initially introduced alongside version 1.0 of the Arduino Software (IDE), the Uno has since become the foundational model for subsequent Arduino releases, embodying the platform's evolution.
Microcontroller Overview
MCU Card / MCU
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/ATmega328P.jpeg)
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
28
RAM (Bytes)
2048
You complete me!
Accessories
Click Shield for Arduino UNO has two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the Arduino UNO board without effort. The Arduino Uno, a microcontroller board based on the ATmega328P, provides an affordable and flexible way for users to try out new concepts and build prototypes with the ATmega328P microcontroller from various combinations of performance, power consumption, and features. The Arduino Uno has 14 digital input/output pins (of which six can be used as PWM outputs), six analog inputs, a 16 MHz ceramic resonator (CSTCE16M0V53-R0), a USB connection, a power jack, an ICSP header, and reset button. Most of the ATmega328P 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 Arduino UNO board with our Click Shield for Arduino UNO, 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
![I2C Isolator 5 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee7e4e3-386a-6796-9f2f-0242ac120003/I2C-Isolator-5-click-v100-Schematic-1.png)
Step by step
Project assembly
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.
![Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed554e-d80f-6694-8cb9-02420a000272/AP-Step1.jpg)
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™.
![Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-3c0f-6800-a19f-02420a000272/AP-Step3.jpg)
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.
![Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-d4d0-6b20-a348-02420a000272/AP-Step4.jpg)
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
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 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