DCA1000EVM: Using Python with 160ms read each frame.

Hi Experts,

Good day.

I am using a DCA1000EVM to acquire raw data from an IWR1843BOOST device using a Python library called OpenRadar which makes use of python sockets. Comparing these acquisitions with that of mmWave Studio, I have found that the Python code takes more time to acquire the signals than the frame periodicity (I am using a 70ms periodicity, and Python takes up to 160ms to read each frame). I am worried that I might be losing frames and wanted to know if the DCA1000 board has some buffer to store the frames until they are read from the computer. In this case, even though Python takes up more time to read frames, the information will not be lost.

I am receiving radar data in Python in the same format as the .bin files generated from mmWave Studio. My concern is related to what happens when my Python codes need a time T to read and format the data, and this T is bigger than frame periodicity. For example, let's say I read frame number 1 in t=0. After a time t=t_periodicity, a second frame is ready on the DCA1000 to be read, but my script will not try to read it until a time t=T (T>t_periodicity) because of internal delays. When after a time T a frame is read from Python, is it frame number 2 that has been waiting (stored in a buffer) or is it the frame that corresponds to the time T that has elapsed from the last reading (e.g., frame 3)?

Please advise.

Regards,

Josel