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.

AWR2944EVM: HECR TLVs: side info transfer and range-doppler heat map

Part Number: AWR2944EVM
Other Parts Discussed in Thread: AWR2944

Tool/software:

Hi,

I see that in this application a there is a use in a compact point cloud in place of a standard one. What was the reason and is there any problem if I add to TLVs the side info and the range-doppler heat map?

Arie

  • Hi,

    The purpose of the compact point cloud is to reduce the transfer time. Usually, our demos use the UART to transfer the data to PC. Since UART is not very fast, we use ways to reduce the size of the data that must be transferred. 

    If you add additional data that must be transferred than the transfer time will increase and the demo will no longer work. You will need to increase the frame duration to make sure there is sufficient time to transfer the data

    thank you
    Cesar

  • Thank you for the explanation. Please explain how may I assess whether there is sufficient time for data transfer, i.e. to which extent should I reduce the frame rate. Is there any indication or measurement in the code? and why in this specific application there was not enough time for data transfer?

  • Hi

    The demo provides several timing measurements:

    "outputStats.transmitOutputTime" provides the time it takes to transmit the data. You can check this information to determine increase in transfer time.

    radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2944\mss\mss_main.c

        /* Update current frame transmit time */
        currSubFrameStats->outputStats.transmitOutputTime = (CycleCounterP_getCount32() - startTime) / (SOC_getSelfCpuClk() / 1000000U); /* In micro seconds */

    Thank you
    Cesar