Integrate fiber-optic communication into your project with IF-D91 and PIC32MZ2048EFH100
Send information really fast and reliably between electronic devices
Published Nov 03, 2023
Click board™
Fiber Opt Click 5V
Dev. board
Flip&Click PIC32MZ
Compiler
NECTO Studio
MCU
PIC32MZ2048EFH100
Achieve project excellence through the precision and speed of fiber-optic communication, transforming the way you connect and communicate
A
A
Hardware Overview
How does it work?
Fiber Opt Click 5V is based on one IF-D91, a fiber-optic photodiode, and one IF-E97, a fiber-optic LED, both from Industrial Fiber Optics. IF-D91 is a high-speed photodiode detector housed in a connector-less plastic fiber optic package, where optical response extends from 400 to 1100nm, making it compatible with a wide range of visible and near-infrared LED and laser diode sources. The detector package features an internal micro-lens and a precision-molded PBT housing to ensure efficient optical coupling with standard 1000μm core 2.2mm jacketed plastic fiber cable capable of 100Mbps data rates. The IF-D91 can also be used for analog video links with bandwidths up to
70MHz. The other precision-molded PBT housing with internal micro-lens, the IF-E97, is a high-optical-output visible red LED. The housing ensures efficient optical coupling with the same standard jacketed plastic fiber cable. The output spectrum is produced by a GaAlAs die, which peaks at 650nm, representing an optimal transmission window for PMMA plastic optical fiber. The visible red light has low attenuation in PMMA plastic fiber, aids troubleshooting installations, and is the main reason the IF-E97 achieves data rates of 1Mbps. This Click board™ communicates with the host MCU over selectable pins of the mikroBUS™ socket, the UART, or some general-purpose pins.
Communication can be selected through the GPIO UART selection jumper, as UART is selected by default. Otherwise, communication can be achieved directly through GPIO pins, where PWM and INT pins of the mikroBUS™ socket have that role. Also, using an AN pin, it is possible to check the analog voltage of the fiber-optic photodiode. This Click board™ can be operated only with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Flip&Click PIC32MZ is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller, the PIC32MZ2048EFH100 from Microchip, four mikroBUS™ sockets for Click board™ connectivity, two USB connectors, LED indicators, buttons, debugger/programmer connectors, and two headers compatible with Arduino-UNO pinout. Thanks to innovative manufacturing technology,
it allows you to build gadgets with unique functionalities and features quickly. Each part of the Flip&Click PIC32MZ development kit contains the components necessary for the most efficient operation of the same board. In addition, there is the possibility of choosing the Flip&Click PIC32MZ programming method, using the chipKIT bootloader (Arduino-style development environment) or our USB HID bootloader using mikroC, mikroBasic, and mikroPascal for PIC32. This kit includes a clean and regulated power supply block through the USB Type-C (USB-C) connector. All communication
methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, user-configurable buttons, and LED indicators. Flip&Click PIC32MZ development kit allows you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Flip&Click PIC32MZ as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Fiber Opt Click 5V driver.
Key functions:
fiberopt_generic_write- Generic single write function.fiberopt_generic_read- Generic single read 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
* \brief Fiber Opt Click example
*
* # Description
* This example demonstrates the use of an Fiber Opt click board by showing
* the communication between the two click boards.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes device and makes an initial log.
*
* ## Application Task
* Depending on the selected application mode, it reads all the received data or
* sends the desired text message with the message counter once per second.
*
* \author MikroE Team
*
*/
#include "board.h"
#include "log.h"
#include "fiberopt.h"
// Comment out the line below in order to switch the application mode to receiver
#define DEMO_APP_TRANSMITTER
// Text message to send in the transmitter application mode
#define DEMO_TEXT_MESSAGE "MIKROE - Fiber Opt click board\r\n\0"
static fiberopt_t fiberopt;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg;
fiberopt_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.
fiberopt_cfg_setup( &cfg );
FIBEROPT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
fiberopt_init( &fiberopt, &cfg );
#ifdef DEMO_APP_TRANSMITTER
log_printf( &logger, " Application Mode: Transmitter\r\n" );
#else
log_printf( &logger, " Application Mode: Receiver\r\n" );
#endif
log_info( &logger, " Application Task " );
Delay_ms ( 100 );
}
void application_task ( void )
{
#ifdef DEMO_APP_TRANSMITTER
fiberopt_generic_write( &fiberopt, DEMO_TEXT_MESSAGE, strlen( DEMO_TEXT_MESSAGE ) );
log_printf( &logger, "%s", ( char * ) DEMO_TEXT_MESSAGE );
Delay_ms( 1000 );
#else
uint8_t rx_byte = 0;
if ( 1 == fiberopt_generic_read( &fiberopt, &rx_byte, 1 ) )
{
log_printf( &logger, "%c", rx_byte );
}
#endif
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
