Date   
Re: Rtlsdr-install doesn't work

Buffalo Berger
 

Ok I will try again. You are correct 
Program files x86.

On Fri, Dec 6, 2019, 14:23 MadMike <virtualtrains@...> wrote:
You are attempting to install it in c:\Program Files (x86) 

Windows will not allow you to download files into that folder for security reasons. Select some other folder like C:\Radio for sdr# and you will not have any problems.

Regards, Mike Simpson
South Penrith, NSW, Australia


Re: Rtlsdr-install doesn't work

Buffalo Berger
 

Yes
Opened zandig and app as administrator
I'm non technical so go easy.
Ran install rtsldr. As admin. 
Tried to install old versions
Over 5 times total

Re: Rtlsdr-install doesn't work

MadMike
 

You are attempting to install it in c:\Program Files (x86) 

Windows will not allow you to download files into that folder for security reasons. Select some other folder like C:\Radio for sdr# and you will not have any problems.

Regards, Mike Simpson
South Penrith, NSW, Australia


Re: Rtlsdr-install doesn't work

Bill Dailey
 

Did you open that as administrator?

Sent from mobile

On Dec 6, 2019, at 2:46 PM, Buffalo Berger <buffaloberger@...> wrote:


Hi I opened install rtlsdr and cmd window says download rtlsdrr driver.
Then cannot open. 

See attachment for cmd screen

I've installed everything 5 or more times would appreciate a link to download the good rtsldr install or info what to do next.


Attachments:

Install rtsldr not working #software #driver #sdrsharp

Buffalo Berger
 

Hi unable to install rtlsdr 
Where can I get the download I need

Rtlsdr-install doesn't work

Buffalo Berger
 

Hi I opened install rtlsdr and cmd window says download rtlsdrr driver.
Then cannot open. 

See attachment for cmd screen

I've installed everything 5 or more times would appreciate a link to download the good rtsldr install or info what to do next.


Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Mike Tindor
 

USB issues.     I don't have any experience with any of the other Odroids to compare.   I mainly use Rasbperry PIs.     I bought the N2 right before the PI4 came out, since it sounded like it had the horsepower -- and it does have the horsepower.

Mike

#request #satellites #network #request #satellites #network

Seyha Khum
 

Hello from Cambodia!


My name is Seyha Khom. I am a high school student at Liger Leadership Academy in Phnom Penh, Cambodia. I am currently working on a project to distribute Software Defined Radio (SDRs) to secondary public schools in Cambodia. My aim is to introduce a new field to students in Cambodia because this country has never had any major development in this type of technology since the Khmer rouge. The student’s view in the government schools is very narrow since they aren’t exposed to much of the outside world. Many students only have dreams to become doctors or teachers because of their limited exposure. I want to offer this new change hoping to widen their view of the world and create more radio enthusiasts in Cambodia. I am also hoping to lead this into a stepping stone for Cambodia’s establishment of satellite experts and creators in the future generations.


I have a donated SDR in school that I used to learn about this technology. I have also tried the SDR with my homemade antenna to catch the satellite signal. It was a successful trial and I got pictures from the Nova 19 plus various other signals from CubeSats around the globe. My plan is to share my experience with other students in Cambodia by introducing it as a new curriculum. However, my school doesn’t have enough budget to help me with this project. Therefore, I would like to consult all of you on this page about how I could acquire the SDR? Does anyone here know who I can contact or what grants I can apply for that might be able to support this project? My goal is to raise enough money to obtain 4 to 5 SDR.

Here is some more information about the project that utilized the SDR -

http://ligercubesat.org/

https://www.ksby.com/news/local-news/cal-poly-team-travels-to-cambodia-to-help-set-up-cubesat-program


Thank you,

Seyha

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Martin Smith
 

