Provide info of object presence or absence using GP2S700HCP and MK64FN1M0VDC12
Detect – Inform – React !
Published Jun 22, 2023
Click board™
IR REFLECT Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Uncover object presence and precise positioning through the analysis of reflected light
A
A
Hardware Overview
How does it work?
IR REFLECT is based on the GP2S700HCP, a phototransistor output reflective photo interrupter from Sharp Microelectronics. It consists of one infrared emitter and one receiver facing the same direction towards the object. When the infrared beam from the emitter bounces back to the emitter when an object is placed within range, it triggers the photo interrupter, thus activating the sensor. The board can set off a false alarm if the sensor is exposed to other infrared light sources, such as an ordinary incandescent light bulb.
Infrared light will not reflect from the black surface, so the Click board™ will not detect it either. Meanwhile, reflective metallic surfaces will trigger the sensor from a more extensive range. The IR Reflect Click board communicates with the host MCU by sending analog values over the AN pin of the mikroBUS™ socket. In addition, this Click board™ features an LM2903, a low-power dual voltage comparator from STMicroelectronics. With the help of a P1 potentiometer and this voltage comparator, it is possible to set an
interrupt threshold that can provide information over an INT pin of this Click board™. The interrupt will also trigger an INT LED as a visual indicator. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. However, the 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
Clicker 2 for Kinetis is a compact starter development board 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 ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing 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
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
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 Clicker 2 for Kinetis 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 IR REFLECT Click driver.
Key functions:
irreflect_reflect_status- Function detecting interrupt states of IR reflectionirreflect_analog_status- Function detecting states of analog pin of IR reflection
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 IR reflect Click example
*
* # Description
* Example demonstrates the use of IR Reflect Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables - Start write log.
*
* ## Application Task
* This is a example which demonstrates the use of IR Reflect Click board.
* On this type of photointerrupter the infrared emitter and receiver are facing the same direction,
* the infrared beam from the emitter gets bounced back to the receiver when an object
* is placed within the detecting range of the sensor ( optimal range is 3mm ).
* These sensors are used to detect an object's presence or motion, such as a piece of paper passing through a printer
* and counting when sensor is triggered.
* Results are being sent to the Usart Terminal where you can track their changes.
* Data logs on usb uart when the sensor is triggered.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "irreflect.h"
// ------------------------------------------------------------------ VARIABLES
static irreflect_t irreflect;
static log_t logger;
static uint8_t ir_state;
static uint8_t ir_state_old;
static uint16_t counter;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
irreflect_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 ----\n");
// Click initialization.
irreflect_cfg_setup( &cfg );
IRREFLECT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
irreflect_init( &irreflect, &cfg );
ir_state = 0;
ir_state_old = 0;
counter = 1;
}
void application_task ( void )
{
// Task implementation.
ir_state = irreflect_reflect_status( &irreflect );
if ( ir_state_old != ir_state )
{
if ( ir_state )
{
log_printf( &logger, " Counter = %u\n", counter);
counter++;
}
ir_state_old = ir_state;
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
