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.

AWRL6432: Dynamic frame period

Part Number: AWRL6432
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

    In AWRL6432 SDK, w_FramePeriodicity is used for frame period setting. It is a fixed period, for example 100ms. But in my application, dynamic frame period is required due to dynamic processing time. I want to trigger frame by software control instead of timing.For example, frame 1 post process request 66ms, after post process, trigger next frame immediately, frame 2 80ms, frame 3 150ms, frame 4 45ms. 

    What can I do? Thanks.

  • Hello,

    Thank you for reaching out over E2E with your question regarding dynamic frame period. For L-SDK 5.4 and above, the motion and presence detection demo can utilize a feature known as dynamic reconfiguration through the SysConfig MPD_DEMO configuration which enables the demo to switch between a high performance tracking profile and a low power presence profile.

    To understand how this is implemented, I would recommend looking for the DYNAMIC_RECONFIG macro in the following project files: motion_detect.c, mmw_cli.c, dpc.c, and power_management.c. At a high level, there is a state machine that keeps track of a frame counter based on either whether there is a tracking object or not which gets compared with two threshold values to determine what state to go to. If the sensor detects a continuous presence for frmPretoTrack frames, it automatically transitions to the tracker configuration. If no tracker objects are detected for frmTracktoPre frames, the demo reverts to the user-provided presence configuration.

    You can read more about this feature under the "Dynamic Reconfig" section in the SDK documentation of the motion and presence detection demo under: <MMWAVE_LSDK_INSTALL_DIR>/docs/api_guide_xwrL14xx/MOTION_AND_PRESENCE_DETECTION_DEMO.html. The documentation is also accessible via the following TI Resource Explorer link.

    Let me know if you have any other questions.

    Regards,

    Kristien