Beginner
10 min
0

Transform the way you interact with space with PD-V12 and dsPIC30F4011

Doppler delight: Where every move matters

Microwave 4 Click with EasyPIC v8 for dsPIC30

Published Nov 12, 2023

Click board™

Microwave 4 Click

Development board

EasyPIC v8 for dsPIC30

Compiler

NECTO Studio

MCU

dsPIC30F4011

With the magic of the Doppler effect, experience a seamless and responsive environment that adapts to your every move.

A

A

Hardware Overview

How does it work?

Microwave 4 Click is based on the PD-V12, a miniature high-frequency microwave transceiver from Ningbo Pdlux Electronic Technology. This motion sensor is a K-band Bi-Static Doppler transceiver module. It is housed in a metal can and features a built-in resonator oscillator (CRO), providing a stable operation as it improves its front signal-receiving ability and reduces its flank blind area. The Microwave 4 Click detects the frequency shift between a transmitted and a received signal reflected from a moving object within the field of view of the transceiver. The radiated power (EIRP) emissions of <3mW at maximum meet the FCC and CE rules. The noise voltages at the output port inside an anechoic chamber are measured from

10Hz to 100Hz. The received signal strength (RSS) is measured at the total 1 Ways path loss of 70dB. The module uses two antennas (for RX and TX) with a maximum gain of 0dBi and is designed to be installed in such a way that allows it to operate at closer than 20cm to users or nearby persons. The produced low-level output is amplified over the MCP6022, a rail-to-rail input/output 10MHz operational amplifier from Microchip. The amplified output goes to the ADC SEL jumper, which allows you to read the data over an analog pin of the mikroBUS™ socket or the MCP3221, a low-power 12-bit A/D converter from Microchip. The jumper is set to an analog pin by default. If the option is the ADC, you can count up to 22.3ksps in

I2C fast mode. As mentioned, the Microwave 4 Click uses an analog AN pin of the mikroBUS™ socket or a standard 2-Wire I2C interface of the MCP3221 to communicate with the host MCU. The I2C of the ADC supports standard (100KHz) and fast (400KHz) modes. Depending on the ADC of the host MCU, the onboard 12-bit ADC could be a better choice. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL 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.

Microwave 4 Click hardware overview image

Features overview

Development board

EasyPIC v8 for dsPIC30 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit dsPIC30 microcontrollers from Microchip and has 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 for dsPIC30 provides a fluid and immersive working experience, allowing access anywhere and under any circumstances.

Each part of the EasyPIC v8 for dsPIC30 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, CAN,

and LIN are included, alongside 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 16-bit dsPIC30 MCUs, from the smallest dsPIC30 MCUs with only 18 to 40 pins. EasyPIC v8 for dsPIC30 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.

EasyPIC v8 for dsPIC30 horizontal image

Microcontroller Overview

MCU Card / MCU

dsPIC30F4011

Architecture

dsPIC

MCU Memory (KB)

48

Silicon Vendor

Microchip

Pin count

40

RAM (Bytes)

2048

Used MCU Pins

mikroBUS™ mapper

Analog Output
RB11
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
RF3
SCL
I2C Data
RF2
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Microwave 4 Click Schematic schematic

Step by step

Project assembly

EasyPIC v8 for dsPIC30 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the EasyPIC v8 for dsPIC30 as your development board.

EasyPIC v8 for dsPIC30 front image hardware assembly
Buck 22 Click front image hardware assembly
MCU DIP 40 hardware assembly
EasyPIC v8 dsPIC30 DIP 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 DIP 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 Microwave 4 Click driver.

Key functions:

  • microwave4_read_raw_adc - Microwave 4 read raw ADC value function.

  • microwave4_read_voltage - Microwave 4 read voltage level function.

  • microwave4_set_vref - Microwave 4 set vref function.

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 main.c
 * @brief Microwave 4 Click Example.
 *
 * # Description
 * This example demonstrates the use of the Microwave 4 Click board™ 
 * by reading and displaying the results of AD conversion and motion detection.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * The initialization of I2C or ADC module and log UART.
 * After driver initialization, the app calculates the reference ADC value.
 *
 * ## Application Task
 * The demo application reads the ADC results, takes an ADC sample, 
 * compares the difference between the taken samples and the ADC reference value, 
 * and reports the movement if the difference is higher/lower than the selected threshold value.
 * Results are being sent to the UART Terminal, where you can track their changes.
 * 
 * @author Stefan Ilic
 *
 */

#include "board.h"
#include "log.h"
#include "microwave4.h"

#define MICROWAVE4_THRESHOLD    0.5f
#define MICROWAVE4_FLAG_CLEAR   0
#define MICROWAVE4_FLAG_SET     1

static microwave4_t microwave4;   /**< Microwave 4 Click driver object. */
static log_t logger;              /**< Logger object. */
static float reference = 0; 
static float voltage = 0;
static uint8_t flag = MICROWAVE4_FLAG_CLEAR;

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    microwave4_cfg_t microwave4_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.
    microwave4_cfg_setup( &microwave4_cfg );
    MICROWAVE4_MAP_MIKROBUS( microwave4_cfg, MIKROBUS_1 );
    err_t init_flag = microwave4_init( &microwave4, &microwave4_cfg );
    if ( ( ADC_ERROR == init_flag ) || ( I2C_MASTER_ERROR == init_flag ) )
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    log_printf( &logger, " Calibrating the sensor...\r\n" );
    log_printf( &logger, " There must be no movement near the sensor!\r\n" );
    log_printf( &logger, "----------------------------------\r\n" );
    Delay_ms( 3000 );
    
    if ( MICROWAVE4_OK == microwave4_read_voltage( &microwave4, &reference ) )
    {
        log_printf( &logger, " The sensor has been calibrated!\r\n" );
        log_printf( &logger, "  Detector AN Voltage : %.3f[V]\r\n", reference );
        log_printf( &logger, "----------------------------------\r\n" );
        Delay_ms( 100 );
    }
    else
    {
        log_error( &logger, " Communication error." );
        for ( ; ; );
    }
    
    log_printf( &logger, "The motion detector unit is ready.\r\n" );
    log_printf( &logger, "----------------------------------\r\n" );
    Delay_ms( 100 );
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    if ( MICROWAVE4_OK == microwave4_read_voltage( &microwave4, &voltage ) )
    {
        if ( ( ( voltage + MICROWAVE4_THRESHOLD ) < reference ) || 
             ( ( voltage - MICROWAVE4_THRESHOLD ) > reference ) )
        {
            if ( MICROWAVE4_FLAG_SET == flag )
            {
                log_printf( &logger, " Motion detected!\r\n" );
                log_printf( &logger, " Detector AN Voltage : %.3f[V]\r\n", voltage );
                log_printf( &logger, "----------------------------------\r\n" );
                flag = MICROWAVE4_FLAG_CLEAR;
                Delay_ms( 100 );
            }
        }
        else
        {
            flag = MICROWAVE4_FLAG_SET;
        }
    }
}

void main ( void ) 
{
    application_init( );

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

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

Additional Support

Resources