Is It possible that i have a faulty LimeSDR-USB module despite it passes the quick test.
I have a feeling that it is a small detail that makes my LimeSDR total deaf.
But weeks, days and hours have passed testing reading and fiddling and still no signal in my LimeSDR.
Things that i have tried or looked at:
Faulty U.fl - SMA cords and plugs RP vs non RP SMA.
Multiple input plugs RX1 and RX2 all 6 have been tested.
Gain controllers and knobs in end user software, just raises the flat spectrum.
Different computers with different USB controllers USB3 and USB2.
Only one driver tested, (there is only one v18.104.22.168 dated 2015-08-15)
Different versions of firmware and gateware files tested v20.01 v19.04 v19.01 img rbf.
Curious behavior and observations:
when i connect Lime Suite from windows i get:
[09:00:02] INFO: Reference clock 30.72 MHz
[09:00:03] INFO: Connected Control port: LimeSDR-USB FW:4 HW:4 Protocol:1 GW:2.21 Ref Clk: 30.72 MHz
and when i connect Lime Suite from Linux i get:
[11:05:47] INFO: Disconnected control port
[11:05:58] WARNING: Gateware version mismatch!
Expected gateware version 2, revision 22
But found version 2, revision 21
Follow the FW and FPGA upgrade instructions:
Or run update on the command line: LimeUtil --update
[11:05:58] INFO: Reference clock 30.72 MHz
[11:05:58] INFO: Connected Control port: LimeSDR-USB FW:4 HW:4 Protocol:1 GW:2.21 Ref Clk: 30.72 MHz
and when i switch a nob or set a setting in Lime Suite and do GUI->chip and remove the same setting again and then do a Chip->GUI i don´t get my setting back?
In SDR Console and SDR Sharp, the receiver tends to hang and lock up the software after a short while.
any one… help
if some one have the will for it, then i´ll open a VNC to my LimeSDR box.