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.

AWR1642BOOST: "Assumptions and Inputs" for occupancy detection demo

Expert 7150 points
Part Number: AWR1642BOOST

Hi Experts,

 

We would like to know the "Assumptions and Inputs" in mmWave Sensing Estimator from chirp design (.cfg file). Specifically, we are using od_demo_car_0318_1p0.cfg and want to know this "Assumptions and Inputs". It would be best if there is design.json for the chirp configuration.

 

Best regards,

Ken

  • Hi,
    Thread has been assigned to an expert, you will get a response from him soon.

    Regards,
    Jitendra
  • Hello,

    The Sensing Estimator was not used to generate the chirp design for the VOD demo. Do you have a specific question? If you look at the online materials for this demo, you will find that generally, the chirp is designed to maximize velocity resolution over range and range/resolution so that small movements such as a child's breathing can be detected.
  • Hello Dave,

    Thank you for your response. Our goal is to have "Assumptions and Inputs" so that we can fine tune the parameters easily. I watched the webinar and saw the following table.

    I iput "Assumptions and Inputs" in the sensing estimator based on the table, but saw the following error. What should we change in order to have the same configurations with the demo.

    Best regards,

    Ken

  • With attachments...

     

    Hello Dave,

     

    Thank you for your response. Our goal is to have "Assumptions and Inputs" so that we can fine tune the parameters easily. I watched the webinar and saw the following table.

     


     

    I input "Assumptions and Inputs" in the sensing estimator based on the table, but saw the following error. What should we change in order to have the same configurations with the demo.


     

    Best regards,

    Ken

     

  • The Sensing Estimator is a high level chirp tool, that doesn't allow all the specific profile parametrics to be input.  So you won't be able to get to the VOD configuration from the tool.

    You might try examining the chirp/frame/profile configuration in the VOD .cfg files, and plug them into a spreadsheet to compute whatever value you are looking for.  There are several chirp related training resources on ti.com.

    Input configuration: (od_demo_carseats_0302_3p0.cfg)
    Start freq: 77.0GHz
    Freq slope: 98.0MHz/us
    Idle time: 250.0us
    ADC Start time: 10.0us
    TX Start time: 1.0us
    Ramp end time: 40.0us
    Num ADC samp: 64
    ADC samp freq: 2200Ksps
    Rx gain: 40dB