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.

IWR1642BOOST: SRR demo - invalid cfg file

Part Number: IWR1642BOOST

Hello,

We're using the IWR1642BOOST to evaluate a long range tracking application. The SRR demo seems ideal, but I when I load the following cfg file into mmwave visualiser I get an invalid config. Do you have a working version that you can send me please?

We haven't changed the default .bin for the OOB demo, so it's using SDK v2.0. Also, I can't seem to set the range >50m inside the visualer, it would be interesting to see what exactly these settings are.

Regards,

Sanjeev.

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg 0 0 1 1
profileCfg 0 77 3 3 56 0 0 8 1 256 5000 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 64 0 100 1 0
lowPower 0 0
guiMonitor 1 1 1 0 0 1
cfarCfg 0 0 8 4 4 0 5000
cfarCfg 1 0 8 4 4 0 5000
peakGrouping 1 0 1 1 224
multiObjBeamForming 0 0.5
calibDcRangeSig 0 -5 8 256
sensorStart

  • Hi Sanjeev,

    Would you be able to post a screenshot when this error occurs?

    Cheers,

    Akash

  • In the meantime, I found a Perl script hidden away in the SDK folders that updated the script, so it now works. It turns out that the example was made for SDK 1.0. For anybody else, here's the working cfg for SDK2.0:

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 0 1 0
    profileCfg 0 77 3 3 56 0 0  8 1 256 5000 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    bpmCfg -1 0 0 1
    frameCfg 0 1 64 0 100 1 0
    lowPower 0 1
    guiMonitor -1 1 1 1 0 0 1
    cfarCfg -1 0 0 8 4 4 0 3414
    cfarCfg -1 1 0 8 4 4 0 3414
    peakGrouping -1 1 0 0 1 224
    multiObjBeamForming -1 0 0.5
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 1
    clutterRemoval -1 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    nearFieldCfg -1 0 0 0
    CQRxSatMonitor 0 3 5 127 0
    CQSigImgMonitor 0 127 4
    analogMonitor 1 1
    lvdsStreamCfg -1 0 0 0
    sensorStart

    During testing I noticed that not all peaks in the SNR vs. Range plot are returned as detections. Can you please point me in the right direction for some more info? Also, how do I increase the unambigious range of the cfg file?

    -sanjeev.

    Regards,

    Sanjeev.

  • Hi,

    Yes, the algorithm performs peak pruning to avoid false detections.

    There is a configuration provided for 120m. However the detections are not as robust.

    With the memory available on the xWR1642 device, we think that 80m is the maximum range that is robustly detected.

    thank you

    Cesar

  • Thanks, Cesar. Is there any documentation or a script avalaible for configuring the xWR1642 for these ranges? I did manage to get the reference design for the 84m range project to work, but within mmwave Visualizer the maximum is 50m.

    -sanjeev.

  • Can you please look at the SRR demo in the automotive toolbox?
     
    Please see
     
    mmwave_automotive_toolbox\labs\lab0002_short_range_radar\src\common\srr_config_chirp_design_SRR120.h
     
    Cesar
  • Thanks. However, is there a script available for converting these settings into a .cfg file for downloading to the device?

    Regards,

    -sanjeev.

  • Hi,
     
    The configuration is hard coded. The demo must be re-built in order to update the configuration
     
    Thank you
    Cesar