• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 188 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1843: best possible velocity resolution

Pavel Bartoš
Prodigy 70 points
Part Number: IWR1843

Tool/software:

Hello,

we have run into issues when trying to set the velocity resolution below 0.0234 m/s - could you provide a working config which will allow us to further lower the resolution (making it finer)? We aren't that much interested about nr of samples per chirp (range resolution) - 128 is enough, we are much more interested in increasing the number of chirp loops (over the 512 we already have).

Thank you in advance.

  • 0
    TI__Mastermind 33130 points

    Hi,

    You may find it difficult to increase the number of chirp loops beyond 512. Why are you interested in getting a more precise velocity resolution? Is it to detect more points? Or do you need to estimate velocity more precisely than 0.0234 m/s? Perhaps there's a way we can solve the underlying problem without necessarily increasing the velocity resolution.

    Best,

    Nate

  • 0 in reply to Nathan Block
    Prodigy 70 points

    Hello,

    we have an application where the target moves in millimeters per second. So is it possible to increase the number of chirp loops, since you refer to its increase as "difficult" and not impossible?

    Thank you for your cooperation,

    Pavel

  • 0 in reply to Pavel Bartoš
    TI__Mastermind 33130 points

    Hi Pavel,

    Could you use the fine Motion Detection feature to accomplish this? You could also accomplish this by setting the inter-chirp time very long and simply having a smaller maximum velocity. You would not necessarily need 512 chirp loops to do this.

    Best,

    Nate

  • 0 in reply to Nathan Block
    Prodigy 70 points

    I am not sere how to setup the rest of the variables, however this is the config that I have tried to load onto the target:

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    adcCfg 2 1
    profileCfg 0 60.75 1000 10 59.1 0 0 54.71 1 94 3000 2 1 36
    channelCfg 15 7 0
    adcbufCfg -1 0 1 1 1
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    chirpCfg 2 2 0 0 0 0 0 4
    frameCfg 0 2 64 0 50 1 0
    lowPower 0 0
    guiMonitor -1 1 1 0 0 0 1
    cfarCfg -1 0 2 8 4 3 0 15 1
    cfarCfg -1 1 0 4 2 3 1 15 1
    multiObjBeamForming -1 1 0.5
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    bpmCfg -1 0 0 1
    lvdsStreamCfg -1 0 0 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    CQRxSatMonitor 0 3 5 121 0
    CQSigImgMonitor 0 127 4
    analogMonitor 0 0
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 8.92
    cfarFovCfg -1 1 -1 1.00
    calibData 0 0 0
    sensorStart

    and it doesn't allow me to do so. Do you see any issue there?
    I tried even our config:

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    adcCfg 2 1
    profileCfg 0 60.75 1000 10 59.1 0 0 54.71 1 94 3000 2 1 36
    channelCfg 15 7 0
    adcbufCfg -1 0 1 1 1
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    chirpCfg 2 2 0 0 0 0 0 4
    frameCfg 0 2 64 0 50 1 0
    lowPower 0 0
    guiMonitor -1 1 1 1 0 0 1
    cfarCfg -1 0 2 8 4 3 0 15 1
    cfarCfg -1 1 0 4 2 3 1 15 1
    multiObjBeamForming -1 1 0.5
    clutterRemoval -1 0
    calibDcRangeSig -1 0 -5 8 256
    bpmCfg -1 0 0 1
    extendedMaxVelocity -1 0
    lvdsStreamCfg -1 0 0 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    CQRxSatMonitor 0 3 4 79 0
    CQSigImgMonitor 0 127 4
    analogMonitor 0 0
    aoaFovCfg -1 -20 20 -20 20
    cfarFovCfg -1 0 0.5 45
    cfarFovCfg -1 1 -5 5
    calibData 0 0 0
    sensorStart

    without any luck.
  • +1 in reply to Pavel Bartoš
    TI__Mastermind 33130 points

    Hi,

    If you start with a working configuration file and just modify the 3rd parameter of profileCfg to be larger (which corresponds to the chirp idle time in microseconds), it should work.

    Best,

    Nate