AWR1443: About saved data of Vital Sign Demo

Ray丶

Part Number: AWR1443
Other Parts Discussed in Thread: AWR1642

Hi，

I am trying to develop a Vibration monitoring system with AWR1443 so I tested Vital Sign Demo and got data saved by vitalSignsDemo_GUI.

I read 'vitalSignsLab_xwr1443_DevelopersGuide' and parsed the data with matlab scripts provided in 'mmwave_automotive_toolbox_2_4_2'.

I noticed there are so many zero in outPhase and some data are exactly the same .Just like this.

So I back to bin file and get confused about the data of every frame.

In this picture,I can see magic word.According to magicwords ,I select Frame1 data with red line and Frame2 with blue line.

After Frame2 data,I can see many zero data.

After the zero data,I see Frame data again,and the data next is exactly the same with Frame2 data in picure above.

My question is:

why there are so many zero data and what are them?I checked Packet Structure and don't think they are padding data.
why there are some frame data repeat?For example,the Frame2 in both picture.
what's the order of every frame data?Is the data successive frame data?

over 5 years ago

0 Jitendra Gupta over 5 years ago

TI__Guru 68160 points

Hi,
Permit us some time to check this behaviour at our end.

Regards,
Jitendra

0 db_woodall over 5 years ago

TI__Mastermind 21025 points

Yes, that's odd behavior. The automotive "Driver Vital Signs" demo is designed to run on an AWR1642, and you indicated using an AWR1443. Please try the Vital Signs demo in the Industrial toolbox on TIRex. Before you try running it, check the lab's user guide to make sure that it matches your AWR1443's silicon version (ES1.0 or ES2.0).

-dave

0 Ray丶 over 5 years ago in reply to db_woodall

Intellectual 440 points

Hi,

Thanks.

I think my AWR1443's silicon version is ES2.0 cause there is a '964D' mark on that.

The demo I used is 'lab0002-vital-signs' in 'mmwave_industrial_toolbox_2_5_2', not "Driver Vital Signs" .

According to 'vitalSignsLab_xwr1443_DevelopersGuide'in the file,I used 'SDK 1.2.0.5'.

And my ccs version is 8.2.0.The cfg file I used is default 'profile_2d_VitalSigns_20fps.cfg'.

Is there anything wrong about that?

By the way ,I tested TestTone by uncomment code in source code and also meet with same problem.

8510.testTone.txt

Look forward to your reply.

0 Ray丶 over 5 years ago in reply to db_woodall

Intellectual 440 points

Any advice on this problem?

0 db_woodall over 5 years ago in reply to Ray丶

TI__Mastermind 21025 points

Hi Ray,

Your settings seem to be correct. We will need to run this on our side to see if we can replicate this. I will update the thread when I have results.

-dave

0 Ray丶 over 5 years ago in reply to db_woodall

Intellectual 440 points

Hi,
Did you get any results?
thanks

0 db_woodall over 5 years ago in reply to Ray丶

TI__Mastermind 21025 points

Sorry for the delay. Yes, I was able to repeat your issues. I've turned it over to the developer of the GUI.

-dave

0 Ray丶 over 5 years ago in reply to db_woodall

Intellectual 440 points

OK.I will wait for the release of the new version.Thank you so much.

0 Akash Gondalia over 5 years ago in reply to Ray丶

TI__Guru 50240 points

Hi Ray,

The mmWave Industrial Toolbox was recently updated to version 3.0, would you try with this version of Vital Signs demo and compile in a clean Workspace? dev.ti.com/.../

Let us know if you are still having an issue.

Cheers,
Akash

0 Ray丶 over 5 years ago in reply to Akash Gondalia

Intellectual 440 points

Hi Akash,
Thanks for your reply.I tested the demo in 'mmWave Industrial Toolbox version 3.1' and still met with same problem.
I am reading the source code trying to find the answer.If you make any progress please let me know.
Thank you,
Ray

Sensors

Sensors forum

AWR1443: About saved data of Vital Sign Demo