Topics

Help needed to get started with Limesdr mini and sdrangel


Patrick Dohmen
 

Hey guys,

just found SDRAngel while searching for a TX capable Linux SDR frontend.

I have just started to play around with my newly arrived LimeSDR Mini and already managed to get it running with gqrx and did some basic experiments using gnuradio.

As is just build SDRAngel from the git repo following the instructions from the readme, I get it starting and can choose only Test Sources and File Sources. gqrx detects the Lime Mini without problems, but I can't find a way to get it selectable as source or sink in SDRAngel.

Some infos that might be important:

 pd@radiobox ~ $ sdrangel --version
 SDRangel 3.14.6

 pd@radiobox ~ $ LimeUtil --find
   * [LimeSDR Mini, media=USB 3.0, module=FT601, addr=24607:1027, serial=1D3C035375FA8B]

 pd@radiobox ~ $ ls /opt/install/LimeSuite/lib/
 cmake  libLimeSuite.so  libLimeSuite.so.18.04-1 libLimeSuite.so.18.04.2  pkgconfig

 pd@radiobox ~ $ LimeQuickTest
 [ TESTING STARTED ]
 ->Start time: Wed May 16 12:07:52 2018

 Reference clock 40.00 MHz
 ->Device: LimeSDR Mini, media=USB 3.0, module=FT601, addr=24607:1027, serial=1D3C035375FA8B
   Serial Number: 1D3C035375FA8B

 [ Clock Network Test ]
 ->REF clock test
   Test results: 62347; 10008; 23205 - PASSED
 ->VCTCXO test
   Results : 6710983 (min); 6711147 (max) - PASSED
 ->Clock Network Test PASSED

 [ FPGA EEPROM Test ]
 ->Read EEPROM
 ->Read data: 12 03 14 12 03 14 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):
   (SXR=1000.0MHz, SXT=1005.0MHz, TXPAD=0): Result:(-12.3 dBFS, 5.00 MHz) - PASSED
 ->Configure LMS
 ->Run Tests (TX_1 -> LNA_H):
   (SXR=2100.0MHz, SXT=2105.0MHz, TXPAD=0): Result:(-13.5 dBFS, 5.00 MHz) - PASSED
 ->RF Loopback Test PASSED

 => Board tests PASSED <=

 Elapsed time: 8.56 seconds

Any hints?


Thanks in advance, 73,

Patrick, DL4PD


Edouard Griffiths
 

Hello,

sdrangel log that gets printed on the console up to "MainWindow::Mainwindow: end" can reveal issues with the plugins like unresolved references or if they are attempts to load them at all. For the particular case of LimeSDR you should see:

2018-05-16 23:58:48.109 (D) PluginManager::loadPluginsDir: fileName:  libinputlimesdr.so
2018-05-16 23:58:48.110 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
...
2018-05-16 23:58:48.096 (D) PluginManager::loadPluginsDir: fileName:  liboutputlimesdr.so
2018-05-16 23:58:48.097 (I) PluginManager::loadPluginsDir: loaded plugin liboutputlimesdr.so

Brgds, Edouard.


Patrick Dohmen
 

Hey Edouard,


thanks for your reply! Sorry I forgot to add the output of sdrangel, here it comes:


