Need help. No Tx/Rx

[vol4iniche]

Hello, thanks for your work!

I’m experiencing an issue with the firmware from the repository and srsran. I see a spike on the desired frequency only during the eNB boot process, but after that, there’s no signal at all. It seems like the Pluto isn’t transmitting anything. Have you encountered anything like this before?

I’d appreciate any help!

[pumatrax]

same

[pgreenland]

Hi @vol4iniche and @pumatrax,

Apologies for the slow / very slow reply. I keep thinking I've got notifications on for new issues, but GitHub keeps proving me wrong.

In terms of not transmitting, there's a couple of tests scripts in the SoapySDR plugin repository: https://github.com/pgreenland/SoapyPlutoSDR/tree/sdr_gadget_timestamping/support - in C and Python. They should both do the same job.

It could be worth running one of them. An example of the output can be found here: https://www.quantulum.co.uk/blog/private-lte-with-analog-adalm-pluto/#test_loopback_c

The most common reason for not transmitting anything certainly for LTE is a machine that isn't able to meet the timing requirements. For example attempting to schedule a transmission in the past. If the FPGA finds data thats arriving late it simply discards it. Hoping fresh data with current or future timestamps will be arriving.

Quite a few folks have tried running from VMs, which never seems to go well. The emulated USB latency is far too high. A dedicated physical machine is a must. From experience it doesn't have to be all that powerful. I managed to get an LTE setup going with a Pluto and Pi 4.

Hope that helps,

Phil