Provide electrical isolation from high voltage between input and output circuits in various applications, particularly where high-speed data transfer and a wide temperature range are important considerations
A
A
Hardware Overview
How does it work?
Opto Click is based on a double pack of the DIP socket VO2630, dual-channel, high-speed optocoupler modules from Vishay Semiconductors, providing electrical isolation between the input and output source. The VO2630 enables a high speed of 10Mbit/s data transfer between its input and output with galvanic isolation utilizing a highly efficient input LED coupled with an integrated optical photodiode detector. The detector has an open drain NMOS-transistor output, providing less
leakage than an open collector Schottky clamped transistor output. The VO2630 works like a switch connecting two isolated circuits, so when the current stops flowing through the LED, the photosensitive device stops conducting and turns off. It guarantees AC and DC performance withstanding 5300Vrms of isolation voltage over a wide temperature range from -40°C to +100°C. The outputs of the optocouplers are connected to four pins of the mikroBUS™ labeled IN1-IN4 and routed
to the INT, CS, RST, and AN pins of the mikroBUS™ socket. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the I/O Level jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this 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
Fusion for PIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different PIC, dsPIC, PIC24, and PIC32 MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for PIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the Fusion for PIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB
HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet are also included, including the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options (graphical and character-based LCD). Fusion for PIC v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
![default](https://cdn.mikroe.com/rent-a-product/request-setup/mcu-cards/mcu-card-2-for-pic-pic18f87j11.png)
Type
8th Generation
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
80
RAM (Bytes)
3904
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![OPTO Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790d5-a8f3-6b50-a8f9-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for OPTO Click driver.
Key functions:
opto_check_out1
- This function checks the state of OUT1 pinopto_check_out2
- This function checks the state of OUT2 pinopto_check_out3
- This function checks the state of OUT3 pinopto_check_out4
- This function checks the state of OUT4 pin
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
* \brief OPTO Click example
*
* # Description
* This application 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.
*
* ## 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.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "opto.h"
// ------------------------------------------------------------------ VARIABLES
static opto_t opto;
static log_t logger;
uint8_t sel_output;
uint8_t check_output;
uint8_t cnt;
uint8_t tmp;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
void opto_set_logger( uint8_t sel_out1, uint8_t sel_out2, uint8_t sel_out3, uint8_t sel_out4 )
{
if ( sel_out1 > 1 )
{
sel_out1 = 1;
}
if ( sel_out2 > 1 )
{
sel_out2 = 1;
}
if ( sel_out3 > 1 )
{
sel_out3 = 1;
}
if ( sel_out4 > 1 )
{
sel_out4 = 1;
}
sel_output = 0;
sel_output |= sel_out1;
sel_output |= sel_out2 << 1;
sel_output |= sel_out3 << 2;
sel_output |= sel_out4 << 3;
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
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);
}
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( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END