• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 879 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.

Original question:

IWR1642: IWR1642 pplcount gui for 30m config ...IWR1642 ES1.0 hardware

IWR1642: IWR1642 pplcount gui for 50m config ...IWR1642 ES2.0 hardware

Melvin Tsai
Intellectual 600 points
Part Number: IWR1642

Hi,

I had test two condition, Can Launch the Demo Visualizer, both results are the same - when people move, only some noise (a lot of little black point), can't detect people)

 

1.      Hardware: ES 2.0

         Firmware: mmwave_industrial_toolbox_2_3_0\labs\lab0013_traffic_monitoring_16xx\prebuilt_binaries\traffic_monitoring_16xx_lab.bin

       GUI Tool: mmwave\mmwave_industrial_toolbox_2_5_0\labs\lab0011-pplcount\lab0011_pplcount_quickstart\pplcount_gui.exe

        50m configuration: Formal release on Ti Web

   

 

2.      Hardware: ES 2.0

         Firmware: mmwave_industrial_toolbox_2_5_0\labs\lab0013_traffic_monitoring_16xx\prebuilt_binaries\traffic_monitoring_16xx_lab.bin

         GUI Tool: mmwave\mmwave_industrial_toolbox_2_5_0\labs\lab0011-pplcount\lab0011_pplcount_quickstart\pplcount_gui.exe

         50 m configuration: Formal release on Ti Web and change lowPower 0 0 to lowPower 0 1

1881.50m_longRangeTM.cfg

 /Melvin

  • 0
    TI__Mastermind 28055 points

    Hi Melvin,

    From the images you have provided, it seems you do not have enough points in the point cloud.

    We can start by changing the CFAR configuration:

    cfarCfg 4 4 15 16 8 6 0 63 63 0 1 – this is the original

    Try changing the bold values: cfarCfg 4 4 15 16 8 6 0 30 30 0 1

    This will greatly improve the amount of points in the point cloud.

    Try changing the scenery parameters as well, to allow detections in a wider field around the device: sceneryParam 1 -15 15 0.0 75.0 0 0 0 0 1 1.25 11.0 20.0 50.0 0 0 0 0

    In my testing, there seems to be a minimum range of about 3 meters for successful tracking. You can see from the screen cap below. Even though I start walking right in front of the sensor, the tracker doesn’t start tracking me until I am about three meters out:

    You can see in the picture above that there are a lot of points centered around the track - unlike the examples you have posted.  If you still cannot improve the tightness of the cluster, try changing some of the GTrack parameters to allow for a looser cluster:

    allocationParam 30 60 1.0 3 2.8 2.0  - The bolded value is the diameter of the cluster in meters - This can be increased to allow larger clusters, but in my testing I have not seen a need to do that.

    Regards,

    Justin