To be fair, they do mention no X11 ("Unfortunately, there is no X11 GPU driver
since Arm has no plan to support X11 for Bifrost GPUs anymore") on the
specification page https://www.hardkernel.com/shop/odroid-n2-with-4gbyte-ram
<https://www.hardkernel.com/shop/odroid-n2-with-4gbyte-ram/> Scroll down to
"Software support" and read the "Linux" subheading . And they mention that a
Wayland driver is on the way.

On 05/12/2019 20:28, Jeff Breitner wrote:
The N2 is a real workhorse. I use one as a DVR headend and it is just as capable as the PC it replaced.

But it has USB issues that make attached USB storage a bit persnickety, and a lack of hardware drivers for X make it less than desirable for a desktop.

I had a bunch of USB issues trying it with Armbian.




Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Marcus D. Leech
 

On 12/05/2019 03:28 PM, Jeff Breitner wrote:
The N2 is a real workhorse.  I use one as a DVR headend and it is just as capable as the PC it replaced.

But it has USB issues that make attached USB storage a bit persnickety, and a lack of hardware drivers for X make it less than desirable for a desktop. 

I had a bunch of USB issues trying it with Armbian.

USB issues sounds like a killer.  I run my SBCs headless mostly.  Hmmmm.



Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Jeff Breitner
 

The N2 is a real workhorse.  I use one as a DVR headend and it is just as capable as the PC it replaced.

But it has USB issues that make attached USB storage a bit persnickety, and a lack of hardware drivers for X make it less than desirable for a desktop. 

I had a bunch of USB issues trying it with Armbian.

Re: Spyserver running on Mint

jdow
 

Have you read the last few messages? They are likely to apply to Mint as to anything else.
{o.o}

On 20191205 10:38:10, Robin wrote:
As a newbie here, can someone point me in the right direction for information on how to set up spyserver on Mint 18.3 with my Airspy HF+ to allow access remotely over the internet.
Thanks

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Marcus D. Leech
 

On 12/05/2019 08:50 AM, Mike Tindor wrote:


I will say that the only thing I like about the Odroid N2 is the EMMC support.   The EMMC card is mush faster than an SD Card.   Other than that, I am not impressed with an Odroid N2 for the purposes of running an ADSB setup or a spyserver setup.   But it works :)

Mike
_._,_._,_


What is it you don't like about the N2?  I have a couple that I haven't done anything with yet.  Have you experience with the XU4 to compare against?

Just curious.


Spyserver running on Mint

Robin
 

As a newbie here, can someone point me in the right direction for information on how to set up spyserver on Mint 18.3 with my Airspy HF+ to allow access remotely over the internet.
Thanks

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Mike Tindor
 
Edited

To shorten things up, here is what I had to do to get spyserver (32-bit ARM version) functional on an OdroidN2 running Armbian Stretch Legacy (64-bit system)

  sudo dpkg --add-architecture armhf
  sudo apt-get update
  sudo apt-get install libc6:armhf libstdc++6:armhf

  sudo apt install build-essential cmake pkg-config gcc-arm-linux-gnueabihf g++-arm-linux-gnueabihf

  sudo apt-get install libusb-1.0-0:armhf libusb-1.0-0-dev:armhf usbutils:armhf

  follow relevant instructions on https://limesdr.ru/en/2019/02/23/spyserver-aarch64/
    - note:  you don't need to do everything listed on that page, but the whole page is useful info

And, lastly, because I wanted Spyserver to run on the big cores of the Odroid N2, I use "taskset -c 2-5 ./spyserver spyserver.config" to force spyserver to run on only the "big" cores of the Odroid N2.

I would have rather omitted the reference to the external site, but I was not comfortable copying/pasting that information verbatim into this thread since I wasn't the creator of the original writeup.

Mike

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Mike Tindor
 

Tomasz was correct (Thanks, Tomasz).

All I really had to do was leave the 64-bit versions of libusb-1.0-0 , libusb-1.0-0-dev and usbutils installed and simply add the armhf versions:

apt-get install libusb-1.0-0:armhf libusb-1.0-0-dev:armhf usbutils:armhf

Then, with both versions installed I did not have any issue with LIBUSB_INCLUDE_DIR.   I simply had to perform the original step #5 from the article to use the CMAKE_TOOLCHAIN_FILE and the Airspy Host Tools built fine.   Spyserver works fine.

Of course, I'm not sure spyserver is using the correct cores (it may be using the small ones).   I'll need to play with that to force it to use the big ones.    Right now, the spyserver process uses about 160% when it's running.

I will say that the only thing I like about the Odroid N2 is the EMMC support.   The EMMC card is mush faster than an SD Card.   Other than that, I am not impressed with an Odroid N2 for the purposes of running an ADSB setup or a spyserver setup.   But it works :)

Mike

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Mike Tindor
 

Thanks Tomasz (and others).  I did not know that (about multilib).   I did figure it out last night but could not reply until the message showed up.

Here is what I ended up doing:

  dpkg --remove libusb-1.0-0 libusb-1.0-0-dev usbutils   #  removed the installed versions, which were 64-bit

  apt-get install libusb-1.0-0:armhf libusb-1.0-0-dev:armhf usbutils:armhf  # install the 32-bit armhf versions

Then I performed step #5 again.    Apparentely with just the armhf versions of the above installed, something was missing that defined LIBUSB_INCLUDE_DIR and the build wouldn't complete.   So I added on to the cmake line in step #5:

  cmake ../ -DINSTALL_UDEV_RULES=ON -DCMAKE_TOOLCHAIN_FILE=../toolchain-arm32.cmake -DLIBUSB_INCLUDE_DIR=/usr/include/libusb-1.0

