• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 653 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

IWR1443BOOST: Chirp configuration for level sensing (detecting static objects)

Bart Abel
Prodigy 70 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443, MMWAVE-SDK

Dear TI,

We're trying to find an optimal configuration for a level sensing application at a max distance of around 15 meters. Were trying to use the mmWaveSensingEstimator to generate a chirp design. Unfortunately the design generated with the estimator is not accepted by the device (an error is thrown). As we're trying to detect static objects I've set the max velocity to 12 and velocity resolution to 50. The resulting configuration is not accepted. I've also tried to load the configuration that is used in the level sensing demo of the high accuracy lab (profile_2db.txt), this one also throws an error.

I have attached a screenshot of the level sensing estimator and the configuraion file created based on the level sensing estimator output. Could you help out in finding what may cause the error in this configuration? Or would you have a general suggestion for a configuration that can be used for our application?

Kind regards,

Bart

short_range_non_moving.cfg

  • 0
    TI__Guru 50240 points

    Hi Bart,

    I'll need some more information in order to assist you. Can you confirm which SDK version you are using? Can you also confirm whether your IWR1443 is ES2.0 or ES3.0? The High Accuracy lab is only compatible with mmWave-SDK 1.2 on ES2.0 at this time.

    I am also wondering which visualizer you are using. The standard mmWave-SDK visualizer is intended for evaluation and may not support all chirp configurations that are generated by the Sensing Estimator.

    Cheers,

    Akash

  • 0 in reply to Akash Gondalia
    Prodigy 70 points

    Hi Akash,

    We're using SDK version 2.1 with ES3.0.

    I'm using this version of the visualizer: 

    Kind regards,

    Bart

  • 0 in reply to Bart Abel
    TI__Guru 50240 points

    Hi Bart,

    Would you be able to post what kind of error you are seeing?

    Also please keep in mind that the mmWave Demo Visualizer does not support all chirp settings out of the sensing estimator, as it is just an evaluation tool.

    Have you tried a separate visualizer such as the zone occupancy demo?

    Cheers,

    Akash

  • 0 in reply to Akash Gondalia
    Prodigy 70 points

    Hi Akash,

    An assertion is hit on this line of the mmWave Demo (in MmwDemo_frameStartIntHandler()):

        /* Check if previous chirp processing has completed */
    MmwDemo_debugAssert(dpObj->interFrameProcToken == 0);

    I have not tested the separate visualizer yet. I can do that, but my main goal was to get an understanding of what settings from the mmWave estimator are best suitable for our application and will be accepted by the sensor.

    I have manually created some settings that do work. This also raised some additional questions, could you maybe answer these as well?

    1. What is the purpose of explicitly defining the ramp end time? In my understanding the sample time during ramping is determined by the number of samples per chirp and the sample frequency. So what is the purpose of being able to set a ramp time longer than the sample time (why isn't it automatically set to the sample time)? The part of the ramp that extends beyond the sample time does not seem to have any use?

    2. I have created two chirp profiles that seem to provide the same results in terms of range and range resolution. One has about double the slope of the other, and double the sample frequency. In case of detecting static objects at short range (10m), would there still be a reason to select one of the two above the other?

    • profileCfg 0 77 10 7 60.1 0 0 55 1 256 7250 0 0 30
    • profileCfg 0 77 10 7 120.1 0 0 30 1 256 3750 0 0 30

    3. When switching the number of Tx antennas from 2 to 1 in the mmWave estimator, the slope constant is halved (and doubled vice versa). What is the purpose of using steeper slopes when more Tx antennas are used?

    Kind regards,

    Bart

  • 0 in reply to Bart Abel
    TI__Guru 50240 points

    Hi Bart,

    For queries about chirp configurations I'd recommend looking at the chirp programming guide. For further queries then I'd recommend opening up a new thread!

    Cheers,

    Akash