Completely isolated I2C interface
A
A
Hardware Overview
How does it work?
I2C Isolator 4 Click is based on the MAX14937, a two-channel, 5kVRMS I2C digital isolator from Analog Devices. The MAX14937 bidirectionally buffers the two I2C signals across the isolation barrier and supports I2C clock-stretching while providing 5kVrms of galvanic isolation. It transfers digital signals between circuits with different power domains at ambient temperatures and offers glitch-free operation, excellent reliability,
and very long operational life. The wide temperature range and high isolation voltage make the device ideal for harsh industrial environments. This Click board™ also possesses two terminals labeled as VIN and SDA/SCL at the bottom of the Click board™, where VIN represents the B-side power supply of the isolator, while the other corresponds to the isolated bidirectional logic-bus terminal.
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
PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive
mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI
GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
You complete me!
Accessories
Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
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 I2C Isolator 4 Click driver.
Key functions:
i2cisolator4_generic_write
I2C Isolator 4 I2C writing function.i2cisolator4_generic_read
I2C Isolator 4 I2C reading function.i2cisolator4_set_slave_address
I2C Isolator 4 set I2C Slave address 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 I2cIsolator4 Click example
*
* # Description
* This library contains API for the I2C Isolator 4 click driver.
* This demo application shows an example of an I2C Isolator 4 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 4 click board™.
* Logs pressure difference [ Pa ] and temperature [ degree Celsius ] values
* of the VAV Press click wired to the I2C Isolator 4 click board™.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @note
* void get_dif_press_and_temp ( void ) - Get differential pressure and temperature function.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "i2cisolator4.h"
#define I2CISOLATOR4_VAV_PRESS_DEV_ADDR 0x5C
#define I2CISOLATOR4_VAV_PRESS_CMD_START_PRESSURE_CONVERSION 0x21
#define I2CISOLATOR4_VAV_PRESS_PRESS_SCALE_FACTOR 1200
#define I2CISOLATOR4_VAV_PRESS_TEMP_SCALE_FACTOR 72
#define I2CISOLATOR4_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE 105
#define I2CISOLATOR4_VAV_PRESS_KNOWN_TEMPERATURE_C 23.1
static i2cisolator4_t i2cisolator4;
static log_t logger;
static float diff_press;
static float temperature;
void get_dif_press_and_temp ( void ) {
uint8_t rx_buf[ 4 ];
int16_t readout_data;
i2cisolator4_generic_read( &i2cisolator4, I2CISOLATOR4_VAV_PRESS_CMD_START_PRESSURE_CONVERSION, &rx_buf[ 0 ], 4 );
readout_data = rx_buf[ 1 ];
readout_data <<= 9;
readout_data |= rx_buf[ 0 ];
readout_data >>= 1;
diff_press = ( float ) readout_data;
diff_press /= I2CISOLATOR4_VAV_PRESS_PRESS_SCALE_FACTOR;
readout_data = rx_buf[ 3 ];
readout_data <<= 8;
readout_data |= rx_buf[ 2 ];
temperature = ( float ) readout_data;
temperature -= I2CISOLATOR4_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE;
temperature /= I2CISOLATOR4_VAV_PRESS_TEMP_SCALE_FACTOR;
temperature += I2CISOLATOR4_VAV_PRESS_KNOWN_TEMPERATURE_C;
}
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
i2cisolator4_cfg_t i2cisolator4_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.
i2cisolator4_cfg_setup( &i2cisolator4_cfg );
I2CISOLATOR4_MAP_MIKROBUS( i2cisolator4_cfg, MIKROBUS_1 );
err_t init_flag = i2cisolator4_init( &i2cisolator4, &i2cisolator4_cfg );
if ( init_flag == I2C_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
Delay_ms( 100 );
log_printf( &logger, "--------------------------------\r\n" );
log_printf( &logger, " Set I2C Slave Address \r\n" );
i2cisolator4_set_slave_address ( &i2cisolator4, I2CISOLATOR4_VAV_PRESS_DEV_ADDR );
Delay_ms( 100 );
}
void application_task ( void ) {
get_dif_press_and_temp( );
log_printf( &logger, " Diff. Pressure : %.4f Pa\r\n", diff_press );
log_printf( &logger, " Temperature : %.4f C\r\n", temperature );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms( 2000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END