IWR6843ISK: converting .bin data stored from mmWave Demo Visualiser, into Relative Power (dB)

Dear Steve:

Can you please elaborate more on what you are parsing out of the .bin file that you are using to generate the Matlab plot that you referenced.

Best regards,

Connor Desmond

Hi Connor,

From the .bin file, I’m reading the logMagRange, Range Profile data.

This is enumerated as type 2, in CCS, before being sent to the mmWave Demo Visualiser, from where they’re saved into the .bin

if (pGuiMonSel->logMagRange)

{

       tl[tlvIdx].type = MMWDEMO_OUTPUT_MSG_RANGE_PROFILE;

       tl[tlvIdx].length = sizeof(uint16_t) * subFrameCfg->numRangeBins;

I find these in the .bin file by looking for the same .type

In my .bin file, there 2048 bytes (.length), which I’m reading as uint16 into 1024 values, and then plotting in Matlab

The shape of the Matlab plot looks just like the plot I can create in real time in the mmWave Demo Visualizer. However, the scaling of the Matlab isn’t correct in the y-axis, and isn’t in Relative Power (dB). In Demo Visualiser, the Noise level for my setup is around 25dB and the peak power at around 95dB. The values from the .bin file are approx. 2400 and 5350 respectively.  Is there a scaling factor or dB conversion ?

Thanks

Dear Steve:

I would look at the function processRangeNoiseProfile() contained in the mmWave.js file. You can get access to this file by importing the Visualizer into GUI composer to look at the code. The function is located at around line 2560. Let me know if this gives an insight in the scaling issue that you are facing.

Best regards,

Connor Desmond