Video Doorbell Users Guide

Table of Contents

Introduction

Outdoor video surveillance systems are used to detect and identify people in a variety of different environments. Identifying people in a video frame can be extremely accurate in a controlled setting. But, many of the locations that video surveillance systems get installed in are noisy environments. Additionally, capturing and recording camera data can be a very power-intensive process, which drains battery life for battery-powered systems.

Using radar to detect movement and alert the video surveillance system increases battery life by keeping the camera off in times when it is unnecessary. Radar outperforms similar presence detection technologies such as PIR, ultrasonic, or just the camera operating alone, by reducing the number of false positive detections. This leads to longer battery life for camera systems.

More than just saving battery power, the radar also adds functionality to the system. Its precise distance measurements keep the camera from unnecessarily recording neighbors as they pass on the sidewalk. Its long range detects people at 15+ meters. It can detect people and objects in conditions that are challenging for cameras such as darkness, glare, smoke, fog, and rain.

Quickstart

Prerequisites

Prerequisite 1 - XDS Firmware

If using an IWRL6432BOOST EVM, the latest XDS110 firmware is required. The XDS110 Firmware runs on the microcontroller onboard the IWRL6432BOOST, which provides the JTAG Emulation and serial port communication over the XDS110 USB port. Packet loss has been observed on the serial port (COM ports) with some versions of the XDS110 firmware which can cause the demo to fail.

The latest XDS110 firmware is installed with the latest version of Code Composer Studio. CCS version 12.2 or later required.


Prerequisite 2 - PC CPU and GPU Resources

The Industrial Visualizer requires sufficient GPU and CPU resources to process the incoming UART data every frame and run the demo smoothly. Users with insufficient PC resources may notice occasional visualizer lag or missed frames in the log file. The demo should still run on most PCs regardless of hardware resources, but performance might vary.


Requirements

Hardware Requirements

Item Details
Device IWRL6432BOOST
Computer PC with Windows 10. If a laptop is used, please use the ‘High Performance’ power plan in Windows.
Micro USB Cable

Software Requirements

Tool Version Download Link
TI mmWave L SDK 5.3.0.x TI mmWave SDK 5.3.0.x
Uniflash Latest Uniflash tool is used for flashing TI mmWave Radar devices. Download offline tool or use the Cloud version
Code Composer Studio CCS 12.2 or later Code Composer Studio
TI Radar Toolbox Latest Radar toolbox should be downloaded to access binaries and source code. Download Instructions in the readme file.

1. Configure the EVM for Flashing Mode

Follow the instructions for Hardware Setup of Flashing Mode

2. Flash the EVM using Uniflash

Flash the binary listed below using UniFlash. Follow the instructions for using UniFlash

The flashable binary can be found at: <MMWAVE_L_SDK_INSTALL_DIR>\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL64xx

3. Configure the EVM for Functional Mode

Follow the instructions for Hardware Setup of of Functional Mode

4. Open the Radar Toolbox Industrial Visualizer

Navigate to the Radar Toolbox download location and find the Industrial Visualizer directory at <RADAR_TOOLBOX_INSTALL_DIR>\tools\visualizers\Industrial_Visualizer\. Then, run the visualizer either directly from source with python gui_main.py, or as an executable by running the mmWaveIndustrialVisualizer.exe

📝 NOTE
In general, running the visualizer from the Python source runs faster and results in fewer errors over long periods of time. If running Python directly from source, use Python version 3.7.3, and run the setUpEnvironment.bat script first to ensure all the correct packages and versions are installed.

5. Connect the Device

  1. Look for the “XDS110 Class Application/User UART” COM port in your Device Manager, and select this port in the GUI. If you do not see this, you need to install the XDS110 drivers listed in the Requirements section above.

  2. Make sure the correct device is selected and choose the COM port found in the previous step, and then select “Connect”.

6. Send Device Configuration

In the “Configuration” section, click on “Select Configuration”. Select one of the pre-written configurations in <RADAR_TOOLBOX_INSTALL_DIR>\source\ti\examples\Video_Doorbell\chirp_configs\. Then, click “Start and Send Configuration”

In the visualizer’s console window commands should be seen being sent to the device.

Doorbell-Specific Features

mpdBoundaryArc

Feature Description

The motion and presence state machine included in the MMWAVE-L-SDK has been extended in the doorbell demo to allow for radial “arc” shaped boundary boxes. This enables system alerts when a person is within a specific radius of the video doorbell. The boundary arc processing currently happens in the visualizer, but can be easily implemented on the device.

CLI structure

An mpdBoundaryArc can be implemented with the following CLI command:

mpdBoundaryArc <zoneIdx> <minimumRadius> <maximumRadius> <minimumTheta> <maximumTheta> <minimumZ> <maximumZ>

CLI Argument Descriptions:

zoneIdx : Number used to order the zones, must be unique from other zones, included mpdBoundaryBoxes

minimumRadius : Minimum radius in meters setting the zone boundary box

maximumRadius : Maximum radius in meters setting the zone boundary box

minimumTheta : Minimum azimuth angle in degrees setting the zone boundary box

maximumTheta : Maximum azimuth angle in degrees setting the zone boundary box

minimumZ : Minimum Z coordinate in meters setting the zone boundary box

maximumZ : Maximum Z coordinate in meters setting the zone boundary box

📝 NOTE
The mpdBoundaryArc logic runs on a cylindrical coordinate system, meaning that the Z coordinate is not included in the calculation of the radius and azimuth angle.

Results

Configuration Range @ 0° Range (m) @ +/- 30° Range (m) @ +/- 45° Range (m) @ +/- 60° Range (m) @ +/- 70° Average Power Consumption (mW)
low_power.cfg 15.05 13.61 12.63 8.61 7.30 2
medium_range.cfg 19.91 18.00 16.70 12.51 8.79 6
high_range.cfg 22.90 20.70 19.21 15.52 11.6 15

📝 NOTE
Range refers to the maximum range at which a points from a person can be detected using the IWRL6432BOOST EVM. The range can be increased/decreased depending on the IC used, the antenna gain pattern and the design of the PCB.

📝 NOTE
Power results posted in the table above show the best potential results, which require limiting the UART output to the bare minimum and removing much of the unnecesary processing and peripherals found on the IWRL6432BOOST device. Measured power using the .cfgs files will be higher without these changes.

Video Results