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.

MMWAVEICBOOST: IWR6843ISK Radar and Carrier board Sampling Rate

Part Number: MMWAVEICBOOST
Other Parts Discussed in Thread: IWR6843ISK

Hi, 

I have a technical question regarding the sampling rate of the IWR6843ISK radar and more generally of the MMWAVEICBOOST carrier board.

Looking into the radar datasheets I noticed that the radar sampling rate is 25 MSPS if using Real and 12.5 if using Complex, but I haven't found any info regarding the sampling rate that can actually be read by the serial port once the raw data are pre-processed by DSP and ARM and eventually written to UART.

My doubts are: 

1) What is the difference between the two cases Real and Complex mentioned in the datasheets?

2) According to the datasheet, the radar is able to provide up to 25 Millions of samples per second. But what does a sample consist of? are they raw signals? And I suppose this sample rate can't be the same after the DSP/ARM as the processing takes some time. Is that correct?

 

To summarise my final question is: understand how many samples (points cloud) per second the board is capable to provide on the UART.

It would be very helpful if anyone can clarify these aspects or point me to any suitable docs where I can find this information.

Thank you very much, 

Regards,

Alessandro

  • HI, Alessandro:

    You are right, UART is not fast enough for raw data transfer.   Usually, the post processing is done on the device (through DSP or arm or hardware accelerator), and the point cloud can be transferred out using UART for visualization.    If you are thinking of getting the raw data out or range FFT data out, you can use LVDS for high speed data transfer.    You can find documentation on this topic at: file:///C:/ti/mmwave_sdk_03_03_00_03/packages/ti/demo/xwr68xx/mmw/docs/doxygen/html/index.html#LVDSStreamingNotes

    For offline raw data capture, you can check this app note: http://www.ti.com/lit/an/swra581b/swra581b.pdf

    For real and complex baseband signal chain, you can read this app note: http://www.ti.com/lit/wp/spyy007/spyy007.pdf

    Best,

    Zigang

     

  • Hi Zigang,

    Thank you for your reply and explanations. Now it's getting clearer to me.

    By the way, actually my goal is NOT to capture the raw data signal, since as you said the processing can be done directly by DSP and ARM. 

    What I wanted to understand is the sampling rate after DSP/ARM and whether it can be tuned or not. 

    How many points cloud per second is able to provide the board after DSP/ARM processing?

    This way, I can then estimate the amount of data (in terms of M/G bytes) I will collect during my experiments and set up the data collection architecture accordingly. 

    If I'm not wrong, in the configuration file, it is possible to configure the frame parameters (frameCfg) and the 5th argument should be the period of the frame, which means how long one frame should last. 

    From this I can suppose that the sampling rate can change according to that setting. 

    Am I on the right way?

    Thank you very much.

    Alessandro

  • HI, 

    The ADC sampling rate is always the same as you defined in the profileCfg.  But with the same profileCfg, you can still have different frame period.  In one frame, you will have certain number of chirps, and after that sensor is idle till the end of the frame duration.   So, ADC rate is fixed, but the sensor is not always chirping.  

    Depend on the number of detection, the point cloud size is different.  But we always have a maximum allowed point cloud defined for one frame because we can not have unlimited memory.   This maximum number is code based, the value can be 250.   

    Best,

    Zigang

  • Hi Zigang,

    It's clear to me that the sampling rate of the ADC is 25 Msps, at least for the radar that I am using IWR6843ISK.

    It's also clear that the number of points clouds can change frame by frame depending on what the radar can detect.

    What it's not clear yet is:  

    How many frames (each one with a different number of point clouds) per second can we get? Can this value be tuned in the configuration file?

    Regards,

    Alessandro

  • Hi, Alessandro:

    Yes, frame periodicity is programmed in frameCfg.  You can check the user guide C:\ti\mmwave_sdk_03_03_00_03\docs\mmwave_sdk_user_guide.pdf

    Search for frameCfg, the fifth parameter is frame periodicity in ms. 

    frameCfg 0 1 32 0 100 1 0

    Best,

    Zigang