pd@radiobox ~/software/sdrangel/build (master) $ sdrangel
17.05.2018 06:15:10.027 (I) SDRangel 3.14.6 Qt 5.9.5 64b x86_64 Ubuntu 18.04 LTS DSP Rx:16b Tx:16b PID 2499
17.05.2018 06:15:10.618 (W) qUncompress: Input data is corrupted
17.05.2018 06:15:10.618 (W) qUncompress: Input data is corrupted
17.05.2018 06:15:10.618 (W) qUncompress: Input data is corrupted
17.05.2018 06:15:10.619 (I) PluginManager::loadPluginsDir: loaded plugin libchanalyzer.so
17.05.2018 06:15:10.619 (I) PluginManager::loadPluginsDir: loaded plugin libchanalyzerng.so
17.05.2018 06:15:10.620 (I) PluginManager::loadPluginsDir: loaded plugin libdemodam.so
17.05.2018 06:15:10.620 (I) PluginManager::loadPluginsDir: loaded plugin libdemodatv.so
17.05.2018 06:15:10.621 (I) PluginManager::loadPluginsDir: loaded plugin libdemodbfm.so
17.05.2018 06:15:10.660 (I) PluginManager::loadPluginsDir: loaded plugin libdemoddatv.so
17.05.2018 06:15:10.661 (I) PluginManager::loadPluginsDir: loaded plugin libdemodlora.so
17.05.2018 06:15:10.661 (I) PluginManager::loadPluginsDir: loaded plugin libdemodnfm.so
17.05.2018 06:15:10.662 (I) PluginManager::loadPluginsDir: loaded plugin libdemodssb.so
17.05.2018 06:15:10.662 (I) PluginManager::loadPluginsDir: loaded plugin libdemodtcpsrc.so
17.05.2018 06:15:10.663 (I) PluginManager::loadPluginsDir: loaded plugin libdemodudpsrc.so
17.05.2018 06:15:10.663 (I) PluginManager::loadPluginsDir: loaded plugin libdemodwfm.so
17.05.2018 06:15:10.664 (I) PluginManager::loadPluginsDir: loaded plugin libmodam.so
17.05.2018 06:15:10.755 (I) PluginManager::loadPluginsDir: loaded plugin libmodatv.so
17.05.2018 06:15:10.755 (I) PluginManager::loadPluginsDir: loaded plugin libmodnfm.so
17.05.2018 06:15:10.756 (I) PluginManager::loadPluginsDir: loaded plugin libmodssb.so
17.05.2018 06:15:10.757 (I) PluginManager::loadPluginsDir: loaded plugin libmodudpsink.so
17.05.2018 06:15:10.757 (I) PluginManager::loadPluginsDir: loaded plugin libmodwfm.so
17.05.2018 06:15:10.758 (I) PluginManager::loadPluginsDir: loaded plugin liboutputfilesink.so
17.05.2018 06:15:10.759 (I) PluginManager::loadPluginsDir: loaded plugin liboutputlimesdr.so
17.05.2018 06:15:10.760 (I) PluginManager::loadPluginsDir: loaded plugin libinputfcdpro.so
17.05.2018 06:15:10.761 (I) PluginManager::loadPluginsDir: loaded plugin libinputfcdproplus.so
17.05.2018 06:15:10.761 (I) PluginManager::loadPluginsDir: loaded plugin libinputfilesource.so
17.05.2018 06:15:10.762 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
17.05.2018 06:15:10.763 (I) PluginManager::loadPluginsDir: loaded plugin libinputrtlsdr.so
17.05.2018 06:15:10.763 (I) PluginManager::loadPluginsDir: loaded plugin libinputtestsource.so
17.05.2018 06:15:11.311 (I) WebAPIServer::start: starting web API server at http://127.0.0.1:8091
17.05.2018 06:15:13.299 (I) WebAPIServer::stop: stopped web API server at http://127.0.0.1:8091
SDRangel quit.

It's looking good to me.


73,

Patrick



Am 17.05.2018 um 00:02 schrieb Edouard Griffiths:

Hello,

sdrangel log that gets printed on the console up to "MainWindow::Mainwindow: end" can reveal issues with the plugins like unresolved references or if they are attempts to load them at all. For the particular case of LimeSDR you should see:

2018-05-16 23:58:48.109 (D) PluginManager::loadPluginsDir: fileName:  libinputlimesdr.so
2018-05-16 23:58:48.110 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
...
2018-05-16 23:58:48.096 (D) PluginManager::loadPluginsDir: fileName:  liboutputlimesdr.so
2018-05-16 23:58:48.097 (I) PluginManager::loadPluginsDir: loaded plugin liboutputlimesdr.so

Brgds, Edouard.


