Limenet micro install problems

After waiting 8 months I finally received my LimeNet micro. I would like to use the board as a remote Ham tranceiver, but first would like to test peripheral equipment through GNU radio.
Having a fresh Raspbian image installed I tried to get the software installed following the described install procedure to the letter, but get very confused.

So far it refers me to link after link after link after link. I get totally confused. It looks like I need SoapySDR, but also refers to a PPA (=Ubuntu) method.
Isn’t there a better description of what to use and how to install it?

I have even tried to use the PiSDR image but this gave also no success, also lack of proper documentation. There is a lot of software in the image but it is not clear how to use it. I had GNURadio installed but this did not connect the LimeNet micro. Now I am back to the original Rasbian Lite version.

Don’t set up the PPAs, since these are for Ubuntu only.

Don’t install SoapySDR or Lime Suite packages from the Raspbian repos, as these will be quite old.

Install SoapySDR from source:

If you want to use the SDR remotely over the network, e.g. with SDRangel running on a laptop, also install the SoapyRemote software.

Next install Lime Suite from source:

https://wiki.myriadrf.org/Lime_Suite#Building_from_source

If you want to use GNU Radio, it is recommended to use the gr-limesdr source/sink blocks.

Examples are included in the repo.

It wouldn’t make sense to distribute documentation with PiSDR that explained how to use all the software it packages, when those software projects will have their own documentation and development/support communities. The best place to look for such resources is those upstream projects.

SDR Angel is not able to run over Soapy Remote on my side…
Like to see report if someone have success on that matter :slight_smile:

CubicSDR and SdrGlut are working as expected…

Works fine for me. Built it and Soapy etc. from source on Ubuntu 18.04. Raspbian running on the LimeNET Micro and if I first start SoapySDRServer on this, then run up SDRangel on my laptop, it automatically finds the SDR via mDNS.

1 Like

Yes, on my side SDR is visible over the NET also on Ubuntu 18.04

Works great on Cubic and SdrGlut, can get up to 800 kHz bandwith.
Just must test TX on SdrGlut at the moment my RX system is still
on upcoverted high 10,7 IF from ICOM PCR1000.

It is visible on SDRangel too, just Angel crashing on start. The same instalation
of Angel is able to run Lime USB and LimeNET micro locally over USB.

Does just SDRangel on the client system crash, or does SoapySDRServer also crash on the LimeNET Micro? I had the latter happen and the server process would segfault when using the turnkey PiSDR image. Rebuilding SoapySDR and SoapyRemote fixed this.

SDRanglel crash only on client side…
tested with Ubuntu 18.04 and Win10

After SDRangel crash it is possible to reach Soapy Remote
with Cubic or SdrGlut from the same client PC

Which version of SDRangel working good, on your side?

Thanks for the help. Seems that this did the trick. SoapySDR Util --find shows it over the network.
Have not been able to see it in SDRangel.
I will do a fresh install SDRangel on my desktop and hope that will solve the connectivity problem.

Trying to install SDRangel on the Device dependencies my cmake reports the following :

– Enabling native optimizations
– Found libusb-1.0:
– - Includes: /usr/include/libusb-1.0
– - Libraries: /usr/lib/x86_64-linux-gnu/libusb-1.0.so
– USB_INCLUDE_DIRS: /usr/include/libusb-1.0
– USB_LIBRARIES: /usr/lib/x86_64-linux-gnu/libusb-1.0.so
– USB_INCLUDE_DIRS: /usr/include/libusb-1.0
– USB_LIBRARIES: /usr/lib/x86_64-linux-gnu/libusb-1.0.so
– Could NOT find wxWidgets (missing: wxWidgets_LIBRARIES wxWidgets_INCLUDE_DIRS)
– wxWidgets_DEFINITIONS:
– wxWidgets_INCLUDE_DIRS:
– wxWidgets_LIBRARIES:
– Could NOT find Gnuplot (missing: GNUPLOT_EXECUTABLE)
– Could NOT find FLTK (missing: FLTK_LIBRARIES)
– Could NOT find SoapySDR (missing: SoapySDR_DIR)
– octave-config not found (need liboctave-dev), disabling LimeSuiteOctave

– ######################################################
– ## LimeSuite enabled features
– ######################################################

  • LimeSuiteHeaders, The lime suite headers
  • LimeSuiteLibrary, The lime suite library
  • ConnectionFX3, FX3 Connection support
  • ConnectionFTDI, FTDI Connection support
  • ConnectionXillybus, PCIE Xillybus Connection support
  • LimeSuiteExamples, LimeSuite library API examples
  • LimeUtilCommand, Command line device discovery utility
  • LimeQuickTest, LimeSDR-QuickTest Utility

– ######################################################
– ## LimeSuite disabled features
– ######################################################

  • ConnectionEVB7COM, EVB+COM Connection support
  • ConnectionSTREAM_UNITE, STREAM+UNITE Connection support
  • ConnectionRemote, Remote Connection support for testing
  • ConnectionSPI, Rasp Pi 3 SPI Connection support
  • LimeSuiteGUI, GUI Application for LimeSuite
  • SoapySDRLMS7, SoapySDR bindings for LMS7
  • LimeSuiteDocAPI, LMS API Doxygen documentation
  • LimeSuiteDesktop, LimeSuite freedesktop integration
  • LimeSuiteOctave, LimeSuite Octave integration

– Install prefix: /opt/install/LimeSuite
– Build timestamp: 2020-04-12
– Lime Suite version: 20.01.0-g1c1c202f
– ABI/so version: 20.01-1
– Configuring done
– Generating done
– Build files have been written to: /opt/build/LimeSuite/builddir

It looks to me that it is not going the way it should go.
I will stop here and see what your comment is on this.

SDRangel 4.12.4 Qt 5.9.5 64b x86_64 Ubuntu 18.04.4 LTS DSP Rx:24b Tx:16b PID 17728

1 Like

ConnectionFX3 = LimeSDR USB support.
ConnectionFTDI = LimeSDR Mini support.

So Lime Suite would support the SDR hardware directly.

SoapySDRLMS7 = support for using the SDR via SoapySDR.

Hence it’s not finding your SoapySDR installation. If you installed this via packages, you would need to have libsoapysdr-dev installed for Lime Suite to build the SoapySDRLMS7 module for it. If you built SoapySDR from source and it’s installed to /usr/local/, then it should find it.