IWR1642BOOST: Driver's vital signs lab used on IWR1642?

HI, Celine: 

Usually the lab works for AWR1642 will works for IWR1642 as well.  Can you give a try?

Best,

Zigang

I have successfully completed the developers guide for the driver's vital sign lab in the automative toolbox up to step 5. However, when I run the gui, the sensor starts to collect data, and then it all of a sudden stops. I am using mmwave sdk 1.1.0.2 and the latest version of CCS. Here is a picture of the Display Prompt window for reference

I have successfully completed the developers guide for the driver's vital sign lab in the automative toolbox up to step 5. However, when I run the gui, the sensor starts to collect data, and then it all of a sudden stops. I am using mmwave sdk 1.1.0.2 and the latest version of CCS. Here is a picture of the Display Prompt window for reference

I have successfully completed the developers guide for the driver's vital sign lab in the automative toolbox up to step 5. However, when I run the gui, the sensor starts to collect data, and then it all of a sudden stops. I am using mmwave sdk 1.1.0.2 and the latest version of CCS. Here is a picture of the Display Prompt window for reference

HI, there:

Are you trying to re-build the binary?  Can you just try to flash the pre-built binary that comes with the demo?

Best,

Zigang 

hi, I already flashed the pre-built binary that comes with the demo. There are no errors with that, the problem occurs when running the GUI.

Can you download the latest lab at: dev.ti.com/.../node

And the driver vital sign lab should be located at:

C:\ti\mmwave_automotive_toolbox_3_2_0\labs\incabinsensing\driver_vital_signs\vitalSigns_target

Best,

Zigang

You can just flash the prebuild binary xwr16xx_vitalSignsDemo_lab.bin.   I am not sure why you need ccs and mentioned about SDK version.   

Best,

Zigang

im not sure you understand my problem. I am running the vital signs lab and it is not giving me heart rate readings. What is the cause of this?

OK.   I see what you mean.  You have been following the users guide step by step.   

What I was suggesting is to

1) download the latest toolbox from: dev.ti.com/.../node

2) flash the pre-build binary located at: C:\ti\mmwave_automotive_toolbox_3_2_0\labs\incabinsensing\driver_vital_signs\vitalSigns_target\pre-built-Binaries\xwr16xx_vitalSignsDemo_lab.bin,

3) run the visualizer located at: 

C:\ti\mmwave_automotive_toolbox_3_2_0\labs\incabinsensing\driver_vital_signs\vitalSigns_host\gui\gui_exe\VitalSignsRadar_Demo.exe

This method works for me.  If this method does not work for you, please go ahead and try the xwr16xx OOB demo, which is located at  

https://dev.ti.com/tirex/explore/node?node=ABIxMTvUolT1ZHVYdpbDjQ__VLyFKFf__LATEST

to prove that the board is working fine. 

Best,

Zigang

Ok I have already run the OOB demo and it worked fine. Does that mean the board is working fine?

Yes, that means the board is working fine.  Please then follow my step to use the pre-build binary.   

Best,

Zigang

If the pre-build binary works for you, then it means the re-compiling has some issues.  If you have to deal with code change and re-compiling, you can try to follow this e2e thread on the similar topic of recompiling issue. 

https://e2e.ti.com/support/tools/ccs/f/code-composer-studio-forum/942636/ccs-awr1642boost-errors-in-rebuilding-the-driver-vital-signs-monitoring-demo/3490373?tisearch=e2e-sitesearch&keymatch=driver%252525252527s%252525252520vital%252525252520sign#3490373

Best,

Zigang

Pre-build binary works. I don't have any of the errors that the thread is discussing. How do I fix my original problem?

HI, Ertin:

Please read through this e2e thread to see whether it is helpful

https://e2e.ti.com/support/tools/ccs/f/code-composer-studio-forum/942636/ccs-awr1642boost-errors-in-rebuilding-the-driver-vital-signs-monitoring-demo/3490373?tisearch=e2e-sitesearch&keymatch=driver%252525252527s%252525252520vital%252525252520sign#3490373

It could be a SDK version problem.  Make sure you download the right SDK version before importing the ccs project.  From the above e2e thread, it is suggested to download the SDK 2.0.0.4. 

Best,

Zigang

I read it, and it was not helpful. Yes that is the version of SDK that I have

I downloaded the latest version of the automotive tool box and now I am getting a completely different error 

 MMWDemoMSS mmWave open configuration failed [Error code -203554190]

I have trouble building the code.  I will need to consult with a software expert and get back to you. 

Best,

Zigang 

I am trying that but when building the mss it has been building for an hour stuck on 38% is this supposed to happen?

I got it working now! is there anything I can do to improve the accuracy of the measurements, for example when I hold my breath it says I am still breathing

Great to hear that it is working for you.   Regarding the performance, are you the only person in front of the sensor?   Can you check whether the performance will be better if you move closer and move to face directly to the sensor?

Best,

Zigang

Yes i am the only person in front of the sensor. I have tried different distances and they are all the same and i am facing directly to the sensor similar to what it shown it the getting started guide

I will give a try and get back to you next week.

Best,

Zigang

HI, there:

Sorry for the late reply.  I have tried it and have the same issue with you.   I talked to the design engineer and we will need some time to check the code.  Two things you can try is 

1) Use a lens to focus on the chest area. 

2) There are some experimental scaling factor used in the code inside dss_data_path.c. 

sumEnergyBreathWfm = breathWfmOutUpdated*10000;

It probably a good idea to try some other scaling factor. 

Best,

Zigang 

Do you have a specific recommendation for the lens and scaling factor? Thanks