Patrick Dohmen
 

Hi again,

I have tried to build it on another computer (it's a laptop) but it only supports USB2.0.

Anyway: the same as with the first computer! Everything builds fine, gqrx detects the Lime mini, but sdrangel does not. There's no error message or something.


I hope someone could help out...


73,

Patrick



Am 17.05.2018 um 06:17 schrieb Patrick Dohmen:

Hey Edouard,


thanks for your reply! Sorry I forgot to add the output of sdrangel, here it comes:


pd@radiobox ~/software/sdrangel/build (master) $ sdrangel
17.05.2018 06:15:10.027 (I) SDRangel 3.14.6 Qt 5.9.5 64b x86_64 Ubuntu 18.04 LTS DSP Rx:16b Tx:16b PID 2499
17.05.2018 06:15:10.618 (W) qUncompress: Input data is corrupted
17.05.2018 06:15:10.618 (W) qUncompress: Input data is corrupted
17.05.2018 06:15:10.618 (W) qUncompress: Input data is corrupted
17.05.2018 06:15:10.619 (I) PluginManager::loadPluginsDir: loaded plugin libchanalyzer.so
17.05.2018 06:15:10.619 (I) PluginManager::loadPluginsDir: loaded plugin libchanalyzerng.so
17.05.2018 06:15:10.620 (I) PluginManager::loadPluginsDir: loaded plugin libdemodam.so
17.05.2018 06:15:10.620 (I) PluginManager::loadPluginsDir: loaded plugin libdemodatv.so
17.05.2018 06:15:10.621 (I) PluginManager::loadPluginsDir: loaded plugin libdemodbfm.so
17.05.2018 06:15:10.660 (I) PluginManager::loadPluginsDir: loaded plugin libdemoddatv.so
17.05.2018 06:15:10.661 (I) PluginManager::loadPluginsDir: loaded plugin libdemodlora.so
17.05.2018 06:15:10.661 (I) PluginManager::loadPluginsDir: loaded plugin libdemodnfm.so
17.05.2018 06:15:10.662 (I) PluginManager::loadPluginsDir: loaded plugin libdemodssb.so
17.05.2018 06:15:10.662 (I) PluginManager::loadPluginsDir: loaded plugin libdemodtcpsrc.so
17.05.2018 06:15:10.663 (I) PluginManager::loadPluginsDir: loaded plugin libdemodudpsrc.so
17.05.2018 06:15:10.663 (I) PluginManager::loadPluginsDir: loaded plugin libdemodwfm.so
17.05.2018 06:15:10.664 (I) PluginManager::loadPluginsDir: loaded plugin libmodam.so
17.05.2018 06:15:10.755 (I) PluginManager::loadPluginsDir: loaded plugin libmodatv.so
17.05.2018 06:15:10.755 (I) PluginManager::loadPluginsDir: loaded plugin libmodnfm.so
17.05.2018 06:15:10.756 (I) PluginManager::loadPluginsDir: loaded plugin libmodssb.so
17.05.2018 06:15:10.757 (I) PluginManager::loadPluginsDir: loaded plugin libmodudpsink.so
17.05.2018 06:15:10.757 (I) PluginManager::loadPluginsDir: loaded plugin libmodwfm.so
17.05.2018 06:15:10.758 (I) PluginManager::loadPluginsDir: loaded plugin liboutputfilesink.so
17.05.2018 06:15:10.759 (I) PluginManager::loadPluginsDir: loaded plugin liboutputlimesdr.so
17.05.2018 06:15:10.760 (I) PluginManager::loadPluginsDir: loaded plugin libinputfcdpro.so
17.05.2018 06:15:10.761 (I) PluginManager::loadPluginsDir: loaded plugin libinputfcdproplus.so
17.05.2018 06:15:10.761 (I) PluginManager::loadPluginsDir: loaded plugin libinputfilesource.so
17.05.2018 06:15:10.762 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
17.05.2018 06:15:10.763 (I) PluginManager::loadPluginsDir: loaded plugin libinputrtlsdr.so
17.05.2018 06:15:10.763 (I) PluginManager::loadPluginsDir: loaded plugin libinputtestsource.so
17.05.2018 06:15:11.311 (I) WebAPIServer::start: starting web API server at http://127.0.0.1:8091
17.05.2018 06:15:13.299 (I) WebAPIServer::stop: stopped web API server at http://127.0.0.1:8091
SDRangel quit.

It's looking good to me.


73,

Patrick



Am 17.05.2018 um 00:02 schrieb Edouard Griffiths:
Hello,

sdrangel log that gets printed on the console up to "MainWindow::Mainwindow: end" can reveal issues with the plugins like unresolved references or if they are attempts to load them at all. For the particular case of LimeSDR you should see:

2018-05-16 23:58:48.109 (D) PluginManager::loadPluginsDir: fileName:  libinputlimesdr.so
2018-05-16 23:58:48.110 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
...
2018-05-16 23:58:48.096 (D) PluginManager::loadPluginsDir: fileName:  liboutputlimesdr.so
2018-05-16 23:58:48.097 (I) PluginManager::loadPluginsDir: loaded plugin liboutputlimesdr.so

Brgds, Edouard.



Evariste Courjaud
 

Hi Patrick, 
Could you provide info :
LimeUtil --info

Mine report : 
Version information:
  Library version: v18.04.1-g2db5552c
  Build timestamp: 2018-05-03
  Interface version: v2018.3.0
  Binary interface: 18.04-1

And what SdrAngel should output :
2018-05-18 11:24:59.250 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
2018-05-18 11:24:59.252 (I) PluginManager::loadPluginsDir: loaded plugin libinputplutosdr.so
2018-05-18 11:24:59.254 (I) PluginManager::loadPluginsDir: loaded plugin libinputrtlsdr.so
2018-05-18 11:24:59.255 (I) PluginManager::loadPluginsDir: loaded plugin libinputsdrdaemonsource.so
2018-05-18 11:24:59.257 (I) PluginManager::loadPluginsDir: loaded plugin libinputtestsource.so
Reference clock 40,00 MHz
Reference clock 40,00 MHz
2018-05-18 11:25:01.837 (I) WebAPIServer::start: starting web API server at http://127.0.0.1:8091
Reference clock 40,00 MHz
Rx calibration finished
Rx calibration finished
 
73's Evariste F5OEO


Patrick Dohmen
 

Evariste, here's the output:

pd@radiobox ~/software/sdrangel (master) $ LimeUtil --info
######################################################
## LimeSuite information summary
######################################################

Version information:
  Library version:    v18.04.1-myriadrf1~bionic
  Build timestamp:    2018-04-29
  Interface version:    v2018.3.0
  Binary interface:    18.04-1

System resources:
  Installation root:    /usr
  User home directory:    /home/pd
  App data directory:    /home/pd/.local/share/LimeSuite
  Config directory:    /home/pd/.limesuite
  Image search paths:
     - /home/pd/.local/share/LimeSuite/images
     - /usr/share/LimeSuite/images

Supported connections:
   * FT601
   * FX3
   * PCIEXillybus

And you can see the output of my sdrangel startup at one of the answers I gave - it looks pretty good to me.


Thanks for your effort,

73,

Patrick




Am 18.05.2018 um 11:46 schrieb Evariste Courjaud:

Hi Patrick, 
Could you provide info :
LimeUtil --info

Mine report : 
Version information:
  Library version: v18.04.1-g2db5552c
  Build timestamp: 2018-05-03
  Interface version: v2018.3.0
  Binary interface: 18.04-1

And what SdrAngel should output :
2018-05-18 11:24:59.250 (I) PluginManager::loadPluginsDir: loaded plugin libinputlimesdr.so
2018-05-18 11:24:59.252 (I) PluginManager::loadPluginsDir: loaded plugin libinputplutosdr.so
2018-05-18 11:24:59.254 (I) PluginManager::loadPluginsDir: loaded plugin libinputrtlsdr.so
2018-05-18 11:24:59.255 (I) PluginManager::loadPluginsDir: loaded plugin libinputsdrdaemonsource.so
2018-05-18 11:24:59.257 (I) PluginManager::loadPluginsDir: loaded plugin libinputtestsource.so
Reference clock 40,00 MHz
Reference clock 40,00 MHz
2018-05-18 11:25:01.837 (I) WebAPIServer::start: starting web API server at http://127.0.0.1:8091
Reference clock 40,00 MHz
Rx calibration finished
Rx calibration finished
 
73's Evariste F5OEO


Evariste Courjaud
 

Patrick,

As we can note difference :
- you use LimeSuite from PPA
- don't know your firmware number

What's strange is SdrAngel should output a message if there is any issue on opening LimeSDR(don't know if you have to set a verbose level for that) : https://github.com/f4exb/sdrangel/blob/91b000c3ed8b51c88ae3dfce1ad31d9d811931d9/devices/limesdr/devicelimesdrparam.cpp#L26

