• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 496 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.

IWR6843AOP: profileCfg issue

Tony Simple
Intellectual 390 points
Part Number: IWR6843AOP

hi,

I was trying to configure a shorter distance profile in over head people counting based on a working profileCfg command:
profileCfg 0 61.2 60.0 17.0 50.0 328965.0 0.0 99.27 1.0 64 1000 2.0 1.0 36

According to my understanding, the distance is related with the tx power and sampling rate. I kept the tx power untouched and set the digOutputSampleRate to 1000 (a half), then got an error message -1 from sensor.

I also tried to combine lower digOutputSampleRate with shorter ramp end time and failed without luck.

Would you guys please point out what parameters else I should modify in order to sensor shorter distance? The target range is 3m.

thinks.

  • 0
    TI__Genius 10550 points

    Hi, 

    Have you already looked at the user guide

    https://www.ti.com/lit/an/swra553a/swra553a.pdf

    This should help the customers design their own chirp profile. Please let me know if this user guide did not help resolve the issue mentioned above. 

    Regards, 

    Sudharshan K N 

  • 0 in reply to Sudharshan KN
    Intellectual 390 points

    Hi, Yes, I have read the doc you referred for a couple of times and understand how to design chirps. But still not able to figure this out. Would you experts give some hints on this?

  • 0 in reply to Tony Simple
    TI__Genius 10550 points

    Hi, 

    Can you please let me know which sample configuration are you looking at? Is this from the SDK 3.5 labs? 

    Regards, 

    Sudharshan K N 

  • 0 in reply to Sudharshan KN
    Intellectual 390 points

    Hi,

    here is the cfg from the overhead people counting （470） project:

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 7 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    lowPower 0 0
    profileCfg 0 61.2 60.00 17.00 50 328965 0 55.27 1 64 2000.00 2 1 36
    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 224 0 120.00 1 0
    dynamicRACfarCfg -1 10 1 1 1 8 8 6 4 4.00 6.00 0.50 1 1
    staticRACfarCfg -1 4 4 2 2 8 16 4 6 6.00 13.00 0.50 0 0
    dynamicRangeAngleCfg -1 7.000 0.0010 2 0
    dynamic2DAngleCfg -1 5 1 1 1.00 15.00 2
    staticRangeAngleCfg -1 0 1 1
    %classifierCfg 1 1 1 500 0.6 1.0 0.95 10
    antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0
    antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2
    antPhaseRot -1 1 -1 1 -1 1 -1 1 -1 1 -1 1
    fovCfg -1 64.0 64.0
    compRangeBiasAndRxChanPhase 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 
    staticBoundaryBox -3 3 -3 3 -0.5 3
    boundaryBox -4 4 -4 4 -0.5 3
    sensorPosition 2.9 0 90
    gatingParam 3 2 2 3 4
    stateParam 3 3 6 20 3 1000
    allocationParam 20 20 0.05 20 1.5 20
    maxAcceleration 1 0.1 1
    trackingCfg 1 4 800 20 37 33 120 1
    presenceBoundaryBox -4 4 -4 4 0.5 2.5
    sensorStart

    thanks.
  • 0 in reply to Tony Simple
    TI__Genius 10550 points

    Hi, 

    Sorry for the late response. 

    The detection range can also be reduced by changing the boundary box parameters. Let me know if this served the purpose. 

    Regards, 

    Sudharshan K N