• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 35 subscribers
  • Views 865 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.

IWR1642: People Counting Lab With Fine Doppler Resolution

Boaz Menis
Intellectual 510 points
Part Number: IWR1642

Hi,
I am trying to work with a finer doppler resolution than the default
configuration attached to the people counting lab ("mmw_pplcount_demo_default.cfg"),
in order to still detect people at rest, in the cost of decreasing the max velocity parameter.
I am trying to work with the following configuration, but it won't work:

dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg 0 0 1 0
profileCfg 0 77 370 7 20 0 0 100 1 64 5333 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 32 0 50 1 0
lowPower 0 1
guiMonitor 1 1 0 0
cfarCfg 6 4 4 0 0 16 16 4 4 50 62 0
doaCfg 600 1875 30 1
SceneryParam -6 6 0.05 4
GatingParam 4 3 2 0
StateParam 10 5 10 100 5
AllocationParam 250 0.01 5 1 2
VariationParam 0.289 0.289 1.0
trackingCfg 1 2 250 20 200 50 90
sensorStart

This config still define 6.4[m] max range.
do you know what may be the problem?
do you have a working configuration with fine doppler resolution for the people counting?

Thanks,
Boaz      .

  • 0
    TI__Guru*** 138349 points
    Hi Boaz

    Can you please provide more details about "it won't work"?

    Thank you
    Cesar
  • 0 in reply to Cesar
    Intellectual 510 points
    Hi Cesar,

    If you run the demo with the matlab file "main_pplcount_viz.m" (industrial toolbox 2.3.1) you get
    to the line 509, where the script reads the header of the data .
    The rxHeader variable is empty when using my configuration (a config which was created with the mmWave demo visualizer).

    Boaz
  • 0 in reply to Boaz Menis
    TI__Mastermind 28055 points
    Hi Boaz,

    I apologize for the very late reply. If you still have an issue with this configuration, please change the configuration to this:

    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg 0 1 1 1
    profileCfg 0 77 370 7 20 0 0 100 1 64 5333 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    frameCfg 0 1 32 0 50 1 0
    lowPower 0 1
    guiMonitor 1 1 0 0
    cfarCfg 6 4 4 0 0 16 16 4 4 50 62 0
    doaCfg 600 1875 30 1
    SceneryParam -6 6 0.05 4
    GatingParam 4 3 2 0
    StateParam 10 5 10 100 5
    AllocationParam 250 0.01 5 1 2
    VariationParam 0.289 0.289 1.0
    trackingCfg 1 2 250 20 200 50 90
    sensorStart

    If you run the device in debug mode with CCS, often errors like these are caught with an assert statement. Finding this statement in the code will usually tell you exactly what is wrong.

    Regards,
    Justin