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: Frame Rate Ignoring frameCfg Setting

Part Number: IWR6843AOP
Other Parts Discussed in Thread: IWR6843

Tool/software:

Hello, 

I'm working with the IWR6843 3D People Tracking demo and experiencing unexpected frame rate behavior that doesn't match my configuration.

Configuration:

frameCfg 0 2 96 0 900.00 1 0
trackingCfg 1 2 800 1 46 96 900

Both commands are set to 900ms frame period, but the actual output behavior is around 55ms! Can it be overwritten somewhere else in the code? 

Cheers,

/S

  • Hey Sina!
    Sorry for the delay in response. I am looking into your query and will get back to you soon.
    Thanks

  • Thank. Appreciate nay update on this

  • Hello Sina!

    Sorry for the delay in response. I have tried to replicate your issue.

    However, I can see the frame period change to 900ms when I make your changes in 'frameCfg' and 'trackingCfg' CLI commands of 3D_People_Tracking/chirp_configs/AOP_6m_default.cfg present in Radar Toolbox.

    Can you please share:
    1. What config are you using when you face this issue?
    2. How are you checking and concluding that the frame rate behavior is 55ms?

    Regards
    Saransh

  • Hi Saransh,

    Thanks for your message. I use the original AOP_6m_staticRetention_FallDetection.cfg 

    I sends the commands after the sensor boots and then I just check the rate of serial output from the sensor as an indictor of the frame rate assuming the rate of spitting  out data would change based on the frame ratr adjustment, am I right? 

    The sensor keeps sensing data every 55ms regardless of frameCfg values. 

  • Hello Saransh, any update on this post? Thanks in advance.

  • Hello!

    Upon doing the following steps:
    1. Flash 3D People Tracking demo on IWR6843 device
    2. Use Industrial_Visualizer.exe located at: radar_toolbox\tools\visualizers\Applications_Visualizer\Industrial_Visualizer
    3. Select configuration: AOP_6m_staticRetention with the above 2 specified CLI commands changed

    I am able to see the output of point-cloud on visualizer change to 900ms frame period. The serial output from sensor over UART is visualized by the Industrial Visualizer.

    Hence, I am still unable to replicate your issue.

    Can you confirm if you are also following the above steps and can see the frame period change by observing the output on UART?
    Also, by any chance, have you put any debug statements inside Fall Detection logic to check the frame Rate?

    Thanks,
    Saransh