This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1642, Configuration, vital sign lab IWR1443

Other Parts Discussed in Thread: IWR1443, AWR1642

Hi,

I am getting the dataOutputFromEVM.bin file out from the vital signs lab and want to analyse it. I am confused in the Data structure. 

I am following this structure: 

to read this file, I'm processing the file as follows: 

Magic Word            (1st iteration)  (8 bytes)
Frame Number          (1st iteration)
   :
   :
Complex Range Profile (1st iteration)
Frame Number          (2nd iteration)
   :
   :
Complex Range Profile (2nd iteration)
Frame Number          (3rd iteration)
   :
   :
Complex Range Profile (3rd iteration)
        :
        :
        :
Frame Number          (n-th iteration)
   :
   :
Complex Range Profile (n-th iteration)

my questions are:

- how many iterations should I use to iterate over the hole file ? (I am using the length of the file / number of bytes of one iteration: 80 bytes (without magic word))

- how can I get the timestamps for each frame ? 
- If I iterate over each frame, what are the variables that stock each frame informations ? 

I tried to read the file using the data structure I found in the documentation, but I am getting some false results especially concerning the HR and BR from FFT and from peak. 

can any one help me to analyse the file correctly  ?

than you in advance,

Ahmed

  • Hi,

    As I mentioned in your previous thread, we are working on releasing an update for Driver Vital Signs Lab for SDK 2.0 This update will support the same output data forma as the IWR1443 Vital Signs Lab. NOTICE that this update will not run on the AWR1642 ES1.0 EVM (the EVM you are currently using)

    The current release of the AWR1642 Driver Vital Signs does not support the same output data format.

    As I mentioned in previous thread, for current AWR1642 driver vital signs implementation, one would need to look into code to understand the output data buffers structure.

    thank you
    Cesar