The Airspy Tools built, and I did the make install; ldconfig.

I fired up the Spyserver and was able to successfully connect to it via SDRSharp, with spyserver reporting the expected "Acquired an AirspyOne device".

So, all is good now.   However, based upon what Tomasz said, I'm going to go back and attempt to install both versions of the USB stuff and then see if everything still works, and at the same time will see if I am able to omit the additional step of adding the -DLIBUSB_INCLUDE_DIR= to the cmake.

@prog :   Yes, I understand the "big boy" thing about Linux users, and I agree.   I don't see any harm in asking for suggestions though, as what I was asking was different ffrom what some others have asked.    I have put some time into getting it to work and didn't just immediately post as soon as it didn't work.

Mike

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Tomasz Lemiech
 


On Thu, Dec 5, 2019 at 5:33 AM Mike Tindor <mtindor@...> wrote:

2.   Installed support for 32-bit apps on Armbian
  dpkg --add-architecture armhf
  apt-get update
  apt-get install libc6:armhf libstdc++6:armhf
(...)
/usr/lib/aarch64-linux-gnu/libusb-1.0.so: file not recognized: File format not recognized
 
It looks like it is indeed attempting to compile a 32-bit version of the Airspy Host Tools, but it also looks like it is having a conflict with the installed libusb library (64-bit) that is / was already on the system.

It's not a "conflict". 32-bit binaries just can't be linked with 64-bit libraries and vice versa. You have installed libc6 and libstdc++ for armhf architecture, but this is not enough - you also need libusb for armhf and any other lib this program depends on. Most Linux distros these days support multilib which means both versions (32 and 64-bit) of the same library may be installed simultaneously.

Regards,
 
--
Tomasz Lemiech

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

Airspy US
 

It is noted that your step 1 is for Airspy HF+ but step 3 is for the original Airspy.

Not sure which one you are using, but they are not the same.

---------
Airspy.US
Your USA source for quality SDR products!
www.Airspy.US

NOTE! This email address is not routinely monitored.
If you have an issue, please contact us at airspy@...

On 12/4/2019 9:12 PM, Mike Tindor wrote:
Hi Folks,

I'm running an Odroid N2 with the latest Armbian ( Linux odroidn2 4.9.196-meson64 #20 SMP PREEMPT Mon Nov 18 22:30:06 CET 2019 aarch64 GNU/Linux )

I'm having a similar problem to some others in that I have installed spyserver (and all of its prerequisites) on an Odroid N2 (64-bit arm architecture) running Armbian and am getting the dreaded message when attempting a remote connection from SDRSharp:

Device was sleeping.
Wake up! Could not finda ny suitable device

My thought is/was there is incompatibility between (a) 32-bit spyserver, (b) 64-bit compiled Airspy Host Tools and (c) 64-bit installed libusb-10.so.

At any rate, here is what I've done:

1. installed the latest Armbian on an Odroid N2

2. Installed support for 32-bit apps on Armbian
dpkg --add-architecture armhf
apt-get update
apt-get install libc6:armhf libstdc++6:armhf

3. Followed instructions on github for Airspy Host Tools installation

sudo apt-get install build-essential cmake libusb-1.0-0-dev pkg-config

wget https://github.com/airspy/airspyone_host/archive/master.zip
unzip master.zip
cd airspyone_host-master
mkdir build
cd build
cmake ../ -DINSTALL_UDEV_RULES=ON
make
sudo make install
sudo ldconfig

The Host Tools install went fine. I can access the Airspy using the Host Tools and everything checks out. Proper sample rates supported, latest firmware, etc.

4. I then downloaded and ran spyserver (with both default and custom config)

wget http://airspy.com/downloads/spyserver-arm32.tgz
tar xzf spyserver-arm32.tgz
./spyserver spyserver.config

Of course, this is the point where when I would connect via SDRSharp I would get:

Accepted client 192.168.0.107:56840 running SDR# v1.0.0.1732 on Microsoft Windows NT 6.2.9200.0
Device was sleeping. Wake up!
Could not find any suitable device

5. Found online article at: https://limesdr.ru/en/2019/02/23/spyserver-aarch64/

This looks/looked promising. I followed the instructions in the article, but unlike the author of the article I did not get a clean build -- apparently because it had an issue with the installed version of libusb.

