Other Parts Discussed in Thread: IWR1843, , AWR1642, IWR6843
Hello!
I'm studying mmWave technology with an IWR1843BOOST. My final goal is the extraction of vital signs through IWR1843. I have some experience in radar processing, so I decided first extract the complex FFT via UART and do some post-processing. Once I'm not an expert in embedded programming, I saw that I'm able to extract this complex FFT with Driver Vital Signs example (for AWR1642) flashing into IWR1843. This little study, give me some questions and an interesting report problem that I hope you can help with an explanation.
Questions:
1) What is the maximum value of the range that vital signs can be accurately measured?
2) I don't understand why sometimes I can achieve so good signals (see the figure below) and other times I can't even reach breath. Can it be related to the number of bin available?
3) I would like to have more samples in range profile data, should I change it in configure vital signs profile? I change ADC profileCfg in <numAdcSamples> parameter to 400 (default is 200) but it doesn't work with the interface. After I did this change, some interesting thing happened! During the first time that I ran the demo, the interface didn't work as supposed (but it's ok because I was just saving the values of range profile there and opening them in the matlab interface). Naturally, I was expecting this behaviour because I was running a demo for AWR1642 into IWR1843 without a migration, but after the change in profile settings, the demo started to work ?? How is it possible? In resume I changed <numAdcSamples> to 400, run the demo with an error, and changed 400 to 200 value again, after this, the demo started to work well as never did before! There is an screenshot:
Thank you!
