Create secure and environmentally conscious spaces with EKMC1607112 and PIC18F4458
Invisible guardians: Your pyroelectric motion sensor!
Published Nov 01, 2023
Click board™
Motion 2 Click
Dev. board
EasyPIC v8
Compiler
NECTO Studio
MCU
PIC18F4458
Our PIR motion sensor technology is designed to enhance security and energy efficiency by providing reliable, real-time detection of human presence, revolutionizing the way spaces are monitored and managed
A
A
Hardware Overview
How does it work?
Motion 2 Click is based on EKMC1607112, a PIR motion sensor from Panasonic used as a human motion detector. This PIR sensor can detect changes in the amount of infrared radiation impinging upon it, which varies depending on the temperature and surface characteristics of the objects in front of the sensor. Detection performance of EKMC1607112 at ambient temperature of 25°C with temperature difference of 8°C is up to 7m and for temperature difference of 4°C it's up to 5m. Output from PIR sensor is feed into buffer and then photorelay alowing users to directly control with galvanic isolation from sensor and MCU electronic devices such as lights, motors, gates, and more. The TLP241A photorelay is able to effectively replace traditionally used mechanical
relays, bringing up the full set of inherited benefits: virtually unlimited number of cycles since there are no moving parts that would wear off, no bouncing effect on the output contacts, high resistance to mechanical shock and environmental influence, low current required for the activation, constant resistance since no carbon and rust can build up on contacts, there is no sparking or electric arc forming while operated, compact size, higher isolation voltage, and so on. When an object, such as a person, passes in front of the background, such as a wall, the temperature at that point in the sensor's field of view will rise from room temperature to body temperature, and then back again. The sensor converts the resulting change in the incoming infrared radiation into
a change in the output voltage, and this triggers the detection. Objects of similar temperature but different surface characteristics may also have a different infrared emission pattern, and thus moving them with respect to the background may trigger the detector as well. In some cases, going back and forth towards the sensor (parallel movement to the axis Z), may not be detected. Difficulty in sensing the heat source is that glass, acrylic or similar materials standing between the target and the sensor may not allow a correct transmission of infrared rays and also non-movement or quick movements of the heat source inside the detection area.
Features overview
Development board
EasyPIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports many high pin count 8-bit PIC microcontrollers from Microchip, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer. 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, EasyPIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the EasyPIC 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 DEVICE, and CAN are also included, including the well-established mikroBUS™ standard, two display options (graphical and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from the smallest PIC MCU devices with only eight up to forty pins. EasyPIC 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
Architecture
PIC
MCU Memory (KB)
24
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
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 EasyPIC v8 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 Motion 2 Click driver.
Key functions:
motion2_enable- Enable motion sensor functionmotion2_detect_state- Get detection state 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 main.c
* @brief Motion 2 Click Example.
*
* # Description
* This example demonstrates the use of Motion 2 Click boards.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the motion sensor.
*
* ## Application Task
* It checks if the sensor has detected movement and therefore displays
* the desired message on the USB UART.
*
* @author Jelena Milosavljevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "motion2.h"
// ------------------------------------------------------------------ VARIABLES
static motion2_t motion2; /**< Motion 2 Click driver object. */
static log_t logger; /**< Logger object. */
motion2_detect_state_t motion_state;
motion2_detect_state_t motion_old_state;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
motion2_cfg_t motion2_cfg; /**< Click config object. */
/**
* 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.
motion2_cfg_setup( &motion2_cfg );
MOTION2_MAP_MIKROBUS( motion2_cfg, MIKROBUS_1 );
if ( motion2_init( &motion2, &motion2_cfg ) == DIGITAL_OUT_UNSUPPORTED_PIN ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
motion2_enable( &motion2, MOTION2_MODULE_ENABLE );
Delay_ms ( 100 );
log_printf( &logger, "The sensor is ready.\r\n" );
log_printf( &logger, "-----------------------\r\n" );
}
void application_task ( void ) {
uint8_t int_status;
int_status = motion2_detect_state( &motion2 );
if ( int_status == MOTION2_DETECT_OBJECT ) {
log_printf( &logger, "Motion detected!\r\n" );
log_printf( &logger, "-----------------------\r\n" );
while ( int_status == MOTION2_DETECT_OBJECT ) {
int_status = motion2_detect_state( &motion2 );
}
log_printf( &logger, "The sensor is ready.\r\n" );
log_printf( &logger, "-----------------------\r\n" );
Delay_ms ( 100 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