Edouard should could confirm, but I suggest :
- Compiling LimeSuite from sources (github)
- Update your firmware : LimeUtil --update

Evariste


Edouard Griffiths
 

Hello,

it does not seem you have the debug level activated for the log. It could certainly help although the most critical messages should appear. To activate debug: from the main window go to Preferences > Logging then in the "Console log level" combo choose "Debug". Confirm with OK. You may need to stop and start SDRangel for it to take effect.

When in doubt compiling from source can help also because you may discover issues with your installation at cmake and/or compile time and also it will fit your hardware better possibly solving hard to detect architecture issues.

The firmware version to be used for the mini is the latest (still the latest I believe) which should be 1.24

Best regards, Edouard.


Patrick Dohmen
 

Edouard,

logging is enabled and my installation of sdrangel is a source build. The firmware version is the latest (r1.24). No errors occur during the build.

Still no information why it does not detect the Lime mini :\


73,

Patrcik



Am 18.05.2018 um 18:11 schrieb Edouard Griffiths:

Hello,

it does not seem you have the debug level activated for the log. It could certainly help although the most critical messages should appear. To activate debug: from the main window go to Preferences > Logging then in the "Console log level" combo choose "Debug". Confirm with OK. You may need to stop and start SDRangel for it to take effect.

When in doubt compiling from source can help also because you may discover issues with your installation at cmake and/or compile time and also it will fit your hardware better possibly solving hard to detect architecture issues.

