opto 2.0.0.0
Main Page

OPTO click

OPTO Click is an accessory board in mikroBUS form factor. It features two VO2630 dual channel, high speed optocoupler modules.

click Product page


Click library

  • Author : MikroE Team
  • Date : Dec 2019.
  • Type : GPIO type

Software Support

We provide a library for the OPTO Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

‍This library contains API for OPTO Click driver.

Standard key functions :

  • Config Object Initialization function.

    ‍void opto_cfg_setup ( opto_cfg_t *cfg );

    - Initialization function.

    ‍OPTO_RETVAL opto_init ( opto_t *ctx, opto_cfg_t *cfg );

  • Click Default Configuration function.

    ‍void opto_default_cfg ( opto_t *ctx );

Example key functions :

‍This example checks the state of selected inputs and prints it.

The demo application is composed of two sections :

Application Init

‍Initialization driver enables GPIO and also starts write log.

void application_init ( void )
{
log_cfg_t log_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info(&logger, "---- Application Init ----");
// Click initialization.
opto_cfg_setup( &cfg );
OPTO_MAP_MIKROBUS( cfg, MIKROBUS_1 );
opto_init( &opto, &cfg );
opto_set_logger(1,1,1,1);
}
#define OPTO_MAP_MIKROBUS(cfg, mikrobus)
Definition opto.h:65
OPTO_RETVAL opto_init(opto_t *ctx, opto_cfg_t *cfg)
Initialization function.
void opto_cfg_setup(opto_cfg_t *cfg)
Config Object Initialization function.
void application_init(void)
Definition main.c:65
void opto_set_logger(uint8_t sel_out1, uint8_t sel_out2, uint8_t sel_out3, uint8_t sel_out4)
Definition main.c:37
Click configuration structure definition.
Definition opto.h:108

Application Task

‍This example demonstrates the use of OPTO Click board by performing the check procedure for selected outputs and displays the results on USART terminal.

void application_task ( void )
{
tmp = 1;
for( cnt = 0; cnt < 4; cnt++ )
{
switch ( sel_output & tmp )
{
case 0x01 :
{
if ( check_output == 0 )
{
log_printf( &logger, "OUT1 is low\r\n" );
}
else
{
log_printf( &logger, "OUT1 is high\r\n" );
}
break;
}
case 0x02 :
{
if ( check_output == 0 )
{
log_printf( &logger, "OUT2 is low\r\n" );
}
else
{
log_printf( &logger, "OUT2 is high\r\n" );
}
break;
}
case 0x04 :
{
if ( check_output == 0 )
{
log_printf( &logger, "OUT3 is low\r\n" );
}
else
{
log_printf( &logger, "OUT3 is high\r\n" );
}
break;
}
case 0x08 :
{
if ( check_output == 0 )
{
log_printf( &logger, "OUT4 is low\r\n" );
}
else
{
log_printf( &logger, "OUT4 is high\r\n" );
}
break;
}
default :
{
break;
}
}
tmp <<= 1;
}
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
uint8_t opto_check_out4(opto_t *ctx)
OUT4 Check function.
uint8_t opto_check_out3(opto_t *ctx)
OUT3 Check function.
uint8_t opto_check_out1(opto_t *ctx)
OUT1 Check function.
uint8_t opto_check_out2(opto_t *ctx)
OUT2 Check function.
uint8_t cnt
Definition main.c:33
void application_task(void)
Definition main.c:91
uint8_t sel_output
Definition main.c:31
uint8_t tmp
Definition main.c:34
uint8_t check_output
Definition main.c:32

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.OPTO

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.