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.

IWR1642: When can we reconfig the frame/chirp when the sensor stops after number of frame we set?

Part Number: IWR1642

Hi,

As far as I know, when reaching the number of frame we set, the sensor will stop automatically and we do not need to call sensorStop.

My question is when we can reconfig the frame/chirp? My customer plans to use a timer to counter the time of frame period. When the frame time is reached,  then reconfig the frame/chirp. Is this a right way? Do you have any other suggestion? Can we config a little earlier before the sensor stop automatically?

  • Hello Chris,

    The timing engine is using the frameCfg, which selects the ChirpCfg.  The Chirp identifies which one of 4 profiles, different RF ranges that can be specified.

    So you can preprogram several different Profiles, for different distance, velocity, or other use.   The Chirp config refers to the profiles.  You can store upto 255 chirps.

    The Frame cfg allows you to pick which chirps are used (which selects the profiles) , and how many cycles of the chirp sets are used.

    So the fastest reconfiguration, is to have preset for the 4 profiles, blocks of chirps, and change which block of chirps or individual chirps are used.

    Its not just the chirp, you have to be able to process the data after the chirp as well.   So we could have multiple frames that are reprogrammed, you need to consider the other data.  

    I will ask the designers, but I think you have to complete the first frame, before sending different commands.  I think the mailbox understands one command at a time.

    Regards,

    Joe Quintal