• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 362 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: How do I get datapoints from static objects that are further away?

Starceus001
Prodigy 50 points
Part Number: IWR6843AOP

Tool/software:

Hello,
I'm currently working on a project where I'm using the TI mmWave sensor to detect and track static objects in a room to determine if changes have been made in the setup of a room (classrom tables or desks etc).
I currently have the TI Area Scanner demo running on the IWR6843AOP with a Python visualiser plotting the static and dynamic points into a 3D plot (in the config, I turned off heatmapGenCfg > recordingMode to plot all data without filtering). I'm running into some limitation which I've also seen in the TI Area Scanner demo video, it seems that the range (distance) of the sensor to detect static objects is limited to 3 meters whereas dynamic objects can be detected and plotted from farther distances. 
As such, my question is as follows:
Is there a way to generate/collect more data (points) of static objects in a room, as well as data of static objects that are further away from the sensor than 3 meters, so this can be plotted in a 3D visualiser?
As I've used the pymmwave parser with some modifications of my own, as well as a custom built Python visualiser, my question is about the TI mmWave Area Scanner .bin file proved from TI.
I hope anyone can shine some light on this matter.
Regards
  • 0
    TI__Mastermind 23347 points

    Hello,

    The static object detection algorithm exclusive to the area scanner demo only works between the min and max range bins set in heatmapGenCfg. Due to the amount of memory the heatmap takes up, it is currently limited to about 60 range bins with no changes to the demo. If you calculate your chirp configuration's range resolution, you can use this value and multiply it by the min and max range bin value to know what ranges the algorithm will cover.

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 50 points

    So if I were to increase the RangeBin, my range would improve and I could see more data points.

    Are there any specific limits I should keep in mind or calculations I should do to determine these values? (or any other variables that need to be changed when changing the RangeBin?)

    Regards,

    Star

  • 0 in reply to Starceus001
    TI__Mastermind 23347 points

    Hello Star,

    Let me use an example. Lets say you copy and paste your configuration to the mmWaveSensingEstimator's advanced tab, and it says your range resolution is 7cm. If minRangeBin and maxRangeBin are set to 20 and 80 respectively, that means the static detection chain will be running on ranges 20*7=140cm= 1.4m to 80*7 = 560cm = 5.6m. If you were to make you range resolution larger, which means worse resolution, you will have larger distances between detections within the same angle bin, but the static detection chain will cover a larger distance. A range resolution of 10cm will cover ranges 2m to 8m, or 3m to 9m, 4m to 10m, etc. This is due to the 60 bin limitation caused by memory shortage of the chip.

    Best Regards,

    Pedrhom