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: Range Doppler Image Heat Map frame rate limitations

Part Number: IWR6843AOP

When using the mmWave Demo Visualizer the frame rate is limited to 4 frames per second if the Range Doppler Heat Map is selected. I assumed it had something to do with the CPU limitations, but when I load a config from the pc, I can get the Doppler heat map at 10 frames per second and the CPU load is only at 55%. I can actually run the frame rate up to 16 frames/sec at a CPU load of 92%, but I don't want to load the CPU that much. What is the limiting factor for the frame rate with the Range Doppler Image Heat Map? I am using the radar to determine mass flow of small, high speed objects and I think the higher frame rate would provide more accurate information but only if the radar is providing good data.

This is the config file I am running (generated by the mmWave Sensing Estimator):

profileCfg 0 60 8 7 23 0 0 170 1 64 4000 0 0 158
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 0 0 0 0 0 4
frameCfg 0 2 16 0 100 1 0
lowPower 0 0
guiMonitor -1 0 0 0 0 1 0
  • Hello, most are out for winter holidays the next week. Please expect delayed responses.

    The main limitation is UART transmission time each frame. If not streaming other data you can sometimes increase the framerate without errors. It will depend on how much other data you are sending.

    Regards,

    Jackson