IWR6843ISK-ODS: Why sometime the heartbeat become too high or too low when someone standstill

Hi Angela,

Thanks for evaluating our vital signs demo!

This can happen if the algorithm starts to detect something other than the chest as the chest. It is important that the user stay at the distance given in the lab with the EVM at the same level of the chest. To improve the lab you can edit the configuration file to change the chirp profile, please let me know if you need more details on this.

Our new lab, 3D People Counting with Vital Signs, is an improved algorithm which is less likely to have this issue. The binary is on the mmWave industrial toolbox. If you need the source code please reach out to your TI sales representative.

Thank you,

Angie

Hi, Angie,

Thanks for your information!   We have read the description of the lab carefully. The user stays at the 0.5m distance given in our lab with the EVM at the same level of the chest in the front solution. 

TO improve the lab based on your two solutions. Would you mind giving us more details?

1. edit the configuration file to change the chirp profile

Which parameters should be modified in the configuration file? At the same time, Does the relative codes need to be updated?

2.3D People Counting with Vital Signs is an improved algorithm that is less likely to have this issue.

We will set up the demo based on IWR6843AOP EVM. What are the improved details about the algorithm? Can we run the lab demo useing the IWR6843ISK-OSD EVM?

Thanks!

B..R,

Thomas

1. Which parameters should be modified in the configuration file? At the same time, Does the relative codes need to be updated?

Answer: There are 2 changes you can try to make without changing the code. These involve editing config commands, this is editing the xwr1642_profile_VitalSigns_20fps_xxx.cfg files which are sent to the gui. 

a. Edit vital sign config commands, see information on these in the configuring the GUI section of the Vital Signs 68xx Users Guide

b. Edit the chirp profile itself by editing the profileCfg command. Information can be found here on programming chirp parameters. If you feel you need this please let me know and I can share some tools to help here. 

2. We will set up the demo based on IWR6843AOP EVM. What are the improved details about the algorithm? Can we run the lab demo using the IWR6843ISK-OSD EVM?

Answer: This demo does need to be run with the IWR6843AOP EVM. However, I would suggest this demo over the one you are using as it is our latest demo. The improvements are twofold.

The first is an improved signal processing algorithm for the vital sign detection.

The second is in this lab vital signs detection is performed on top of our People Counting lab. This means the device first detections the location of the person in space and then starts detecting vital signs in the location it finds the person. 

Thank you,

Angie

Hi, Angie,

1. Which parameters should be modified in the configuration file? At the same time, Does the relative codes need to be updated?

According to your advice, I have modified the parameters (0 61 500 7 20 0 0 100 1 64 5333 0 0 48) of profilecfg command in the xwr1642_profile_VitalSigns_20fps_front.cfg file based on my understanding. Unfortunately, there are not any improved sides to the issue. So would you mind giving us more information about how to modify the parameters? Can you offer some parameters of profilecfg command to correct the issue?

2. We will set up the demo based on IWR6843AOP EVM. What are the improved details about the algorithm? Can we run the lab demo using the IWR6843ISK-OSD EVM?

3D People Counting With Vital Signs lab demo has been set up for testing. Details are as follows:

1) lab demo version: C:\ti\mmwave_industrial_toolbox_4_10_1\labs\Vital_Signs\3D_People_Counting_with_Vital_Signs

2) platform(two mode): IWR6843AOP EVM / IWR6843AOP EVM + Industrial mmwave carrier board (switchs have been set correctly)

3) GUI version: C:\ti\mmwave_industrial_toolbox_4_10_1\labs\People_Counting\visualizer\vital_signs_gui

when the GUI is running, The com ports can be connected and cfg parameters can be sent. but there are not any informations in the statistics area. Please give us some advice on the issue. The issue is the same when GUI is running in the IWR6843AOP EVM standalone mode and EVM with mmwaveICBooset attached. Thanks! 

Hi Thomas

Thank you for all your detailed responses! Here is my answer for question 2.

Vital signs 3D people count:

• Can only run on the IWR6843AOP
• Runs better because it is built on top of tracking and has an improved vital signs algorithm (details and source code are under NDA). 

GUI debug:

• Do you have teraterm or any other programs open that might also be connected to these com ports?
• Did you move the device into functional mode?

