Spyserver could not acquire the device. Could not find any suitable device .

Spyserver could not acquire the device /spyserver: cannot 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. Aug 26 22:05:07 jupiter64 systemd[673]: Invalid line "env=_JAVA_OPTIONS=-Dawt. # device_serial = 0 # Device Sample Rate # Possible Values: # Airspy R0, R2 : 10000000 or 2500000 # Airspy Mini : 6000000 or 3000000 # Airspy HF+ : 768000 # RTL-SDR : 500000 to 3200000 # Comment to use the device's default # #device_sample_rate = 2500000 # Force 8bit Compression Mode Check the latest version of SDR# with the new SpyServer options. This build can be used with any x86 Windows computer. Thank you very much for sdr sharp, without this program we would be stuck with hdsdr. The [airspy] Help me debug my SpyServer " Device was sleeping. Everything looks completely peachy until I actually try to connect to it. Chris Fink #24342 . Docker container for AirSpy SpyServer for x64 and arm32 - compsci282/spyserver. with files: rtlsdr. Maybe OP could still check if he got rtl-sdr package installed but I doubt that's the issue. Now I see other messages on this topic particularly with Sent: Tuesday, November 16, 2021 2:52 PM To: airspy@groups. When I run spyserver and try to connect to it, I get the following output: A number of people have asked how to use SDR#'s SpyServer with an RTL-SDR. I have only have one dongle, and mine is configured as. 3. # device_serial = 0 # Device Sample Rate # Possible Values: # Airspy R0, R2 : 10000000 or 2500000 Could not acquire the device; Running ARM spyserver on rpi3 (ubuntu) or BBB (debian) after setting up the config file and blacklisting the Airspy (and installing libairspy) it displays the following at execution which I assume is normal: $ . config” file Docker container for AirSpy SpyServer for x64 and arm32 - compsci282/spyserver. All Messages By This Member #32696 Did this thread ever get resolved? I have a similar problem running linux spyserver, and googling finds other people who have similar problems like this, but no resolution. Or use I follow as guide this answer:The package lists or status file could not be parsed or opened I assumed my lists were corrupted. SpyServer enables you to connect remotely and use the SDR receivers. I have verified my Mini is indeed working by running SDR# on the server machine. # I did not make any changes to the spyserver. exe", the program finds the dongle and starts the server so that it becomes visible ob the world map with a green dot. Do I miss something ? I'm using the last night build for Ubuntu Thank you to Matt from SDRx. config ==> ('Accepted client xxx. The only way to find out the SRN seem to be rtl_test or rtl_eeprom. dll+rtl-sdr. conf. Wake up! Could not find any suitable From: bachelder. On 2/20/2019 12:29 PM, Tom Snyder wrote: I think you need a crossover ethernet cable for communication to take place. Could not acquire the device spyserver. " in the command window. AirSpyHF+ on Spyserver on Raspberry Pi What is a Spyserver and why do you NEED one? A spyserver takes an RTL-SDR software radio and allows it to be used over the network or controlled from the internet if you Contribute to crsystems/spyserver development by creating an account on GitHub. rob@ Sent: Tuesday, November 16, 2021 6:02 PM To: airspy@groups. That is a virtual disconnect. Other hacks that are not supported by the official librtlsdr arz ignored. 4msps only is not necessary. My config has the following for the first reciever: # Device Serial Number as 64bit Hex # For example: 0xDD52D95C904534AD # A value of 0 will acquire the first available device. Spyserver doesn't seem to verbosely report issues with library versions. Wake up! Could not finda ny suitable device 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 acquire the device" message in the terminal. To join the Also, the SpyServer has its own . 40:30551. Navigation Menu Toggle navigation. 1707 on Microsoft Windows NT 6. Could not acquire the device Sometimes it reports: "could not find any suitable device". Example for localhost: # A value of 0 will acquire the first available device. I tried connecting SDR# to each SpyServer instance and everything seems to work. Yesterday evening I had the strange stuttering issue too on my Pi5+Mini after installing the latest Spyserver Client (dated Oct 24 01:15). rules I've set everything correctly (I think) in spyserver. Wake up! Could not acquire the device #spyserver. I need SpyServer because my antenna array is remotely located. config file, and I'll put at the end of this post. SpyServer runs on the RasPi 4, and as noted above (and copied below) has its own config file. 99. 66. I guess that console (text-only) sessions over SSH are not affected by these problems. 2021-05-31 19:09:49 hf_dual. com Tue Mar 21 20:00:39 UTC 2017. My linux debugging skills are a little rusty but eventually i looked up the syntax to have strace dump to a text file and then it was pretty obvious. Show Gist options. xxx:63277 Try changing the serial number to 1 then restart and check, if that doesn't work try 2, then restart, then 3, etc. Device 1004 is specified in the spyserver config as My Spyserver on a Raspberry Pi3 with a HF+ always crashes after a certain time with this message: # A value of 0 will acquire the first available device # upper right corner. 0, which improves the streaming So my network looks like this: Att Router in bridge mode -> USG-3p->Unifi 8 port switch-> a bunch of other stuff. config. export XLNX_VART_FIRMWARE=/opt/xilinx/overlaybins/dpuv4e/8pe/<name of the xclbin> Thanks, Nithin generic usb device sharing - usbip sdr device sharing - soapy-remote, rtl_tcp headless counterparts for some GUI programs - spyserver for sdr#, sdrangelsrv for sdrangel, sdr++ in server mode remote terminal session - vnc, rdp, nx, ssh *Subject:* Re: [airspy] Beginner Questions: spyserver config Most PCs will auto-configure so the crossover is not needed. 168. Wake up! Could not acquire the device I tried installing and running airspy_info, but apparently this is only for AirSpy devices, as it reports no devices. dll+libusb-1. 9200. 6-BB Available sample rates: Currently it appears Spyserver does not properly parse a given serial number in the config. bat from within the extracted folder run zadig file and install drivers for RTL-SDR I have an Airspy R2 connected to my Fedora Core 39 computer. │ Error: building account: could not acquire access token to parse claims: clientCredentialsToken: cannot request token: If i can hit the outside world, such as google. ModemManager1' service name Next message: Could not acquire the 'org. Device 1004 is specified in the spyserver config as Currently it appears Spyserver does not properly parse a given serial number in the config. config To get the serial Glenn and prog, Moving the SpyServer files to the SDR# folder did the trick. "Multiple dongles can be used by editing the “device_serial” string in the config Could not acquire management access for admionistration RuntimeError: Unable to execute comand chcp. You switched accounts on another tab or window. It was fine for a few hours before stuttering started. AirSpy R0 does not work with ubuntu+spyserver, but R2 works OK There are three steps I'd try 1 uninstall any old out of date packages that you may have installed for the airspy (for Debian based distributions, which is probably the default Linux OS for Odroid) : Find out the names of the packages $ sudo apt-cache search airspy And try and uninstall them (I'm not even checking if they are installed first to keep the command as simple as possible) $ And without that information how do you know if you are interfering or are sub-optimizing some mission critical app? Seems like it could just disrupt an otherwise finely tuned and balanced system if the priority class refers to resource priority and not just start precedence priority. Once the correct sample rate is selected Spyserver is running like a finely tuned watch Mike. maybe make a backup of your config, and using the default config with The 2. 478888] Could not acquire the 'org. Skip to content. I also have two RTL dongles running in Direct Sampling mode on two additional instances of Spyserver (on the same PC as the Airspy), which I can connect to locally and via the internet, however they don't appear in the Spyserver directory. Another issue is firewalls blocking it. Wake up! Could not acquire the device 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. It seems like the issue is with Spyserver actually seeing the device, but I I am currently trying to setup a SpyServer with an Nooelec Nesdr Smartee. g. useSystemAAFontSettings=on\n": Invalid argument Aug 26 22:05:07 jupiter64 systemd[673]: Failed to parse returned data: Invalid argument Aug 26 22:05:07 jupiter64 This is not apparent with other SDR software nor a locally connected device like an RSP connected to Console. Also, is the idea to make a server that emulates the airspy network protocol so any SoapySDR device can appear as a remote airspy device? Input buffer to smooth sending iq data to remote applications And, It's not limited to recieve only. Is there something else I need to run as super user I might have missed? SpyServer is a free RTL-SDR compatible SDR server designed to work with SDR# software. The workaround is to run the airspy Linux spyserver locally on the same machine, and connect the Wine SDR# to the local machine network and thus to the spyserver. " in the command The following case is not handled correctly - it counts as open connection that never closes. The documentation provided did not really spell that out. com. Raspberry Pi 4 and RTL-SDR ~Could not acquire the device~#spyserver; Could not acquire the device BUT rtl_test running ok pi@raspberrypi:~ $ rtl_test Found 1 device(s): 0: Realtek, RTL2838UHIDIR, SN: 00000001. I select Airspy on the top dropdown menu but in the dropdown menus just below, the lists are empty. More All Messages By This Member Michał Frątczak #32647 I am experiencing similar problem. The main difference between spyserver and rtl_tcp is that it requires less network A number of people have asked how to use SDR#'s SpyServer with an RTL-SDR. If you observe no further output, everything is fine. [R82XX] PLL not locked! Sampling at 2048000 S/s. Download: SPY Server – SDR Server for Linux ARMHF One thing that i found: When the RTLSDR is aquired by spyserver, i get these messages: Device was sleeping. Any one experienced the same errors and worked through them? Running ARM spyserver on rpi3 (ubuntu) or BBB (debian) after setting up the config file and blacklisting the Airspy (and Hi I had this running once but it now absolutely refuses. Wake up! Could not find any suitable device Accepted client 192. xxx. Device was sleeping. However, SpyServer is regarded as superior because it is signficantly more efficient at network usage. wb@gmail. Wake up! Could not acquire the device. 11:3056 running SDR# v1. A value of 0 will acquire the first available device. I could connect over SSH and terminate or kill any RDP sessions associated to my username that may be Aug 26 22:05:07 jupiter64 systemd[1]: Started Session c2 of user john. This works fine. If left as default (as above), the pi3 will struggle handling the data over its usb port. Unlike soapy, spyserver doesn't just provide a remote interface to a devices drivers. But I´m not able to connect from the Console, only from Sharp. sudo nano spyserver. Would you like to switch to your primary association now ()? Could not acquire library handle for device 'DeviceName'. Wake up! Could not acquire the device Here is mine, # SPY Server Configuration File # TCP Listener # bind_host = 0. A value of 0 will acquire the first available Over on YouTube SignalsEverywhere/Harold is back with a new video tutorial that shows users how to set up a SDR# SpyServer with an RTL-SDR dongle. 156. The client is connecting to the server but the server does not seem to be able to find the (known working) Reading the configuration file: spyserver. Maybe a file(s) is/are missing in the SpyServer download? I’m working now! Glenn, I'm not planning on allowing outside access for my radio. io Subject: [airspy] Spyserver on Raspberry Pi ""server is busy" #spyserver OK, first of all let me say that all this hardware worked great a year or two back last time I used it. Once the correct sample rate is selected Spyserver I have and HF+ and an R2, regardless - at any logon attempt I get "Server Busy" in SDR# and "Device was sleeping. In this tutorial we will show how to set up SpyServer on both Windows and Linux systems. config: # SPY Server Configuration File # TCP Listener # bind_host = 0. Wake up! Could not finda ny suitable device Could not acquire the device Accepted client 192. 1 17. That is: sudo . 10:50521 running SDR# v1. 1:54014 running gr-osmosdr. I'm continuing to see this error in the spyserver window on a Win10 PC. Wake up! Could not acquire the device #spyserver Randall Wayth. Download ZIP # A value of 0 will acquire the first available device. dll. Would anyone here happen to Not an issue with Radiosonde_Auto_RX, but with me, could not talk well to Linux, still learning I tried to run few already built Docker images of Spyserver on Android TV Box H96max, bought used for 30EU. ModemManager > > > does not usually auto-probe various platform drivers, because it > > > cannot know that a modem is connected as these are not > > > USB/PCI/etc > > > and either do not provide device identifiers, or the device is a > > > generic serial adapter which doesn't necessarily indicate a > > > modem > > > either (eg, it could have a UPS attached or something). Accepted client 127. config: # Initial Center Frequency # initial_frequency = 7100000 # Minimum Tunable Frequency # Comment if using Glenn and prog, Moving the SpyServer files to the SDR# folder did the trick. Anything else I could try? Because I don't want and should not need to run any RTL-SDR sticks and software as root. I faced this problem on Windows 7 Could not acquire the device Sometimes it reports: "could not find any suitable device". I've not made any changes to the SDRSharp config file on my PC. It works well with my Airspy Mini via a remote server running the latest Spyserver. config and if I want to connect via SDR# I based on this, all you should need to do is set device_type to RTL-SDR. freedesktop. Created January 7, 2021 23:01. I've got 2 RTL-SDR dongles working fine with other softwares on Windows 10. All Could not acquire the device. started @anton_xonp3 can you try pointing the xclbin using the env variable. You signed out in another tab or window. Maybe a file(s) is/are missing in the SpyServer download? I’m working now! Currently it appears Spyserver does not properly parse a given serial number in the config. 5、make driver for Airspy HF+ 'upper_string' defined but not used [-Wunused-function] static void upper_string(unsigned char *string, size_t len) ^~~~~~ [ 14%] Building C Could not acquire the device. It was accessed via my LAN. The USG-3p is always showing You signed in with another tab or window. In this new setup rtlsdr is running ok with Satnogs and with As mentioned earlier, if you have a device with a 64-bit ARM processor (like NanoPi NEO2 with ARM Cortex-A53 (Allwinner H5)), in order to SpyServer worked fine – you need to compile libairspy library for the armhf (ARM hard-float) architecture, because the spyserver itself compiled for the same architecture. Wake up! Found Rafael Micro R820T tuner [R82XX] PLL not locked! Acquired an RTL-SDR device Allocating 15 zero-copy buffers I would have assumed that the "PLL not locked" happens only during start up, but who knows. It was originally developed for AirSpy SDR receivers, but the author also made it compatible with RTL-SDR receivers. # A value of 0 will acquire the first available device # device_serial = 0xDEADBEEF # Device Sample Rate # Possible Values: # Airspy R0, R2 : 10000000 or 2500000 # Airspy Mini : 6000000 or 3000000 Since v 1. Is there an existing issue for this? I have searched the existing issues; Community Note. The reciever is unavaiable if it's not done. However, on the retry, the user is logged in successfully. Back in March the team behind the Airspy SDR and SDRSharp software released the SpyServer, a piece of software that allows you to stream radio data from a remote Airspy receiver over a network. I'm using it to capture weather satellite imagery from NOAA and GOES birds. I think that's what tripped me up my first go-around installing Spyserver. S is windows 10 x64, the other is 7 x32, both stock, As far as i know cmd was the only way i got spyserver to load the config file at all on both of my machines. 0 7. I can run it as sudo spyserver but that does not change anything. Thanks to it's compression techniques and that it Device was sleeping. Device 1004 is specified in the spyserver config as If you are using RTL-SDR V3 dongles, you can set their serial number and give it to Spyserver in the config. I went to /var/lib/apt/ I saw a file (lists@) instead of a directory. ModemManager1' service name ModemManager[1624]: [1596559087. 116:31256 running SDR# v1. Listening for connections on 127. e the ones that are plugged directly to your computer (the one that runs your web-browser). (SDR# was working fine) I could solve this topic by replacing the file (within aisdeco2 folder): rtlsdr. dll How I solved it: Download sdrsharp-x86. If, for example, you have installed libairspyhf or libairspy from a system package manager, and it's an out of date version, SpyServer will likely just complain and say "could not acquire device!" without much further detail. There doesn't seem to be a easy was of doing that. This Easter the Airspy team have released SpyServer 2. Taubin / spyserver. 1631 on Microsoft Windows NT 6. ModemManager1' service name. What could be the problem as it is not all the time that it happens, only when there is no authentication attempt on the webseal for a little longer. io for submitting a story on our forums about his project called SDRx. Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request; What is the purpose of the device_serial argument if not to support multiple dongles? It supports the serial numbers of hardware that has a real unique serial number, like the hardware it was developed for, the Airspies. SDR# has just been updated to version 1525 (changelog) and it now includes a new program called 'SpyServer'. The Airspy download contains the SpyServer for Windows and Linux, and the Raspberry Pi and Odroid server is available here. Also featuring Airspy, HackRF, FCD, SDRplay and more. # device_serial = "00000005" The server runs and doesn't complain about the device not being found either, it just doesn't work when I try to attach with SDR# or SDR++, I get the "Device was sleeping. However, the functions may be able to be used via a USB connection, depending on the device or driver you are using. Hardware is Amlogic S905X3 ARM If you only want your spyserver accessible locally on your home network then do not enable port forwarding on your home router for that port and also set "list_in_directory The first setup would be unusual and mean that neither device would by default be assigned an IP Could not connect to SDR://127. Application Level (tier 3) Spyserver(XXXX) - Much like Soapy(tier 2), there is the sdr spyserver application. Airspy R0, R2, Mini, Airspy HF+, RTL-SDR and AOR radios can be used as a high performance SDR receiver capable of streaming separate chunks of the spectrum to multiple clients over the LAN or the Internet. Not the first time it came up, but FWIW I coudn't find the spec, so I'm glad there is some open source code to show the format if thats what it takes. 18 uia2 driver uses file-based locks on device port allocation operations to avoid unexpected port conflicts when multiple drivers running in parallel are trying to acquire the same system port. Followed this guide and all went well. zip Double click on install-rtlsdr. " when trying to start the server on SDR Sharp I followed the quickstart guide for ARM Linux found here. The device is well recognized by GQRX but not by SR++. RTL-SDR Tutorial: Setting up and using the SpyServer Remote Streaming Server with an RTL-SDR and went with the SPY Server – SDR Server for Linux x64 download But when I try to run, I get pi@raspberrypi:~/spyserver $ . 174 MHz Open MySQL Workbench click on “Manage Server Instances” under “Server Administration” column close the screen again. /spyserver bash: . This does not happen for the local user but only for AD user. Wake up! Could not acquire the device Could not acquire the device Accepted client 192. Docker container for AirSpy SpyServer for x64 and arm32 - lloydpick/docker-spyserver. When spyserver receives a connection and is configured for an rtl-sdr device, it beats the Could not acquire the device Accepted client 192. HF/VHF/FM Radio Receiver - West Lyon, France. Could not acquire the device Accepted client 192. 16. 0 Device was sleeping. 9 -4. On Wed RTL-SDR (RTL2832U) and software defined radio news and projects. 2. 2 Sampling at 2048000 S/s. The maximum number of images that the application can simultaneously acquire from this swapchain is derived by subtracting VkSurfaceCapabilitiesKHR::minImageCount from the ModemManager > > does not usually auto-probe various platform drivers, because it > > cannot know that a modem is connected as these are not USB/PCI/etc > > and either do not provide device identifiers, or the device is a > > generic serial adapter which doesn't necessarily indicate a modem > > either (eg, it could have a UPS attached or ModemManager > does not usually auto-probe various platform drivers, because it > cannot know that a modem is connected as these are not USB/PCI/etc > and either do not provide device identifiers, or the device is a > generic serial adapter which doesn't necessarily indicate a modem > either (eg, it could have a UPS attached or something). Reload to refresh your session. A definitive response on what is the root I had this running once but it now absolutely refuses. /spyserver. Wake up! Could not acquire the device Accepted client 192. exe runs on my PC, has its own config file on my PC. But if the correct IP is not used, it will not matter if they are connected by a wet noodle. I'm hoping it works for you too, cheers! Could not acquire the device If the unit is connected to the USB port, maybe you need to run as root or use sudo. IO which is a service that hopes to be a platform that allows remote users to find and connect to public RTL_TCP Hey Simon Many thanks for the latest version of the SW. Just downloaded the latest SDR# and there's a drop-down that's greyed out to where I can't select the device. Could not acquire the device The airspyHF+ is connected because when I run airspyhf_info I get the result: AirSpy HF library version: 1. 61. Troubleshooting - airspy/airspyone_host GitHub Wiki sdr://82. io Subject: Re: [airspy] Spyserver on Raspberry Pi ""server is busy" #spyserver Please elaborate on what you mean. I'm sure I have overlooked something glaringly obvious here. Please make shure that C:\Windows\System32 directory is in your PATH environment variable. ModemManager1' service name Dan Williams dcbw at redhat. Unfortunately it does not appear to work well with my Flightaware Orange Dongle on the same server which is configured for a different port to the Airspy mini. Wake up!" That is your clue to turn off all sleep options. # device_serial = "00000005" # Device Sample Rate # Possible Values: # Airspy R0, R2 : 10000000 SPY Server – SDR Server for Windows. 201. Guidance in comments on that site indicate that spyserver should work if the device works in SDR# and the spyserver files are set up in the same folder. Using device #0 Realtek RTL2838UHIDIR SN: 00000001 Found Rafael Micro R820T tuner [R82XX] PLL not locked! [R82XX] PLL not locked! Using two-stage decimator for 📅 Last Modified: Thu, 04 Apr 2024 11:34:19 GMT. I have experimented with buffer settings and gain settings, both on Console and the Spyserver and haven't been able to tame the problem. . To use SpyServer with the RTL-SDR you’ll first need to edit the “spyserver. Wake up! Could not finda ny suitable device Spyserver: Could not acquire the device Ruben Navarro Huedo (EA5BZ) #30304 . 19041. SpyServer is a program included with SDR# that allows you to access your Airspy or RTL-SDR dongle remotely through the internet or local network connection. All Messages By This Member; jdow No address associated with hostname sudo: spyserver: command not Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers; Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand; OverflowAI GenAI features for Teams; OverflowAPI Train & fine-tune LLMs; Labs The future of collective knowledge sharing; About the company Alternatively, is there a way to have SpyServer report to you what the serial # is of the device that it sees? I actually looked into that. I checked the windows path Your active customer number (- ) is not your primary association. and I also followed the instructions for installing libairspy from here. The link in the Spyserver on ARM-Linux instructions for the Airspy library point to those for AirspyOne. Then the SD card got corrupted in my Raspberry Pi and I put it on the shelf for a while. 8 S/N: 0x3B528E80E8343F47 Part ID: 0x00000001 Firmware Version: R3. SDRSharp. 10:50522 running SDR# v1. io? This cannot be undone. Config file. FWLIB error: 65520 KEPServerEX / ThingWorx Industrial Connectivity Modified: 09-May-2019 # A value of 0 will acquire the first available device. 0. It will then pick the first available device. I have another question. Started up the first instance, and then the second one. Also for the Linux/Raspberry Pi setup we need to assume that you have some Locked How to run spyserver on AArch64 boards？ #airspyhfplus #spyserver yuan. Previous message: Could not acquire the 'org. Could not acquire the device-----The spyserver is installed on a Rasperry, as receiver, an Arispy HF+ is installed. It will throttle down or even reset. 1:5555. Wake up! Could not acquire the device Are you sure you wish to delete this message from the message archives of airspy@groups. zip Extract (unzip) sdrsharp-x86. FFT_FPS: 15: FFT Frames Per Second: FFT_BIN_BITS: 16: FFT Bins, Bins = 2^fft_bin_bits: INITIAL_FREQUENCY Could not find any suitable device 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: Edit: I managed to get two SpyServer instances running with two different dongles on my Linux machine. I had the same issue with this (and a second differend dongle) using aisdeco2 also at my Windows7 PC. Hello friends: I was running fine spyserver with rtl-sdr on my rasp but i had a problem with the SD and i had to reinstall raspbian. Joe M. 0 for no limit # #maximum_session_duration = 30 # Allow clients to retune Could not acquire the device spyserver. I did notice systemd had upgraded earlier today but a downgrade to the previous version did not change the outcome. device_serial = 4 , and I only have on V3 Dongle on it. config file nor the SDR# config file on the other Win10 PC and I'm still having the "server Busy" problem. 0 Hz . For your ip-cam, simply set its feed's url (if any) as the src of a video element. 0 bind_port = 5555-6666 # List Server in Airspy Directory # list_in_directory = 1 # Owner Name # For example: John Doe L8ZEE owner_name = # Owner email # For example: john@ owner_email = # Antenna # For example: Random The other drivers were blacklisted as is normally required. On linux distribution the drivers are in the official repository and get install whenever you install gqrx or other rtl sdr related software. Device 1004 is specified in the spyserver config as follows: Docker container for AirSpy SpyServer for x64 and arm32 - lloydpick/docker-spyserver. I found out that the response “Could not acquire the device” is caused by a bad sample rate in the “Spyserver. 11:3152 running SDR# v1. I have and HF+ and an R2, regardless - at any logon attempt I get "Server Busy" in SDR# and "Device was sleeping. Could not acquire the 'org. 6. com from my container, does it not mean my dns queries With NAT routers(IPv4) the ports needed for the server needs to be forwarded, ofen not done. Now I see other messages on this topic particularly with Raspberry or so but nothing has helped so far. Not sure about environment variables, i am not skilled to this level, all i know is one O. SpyServer is a Windows based streaming server for Airspy devices, and is somewhat similar to what rtl_tcp is Use another connection environment such as a TCP/IP network connection environment for the acquire device information, department ID management, and user authentication functions. bind_port = 5555 # List Server in Airspy Directory # list_in_directory = 1 # Maximum session duration # In minutes. Devices 1001, 1002, and 1003 are in use by other SDR applications and I've confirmed that with rtl_eeprom. config you need to make sure you add the serial number of the Airspy device. Once the Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers; Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand; OverflowAI GenAI features for Teams; OverflowAPI Train & fine-tune LLMs; Labs The future of collective knowledge sharing; About the company You can probably do what you want here by simply not presenting the images to the device. Sent from Mail for Windows 10 Spyserver: Could not acquire the device Ruben Navarro Huedo (EA5BZ) #30304 . In this new setup rtlsdr is running ok with Satnogs Re: Raspberry Pi 4 and RTL-SDR ~Could not acquire the device~#spyserver # Device Type # Possible Values: # AirspyOne (R0, R2, Mini) # AirspyHF+ # RTL-SDR # Auto (Scans for the first available device) # device_type = Auto # Device Serial Number as 64bit Hex # For example: 0xDD52D95C904534AD # A value of 0 will acquire the first available device. If I run "SpyServer. 0 bind_port = 5555-6666 # List Server in Airspy Directory # list_in_directory = 1 # Owner Name # For example: John Doe L8ZEE owner_name = # Owner email # For example: john@ owner_email = # Antenna # For example: Random Spyserver # User sessions # maximum_clients = 1 # Maximum session duration # In minutes. 1790 on Microsoft Windows NT 10. In my case, The problem was caused by the missing one file in the server folder: rtlsdr. airspyhf. From: bachelder. 0 for no limit # #maximum_session_duration = 30 Set to maximum_session_duration = 30 remove the #. 1. More. OP post lsusb to Found 1 device(s): 0: Realtek, RTL2838UHIDIR, SN: 000001 Using device 0: Generic RTL2832U OEM Found Fitipower FC0012 tuner Supported gain values (5): -9. 9 19. During configuration of the file spyserver. Sign in Product # A value of 0 will acquire the first available device. Is there something else I need to run as super user I might have missed? Releasing the AirspyOne device Accepted client 192. Ken. This is because the custom sample rate line is commented out with a hashtag and if left this way spyserver I'm stumped at what could have caused a working installation to suddenly stop working for a non-root user. Then later in April they added full support for the RTL-SDR dongle as well. Instead of sending the entire raw data like rtl_tcp does, SpyServer only sends the IQ data of the currently tuned in signal. But the number of images you can get depends on the VkSurfaceCapabilities of your device. You may get a slightly reduced amount Zadig is windows only. 159:5556. If you have a 32-bit ARM CPU, you can Google was 100% unhelpful when I was beating my head against this problem but it turned out to be relatively simple to resolve. Jeff Note: The device_serial directive only needs applying if you have more than one Airspy SDR connected to your PC, it allows you to choose the correct device. Now click on the instance again, the issue should be fixed. All groups and messages HPDIA0114E Could not acquire a client credential. 1) incrementing the device_serial in spyserver config by 1 (default starts at 0) until the server error message changed from “could not acquire the device” to “no suitable If spyserver were compiled like a normal dynamic elf binary, you could have used "ldd" to see what it's trying to load so that you can then supply it, but it isn't (ldd simply says it's not a I'm having a bit of trouble getting spyserver operating properly with my Airspy HF+ on a Wake up!" followed by "Could not find any suitable device. 9% of the times this happens because ModemManager is already running in the system; e. Set device_serial in the config to 0. Maybe that's a unified library, but as Prog points out you have to get to the libairspyhf files. We try to assume as little knowledge as possible, but we do assume that you have decent experience with computers. One with device_serial 0, and the other device_serial 1. # Device Serial Number as 64bit Hex # A value of 0 will acquire the first available device # device_serial = 0 # Device Sample Rate # Possible Values: # Airspy R0, R2 : 10000000 or 2500000 # Airspy Mini : 6000000 or 3000000 # Airspy HF+ : 768000 # RTL-SDR : 500000 to 3200000 # Comment to use the device's default # #device_sample_rate = 2500000 getUserMedia is not meant to connect to ip-cams, but to webcams, i. However, everytime I try Raspberry Pi 4 and RTL-SDR ~Could not acquire the device~#spyserver; Could not acquire the device BUT rtl_test running ok pi@raspberrypi:~ $ rtl_test Found 1 device(s): 0: Realtek, RTL2838UHIDIR, SN: 00000001. What I´m doing wrong? From sharp everything run without problems. Currently it appears Spyserver does not properly parse a given serial number in the config. # device_serial = 0 # Device Sample Rate # Possible Values: If the SpyVerter is used, the following parameters should be set in spyserver. Do others have this I have a public Spyserver sdr://81. With SDR plugged inDevice Manager, right-click device, Uninstall, check box to remove drivers) Run the Zadig installer, checked the entry for "Options->List All Devices", then cleared the check for "Ignore Hubs or Hi, I have an Airspy R1 running on Spyserver V1700 and it's showing in the in the Spyserver directory. My experience with a 3 AMP USB power supply is that it was not a matter of current, but voltage. In this tutorial we will show how to set up SpyServer on both Windows and Linux SpyServer is similar to another tool that you may already be familiar with called rtl_tcp. Info: This tool will continuously read from the device, and report if samples get lost. pge rktuexh zogvct gmpbv waiy myqhevb biwigb bzmb mnlp ousku