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.

AWR1642BOOST: Issue with the range doppler heat map from the lab 4 obstacle detection

Part Number: AWR1642BOOST

I am having an issue getting any data from the Range-Doppler Heat Map when using the obstacle detection demo. I have changed the guiMonitor line in the configuration file appropriately to get a range doppler heat map. I am using the getRangeDopplerHeatMap function that is provided in the MATLAB code.

Here is the section of code that I call the function and try to plot the heatmap:

[rangeDoppler, byteVecIdx] = getRangeDopplerHeatMap(bytevec_cp, ...
                            byteVecIdx, ...
                            Params.dataPath.numRangeBins, ...
                            Params.dataPath.numDopplerBins);

range = (0:Params.dataPath.numRangeBins-1) * Params.dataPath.rangeResolutionMeters;
doppler = (-Params.dataPath.numDopplerBins/2:Params.dataPath.numDopplerBins/2)*Params.dataPath.dopplerResolutionMps;

figure(1)
cLim = [0, Inf];
imagesc(range, doppler, rangeDoppler, cLim);
set(gca,'YDir','normal')
ylabel('Doppler [m/s]');
xlabel('Range [m]');
colorbar;

Here is the provided getRangeDopplerHeatMap function:

function [rangeDoppler, idx] = getRangeDopplerHeatMap(bytevec, idx, numDopplerBins, numRangeBins)
    len = numDopplerBins * numRangeBins * 2;
    rangeDoppler = bytevec(idx+(1:len));
    idx = idx + len;
    rangeDoppler = rangeDoppler(1:2:end) + rangeDoppler(2:2:end)*256;
    rangeDoppler = reshape(rangeDoppler, numDopplerBins, numRangeBins);
    rangeDoppler = fftshift(rangeDoppler,1);
return

Here is what my output looks like:

Everything else seems to work fine. I've tested the demo and the range-azimuth heat map without any problems, but I can't figure out what is going wrong with the range-doppler heat map.

Thanks,

-AJ

  • Hi,

    Can you try to increase the frame duration to make sure there is sufficient time to transfer the heat map?

    thank you

    Cesar

  • Hi Cesar,

    I increased the frame duration from 100 to 333.33. I still have the same issue. I got this number from the out of box demo that properly displayed the range-doppler heatmap. If that is not sufficient is there a number that you would suggest increasing it to?

  • Hi, I think this frame duration should allow sufficient time to transfer the heat map.

    The next step would be to check the heat map before it is transferred to the GUI.

    In order to do that one would have to use Code Composer Studio to set a break point after heat map computation. Then one could copy the heatmap to a binary file and display in python or matlab.

    This would allow to check if heatmap before it is sent to PC host.

    I will report this to our development team to debug/test for the next release of the lab.

    Unfortunately I don't have a date when this will happen yet.

    thank you

    Cesar

  • Understood.

    Is there any other lab or demo in python or matlab that displays a range-doppler heat map that I may be able to reference in the meantime? I have looked at the out-of-box demo, but I don't know JavaScript as well. If that's the only other one then that will have to do, but if you're able to point me in the direction of any other examples that would be appreciated.

  • Hi,

    I can provide you a matlab gui that we use internally for the mmWave SDK 3.5 demo.

    I think it will be useful for you

    thank you

    Cesar

  • I have just downloaded it. I'll go through and start working with it.

    Thank you for your help.

  • Thank you

    I will close this thread now.

    Cesar