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.

IWRL6432: Questions about SDK and Config

Part Number: IWRL6432


Hello TI guys,

I have made IWRL6432 custom board and been developing. Recently I asked a question about Radar Cube Size.
Now I have other questions.

I tried to find out available Config values by using TI Estimator, but it is very hard.
There are many questions and I hope you answer all.

** About Estimator
1. In Basic Chirp Creation and Design page, There are only 4 types of provided config at below side. Why all Congif is not provided?

2. After clicking "Send to Advanced Chirp Design", the result numbers that automatically calculated are not the same as values from previous page.

3. In Advanced Chirp Design and Tunig page, also only 4 types of config are provided. It is not sufficient information in case of I put 32 to both azimuthFftSize and ElevationFftSize. Because it cause config download failier due to memory exceed. Are you plannig to support all config in this page?

** About SDK(Config)
1. chirpTimingCfg - ChirpAdcSkipSamples means that not using sampled data during ADC Valid Start Time, from the Chirp image of Estimator?

2. I don't fully get it about Burst. Simply, a group of Chirp? Let me know the relation among Frame, Burst, Chirp.
Then, I want to know each meaning of NumOfChirpsInBurst, BurstPeriodicity, NumOfBurstsInFrame, FramePeriodicity. And how to effect each other.

3. Isn't there a unit of BurstPeriodicity? Not milisecond?

4. After checking config values, sometimes I failed download even though no error in Estimator. A message shows up like "No data". Why is that?

5. In description of frameCfg, all values are explained as "Limited support in current OOB". What each value range can I put in?

Could you recomend all config value suit to my requirment?
My board is consisted of same circuit design and antenna as EVM board. I checked working it by downloading appimage and config for EVM.
The Requirments are,
- Maximum detection range 15m
- Range resolution 10cm
- No matter Max velocity and resolution
- Frame period 100ms below (as fast as possible)
- As big as azimuthFftSize and ElevationFftSize
- Doppler output (coherentDoppler)


Regards.

  • Hello,

    As a general note about the Sensing Estimator: this tool is designed only to consider the configuration commands which directly impact and shape the chirping behavior of the radar. This is why on both the Basic and Advanced tabs, only a subset of the commands are output. Those are the commands which the tool regards.

    However, if you choose to "save" the config from the Basic tab, the tool will try its best to generate a complete config with some default values for the other commands.

    The Sensing Estimator has error checking on the timing and hardware limitations of the chirping behavior, but it cannot provide exhaustive validity checking of an entire config file, like in the case of your FFT size exceeding the memory. The tool is best utilized as an aid in chirp design rather than solely relying upon it. 

    You will find the best success in obtaining an optimal configuration for your application if you start from one of our existing configurations used in our demos. Find the demo that is closest to the application you're developing, then utilize the Sensing Estimator to optimize the chirp further.

    About the SDK5:

    1. SDK5, which is utilized by the IWRL6432, treats ADC Valid Start Time differently than SDK3. In SDK5, ADC Valid Start Time = ChirpAdcSkipSamples / Sampling Rate.

    2. In SDK5, a burst is a sub-grouping of chirps within a frame. A frame is the larger repeating sequence. A chirp is an individual transmit sweep emitted from the device. Please refer to [SDK5_install_directory]/docs/MotionPresenceDetectionDemo_documentation.pdf and [SDK5_install_directory]/docs/MotionPresenceDetectionDemo_TuningGuide.pdf for complete definitions.

    3. burstPeriodicity is in microseconds

    4. See above comments about the Sensing Estimator

    5. See this E2E regarding the "limited support comment": https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1218462/iwrl6432-i-am-curious-about-the-framerate-of-the-detected-output-data

    Regards,
    Luke

  • Thanks for your answer.

    I should the documents of the Tuninng Guide.

    I will check that and keep researching.