Lime SDR Mini problem - no RF output

[g7kpm]

Hi, the Lime SDR mini on GB3CT's transmitter appears to have ceased functioning as there is no RF output from it. It has been working ok, but stopped transmitting last week. The SDR LEDs are flashing and the Pi is communicating OK with it as I have tried the Lime diagnostic function in the menu which talks to the Lime OK. It reports a board failure on the loopback test, which I assume is due to no loopback connection between the SMA ports?
Can anyone advise upon any further diagnostic steps to take to find where the problem is?

Thanks, G7KPM

[G8GKQ]

Hi Jason

If you go to the ssh prompt and run

Code: Select all

LimeQuickTest

Then post the resulting text here and we can see what the failure is.

Marginal test failures are normal. Here's one that I use all the time:

Code: Select all

pi@raspberrypi:~/rpidatv $ LimeQuickTest
[ TESTING STARTED ]
->Start time: Tue Aug 17 21:41:43 2021
->LimeSuite version: 20.10.0-unknown

->Device: LimeSDR Mini, media=USB 3.0, module=FT601, addr=24607:1027, serial=1D4C2CAE8C28A4, HW=2, GW=1.30
  Serial Number: 1D4C2CAE8C28A4
 Chip temperature: 25 C

[ Clock Network Test ]
->REF clock test
  Test results: 36657; 49854; 63051 - PASSED
->VCTCXO test
  Results : 6711006 (min); 6711164 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 13 02 0C 13 02 0C 02
->FPGA EEPROM Test PASSED

[ LMS7002M Test ]
->Perform Registers Test
->External Reset line test
  Reg 0x20: Write value 0xFFFD, Read value 0xFFFD
  Reg 0x20: value after reset 0x0FFFF
->LMS7002M Test PASSED

[ RF Loopback Test ]
->Configure LMS
->Run Tests (TX_2 -> LNA_W):
  CH0 (SXR=1000.0MHz, SXT=1005.0MHz): Result:(-18.6 dBFS, 5.00 MHz) - PASSED
->Run Tests (TX_1 -> LNA_H):
  CH0 (SXR=2100.0MHz, SXT=2105.0MHz): Result:(-20.2 dBFS, 5.00 MHz) - FAILED
->RF Loopback Test FAILED

=> Board tests FAILED <=

Elapsed time: 2.79 seconds

Dave

[VK3IE]

Have you tried re flash 1.30 or re upload dvb firmware.
Rob

[g7kpm]

Thanks for the replies. A Lime firmware reflash appears to have solved the problem, so not sure what has happened there!
Panic over!

Thanks again,

Jason G7KPM