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.

IWR6843AOPEVM: Low-BW Human Presence Detection

Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843AOP

We're trying to do human presence detection to a minimum of 4.4m.  Ideally we'd like to do static detection (sitting, lying still, etc), but if that's not possible, then movement detection within the same 4.4m zone minimum is required.  We don't care to know the exact number of people present in this zone, just that there is presence in the zone.

Ideally, we’d like to do this without requiring an FCC waiver but understand if that’s not feasible.
 
We’ve been using the Vital Signs lab as part of an initial validation testing of the IWR6843AOP’s static detection capability (test subject sitting still / lying down) in our application.  This lab was selected as it seemed to provide the highest sensitivity for human detection.  We do not care about the exact vital signs information, just that the person is detected even if the detection is intermittent over a period of a few minutes.  For movement detection, we’ve also tested with 3D people counting lab.  Please advise if there’s a better lab to start with for what we’ve trying to do.
 
[Q1]: Can we modify one of your pre-existing mmWave Industrial Toolbox labs and change the frequency and chirp signal bandwidth to occupy just the 61–61.5GHz ISM band?
      a. If so, what exactly is the range degradation?
      b. Can you provide Python code change required and/or tell us exactly which TI mmWave Industrial Toolbax lab to start with and what exactly to modify to test this?

[Q2]: If we go the FCC waiver route, can we still human presence detection out to 4.4m minimum?

Thanks!

  • [Q1]: Can we modify one of your pre-existing mmWave Industrial Toolbox labs and change the frequency and chirp signal bandwidth to occupy just the 61–61.5GHz ISM band?

    Yes they're intended to be modified as such. In fact, you can look at our Area Scanner lab to find a configuration that does exactly what you're looking for in the area_scanner_68xx_AOP_full_power_low_bandwidth.cfg. Note that the config files between Area Scanner and People Counting are not inter-compatible, so you'll just want to look at the profileCfg line.

          a. If so, what exactly is the range degradation?

    Range does not degrade, rather, range resolution decreases to approximately 30 cm, but for presence detection, this is more than enough. See our sensing estimator tool for more info.

    b. Can you provide Python code change required and/or tell us exactly which TI mmWave Industrial Toolbax lab to start with and what exactly to modify to test this?

    I would recommend using the people counting examples, but modifying the profileCfg as mentioned above for your bandwidth requirements. We have labs for overhead sensors and for wall-mounted sensors. Regardless of the orientation of the sensor though, I would recommend using a configuration file that enables static detection, such as pc_6843_3d_aop_overhead_3m_radial_staticRetention.cfg as a starting point. Look at our labs page on TiRex for more information about how to get up and running

    [Q2]: If we go the FCC waiver route, can we still human presence detection out to 4.4m minimum?

    A waiver should only improve your ability to detect people, as it will allow you to increase your power or bandwidth, both of which will enable better detection. For detecting people at 4.4m, it's likely you would still be able to do it even without a waiver if I understand your requirements correctly.

    Best,

    Nate