Sorry, it's not the same problem. You are using the HF+, not the R2 or the Mini. This means you need the driver for the HF+, not the driver for the R2 or the Mini. https://github.com/airspy/airspyhf#h

#spyserver

Hello ejo60, A screencap. Monday, January 22, 2018, 12:51:13 AM, you wrote: e> Running into the same problem, in my case the device is busy, so can I build e> the spyserver from scratch on a raspberry

#spyserver

Hello ejo60, After tearing my hair out for 3 days, found a solution. Try it now, PI-3 with SDR-RTL dongle, sdr://p.uio.pw:5555 Monday, January 22, 2018, 12:51:13 AM, you wrote: > Running into the same

#spyserver

Guys, I got it to work, you need indeed to install the airspyone_host-master (or the airspyhf_host-master) software from github, and replace the device_type = AirspyOne and follow the rest of the sett

#spyserver

I tried to set up a spyserver on my 1st gen pi, and experience the same problem you describe, it won't start and gives me a segmentation fault. I ran a spyserver on this pi (running jessie) sucesfully

#spyserver

Hello Rick, This happened with me on a PI-3. 1) The unit developed an intermittent cold solder joint. 2) Had to replace the uSD card with a faster, brand name card. The problem went away. Tuesday, Jan

#spyserver

Can I have the software for the hf+ and the R2 on the same /usr/local on the r2p? The R2 is correctly installed, runs like a king over a wired network, the BW limitation comes from the r2p which has n

#spyserver

With a raspberry pi 3 the set-up is explained here: https://pa1ejo.wordpress.com/2018/01/24/your-own-websdr/ Thanks for all your support!

#spyserver #sdrsharp

Thanks Blogger, i now tested it on another pi (brand new pi0w) , other (10x fast brand name card) sd card, full re-install. but same problem, segmentation fault. Might be problem in how they compiled

#spyserver

Well that's not a websdr, but a spyserver, would love to see some real websdr (like uttwente, not openwebrx) install setup.

#spyserver #sdrsharp

I saw the recent changelogs for SDR# sound interesting for HF+ users, will those options also be made available to those listening in via spy server? Also, maybe far-fetched, but could it be possible

#spyserver #airspyhfplus

At some point it will happen. Note that these optimizations will only work when there is one user connected.

#spyserver #airspyhfplus

Never got much of a meaningful response to this. My eventual conclusion, based on experimentation, is that device_serial only works if you give it a hex serial number for an AirSpy hardware device, e.

#RTL #spyserver

The official RTLSDR API does not offer any means to open the dongles by "serial". The existing API can only open the dongles by index. Btw, 99% of the dongles in circulation don't even have a unique s

#RTL #spyserver

That last is why rtl_eeprom exists. The new serial number can be quite long and any characters you want. There is room for about 240 letters for the three strings combined. {^_^}

#RTL #spyserver

And more than 50% of the dongles don't have an eeprom...

#RTL #spyserver

Fascinating - I've not run into one that doesn't. I suppose a phony serial number could be invented from the USB path. As long as the user does not change that path all would work OK. I have seen the

#RTL #spyserver

I think that's why the current API uses indexes. It certainly could be better if the hardware was more consistent.

#RTL #spyserver

Hi Yussef, In Linrad I use for(i=0; i<no_of_rtl; i++) { rtlsdr_get_device_usb_strings(i, vendor, product, serial); sprintf(s," %2d: %s MFG:%s, PROD:%s, SN: %s", i, rtlsdr_get_device_name(i), vendor, p

#RTL #spyserver

No fooling. +1 for AirSpy. {o.o}

#RTL #spyserver