Engineered for resilience in challenging environments, this robust high-speed transceiver extends a single-master I2C bus at speeds up to 400kbps, utilizing the CAN-physical layer to ensure reliable communication even in harsh or noisy conditions
A
A
Hardware Overview
How does it work?
I2C to CAN Click is based on the LT3960, I2C to CAN-Physical transceiver used to send and receive I2C data up to 400kbps using the CAN-Physical layer for differential signaling over twisted pair connections from Analog Devices. Using two integrated CAN transceivers, the LT3960 creates a differential proxy for each single-ended I2C clock and data signal capable of crossing harsh or noisy environments across two twisted pairs. Each transceiver consists of a transmitter and receiver capable of quickly converting an I2C dominant signal into a differential dominant signal and vice versa. Also, it extends functionality in environments with high common-mode voltages due to electrical noise or local ground potential differences. I2C to CAN Click communicates with MCU using the standard I2C 2-Wire interface to
read data and configure settings, supporting Fast Mode operation with a clock frequency up to 400kHz. The LT3960 provides a mode selection feature selectable via jumper labeled as MODE, where the user can choose between the Master or Slave mode of operation. The SHD pin routed to the CS pin of the mikroBUS™ socket is used to put the LT3960 in a low-power Shutdown mode, disabling both the LDO and transceivers and allowing selection between Master and Slave modes when enabled. The selection between Master and Slave modes is performed by positioning the SMD jumper labeled as MODE to an appropriate position marked as SLV and MST. When a jumper is on the MST position, Master mode is selected, and the EN/MODE pin of the LT3960 is tied to a high logic state while floating
this pin, more precisely positioning the SMD jumper to an SLV position, allows the user to select Slave mode of operation. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the VCC SEL jumper. It allows both 3.3V and 5V capable MCUs to use the I2C communication lines properly. Additionally, there is a possibility for the LT3960 power supply selection via jumper labeled as VIN SEL to supply the LT3960 from an external power supply terminal in the range from 4 to 60V or with VCC voltage levels from mikroBUS™ power rails. 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
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/PIC18F57Q43.jpeg)
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
Click board™ Schematic
![I2C to CAN Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790bf-6ee1-6c34-a116-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
This Click board can be interfaced and monitored in two ways:
Application Output
- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal
- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for I2C to CAN Click driver.
Key functions:
i2ctocan_set_slave_address
- Set I2C Slave address functioni2ctocan_generic_write
- I2C to CAN I2C writing functioni2ctocan_generic_read
- I2C to CAN I2C reading 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 I2cToCan Click example
*
* # Description
* This library contains API for the I2C to CAN click driver.
* This demo application shows an example of an I2C CAN 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 to CAN click board™.
* Logs pressure difference [ Pa ] and temperature [ degree Celsius ] values
* of the VAV Press click wired to the I2C to CAN 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 "i2ctocan.h"
#define I2CTOCAN_VAV_PRESS_DEV_ADDR 0x5C
#define I2CTOCAN_VAV_PRESS_CMD_START_PRESSURE_CONVERSION 0x21
#define I2CTOCAN_VAV_PRESS_PRESS_SCALE_FACTOR 1200
#define I2CTOCAN_VAV_PRESS_TEMP_SCALE_FACTOR 72
#define I2CTOCAN_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE 105
#define I2CTOCAN_VAV_PRESS_KNOWN_TEMPERATURE_C 23.1
static i2ctocan_t i2ctocan;
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;
i2ctocan_generic_read( &i2ctocan, I2CTOCAN_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 /= I2CTOCAN_VAV_PRESS_PRESS_SCALE_FACTOR;
readout_data = rx_buf[ 3 ];
readout_data <<= 8;
readout_data |= rx_buf[ 2 ];
temperature = ( float ) readout_data;
temperature -= I2CTOCAN_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE;
temperature /= I2CTOCAN_VAV_PRESS_TEMP_SCALE_FACTOR;
temperature += I2CTOCAN_VAV_PRESS_KNOWN_TEMPERATURE_C;
}
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
i2ctocan_cfg_t i2ctocan_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_printf( &logger, "\r\n" );
log_info( &logger, " Application Init " );
// Click initialization.
i2ctocan_cfg_setup( &i2ctocan_cfg );
I2CTOCAN_MAP_MIKROBUS( i2ctocan_cfg, MIKROBUS_1 );
err_t init_flag = i2ctocan_init( &i2ctocan, &i2ctocan_cfg );
if ( init_flag == I2C_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
i2ctocan_default_cfg ( &i2ctocan );
log_info( &logger, " Application Task " );
Delay_ms ( 100 );
log_printf( &logger, "--------------------------------\r\n" );
log_printf( &logger, " Set I2C Slave Address \r\n" );
i2ctocan_set_slave_address ( &i2ctocan, I2CTOCAN_VAV_PRESS_DEV_ADDR );
Delay_ms ( 100 );
log_printf( &logger, "--------------------------------\r\n" );
log_printf( &logger, " Enable Device \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
i2ctocan_enable_device( &i2ctocan );
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 ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* @file main.c
* @brief I2cToCan Click example
*
* # Description
* This library contains API for the I2C to CAN click driver.
* This demo application shows an example of an I2C CAN 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 to CAN click board™.
* Logs pressure difference [ Pa ] and temperature [ degree Celsius ] values
* of the VAV Press click wired to the I2C to CAN 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 "i2ctocan.h"
#define I2CTOCAN_VAV_PRESS_DEV_ADDR 0x5C
#define I2CTOCAN_VAV_PRESS_CMD_START_PRESSURE_CONVERSION 0x21
#define I2CTOCAN_VAV_PRESS_PRESS_SCALE_FACTOR 1200
#define I2CTOCAN_VAV_PRESS_TEMP_SCALE_FACTOR 72
#define I2CTOCAN_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE 105
#define I2CTOCAN_VAV_PRESS_KNOWN_TEMPERATURE_C 23.1
static i2ctocan_t i2ctocan;
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;
i2ctocan_generic_read( &i2ctocan, I2CTOCAN_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 /= I2CTOCAN_VAV_PRESS_PRESS_SCALE_FACTOR;
readout_data = rx_buf[ 3 ];
readout_data <<= 8;
readout_data |= rx_buf[ 2 ];
temperature = ( float ) readout_data;
temperature -= I2CTOCAN_VAV_PRESS_READOUT_AT_KNOWN_TEMPERATURE;
temperature /= I2CTOCAN_VAV_PRESS_TEMP_SCALE_FACTOR;
temperature += I2CTOCAN_VAV_PRESS_KNOWN_TEMPERATURE_C;
}
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
i2ctocan_cfg_t i2ctocan_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_printf( &logger, "\r\n" );
log_info( &logger, " Application Init " );
// Click initialization.
i2ctocan_cfg_setup( &i2ctocan_cfg );
I2CTOCAN_MAP_MIKROBUS( i2ctocan_cfg, MIKROBUS_1 );
err_t init_flag = i2ctocan_init( &i2ctocan, &i2ctocan_cfg );
if ( init_flag == I2C_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
i2ctocan_default_cfg ( &i2ctocan );
log_info( &logger, " Application Task " );
Delay_ms ( 100 );
log_printf( &logger, "--------------------------------\r\n" );
log_printf( &logger, " Set I2C Slave Address \r\n" );
i2ctocan_set_slave_address ( &i2ctocan, I2CTOCAN_VAV_PRESS_DEV_ADDR );
Delay_ms ( 100 );
log_printf( &logger, "--------------------------------\r\n" );
log_printf( &logger, " Enable Device \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
i2ctocan_enable_device( &i2ctocan );
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 ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END