The firmware version to be used for the mini is the latest (still the latest I believe) which should be 1.24

Best regards, Edouard.


Edouard Griffiths
 
Edited

Simple question: do you connect your Mini on a USB3 or USB2 port? And if on USB3 is there an intermediate cable that could be USB2? The Mini is quite picky on this while the Lime-USB is less sensitive. Both do not use the same USB controller chip. It just happened to me while doing some demo with the Mini: it would not work with a USB2 cable extension but it did when connecting the Mini directly on the USB3 slot.
Best regards, Edouard.


Patrick Dohmen
 

I have tried both: USB 3.0 on a PC and USB 2.0 on a Laptop.

No success... 

73,
Patrick



Am 25.05.2018 12:29 vorm. schrieb Edouard Griffiths <f4exb06@...>:

Simple question: do you connect your Mini on a USB3 or USB2 port?
Best regards, Edouard.


Patrick Dohmen
 

Hey Edouard,

 \o/

Got it running!

Today I did a fresh "git pull origin" and rebuilt the whole repo - now it's working.


Thanks for any help,

Patrick


Am 25.05.2018 um 15:16 schrieb Patrick Dohmen:

I have tried both: USB 3.0 on a PC and USB 2.0 on a Laptop.

No success... 

73,
Patrick



Am 25.05.2018 12:29 vorm. schrieb Edouard Griffiths <f4exb06@...>:
Simple question: do you connect your Mini on a USB3 or USB2 port?
Best regards, Edouard.