Hi Giuseppe, when I try to select airspy mini (with serial number) from Device menu, the program crashes leaving no trace in log file. I've installed soapysdr and device runs when I program it in python. Windows 10, PothosSDR version 2020.12.28. What should I look at? Can I increase the debug level?
Windows error:
Nombre de la aplicación con errores: echoes.exe, versión: 0.0.0.0, marca de tiempo: 0x64d6c264
Nombre del módulo con errores: ucrtbase.dll, versión: 10.0.19041.789, marca de tiempo: 0x2bd748bf
Código de excepción: 0xc0000409
Desplazamiento de errores: 0x0000000000071208
Identificador del proceso con errores: 0x4878
Hora de inicio de la aplicación con errores: 0x01d9d7fea1d4cdfd
Ruta de acceso de la aplicación con errores: C:\Program Files\GABB\echoes\echoes.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\ucrtbase.dll
Identificador del informe: 054b6e9b-4a32-4736-944e-f98894512948
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
Echoes log:
echoes(11:21:20.068)Info: :0x22dbe2af130 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] 1 AirSpy boards found.
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] Serial 4a464c83755420b
echoes(11:21:20.148)Info: :0x22dbb16e760 [SOAPY] 0 AirSpy boards found.
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.1.5
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.3.20
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.88.5
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 213.151.119.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv6 fe80::15d3:d977:2eeb:f069%17
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv4 192.168.56.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv6 fe80::f849:d650:53de:a230%23
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv4 172.20.160.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv6 fe80::b3f6:c664:fbf:2b63%43
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv4 172.17.112.1
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv6 fe80::1db1:6812:babb:8d01%50
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:22.598)Info: Main thread:0x22db4017d20 [SOAPY] AirSpy Lib v1.0 rev 9
echoes(11:21:22.618)Info: Main thread:0x22db4017d20 [SOAPY] 1 AirSpy boards found.
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Serial 4a464c83755420b
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Found device by serial 4a464c83755420b <--- last line
Thanks in advance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Joan,
launch echoes fom command line with options -v -n4 to get a more detailed output. It could be the same problem I found while working with rsp1 clone (due to libusb.dll) mentioned in the manual.Looking forward for feedbacks
Giuseppe
Inviato da Yahoo Mail su Android
Il sab, 26 ago, 2023 alle 11:25, Joan Fjoanfc@users.sourceforge.net ha scritto:
Hi Giuseppe, when I try to select airspy mini (with serial number) from Device menu, the program crashes leaving no trace in log file. I've installed soapysdr and device runs when I program it in python. Windows 10, PothosSDR version 2020.12.28. What should I look at? Can I increase the debug level?
Windows error:
Nombre de la aplicación con errores: echoes.exe, versión: 0.0.0.0, marca de tiempo: 0x64d6c264
Nombre del módulo con errores: ucrtbase.dll, versión: 10.0.19041.789, marca de tiempo: 0x2bd748bf
Código de excepción: 0xc0000409
Desplazamiento de errores: 0x0000000000071208
Identificador del proceso con errores: 0x4878
Hora de inicio de la aplicación con errores: 0x01d9d7fea1d4cdfd
Ruta de acceso de la aplicación con errores: C:\Program Files\GABB\echoes\echoes.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\ucrtbase.dll
Identificador del informe: 054b6e9b-4a32-4736-944e-f98894512948
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
Echoes log:
echoes(11:21:20.068)Info: :0x22dbe2af130 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] 1 AirSpy boards found.
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] Serial 4a464c83755420b
echoes(11:21:20.148)Info: :0x22dbb16e760 [SOAPY] 0 AirSpy boards found.
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.1.5
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.3.20
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.88.5
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 213.151.119.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv6 fe80::15d3:d977:2eeb:f069%17
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv4 192.168.56.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv6 fe80::f849:d650:53de:a230%23
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv4 172.20.160.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv6 fe80::b3f6:c664:fbf:2b63%43
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv4 172.17.112.1
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv6 fe80::1db1:6812:babb:8d01%50
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:22.598)Info: Main thread:0x22db4017d20 [SOAPY] AirSpy Lib v1.0 rev 9
echoes(11:21:22.618)Info: Main thread:0x22db4017d20 [SOAPY] 1 AirSpy boards found.
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Serial 4a464c83755420b
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Found device by serial 4a464c83755420b <--- last line
Hi,
apparently from the log everything seems ok, except that it stops immediately after the recognition of the Airspy. In my opinion you should try installing the latest version of PothosSDR (2021.07.25). You can try as I did too, renaming the c:\program files\PothosSDR directory as PothosSDR2020 and installing the new version, so you have both versions installed and can switch between them by renaming the PothosSDR folder.
Another suggestion I can give is to remove the support dlls related to devices you don't use, for example I see SoapyRemote generates a lot of output but if you don't use it it just confuses the ideas.
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No luck with PothosSDR (2021.07.25) , but I have a much cleaner log ;) . Echoes crashes at same point, after selecting airspy from list of devices. What do you think?
Thanks in advance
you can do this:
1-start echoes, set the MIC audio device and start the acquisition, you should see the audio spectrum; make some noise i.e. by clapping hands and see if the spectrum reacts and is not frozen.
2-stop the acquisition and save the configuration with a name, i.e. audio.rts
3-send me the file
4-I'll send you back a rts file (i.e. airspy.rts) patched to run with an airspy dongle.
5-place that file under the working directory "echoes" in your home
C:/Users/Joan/echoes/airspy.rts
in this way you skip the code that manages the device selection, let's see if it works.
Unfortunatey I have no more an Airspy to do a better debug; the one I had was lent to me for a few months by a friend but then I had to return it.
The unique feedback I have about Echoes with Airspy is from Pierre Terrier (RMOB). On last January he wrote me he could run Echoes 0.50 with Airspy on a Raspberry PI. You could try with 0.50 as last resort
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BTW I had sdrsharp tuned to Graves (with a yagi) and I got this. Is it an artifact? At that time a low flying copter has passed and a starlink train has also passed
Same result (the graphic interface does not appear), same on log. I can test if it runs on a notebook with ubuntu 20... but it is not a solution to have it running 24 hours a day.
One question: echoes can run headless? (without graphic interface)
Thank you Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
About headless:
you can run it into a terminal/cmd window without opening a graphic interface. Under linux it can run even without X, from the console. It generates data dumps and counts only, no screenshots.
See: http://www.gabb.it/echoes/051_console.html
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ubuntu20 has been discontinued, the 0.51 is available from ubuntu 21.04 to 23.04, where soapysdr v0.8 is available. The v.0.7 is not supported and I have no idea if Echoes can work with it, I never tried.
If you find the same problem even on Linux, it becomes more likely that the problem lies with Echoes rather than PothosSDR.
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, good news. It's running on Ubuntu22 in a Virtualbox VM. Airspy is runnig with a 3M bandwidth to optimize FFT. I have some questions:
1- nFFT is limited to 65536?
2-How to activate bias-tee? Through soapysdr maybe? I have a nooelec 2m lna&filter that works fine.
3-I see a strong signal on center freq. Is there a possibility of IQ correction?
Joan
Great Joan,
so the problem you faced is about PothosSDR/Airspy only. Nevertheless, you said you have no problem to use that libraries with Python. I'll keep a note on this, in case someday an Airspy falls into my hands ;)
About your questions:
1-no, that number is limited only by device's MTU, an information that Echoes gets from Soapy. The downsample bandwidth, the resolution in Hz of each point and the number of FFT points (nFFT) respect this MTU limit. Unique exception is when you enable the "direct buffers".
2-bias tee, IQ reversal, and other custom settings specific to certain devices can be set through Soapy but I honestly still didn't care for them, as I had no idea how and why Echoes was supposed to use them.
One of my goals for this release was to keep the GUI as uniform as possible and these settings are just what can't be uniform because they depend on individual devices, so I would find myself generating the GUI dynamically, which would have forced me to further delay the release (there are 15 months of work between 0.50 and 0.51) .
In the future, I might work around this by allowing Echoes to read the device settings and save them in the RTS file, so the user can change them by editing the file.
The next time the rts file is loaded, the new settings would be applied to the SDR.
3-that is the DC component of the signal, that appears in the center of the spectrum. You can set a notch on it or you can tune some khz above/below the GRAVES then center that in the window by moving the offset slider (some zoom is needed).
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Giuseppe, when I try to select airspy mini (with serial number) from Device menu, the program crashes leaving no trace in log file. I've installed soapysdr and device runs when I program it in python. Windows 10, PothosSDR version 2020.12.28. What should I look at? Can I increase the debug level?
Windows error:
Nombre de la aplicación con errores: echoes.exe, versión: 0.0.0.0, marca de tiempo: 0x64d6c264
Nombre del módulo con errores: ucrtbase.dll, versión: 10.0.19041.789, marca de tiempo: 0x2bd748bf
Código de excepción: 0xc0000409
Desplazamiento de errores: 0x0000000000071208
Identificador del proceso con errores: 0x4878
Hora de inicio de la aplicación con errores: 0x01d9d7fea1d4cdfd
Ruta de acceso de la aplicación con errores: C:\Program Files\GABB\echoes\echoes.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\ucrtbase.dll
Identificador del informe: 054b6e9b-4a32-4736-944e-f98894512948
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
Echoes log:
echoes(11:21:20.068)Info: :0x22dbe2af130 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] 1 AirSpy boards found.
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] Serial 4a464c83755420b
echoes(11:21:20.148)Info: :0x22dbb16e760 [SOAPY] 0 AirSpy boards found.
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.1.5
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.3.20
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.88.5
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 213.151.119.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv6 fe80::15d3:d977:2eeb:f069%17
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv4 192.168.56.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv6 fe80::f849:d650:53de:a230%23
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv4 172.20.160.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv6 fe80::b3f6:c664:fbf:2b63%43
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv4 172.17.112.1
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv6 fe80::1db1:6812:babb:8d01%50
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:22.598)Info: Main thread:0x22db4017d20 [SOAPY] AirSpy Lib v1.0 rev 9
echoes(11:21:22.618)Info: Main thread:0x22db4017d20 [SOAPY] 1 AirSpy boards found.
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Serial 4a464c83755420b
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Found device by serial 4a464c83755420b <--- last line
Thanks in advance
Hi Joan,
launch echoes fom command line with options -v -n4 to get a more detailed output. It could be the same problem I found while working with rsp1 clone (due to libusb.dll) mentioned in the manual.Looking forward for feedbacks
Giuseppe
Inviato da Yahoo Mail su Android
Il sab, 26 ago, 2023 alle 11:25, Joan Fjoanfc@users.sourceforge.net ha scritto:
Hi Giuseppe, when I try to select airspy mini (with serial number) from Device menu, the program crashes leaving no trace in log file. I've installed soapysdr and device runs when I program it in python. Windows 10, PothosSDR version 2020.12.28. What should I look at? Can I increase the debug level?
Windows error:
Nombre de la aplicación con errores: echoes.exe, versión: 0.0.0.0, marca de tiempo: 0x64d6c264
Nombre del módulo con errores: ucrtbase.dll, versión: 10.0.19041.789, marca de tiempo: 0x2bd748bf
Código de excepción: 0xc0000409
Desplazamiento de errores: 0x0000000000071208
Identificador del proceso con errores: 0x4878
Hora de inicio de la aplicación con errores: 0x01d9d7fea1d4cdfd
Ruta de acceso de la aplicación con errores: C:\Program Files\GABB\echoes\echoes.exe
Ruta de acceso del módulo con errores: C:\WINDOWS\System32\ucrtbase.dll
Identificador del informe: 054b6e9b-4a32-4736-944e-f98894512948
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
Echoes log:
echoes(11:21:20.068)Info: :0x22dbe2af130 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] 1 AirSpy boards found.
echoes(11:21:20.144)Info: :0x22dbb2ca360 [SOAPY] Serial 4a464c83755420b
echoes(11:21:20.148)Info: :0x22dbb16e760 [SOAPY] 0 AirSpy boards found.
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.1.5
echoes(11:21:20.402)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.3.20
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 192.168.88.5
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {DD61FA09-D2DE-409C-B1AF-90270975FC39} IPv4 213.151.119.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv6 fe80::15d3:d977:2eeb:f069%17
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {773E6BF0-DA3D-4910-8382-081383D96C33} IPv4 192.168.56.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv6 fe80::f849:d650:53de:a230%23
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {C96460FA-54B7-4410-9A8F-A0913681B815} IPv4 172.20.160.1
echoes(11:21:20.403)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv6 fe80::b3f6:c664:fbf:2b63%43
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {F108DC52-FAB0-43E9-B412-62015EE8A16C} IPv4 172.17.112.1
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv6 fe80::1db1:6812:babb:8d01%50
echoes(11:21:20.404)Info: :0x22db70adfe0 [SOAPY] SoapySSDP join multicast endpoint on {B7ADD837-CC72-4657-97AB-6377802734C2} IPv4 172.29.32.1
echoes(11:21:22.598)Info: Main thread:0x22db4017d20 [SOAPY] AirSpy Lib v1.0 rev 9
echoes(11:21:22.618)Info: Main thread:0x22db4017d20 [SOAPY] 1 AirSpy boards found.
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Serial 4a464c83755420b
echoes(11:21:22.619)Info: Main thread:0x22db4017d20 [SOAPY] Found device by serial 4a464c83755420b <--- last line
Thanks in advance
echoes and airspy mini crash
Sent from sourceforge.net because gmbertani@users.sourceforge.net is subscribed to https://sourceforge.net/p/echoes/discussion/troubles/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/echoes/admin/discussion/forums. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Hi again, I've attached log output.
Best regards
Hi,
apparently from the log everything seems ok, except that it stops immediately after the recognition of the Airspy. In my opinion you should try installing the latest version of PothosSDR (2021.07.25). You can try as I did too, renaming the c:\program files\PothosSDR directory as PothosSDR2020 and installing the new version, so you have both versions installed and can switch between them by renaming the PothosSDR folder.
Another suggestion I can give is to remove the support dlls related to devices you don't use, for example I see SoapyRemote generates a lot of output but if you don't use it it just confuses the ideas.
Giuseppe
Thank you Giuseppe, it's complex but l'll try
Joan
No luck with PothosSDR (2021.07.25) , but I have a much cleaner log ;) . Echoes crashes at same point, after selecting airspy from list of devices. What do you think?
Thanks in advance
you can do this:
1-start echoes, set the MIC audio device and start the acquisition, you should see the audio spectrum; make some noise i.e. by clapping hands and see if the spectrum reacts and is not frozen.
2-stop the acquisition and save the configuration with a name, i.e. audio.rts
3-send me the file
4-I'll send you back a rts file (i.e. airspy.rts) patched to run with an airspy dongle.
5-place that file under the working directory "echoes" in your home
C:/Users/Joan/echoes/airspy.rts
6-from cmd.exe window, launch echoes:
echoes -v -n4 -s airspy.rts
in this way you skip the code that manages the device selection, let's see if it works.
Unfortunatey I have no more an Airspy to do a better debug; the one I had was lent to me for a few months by a friend but then I had to return it.
The unique feedback I have about Echoes with Airspy is from Pierre Terrier (RMOB). On last January he wrote me he could run Echoes 0.50 with Airspy on a Raspberry PI. You could try with 0.50 as last resort
Giuseppe
Ok Giuseppe. I've attached rts file. Echoes can run on linux? Or Pierre Terrier connects to an spy-server on a Rpi?
Joan
sure it can. My station runs under Linux. Take a look here: http://www.gabb.it/echoes/051_lin_install.html
Pierre installed the Raspbian11 package, but remember it was 0.50, I have no feedbacks about 0.51 from him
BTW I had sdrsharp tuned to Graves (with a yagi) and I got this. Is it an artifact? At that time a low flying copter has passed and a starlink train has also passed
it looks genuine IMHO
here is the config file modified, I guessed some values but should be enough to make it run with Airspy, pls. cross fingers first.
Same result (the graphic interface does not appear), same on log. I can test if it runs on a notebook with ubuntu 20... but it is not a solution to have it running 24 hours a day.
One question: echoes can run headless? (without graphic interface)
Thank you Giuseppe
mmm... sad :( you can try with 0.50.
About headless:
you can run it into a terminal/cmd window without opening a graphic interface. Under linux it can run even without X, from the console. It generates data dumps and counts only, no screenshots.
See: http://www.gabb.it/echoes/051_console.html
Giuseppe
Ok. In ubuntu 20 only soapysdr modules v0.7 are available. Could echoes+airspy run on v0.7?
ubuntu20 has been discontinued, the 0.51 is available from ubuntu 21.04 to 23.04, where soapysdr v0.8 is available. The v.0.7 is not supported and I have no idea if Echoes can work with it, I never tried.
If you find the same problem even on Linux, it becomes more likely that the problem lies with Echoes rather than PothosSDR.
Giuseppe
Hi, good news. It's running on Ubuntu22 in a Virtualbox VM. Airspy is runnig with a 3M bandwidth to optimize FFT. I have some questions:
1- nFFT is limited to 65536?
2-How to activate bias-tee? Through soapysdr maybe? I have a nooelec 2m lna&filter that works fine.
3-I see a strong signal on center freq. Is there a possibility of IQ correction?
Joan
Great Joan,
so the problem you faced is about PothosSDR/Airspy only. Nevertheless, you said you have no problem to use that libraries with Python. I'll keep a note on this, in case someday an Airspy falls into my hands ;)
About your questions:
1-no, that number is limited only by device's MTU, an information that Echoes gets from Soapy. The downsample bandwidth, the resolution in Hz of each point and the number of FFT points (nFFT) respect this MTU limit. Unique exception is when you enable the "direct buffers".
2-bias tee, IQ reversal, and other custom settings specific to certain devices can be set through Soapy but I honestly still didn't care for them, as I had no idea how and why Echoes was supposed to use them.
One of my goals for this release was to keep the GUI as uniform as possible and these settings are just what can't be uniform because they depend on individual devices, so I would find myself generating the GUI dynamically, which would have forced me to further delay the release (there are 15 months of work between 0.50 and 0.51) .
In the future, I might work around this by allowing Echoes to read the device settings and save them in the RTS file, so the user can change them by editing the file.
The next time the rts file is loaded, the new settings would be applied to the SDR.
3-that is the DC component of the signal, that appears in the center of the spectrum. You can set a notch on it or you can tune some khz above/below the GRAVES then center that in the window by moving the offset slider (some zoom is needed).
Giuseppe
Ok Giuseppe, thank you
Joan