Hi,
With the supplied TLVParser.py script, range FFT data that has been recorded can be written to a txt.
mmw Demo Data Structure_8_16-7.pdf indicates a structure tag at the beginning of each TLV structure.
The script uses struct.unpack for each packet section (range, azimuth, stats,....)
The data sequence of the heat map is: R1[0],R2[0],R3[0],R4[0],R5[0],R6[0], R7[0], R8[0], R1[1],R2[1].....R1[255],R2[255],R3[255],R4[255]
From %MMWAVE_SDK_PATH/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html under 'Azimuth static heatmap':
'The antenna data are complex symbols, with imaginary first and real second' as so:
Imag(ant 0, range 0), Real(ant 0, range 0),...,Imag(ant N-1, range 0),Real(ant N-1, range 0)
Initially this is used for range profile and should work with heatmap, considering Rx, Real, Imag.
However, the output before doing any uint to int conversion and assigning antenna appears to be somewhat false.
e.g.: 46, 137, 32, 65507, 65315, 233,65465, 65453, 65452
How must the structure tags from the pdf be implemented? How should the struct.unpack(format, buffer) input be configured?
Is there a way to get the heatmap plot data directly/ how does Demo Visualizer process the data?
Regards
