What is the maximum FrameLength, which can be received using comm.SDRuReceiver from USRP N210?

Question

Pushpalata T on 13 Oct 2015

0
Link

Direct link to this question

https://nl.mathworks.com/matlabcentral/answers/248323-what-is-the-maximum-framelength-which-can-be-received-using-comm-sdrureceiver-from-usrp-n210

Commented: Pushpalata T on 17 Nov 2015

I want to receive a subframe of 20 MHz LTE system but unable to receive a frame of length 61440 samples from USRP N210

The piece of code which has been executed is given below:

hSDRu_Receive = comm.SDRuReceiver('192.168.10.2', ...
                                    'CenterFrequency',        748.5e6, ...
                                    'Gain',                   0, ...
                                    'DecimationFactor',      10, ...
                                    'EnableBurstMode',          true, ...
                                     'FrameLength',             61440,...
                                    'OutputDataType',         'double');
Received_Waveform = step(hSDRu_Receive);

The error which I am getting is :

Assertion failed.
Error in mapiPrivate (line 159)
Error in openDataConnection (line 6)
Error in mapiPrivate (line 53)
Error in openDataConnection (line 6)
Error in SDRuReceiver/setupImplLocal (line 300)
Error in SDRuBase/setupImpl (line 366)
Error in DL_PBCH_decoding (line 14)
    Received_Waveform = step(hSDRu_Receive);

0 Comments
Show -2 older commentsHide -2 older comments

Sign in to comment.

Sign in to answer this question.

Answer 1

Walter Roberson on 13 Oct 2015

0
Link

Direct link to this answer

https://nl.mathworks.com/matlabcentral/answers/248323-what-is-the-maximum-framelength-which-can-be-received-using-comm-sdrureceiver-from-usrp-n210#answer_195823

I did some checking around, and the maximum size I could see anyone using in the examples was 4000. But that does not prove anything about the maximum length.

The maximum length is not on the spec sheets of the N210 or anywhere obvious in the manuals.

When I looked at the ettus documentation tree, it looked to me as if the limit as far as ettus is concerned is possibly the size of the buffer provided to the receive routine.

I do not have that toolkit (or appropriate hardware) to check the source to see where the assertion is coming in.

Opening a support case would probably be appropriate.