Other Parts Discussed in Thread: AWR1642, UNIFLASH
Hi,
we have some questions about the driver vital signs of TI lab:
The lab we use is in mmwave_automotive_toolbox_3_4_0
Question 1:
we tried to use the driver vital signs lab on the AWR1642 EVM according to the Getting Started Guide,
and our procedures are as follows:
1. flashed the pre-built binary file "xwr16xx_vitalSignsDemo_lab.bin" in the folder
"mmwave_automotive_toolbox_3_4_0\labs\incabinsensing\driver_vital_signs\vitalSigns_target\pre-built-Binaries"
with the UniFlash
2. after flasing the binary, we executed the VitalSignsRadar_Demo.exe, and selected "Measurements from the Front"
option, then pressed the "Start" button
However, we didn't see any vital signal on the GUI after the "sensorStart" command was sent.
Our cmd window information, GUI display and testing scene are listed in the below
How do we get the breathing rate and heart rate by using the "driver vital signs" lab on the AWR1642 EVM?
--------------------------------------------------------------------------------------------------------------------------------------------------
cmd window information:
QT version = 5.8.0
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
Serial Port Found
Data Port Number is "COM7"
User Port Number is "COM8"
Data port succesfully Open
User port succesfully Open
QWindowsWindow::setGeometry: Unable to set geometry 1349x817+8+31 on QWidgetWindow/'MainWindowWindow'. Resulting geometry: 1349x749+8+31 (frame: 8, 31, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 1347x706, maximum size: 16777215x16777215).
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
"COM8"
Configuration File Path is %s/n "C:/Users/edward.lee/Desktop/TI_labs/driver_vital_signs/vitalSigns_host/gui/profiles/profile_2d_VitalSigns_20fps_Front.cfg"
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 77 7 6 57 0 0 70 1 100 2000 0 0 40"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 0"
"guiMonitor 0 0 0 0 1"
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
"motionDetection 1 20 2.0 0"
"sensorStart"
""
"sensorStop"
"flushCfg"
"dfeDataOutputMode 1"
"channelCfg 15 3 0"
"adcCfg 2 1"
"adcbufCfg -1 0 0 1 0"
"profileCfg 0 77 7 6 57 0 0 70 1 100 2000 0 0 40"
"chirpCfg 0 0 0 0 0 0 0 1"
"frameCfg 0 0 2 0 50 1 0"
"lowPower 0 0"
"guiMonitor 0 0 0 0 1"
"vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000"
0.3
0.9
4
"motionDetection 1 20 2.0 0"
"sensorStart"
""
Chirp Duration in us is : 50
Chirp Bandwidth in kHz is : 3500
Maximum Range in Meters is : 4.28571
Range-FFT size is : 128
Range-Bin size is : 0.0334821
Range-Bin Start Index is : 8
Range-Bin End Index is : 26
Total Payload size from the UART is : 220
Padding Factor is : 7
Total Payload size from the UART is : 224
GUI display
testing scene
--------------------------------------------------------------------------------------------------------------------------------------------------
Question 2:
Can we use the "driver vital signs" lab on the AWR1642 ODS EVM?
Thanks for your help.
Edward Lee
