> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/mr-b3rb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nxp.gitbook.io/mr-b3rb/additional-b3rb-modules/cliff-detection-with-vl53l4cd.md). # Cliff Detection with VL53L4CD Measurement of distance within the range 1 mm to 1300 mm for cliff detection using VL53L4CD. ## INTRODUCTION The B3RB can use a TOF distance sensor as a cliff detector and the appropriate software to prevent it from driving off a table, down a stairway or any other "cliff" it may encounter while moving forward. These sensors could also be used pointing in other directions for other proximity detection applications. This tutorial describes how to perform cliff detection on MR-B3RB using TOF VL53L4CD sensor with MR-CANHUBK344 and MR-CANHUBK3-ADAP boards. \ \ The example and configuration shown below is with the MR-CANHUBK344 running Zephyr and Cognipilot but is showing the board outside of the installation on a MR-B3RB. When used with a B3RB, the power is supplied in the normal fashion and not with external connectors shown. ### Operation Explanation The Time of Flight VL53L4CD sensor measures distance within the range 1 mm to 1300 mm. The sample application "samples/sensor/vl53l4cd" polls on the sensor every 1 second and reads the current distance measured from the device. Then it prints the distance on the console (in meters). ## ITEMS REQUIRED {% hint style="info" %} All items except 3 (Cable), 4 (TOF sensor) and 10 (5V DC Power supply) are included with [MR-B3RB-S](/mr-b3rb/archive/whats-in-the-box-pre-production-version/witb-mr-b3rb-s.md). {% endhint %} {% hint style="warning" %} Re: item no. 9, [MR-CANHUBK344](/mr-b3rb/archive/whats-in-the-box-pre-production-version/witb-mr-canhubk344.md) kit that comes with [MR-B3RB-S](/mr-b3rb/archive/whats-in-the-box-pre-production-version/witb-mr-b3rb-s.md), includes multiple cables with "SYP" connector which could be utilized for supplying power to the MR-CANHUBK344. {% endhint %}

S.NO.	NAME	QTY
1	MR-CANHUBK344	1
2	MR-CANHUBK3-ADAP	1
3	STEMMA QT / Qwiic JST SH 4-pin Cable – 100mm	1
4	TOF VL53L4CD	1
5	J-Link EDU MINI DEBUGGER (Complete set)	1
6	DCD-LZ Breakout Board	1
7	CABLE, USB-TTL, FTDI TTL-232R-3V3, 6 PIN CONNECTOR	1
8	CABLE, FOR DCD-LZ, 7 PIN, JST-GH CONNECTOR, 100 MM	1
9	CABLE, SYP CONNECTOR for supplying power to MR-CANHUBK344	1
10	DC Power Supply (any) for supplying 5V to MR-CANHUBK344	1

## SETUP DIAGRAMS

## HARDWARE SETUP This hardware setup shows these boards outside of MR-B3RB on a tabletop. This of course can also be done on the vehicle itself. Simply plug in the sensor and the STEMMA QT cable to the CANHUB-ADAP. The power and other connections do not change from a normal MR-B3RB configuration. {% hint style="info" %} The JLINK can alternatively connect to the small DCD-LZ board if preferred. Power may be supplied using either of the power connectors. In an assembled MR-B3RB this would be using the 5 pin JST-GH power in cable rather than the SYP cable. {% endhint %} 1. Connect hardware components as shown in the block diagram above. The CANHUB-ADAP includes a I2C connector that follows the ADAFRUIT STEMMAQT standard. 2. Attach the MR-CANHUBK3-ADAP board on top of MR-CANHUBK344. 3. Power on the MR-CANHUBK344 board - connect the SYP connector to the MR-CANHUBK344, and the other end of the cable to your bench power supply or any source that could provide 5V DC. ## SOFTWARE SETUP ### Setup West Workspace ``` cd ~ west init -m "https://github.com/NXPHoverGames/zephyr.git" cliff_detection_project cd ~/cliff_detection_project west update ``` ### Building and Flashing {% code lineNumbers="true" %} ``` cd ~/cliff_detection_project/zephyr git checkout tof_vl53l4cd_with_mux_pr west build -b mr_canhubk3 samples/sensor/vl53l4cd -p west flash ``` {% endcode %} ## RESULTS Get the shell of MR-CANHUBK344. ``` sudo chmod 666 /dev/ttyUSBn cu -l /dev/ttyUSBn -s 115200 ``` The shell should display output as: ``` proximity = 1 distance = 0.019 m proximity = 1 distance = 0.021 m proximity = 1 distance = 0.019 m proximity = 1 distance = 0.018 m proximity = 1 distance = 0.020 m proximity = 1 distance = 0.017 m proximity = 1 distance = 0.018 m proximity = 1 distance = 0.019 m proximity = 1 distance = 0.020 m proximity = 1 distance = 0.018 m proximity = 1 distance = 0.020 m proximity = 1 distance = 0.018 m proximity = 1 distance = 0.020 m proximity = 1 distance = 0.020 m proximity = 1 distance = 0.019 m proximity = 1 distance = 0.016 m ```