Intermediate
30 min
0

Guarantee dependable motion sensing and security breach notifications with PL-N823-01 and PIC18F86K22

Guarding your space: Pyroelectric watchdogs!

PIR Click with UNI-DS v8

Published Oct 07, 2023

Click board™

PIR Click

Development board

UNI-DS v8

Compiler

NECTO Studio

MCU

PIC18F86K22

Enhance your security systems and smart home devices with our pyroelectric infrared sensor, providing reliable motion detection and intruder alerts

A

A

Hardware Overview

How does it work?

PIR Click is based on the PL-N823-01, a pyroelectric infrared sensor from KEMET. Due to the absence of a lens, KEMET’s Pyro Sensor is low profile, as it does not protrude, which makes it ideal for gathering visual requirements. With KEMET’s proprietary piezoelectric ceramic material and element structure of the Pyroelectric Infrared Sensor, you can also detect humans through glass or resin. This allows more freedom in the design of the outer appearance of the end product. Such a sensor system aims to provide the reliable human detection and human scenario perception. In order to achieve this goal, a conditioning sensing circuit with a low-noise signal amplifier with adjusted amplification gain is developed. Besides, the gain amplification, the onboard circuit serves also as a proprietary 1Hz signal filter, which ensures rejection of all unwanted components of the signal. That way, a reliable movement

detection system is achieved. The output signal is routed to the AN pin of the mikroBUS™, as well as to the MCP3221 – a 12-Bit A/D Converter with I2C Interface, from microchip. That way, the user can choose whether to read the output signal via the I2C interface, or directly, by reading the voltage on the analog pin of the used MCU. Some of the numerous benefits of using this particular click, equiped with the PL-N823-01 infrared sensor, are a wide view angle up to 60 degrees ether way, detection possible through glass or resin, low power consumption, excellent radio wave performance in high-frequency band, a compact and low profile (5.0x4.8x1.7mm) and all of this is possible without a lens because it is not required. The low power consumption that we are speaking of is down in the μA range. When it comes to the performance characteristics, the operating temperature should be between -40C to +70C

and the storage temperature should be between -40C to +85C. The PIR Click board™ offers a selection between 3.3V and 5V operation, with the onboard SMD jumper, labeled as PWR SEL. This allows both 3.3V and 5V MCUs to be interfaced with this Click board™. The attached device datasheet contains an in-depth explanation of all the mentioned functions. However, Mikroe provides a library with functions that make the final code clean and readable, simplifying working with this device. These functions internally employ the aforementioned communication mechanism and expose only a simple and clean interface to the user. The provided example code demonstrates the functionality of these functions. It can be used as a reference point for a custom development.

PIR Click top side image
PIR Click bottom side image

Features overview

Development board

UNI-DS 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 STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR 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, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it 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 is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS 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.

UNI-DS v8 horizontal image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

PIC

MCU Memory (KB)

64

Silicon Vendor

Microchip

Pin count

80

RAM (Bytes)

3862

Used MCU Pins

mikroBUS™ mapper

Analog Output
PA0
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PC3
SCL
I2C Data
PC4
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

PIR Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.

Fusion for PIC v8 front image hardware assembly
Buck 22 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
v8 SiBRAIN MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware 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

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

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

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

Software Support

Library Description

This library contains API for PIR Click driver.

Key functions:

  • pir_get_adc - Reading 12bit ADC value

  • pir_reg_read - Reading register

  • pir_get_mili_volt - Reading ADC data in mili Volts

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 Pir Click example
 * 
 * # Description
 * This application which generates a voltage when exposed to infrared radiation.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes device.
 * 
 * ## Application Task  
 * Reads ADC data, converts it to miliVolts and logs scaled value in miliVolts.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "pir.h"

// ------------------------------------------------------------------ VARIABLES

static pir_t pir;
static log_t logger;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    pir_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.

    pir_cfg_setup( &cfg );
    PIR_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    pir_init( &pir, &cfg );
}

void application_task ( void )
{
    uint16_t adc_val;
    float map_out;

    adc_val = pir_get_adc( &pir );
    map_out = pir_scale_results( &pir, adc_val, 0, 3303 );
    
    log_printf( &logger, " Voltage: %.2f  miliVolts \r\n", map_out);
   
    Delay_ms( 500 );
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources