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.

AWR1443BOOST: Distance data collected via serial port are repeated every two frames in lab0004_high_accuracy_14xx

Part Number: AWR1443BOOST
Other Parts Discussed in Thread: AWR1642, AWR1443, IWR1443BOOST, IWR1642BOOST

Hi,

I ask this problem again since it's been a long time and I haven't solved this problem.

I collected data of  lab0004_high_accuracy_14xx via serial port and wrote a script to decode it according to DataStructure_table_higAccuLab.pdf.

There is a strange phenomenon.The distance data are repeated every two frames in data.

For example,according to DataStructure_table_higAccuLab.pdf,the data from serial port in red box are ‘Range est,low16-bit’ and ‘Range est,high 16-bit’ .Users can turn they into accurate range .Red boxes in left is in Frame 1 and Red boxes in right is in next frame.They are always the same in two frames before and after.This  situation repeat every two frames.Here are data I decoded.

As you can see,range data repeat every two frames.I don't think my script is wrong based on previous analysis of data from serial port.By the way,the other data in two frames before and after don't repeat,like RangeProfile and so on.

Here is my  chirp setting profile.

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 1 1 0
adcCfg 2 1
adcbufCfg 0 1 0 1
profileCfg 0 77 7 7 212.8 0 0 18.32 1 1024 5000 0 0 40
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 1 0 50 1 0
calibDcRangeSig 0 -5 5 32
guiMonitor 1 1 0 0 0 1
RangeLimitCfg 1 2.0 3.0
sensorStart

I set frame periodicity to 50ms in frameCfg and RangeLimit 2.0-3.0 m.I only changed these two variables.

Simply speaking,I try to Minimize  frame periodicity as much as possible to get a larger sampling rate of distance,so I can estimate the vibration frequency more accurately.

I thought frame periodicity of 50ms was too short to complete the process chain so I checked that.According to the picture below ,the interFrameMssProcessingMargin in my data is 24808us means setting frame periodicity to 50ms can leave enough time for processing.I can even set it to 50-24.808=25ms theoretically as long as interFrameMssProcessingMargin >0.So this is not where the problem lies. 

So why this happened?I will really appreciate it if someone help me solve this problem!!!

Thank you.