We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.18
mikroSDK Library: 2.0.0.0
Category: Optocoupler
Downloaded: 211 times
Not followed.
License: MIT license
OPTO Click is an accessory board in mikroBUS form factor. It features two VO2630 dual channel, high speed optocoupler modules.
Do you want to subscribe in order to receive notifications regarding "OPTO Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "OPTO Click" changes.
Do you want to report abuse regarding "OPTO Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
3635_opto_click.zip [519.49KB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for AVR mikroC AI for dsPIC XC16 |
|
OPTO Click is an accessory board in mikroBUS form factor. It features two VO2630 dual channel, high speed optocoupler modules.
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.
This library contains API for OPTO Click driver.
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 );
Function checks the state of OUT1 pin.
uint8_t opto_check_out1( opto_t *ctx );
Function checks the state of OUT2 pin.
uint8_t opto_check_out2( opto_t *ctx );
Function checks the state of OUT3 pin.
uint8_t opto_check_out3( opto_t *ctx );
Function checks the state of OUT4 pin.
uint8_t opto_check_out4( opto_t *ctx );
This example checks the state of selected inputs and prints it.
The demo application is composed of two sections :
Initialization driver enables GPIO and also starts write log.
void application_init ( void )
{
log_cfg_t log_cfg;
opto_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_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);
}
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 :
{
check_output = opto_check_out1( &opto );
if ( check_output == 0 )
{
log_printf( &logger, "OUT1 is low\r\n" );
}
else
{
log_printf( &logger, "OUT1 is high\r\n" );
}
break;
}
case 0x02 :
{
check_output = opto_check_out2( &opto );
if ( check_output == 0 )
{
log_printf( &logger, "OUT2 is low\r\n" );
}
else
{
log_printf( &logger, "OUT2 is high\r\n" );
}
break;
}
case 0x04 :
{
check_output = opto_check_out3( &opto );
if ( check_output == 0 )
{
log_printf( &logger, "OUT3 is low\r\n" );
}
else
{
log_printf( &logger, "OUT3 is high\r\n" );
}
break;
}
case 0x08 :
{
check_output = opto_check_out4( &opto );
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 );
}
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:
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.