I am using iio-oscilloscope to do loopback sample capture. I have created a custom profile using
matlab profile generator for ad9371. Please find the profile here.
I load this profile and use a .mat data file generated for transmission.
However I think the packets are not transmitted properly since I have intentionally created zeros and power variations within the transmit samples which I cannot see in the loopback captured samples.
Could you please let me know if I have to follow any format while loading/generating mat files? Should the number of samples be a function of transmit/receive sample rate?
I have seen the instructions here
however sometimes when I load the .mat file the osc crashes. So I think I am missing something more than what is described in the above link.
Thanks and Regards
Provide data in your .MAT file as one vector per channel. If OSC is crashing you might be loading data that is too large. Generally, you should not exceed 2^20 samples per channel. This is the default DMA/CMU limit. Number of samples has no relation to the sample rate.
So if I wanted to transmit only on TX1, my mat file will be a matrix of 2 columns and N rows, where N is the sample size, where each column corresponds to I and Q respectively?
Can I also transmit a complex vecor instead, in which case the mat file will be 1 column and N rows?
Also does capturing M time domain samples in iio oscilloscope ensure that these M samples are continuous?That is there is no sample drop in between?
Thanks in advance
Yes for the transceivers successive vectors will be mapped to I and Q.
Yes complex is supported.
A capture is contiguous but not successive captures.
I transmit a symmetric preamble(digital samples in which first K1 samples are identical to next K2 samples), receive them and then perform a correlation(schmidl cox algorithm for timing synchronisation) to detect the preamble all within a single capture.
What I notice is that the received peaks are more frequent than the transmit peaks. I am not sure why this happens. Do you have any idea on what could go wrong?
I would verify the hardware is running at the desired rates and the signal bandwidth is as expected.
You could also verify this in the data by resampling it (by probably 2 or 1/2) and check your successive peak distances.