[ 505245.613][Verbose] - Task:[8038AC44]:[0]:[8038B640] Waiting to receive message
[ 505245.649][Verbose] - Task:[8038AECC]:[1]:[8038B6C0] Waiting to receive message
Figure 70. Verbose logs
In addition to the log messages shown above, setting “log_level” to anything other than “none” or “error” results in some useful
on-screen information as well. This on-screen output reflects information about the face currently being recognized.
In the screenshot below, the face of user 0 has been recognized (hence "id:0") with 89.60 % similarity to its matching face in the
kit’s internal database (hence "sim 89.60 %"), has passed the internal blurriness check (hence “blur: 0”), and most importantly
both the 3D and 2D liveness checks (hence “3d_fake: 0” and “2d_fake: 0”). Finally, the face recognized below is also positioned
correctly because it is facing the camera (hence “pose:front”).
Figure 71. On-screen info for recognized face
6.10 Get BLE address
Type the command “ble address” to easily display the Bluetooth ID from your kit. This identifier will be necessary to quickly identify
your kit in a crowded environment to pair it with the Android Smart Lock Manager App.
SHELL>> ble address
BLE SSID [VN60648E]
Figure 72. Get BLE address command
6.11 Get managers and manager components running
To display a list of the Managers running on your solution, type the serial command “get_manager”.
SHELL>> get_manager
ID- 0 priority- 5 Name- camera_manager
ID- 1 priority- 4 Name- display_manager
ID- 2 priority- 3 Name- vision_algo_manager
ID- 4 priority- 3 Name- output_manager
ID- 5 priority- 6 Name- input_manager
Figure 73. Inference engine and oasis version commands
NXP Semiconductors
Additional features
SLN-VIZN3D-IOT Kit User Guide, Rev. 0, 01 November 2021
User Guide
40 / 47
