This section describes the procedure for configuring mmWave sensors and visualizing point cloud objects generated by the motion and presence detection demo application. The exe for the visualizer is located at $SDK_INSTALL_FOLDER/tools/visualizer folder
You can Flash the appimage generated by the SDK using this feature. This step is not required for every run. Only when you have made some change in the device code, the newly generated appimage needs to be flashed.
On the right-hand side is the image of the EVM for both flashing and functional mode. Configure the switch settings in Flashing mode for below steps.
Upon clicking 'Flash', The console will show the relevant information
If Flashing is successful, a popup is displayed
Upon reaching this step, the device is ready to be used in the Functional mode.
Make sure that the EVM is in Functional mode (as per the image on the Flash Page) before proceeding ahead
This page of the visualizer enables the user to send the cfg file (which contains the CLI commands) to the device.
1. Sending Standard Configurations
2. Custom Configurations If a modified cfg file has to be sent to the device, click on "Browse" button under Add Cfg and upload the file.
3. Custom Configurations - Modifying parameters from the visualizer (Not enabled currently)
Once the device start receiving the configs, the respective commands will be visible in the console of the page, followed by a 'Done'
If all the configs are sent successfully, the Version section of the page will display device-related information
This page contains the Motionction plot, and the boundary box values provided by the CLI commands are also displayed.
The region provided by the user is divided into 4 Zones. The zone in which presence (motion) is detected, that zone will turn green. A Large red dot represents the centroid of a cluster, and the smaller white dots are the pointcloud. Both of them can be shown/hidden using the checkboxes in the right hand side. The right hand side also displays the Frame Number, and the boundary coordinates of the region (as provided by the user in the mpdBoundaryBox command)
Four crucial plots, namely 3-D Scatter, RangeProfile, X-Y Scatter, and Y-Z scatter are shown on this page, along with Frame Number
The plots will be Red in colour for presence detection, and Green in colour for motion detection. Sensor position is represented by a black 'x' in the 3-D Scatter plot
The Visualizer captures a number of errors that can be encountered during the run, and outputs them to the user. 1. No Device Connected - If the system is unable to detect the device, a pop-up is displayed when Auto-Detect COM is clicked
2. ATE Calibration Unavailable - If the latest ATE calibration appimage is not flashed on the device, this pop-up is displayed
3. Device Disconnected - If the device gets unplugged from the system during the run, the following pop-up is displayed
4. No Data Detected - If all the CLI commands are sent successfully to the device, but still no data is being recieved from the device. Or when device is reset, or sensorStop is issued.
5. Cfg Parsing errors - The configurations file (.cfg) contains many parameters, and there are restrictions regarding the combination of parameter values that can be used. If the cfg contains some parameters that are invalid, the visualizer detects them and outputs the relevant error to the user An example is shown below