CCS: vital sign

I've forgotten to let you know that I'm working with the AWR1642 Evaluation Module.

Thanks a lot!

Hi,

thank you for your support.

Now I'm trying the incabinsensing driver_vital_signs with AWR1642 Evaluation Module.
My PC is Lenovo AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 2.10 GHz with Windows 10 64-bit.

I have flashed the image xwr16xx_vitalSignsDemo_lab.bin by using Uniflash.
[SUCCESS] Program Load completed successfully.

Then I removed the jumper SOP2.

When running VitalSignsRadar_Demo.exe, I get the following messages:

QT version =  5.8.0
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
data port did Not Open
User port did not Open
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()
"COM3"
Configuration File Path is %s/n "C:/Users/danie/Desktop/Studium/Sensor auslesen/mmwave_automotive_toolbox_3_2_0/labs/incabinsensing/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

Unfortunately I still see nothing happening after a while in the gui.

I also use the latest runtime library:
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.25.28508
Microsoft Visual C++ 2017 Redistributable (x86) - 14.11.25325

Can you help me to solve this problem, so I can get the heart rate?

Regards
Daniel

Hi,

Do you have any solutions to fix my problem, getting the breathing rate and heart rate?

After flashing the AWR1642 Evaluation Module I'm getting still the same message like above.

Thank you for yiur support

Daniel

Hello

Your original question  was about the Vital signs demo and then you have moved to a newer demo where you are facing setup issues.

Do you see the CLI on com port working to make sure that image is correctly flashed.

As a debug step it may help to make sure you can run the OOB demo if the above step doesnt work. This ensure that the board is working.

Thank you,

Vaibhav

Hello Vaibhav,

Ideally I want to get the vital sign with the driver_vital_signs or the occupancy_plus_vital_signs.

After flashing xwr16xx_vitalSignsDemo_lab.bin or vod_vital_signs16xx.bin from the mmwave_automotive_toolbox_3_2_0 the LEDs DS2 and DS4 are flashing.
Starting the gui I couldn't see any data.

Using the mmWave Demo Visualizer it will work. I can flash the AWR1642 and comine the COM Ports, so the EVM can show me some datas.

Flashing the EVM with lab0002_short_range_radar it will also work. The EVM can detect the objects and display it on the screen.

I hope you can understand what I am lokking for and what's my problem.

I Would be very glad helping me and getting the vital signs on my screen.

Thank you very much,

Daniel

Hello

You have confirmed that board works well.

Now to the debug of you not being able to run the drivervital signs.

Can  you please list at which step you see the failure exactly:

1. Does gui come up

2. Is the uart port visible and available for the gui.

3. is the config selected.

and so on.

These steps are called out in the users' guide.  Based on the  error it seem like

1. Com ports are not available to the gui

oR

Com ports were not selected  during  run steps.

Please confirm and let us know. 

ALso can you please try this run on a different PC that support the QT run time.

Thank you,

Vaibhav

Hello,

1. flashing the xwr16xx_vitalSignsDemo_lab.bin with UniFlash succeeded. The Program Load completed successfully.

2. The gui come up - C:\Users\danie\Desktop\Studium\Sensor auslesen\mmwave_automotive_toolbox_3_2_0\labs\incabinsensing\driver_vital_signs\vitalSigns_host\gui\gui_exe

3. The uart port is visible at the gui.

4. config in the DOS shows me: QMetaObject::connectSlotsByName: No matching signal for on_buttonBox_accepted()

I`ve added some pictures of my steps below.

If I press the start button at the gui, nothing happens.

How can I have a look if the uart port is available for the gui?

I tried it on a different PC. Handling with the same procedure and getting the same problem.

How can I determine if the pc support QT? How can I use it with the AWR1642?

Thank you,

Daniel

Hello

Thank you for detailed steps -  essentially you are using the incabin+vital signs demo. 

Based on the last screenshot  com4 and com5 seem to be selected.  From the windows device manager what do the com4 and com5 show up as ?

Also would you be able to confirm that on this board you have been able to run the OOB demo successfully.

Thank you

Vaibhav

Hello,

the ODS demo runs successfully, so I can detect some obstacles.

The com ports at the device manager are showing in the pictuer below.

Thank you,

Daniel

Hi, Daniel:

So far, I see the same behavior on my xwr1642EVM with the driver vital sign demo.  

But I was able to run the occupancy plus vital sign on the same device.   Can you try the binary below? 

C:\ti\mmwave_automotive_toolbox_3_2_0\labs\incabinsensing\occupancy_plus_vital_signs\prebuilt_binaries\vod_vital_signs_16xx.bin

And for the GUI, I am running the following command on my MATLAB:

vod_vital_signs('15', '16', '..\chirp_configs\vod_vs_16xx_10fps.cfg', '1')

You will need to change the first two COM port numbers.

Best,

Zigang

Hi Zigang,

thank you very much for your support. Now the driver vital sign  is running and I get the heart and breathing rate.

In your Getting Started Guide of mmWave LAB Driver Vital Signs you flash the file "xwr16xx_mmw_demo.bin". I think you should flash the file "vitalSigns_16xx.bin".

Best,

Daniel