• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 691 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.

IWR6843: People counting demo, .cfg file for 14m range configuration

Linus E
Prodigy 30 points
Part Number: IWR6843

Hi,

I'm looking for the .cfg file for the 14m range configuration for the IWR6843.

On the reference design document (www.ti.com/.../tidue71c.pdf), page 10, it indicates that the chirp can be configured for a 14m range. However, I can only find the .cfg files for a 6m range and a 50m range when looking at the System Parameters and Chirp Configuration page.

I've tried rewriting the 6m .cfg file for the 14m range using table 2 provided on page 10 (and I was able to get a running demo), however the measurements were wildly inaccurate.

Thanks

  • 0
    TI__Mastermind 28055 points

    Hi Linus,

    I tested with this configuration:

    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 5 0
    adcCfg 2 1
    adcbufCfg 0 1 1 1
    profileCfg 0 60.6 30 10 62 0 0 24 1 128 2500 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    frameCfg 0 1 128 0 50 1 0
    lowPower 0 1
    guiMonitor 1 1 0 0
    cfarCfg 6 4 4 4 4 16 16 4 4 55 67 0
    doaCfg 600 1875 30 1 1 0
    SceneryParam -6 6 0.5 14
    GatingParam 3 2 2 0
    StateParam 10 5 100 100 5
    AllocationParam 250 250 0.25 30 1 2
    AccelerationParam 1 1 1
    trackingCfg 1 2 250 20 52 82 50 90
    sensorStart

    Can you describe the inaccuracies you are seeing? This tracked me out to 14 meters.  Please note that I modified the profileCfg and the SceneryParam arguments.  SceneryParam has to be modified to allow the track to track targets farther than 6 meters away.

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 30 points

    Hi Justin,

    This is great! It worked much better than the configuration that I had in place (see below).

    I did however notice that this configuration that you sent is having a bit of trouble tracking small movements, for example for people sitting on chairs in the office. It requires people to do big movements in order to be tracked. Is there any way to improve that?

    Also, I was wondering if you could advise on how I should be changing the .cfg file for different ranges (say 10meters for example). I noticed that you not only changed the profileCfg and SceneryParam but also cfarCfg, GatingParam and AllocationParam from the mmw_pplcount_demo_default.cfg. Could you explain why?

    Thanks,

    Linus

    Configuration file that I had for my attempt at increasing range to 14m

    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 5 0
    adcCfg 2 1
    adcbufCfg 0 1 1 1
    profileCfg 0 60.6 30 10 62.2 0 0 24 1 128 2500 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    frameCfg 0 1 128 0 50 1 0
    lowPower 0 1
    guiMonitor 1 1 0 0
    cfarCfg 6 4 4 4 4 16 16 4 4 50 62 0
    doaCfg 600 1875 30 1 1 0
    SceneryParam -6 6 0.5 6
    GatingParam 4 3 2 0
    StateParam 10 5 100 100 5
    AllocationParam 250 250 0.25 10 1 2
    AccelerationParam 1 1 1
    trackingCfg 1 2 250 20 52 82 50 90
    sensorStart

  • 0 in reply to Linus E
    TI__Mastermind 28055 points

    Hi Linus,

    For the issue with the demo missing small movements, try editing the doaCfg line:

    doaCfg 600 1000 30 1 1 0 - the bolded value has been lowered, which should allow the device to react to smaller movements.

    The configuration I sent has slightly higher CFAR parameters - there were some noisy areas where I was testing, so I slightly increased the CFAR thresholds to lower the number of detected points, which removed the noise. SceneryParam -6 6 0.5 14 sets the maximum tracking range to 14 meters.  These values control the area that can be tracked by the device - if the tracker receives points outside the tracking area, it will simply ignore them.

    Regards,

    Justin