• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 1047 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: CFAR setting for Radar Studio and OOB

Hitoshi Sugawara
Mastermind 19960 points
Part Number: IWR1443BOOST

Hi Experts,
It seems that Radar Studio supports 2D-CFAR-CA(CASO, CAGO) in Post Processing.
Let me clarify a couple of things as follows:

1) Is it possible for Out-of-Box Demo to support the same settings as Radar Studio can configure.
2)  We think that Out-of-Box demo functions 1D CFAR for Range and Doppler separately.
    On the other hand, it seems that Radar Studio functions 2D.
    If so, does 2D mean that it functions Range-Doppler? not Range-azimuth?
    Am I making sense?

Best regards,
Hitoshi

  • 0
    TI__Guru 50240 points
    Hi Hitoshi,

    Radar Studio generates values according to the capabilities of the selected device (14xx or 16xx) i.e. what is possible with the device, while the mmWave SDK Demo has been tested/supports only a small sub-set of configurations. This means that not all configurations generated using Radar Studio will work with the SDK demos. The SDK demos show only one possible processing chain and do not claim to be a processing chain which can process all possible use-cases. In other words, the configurations generated using Radar Studio are a Super-set of what is supported by the SDK demos.

    I have asked someone to provide a more detailed answer for your second question.


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    TI__Mastermind 37500 points

    Hello Hitoshi,

    In the folder where the dfp software is installed is another user guide, C:\ti\mmwave_dfp_00_07_00_04\rf_eval\docs

    In section 16.1.1.3 Detection and Angle estimation Results, for Post Processing.

    the detection of targets is per range-velocity bin.   This portion is 2D.   When we add the angle information (comparing the different Rx antennas and creating the angle) this is the 3D portion.

    As Akash stated, with Radar Studio, we export the ADC buffer data for external analysis, on the PC.

    Regards,

    Joe Quintal

  • 0 in reply to Radio-Joe
    TI__Mastermind 19960 points
    Hi Nitin and Joe,

    Thank you for your prompt support.
    It helps me a lot.
    Best regards,
    Hitoshi
  • 0 in reply to Hitoshi Sugawara
    TI__Mastermind 37500 points
    Hello,
    Related to the OOB demo, in the mmwave_UserGuide, if you create the Visualizer configuration, and save it to the PC, you can then see what the CLI functions are:

    cfarCfg - the 1443 uses range, the 1642 uses velocity (User guide pg 23,24)
    CFAR averaging mode
    noise averaging window
    guard samples
    cumulative noise divider
    cyclic / wrapped - only for 1443

    peakGrouping
    range
    velocity
    start range index / end range index (used to crop range or velocity)

    multiObjBeamForming
    enabled
    threshold

    By modifying these parameter sets, saving the file, reloading the visualizer modified configuration and retesting the customer can customize the detection.

    the calibDcRangeSig - is useful to limit the near DC range value also.

    Regardsm
    Joe Quintal