canisolator

---

CAN Isolator Click

CAN Isolator Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.

---

Click Library

• Author : MikroE Team
• Date : Jan 2020.
• Type : UART type

Software Support

Example Description

This is a example which demonstrates the use of Can Isolator Click board.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.CanIsolator

Example Key Functions

• canisolator_cfg_setup Config Object Initialization function.

void canisolator_cfg_setup ( canisolator_cfg_t *cfg );

• canisolator_init Initialization function.

err_t canisolator_init ( canisolator_t *ctx, canisolator_cfg_t *cfg );

• canisolator_default_cfg Click Default Configuration function.

void canisolator_default_cfg ( canisolator_t *ctx );

• canisolator_generic_multi_write Generic multi write function.

void canisolator_generic_multi_write ( canisolator_t *ctx, canisolator_data_t *data_buf,  uart_length_t len );

• canisolator_generic_multi_read Generic multi read function.

void canisolator_generic_multi_read ( canisolator_t *ctx, canisolator_data_t *data_buf,  uart_length_t len );

• canisolator_generic_single_read Generic single read function.

canisolator_data_t canisolator_generic_single_read ( canisolator_t *ctx );

• canisolator_generic_single_write Generic single write function.

void canisolator_generic_single_write ( canisolator_t *ctx, canisolator_data_t tx_data );

Application Init

Configuring Clicks and log objects.

void application_init ( void )
{
    log_cfg_t log_cfg;
    canisolator_cfg_t cfg;

    /** 
     * 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, "---- Application Init ----\r\n" );

    //  Click initialization.

    canisolator_cfg_setup( &cfg );
    CANISOLATOR_MAP_MIKROBUS( cfg, MIKROBUS_POSITION_CANISOLATOR );
    canisolator_init( &canisolator, &cfg );
    
    log_printf( &logger, "---------------------\r\n" );
    log_printf( &logger, " CAN Isolator  Click\r\n" );
    log_printf( &logger, "---------------------\r\n" );
    Delay_ms ( 100 );
}

Application Task

Checks if new data byte has received in RX buffer ( ready for reading ) and if ready than reads one byte from RX buffer. In the second case, the application task writes message data via UART. Results are being sent to the Usart Terminal where you can track their changes.

void application_task ( void )
{
    canisolator_data_t tmp;
    
    //  Task implementation.
    
#ifdef DEMO_APP_RECEIVER

    // RECEIVER - UART polling

    tmp =  canisolator_generic_single_read( &canisolator );
    log_printf( &logger, " %c ", tmp );
    
#endif
#ifdef DEMO_APP_TRANSMITER

    // TRANSMITER - TX each 2 sec
    
    uint8_t cnt;
        
    for ( cnt = 0; cnt < 9; cnt ++ )
    {
        canisolator_generic_single_write( &canisolator, demo_message[ cnt ] );
        Delay_ms ( 100 );
    }
    
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    
#endif

}

Note

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.

Additional Notes and Information

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.

---