As for question 1.. I think it will be best for you to compare the performance of the two labs yourself and then focus on perfecting the configuration parameters.

Thanks,

Angie

Hi, Angie,

Vital signs 3D people count:

• Can only run on the IWR6843AOP (I have try the demo lab based on IWR6843AOP EVM standalone mode)
• Runs better because it is built on top of tracking and has an improved vital signs algorithm (details and source code are under NDA). 

GUI debug:

• Do you have teraterm or any other programs open that might also be connected to these com ports?(NO. I confirmed!)
• Did you move the device into functional mode? (S3 Switch is off status -function mode no flash mode)

any other advice? Thanks!

Thomas

Hi Thomas,

Ok! Thanks for checking those things. Another thing we can check, after b'\rmmwDemo:/sensorStart\n' did it print another line stating "Done" or "Sent" in the python CLI?

Thank you,

Angie

Hi, Angie,

Thanks for your kind support, I have set up and run the 3D People Counting With Vital Signs lab demo successfully.  My set-up platform information is following:

1) lab demo version: C:\ti\mmwave_industrial_toolbox_4_10_1\labs\Vital_Signs\3D_People_Counting_with_Vital_Signs

2) platform: IWR6843AOP EVM + Industrial mmwave carrier board 

3) GUI version: C:\ti\mmwave_industrial_toolbox_4_10_1\labs\People_Counting\visualizer\vital_signs_gui

But I want to try the set-up of the lab demo only using the IWR6843AOP EVM (standalone mode).  there are some following errors during the parameters configuration. 

Please help me confirm that Can I do the lab demo only using the IWR6843AOP EVM with standalone mode. if the answer is yes, How to fix the above issue? Thanks!

Thomas

Thomas,

I am so glad you got this to work! Yes, you can run this lab demo in standalone mode. The issue above can happen if the device was not properly moved to functional mode and then reset with the NRST button before sending the configuration file.

Please try one more time and make sure you have the switch on the back of the AOP moved to it's functional mode setting and press the NRST button before sending the config and see if this works.

Thanks,

Angie

Angie,

I'm so glad that the demo is running successfully  Based on IWR6843AOP EVM with standalone mode. The S1 switches should match the following image.

Thank you a lot!

Thomas

Yes, and the switch on the back of the board needs to be on when flashing and off when running the demo.

Thanks,

Angie

About 3D Vital Signs, sitting 40cm before the sensor. My heart beat is sometimes over 90,however the testing result is low. How to configure or set up to make the result more reasonable

 part of content in config file:

staticBoundaryBox -0.6 0.6 0.3 1 0 3
boundaryBox -0.6 0.6 0.3 1 0 3
sensorPosition 0.86 0 0
gatingParam 3 2 2 2 4
stateParam 3 3 12 500 50 6000
allocationParam 20 100 0.1 20 0.5 20
trackingCfg 1 2 800 1 46 96 110
presenceBoundaryBox -0.6 0.6 0.3 1 0 3
maxAcceleration 0.1 0.1 0.1

vitalsign 15 300
VSRangeIdxCfg 0 21

Angela,

I would start by playing with your vitalsign 15 300 command. 15 is the refresh frame rate and 300 in the window size. 

Refresh frame rate is how often you are doing vital signs processing. Decreasing this will mean the program calculates heart rate more often and will give you better data in real time but will use more MIPS.

Window size is how many frames of radar data the program uses to make a decision on heart rate and breath rate. If you increase this you may need to also increase your frame rate (in framecfg) but you may also see more accurate data.

Thanks,

Angie

Angie,

I update 2 parameters of vitalsign, it works.

But  when I updated  frameCfg, after sending config file to sensor it cannot continue to work.

How to update frameCfg correctly?

Original frameCfg :

frameCfg 0 2  48  0 110.00 1 0

New frameCfg :

frameCfg 0 2  96  0 55.00 1 0

lab demo version: C:\ti\mmwave_industrial_toolbox_4_10_1\labs\Vital_Signs\3D_People_Counting_with_Vital_Signs

========================

part of content in config file:

frameCfg 0 2  96  0 55.00 1 0

vitalsign 10 400

=========================

Thanks ,

Angela

Angela,

With the increased window size you will need to increase the frame rate to above 110. Try 150 and if that does not work go higher.

Thank you,

Angie Mitchell