cmake ../ -DINSTALL_UDEV_RULES=ON -DCMAKE_TOOLCHAIN_FILE=../toolchain-arm32.cmake
-- The C compiler identification is GNU 6.3.0
-- The CXX compiler identification is GNU 6.3.0
-- Check for working C compiler: /usr/bin/arm-linux-gnueabihf-gcc
-- Check for working C compiler: /usr/bin/arm-linux-gnueabihf-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/arm-linux-gnueabihf-g++
-- Check for working CXX compiler: /usr/bin/arm-linux-gnueabihf-g++ --
works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check if the system is big endian
-- Searching 16 bit integer
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of unsigned short
-- Check size of unsigned short - done
-- Using unsigned short
-- Check if the system is big endian - little endian
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Checking for module 'libusb-1.0'
-- Found libusb-1.0, version 1.0.21
-- Found LIBUSB: /usr/lib/aarch64-linux-gnu/libusb-1.0.so
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mike/airspy_host/airspyone_host-master/build


root@odroidn2:/home/mike/airspy_host/airspyone_host-master/build# make
Scanning dependencies of target airspy
[ 4%] Building C object libairspy/src/CMakeFiles/airspy.dir/airspy.c.o
/home/mike/airspy_host/airspyone_host-master/libairspy/src/airspy.c:593:13: warning: ‘upper_string’ defined but not used [-Wunused-function]
static void upper_string(unsigned char *string, size_t len)
^~~~~~~~~~~~
/home/mike/airspy_host/airspyone_host-master/libairspy/src/airspy.c:110:19: warning: ‘str_prefix_serial_airspy’ defined but not used [-Wunused-const-variable=]
static const char str_prefix_serial_airspy[STR_PREFIX_SERIAL_AIRSPY_SIZE] =
^~~~~~~~~~~~~~~~~~~~~~~~
/home/mike/airspy_host/airspyone_host-master/libairspy/src/airspy.c:106:19: warning: ‘str_product_airspy’ defined but not used -Wunused-const-variable=]
static const char str_product_airspy[STR_PRODUCT_AIRSPY_SIZE] =
^~~~~~~~~~~~~~~~~~
[ 8%] Building C object libairspy/src/CMakeFiles/airspy.dir/iqconverter_float.c.o
[ 12%] Building C object libairspy/src/CMakeFiles/airspy.dir/iqconverter_int16.c.o
[ 16%] Linking C shared library libairspyso
*/usr/lib/aarch64-linux-gnu/libusb-1.0.so: file not recognized: File format not recognized*
collect2: error: ld returned 1 exit status
libairspy/src/CMakeFiles/airspy.dir/build.make:147: recipe for target 'libairspy/src/libairspy.so.1.0.9' failed
make[2]: *** [libairspy/src/libairspy.so.1.0.9] Error 1
CMakeFiles/Makefile2:137: recipe for target 'libairspy/src/CMakeFiles/airspy.dir/all' failed
make[1]: *** [libairspy/src/CMakeFiles/airspy.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

It looks like it is indeed attempting to compile a 32-bit version of the Airspy Host Tools, but it also looks like it is having a conflict with the installed libusb library (64-bit) that is / was already on the system.

# ls -alt /usr/lib/aarch64-linux-gnu/libusb-1.0.so
lrwxrwxrwx 1 root root 42 Oct 26 2016 /usr/lib/aarch64-linux-gnu/libusb-1.0.so -> /lib/aarch64-linux-gnu/libusb-1.0.so.0.1.0

# file /lib/aarch64-linux-gnu/libusb-1.0.so.0.1.0
/lib/aarch64-linux-gnu/libusb-1.0.so.0.1.0: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, BuildID[sha1]=18e0d7acc8e7bd5764d1bdb27241fcd6107ed45a, stripped

So, 64-bit libusb stuff installed on system; 64-bit Airspy Host Tools is compiled by default (but I tried a 32-bit compile in step 5). And of course the available ARM spyserver executable is 32-bit. So it all looks to be a conflict between the 32-bit app and 64-bit libraries.

I suspect that the majority of people having this issue on Linux are probably people attempting to run spyserver on a 64-bit ARM system.

If anyone happens to look at that article linked in step #5 above and have any additional thoughts about things I might try, I'm certainly willing to try.

Thanks

Mike

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Device was sleeping. Wake up! Could not find any suitable device (Odroid N2 / latest Armbian) #spyserver

prog
 

On Thu, Dec 5, 2019 at 05:33 AM, Mike Tindor wrote:
/usr/lib/aarch64-linux-gnu/libusb-1.0.so: file not recognized: File format not recognized
You may need: apt-get install libusb-1.0-0-dev
TBH, the Odroid N2 was never tested with the spyserver. There are so many SBCs out there with different configurations and gotchas that watching their evolution and tackling their problems is a full time job. Even established ones break between software upgrades and the end users are required to know what's going on.
The tacit contract with Linux being that "All Linux Users Are Big Boys".