• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 1021 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

IWR1443: The configure profile of the vital sign lab

The configure profile of the vital sign lab / frame periodicity

ahmed amine lamiri
Expert 1095 points
Other Parts Discussed in Thread: AWR1642, DCA1000EVM, MMWAVE-STUDIO

Hi all,

I am using AWR1642 with DCA1000EVM to record radar data , with the same configuration used in the vital signs lab.

In the vital signs config, the chirp period is 50 micro seconds and the frame period is  50 ms and in my case (also vital signs case) they are using only one chirp per frame (two chirps but one for processing), so why should the frame period is much more higher than the chirp period, is it useless to have a frame with 50 ms which is >>> 50 micro second ? should the frame period be just a bit high than the chirp config ? because otherwise the almost the hole frame will be empty is it just contain one chirp with 50 micro sec (1/1000 * frame period ) ! or am I understanding it the wrong way ?

I sow the details in the vital signs lab document and didn't found an explanation to this .

my frame config: ar1.FrameConfig(0, 0, 6000 , 1, 50 , 0 , 1)

my profile config : ar1.ProfileConfig(0, 77, 7.01, 6, 57, 0, 0, 0, 0, 0, 0, 70.106, 1, 100, 2000, 0, 0, 40)

thank you in advance,

Ahmed

  • 0
    TI__Guru 68170 points
    Hello Ahmed,
    Could you please follow this e2e thread which has similar query.
    e2e.ti.com/.../656350

    BR,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Expert 1095 points

    Hi Jitendra,

    I have already seen this similar query but it didn't answer my question.
    I just wanted to be sure that I am using the correct Frameconfig (FrameConfig(0, 0, 0 , 2, 50 , 0 , 1)):
    50 ms ==> refers to frame periodicity right ?
    2 = number of chirps per frame !
    thanks,
    Ahmed

  • 0 in reply to ahmed amine lamiri
    TI__Guru 68170 points
    You can find details of all the mmWaveStudio commands via LUA shell window of mmWave-Studio GUI.

    Run this command in LUA shell -- 'help ar1.FrameConfig'


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    Expert 1095 points
    Hi Jitendra,

    thanks. do you have an explanation to the fact that if the frame periodicity is set to 50 ms and the loop count is set to 1 (one chirp per frame), does that means the information that the hole frame contain (for 50 ms) is exactly the information that the chirp contains but in a less period of time (because the period of a chirp is << period of frame) ? so I can say my frame contains just a small information in the beginning (during the chirp period) and the rest does not contain any information !
    how do I cover measurements for the hole 50 ms and with one chirp ! or should I use more chirps in this case ? (in the vital signs lab htey are using only one chirp and 50ms as a frame period)..

    thanks in advance,
    Ahmed
  • 0 in reply to Jitendra Gupta
    Expert 1095 points

    can I increase the chirp period to reach the frame period or a bit less (then I can gain more information during the hole frame period) ?
    thanks,
    Ahmed

  • 0 in reply to ahmed amine lamiri
    TI__Guru 68170 points
    Chirp duration is based on RampEndTime value which you provide in profileConfig. So with frame periodicity of 50mSec, actual information is during active chirp time (rampEndTime) and remaining time in frame (50mSec) is idle (assumption loopcount =1 and only 1 chirp in a frame).

    As you mentioned in Viatal signs lab,
    profileCfg 0 77 7 6 57 0 0 70 1 100 2000 0 0 40
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 2 0 50 1 0

    Chirp-RampEnd-Time = 57 usec.
    total no. of chirp in a frame = 1*2; (numOfLoops =2)
    no. of frame = infinite.

    So out of 50msec of frame active chirp timing is 57*2 usec.

    Device supports max 5mSec of chirp (rampEndTime) but with this you need to modify FreqSlop parameter which effects the frequency bandwidth (to be within max 4GHz band) and consequently it may not cater your usecase (Vital sign).

    On the other hand you can use multiple number of chirps in a frame to increase active time (more window of information).

    At the last I would recommend you to go over misc. training vidoes on device technology to understand more on chirp/profile parameters.
    training.ti.com/mmwave-training-series


    Regards,
    Jitendra