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

IWR6843AOPEVM: 3D People Tracking – Ceiling config changed to match wall mount FPS, what else needs update?

Alan Chiou
Prodigy 20 points
Part Number: IWR6843AOPEVM

Tool/software:

I’m running a multi-radar HAR setup with one ceiling-mounted and three wall-mounted radars.
Wall-mount default: numLoops=96, framePeriodicity=55 (~18 FPS)
Ceiling-mount default: numLoops=224, framePeriodicity=120 (~8.33 FPS)

To match FPS between radars, I changed the ceiling config’s frameCfg to:

frameCfg 0 2 96 0 55 1 0
trackingCfg 1 4 800 20 37 33 55 1

Other parameters remain from the original ceiling preset.

Issue:

  • When running only the ceiling radar, sometimes I get:

    ERROR: No data detected on COM Port, read timed out

  • When it does run, if I create a dense point cloud (e.g., raise and swing both hands), data streaming stops or errors occur.

  • Reverting to the default ceiling config (224 loops, 120 ms) works fine.

Question:
Besides numLoops, framePeriodicity,trackingCfg’s deltaT what parameters must I change to make this 96-loops / 55-ms ceiling config stable?

Thanks for any guidance or example configs.

  • 0
    TI__Genius 11900 points

    Hi 

    Ceiling mount and wall mount work on different processing chains and you can find separate demos at the below location

    Wall mount : radar_toolbox_3_10_00_05\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\3D_People_Tracking

    Ceiling mount: radar_toolbox_3_10_00_05\source\ti\examples\Industrial_and_Personal_Electronics\People_Tracking\Overhead_3D_People_Tracking

    Both will work with different configurations, so you will not be able to match them. You can make sure that frame periodicity remains same in both cases

     You can set the same periodicity using frameCfg CLI.

    You can set the frame periodicity of 3D people tracking demo to 120ms to make sure both have same FPS. Make sure you make changes in trackingCfg to reflect the change in frame periodicity

    Regards