dl1ksv / gr-funcube

Provide a gnuradio oot module for the for the funcube and the funcube pro plus dongle, requires gnuradio 3.9 and pybind
GNU General Public License v3.0
5 stars 5 forks source link

Funcube Dongle Pro+ with GQRX #10

Closed ik8ozv closed 1 year ago

ik8ozv commented 1 year ago

Please anybody can help me to get it working under GQRX? When i try to select the I/O Device, i can see two devices, one named FUNCube Dongle V2.0 and another one named FUNCube Dongle V2.0 Stereo Analogico. the first one has as Device string FCD=0 while the second one has as Device default_input=True,default_output=False,device_id=0,driver=audio,soapy=0. If i select the first one the program closes down while if i choose the second one i bet the audio distorted and mixed with the background noise. It is not clear. Please any help? Thanks Enzo

dl1ksv commented 1 year ago

Which drivers are linked to gqrx? They are reported on startup. On my system I get $gqrx gr-osmosdr 0.2.0.0 (0.2.0) gnuradio v3.11.0.0git-428-g131e733a built-in source types: file fcd rtl rtl_tcp rfspace soapy redpitaya

Did you build gqrx from source ?

The device string FCD=0 is correct.

ik8ozv commented 1 year ago

I am not so clever on Linux. Will you please tell how to check which drivers are linked to gqrx?

For the GQRX I just gave in terminal the command:

sudo apt-get install gqrx-sdr

Thanks

73’s de Enzo IK8OZV

dl1ksv commented 1 year ago

Just run the gqrx executable in a terminal window and have a look at the output.

ik8ozv commented 1 year ago

When i run gqrx in the Terminal Window i get:

gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.1.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp file_source :warning: file size is not a multiple of item size Resampling audio 96000 -> 48000 BandPlanFile is /home/enzo/.config/gqrx/bandplan.csv BookmarksFile is /home/enzo/.config/gqrx/bookmarks.csv [INFO] [UHD] linux; GNU C++ version 11.2.0; Boost_107400; UHD_4.1.0.5-3 libusb: warning [libusb_exit] device 1.1 still referenced libusb: warning [libusb_exit] device 2.5 still referenced libusb: warning [libusb_exit] device 2.4 still referenced libusb: warning [libusb_exit] device 2.3 still referenced libusb: warning [libusb_exit] device 2.2 still referenced libusb: warning [libusb_exit] device 2.1 still referenced

then i get the gqrx error window which says:

Gqrx has detected problems with the current configuration.Loading the application to crash. Do you want to edit settings?

If i click on NO it continues with:

gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.1.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp Using FUNcube Dongle V2.0 (hw:1) Errore di segmentazione (core dump creato)

but the gqrx seems does not load as i do not see it.

If i click on YES i get the GQRX ConfigureI/o devices window poping up. I leave all at it is and click on OK and it does the same as above, And also in this case, the gqrx seems does not load as i do not see it. Viceversa when i click on YES of the error i change the devece from Funcube Dongle V2.0 to Funcube Dongle V2.0 Stereo Analogico, then i get the final that says:

gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.1.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp [INFO] Using format CF32.

The program loads up but i cannot hear clearly the modulation how i said in the first message Thanks

73's de Enzo IK8OZV

dl1ksv commented 1 year ago

@Enzo in #11 you mentioned that you were able to decode a FM Radio station clearly in gnuradio.
If so it's a problem of gqrx/ gr-osmosdr not of gr-funcube.

What happens if you try to edit the configuration? You should use FUNCube Dongle V2.0 and the fcd=0. Make sure to select the correct inputrate 192000 and decimation none. The libusb warnings look strange. I've never seen them before. But I think you should ask on https://github.com/gqrx-sdr/gqrx/issues

ik8ozv commented 1 year ago

@dl1ksv yes correct but i have also noticed and forgot to say that if i try a satellite flowgraph that it is with gr-satellites i do not get any byte. In the first message above i said:

When i try to select the I/O Device, i can see two devices, one named FUNCube Dongle V2.0 and another one named FUNCube Dongle V2.0 Stereo Analogico. the first one has as Device string:

FCD=0

while the second one has as Device string:

default_input=True,default_output=False,device_id=0,driver=audio,soapy=0.

If i select the first one the program closes down while if i choose the second one i get the audio distorted and mixed with the background noise. It is not clear. Thanks

73's de Enzo IK8OZV

dl1ksv commented 1 year ago

@ik8ozv I need the reason, why the program shuts down. Which messages do you get in the terminal window.

I think soapy has it's own fcd* driver. I have to verify that. The libusb messages may be a hint that soapy blocks the usb device of the dongle.

By the way: which distro are you using? The actual gnuradio version is about 3.10.6

ik8ozv commented 1 year ago

@dl1ksv If i run GQRX in the terminal window, i get:

QSocketNotifier: Can only be used with threads started with QThread gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.5.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp xtrx Resampling audio 96000 -> 48000 BandPlanFile is /home/enzo/.config/gqrx/bandplan.csv BookmarksFile is /home/enzo/.config/gqrx/bookmarks.csv [INFO] [UHD] linux; GNU C++ version 12.2.0; Boost_107400; DPDK_22.11; UHD_4.3.0.0+ds1-4build2 libusb: warning [libusb_exit] device 4.1 still referenced libusb: warning [libusb_exit] device 3.4 still referenced libusb: warning [libusb_exit] device 3.3 still referenced libusb: warning [libusb_exit] device 3.5 still referenced libusb: warning [libusb_exit] device 3.2 still referenced libusb: warning [libusb_exit] device 3.1 still referenced libusb: warning [libusb_exit] device 2.1 still referenced libusb: warning [libusb_exit] device 1.3 still referenced libusb: warning [libusb_exit] device 1.2 still referenced libusb: warning [libusb_exit] device 1.1 still referenced gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.5.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp xtrx Using FUNcube Dongle V2.0 (hw:1) Funcube Pro+ :info: Start init fcdpp Funcube Pro+ :info: Audio device hw:1 opened fcdpp_control :error: FunCube Dongle V2.0 not found. gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.5.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp xtrx

and i get the GQRX Window error that says:

Failed to set input device

FunCube Dongle V2.0 not found. Please select another device

Please what to do? Thanks

73's de Enzo IK8OZV

dl1ksv commented 1 year ago

Did you try to edit the device settings? You must choose the device that has the device string fcd=0. I think, the second entry references a soapy driver that has it's own fcd driver implementation. I just built gqrx from scratch together with gr-funcube and I get only one device for the dongle and this works.

ik8ozv commented 1 year ago

yes i did but i get the error shown here:

https://ibb.co/9ZQH8Q6

Thanks

dl1ksv commented 1 year ago

It seems that the device is in use which may correspond to the libusb warning. So where did you gqrx from? Distro, build by yourself? Just a try: Start gqrx without attached Funcube dongle. Open the device tab. Attach the dongle and start Device scan from the device tab. Which messages do you see in the terminal window and which devices are listed in the Device pull down menu of the device tab?

ik8ozv commented 1 year ago

First please what you mean for "So where did you gqrx from?" and for "Distro, build by yourself? if you mean were did i get it, i have just typed in the terminal:

sudo apt-get insrtall gqrx-sdr

Done what you said but did not understood all. This is whay i have done:

Unplugged the Funcube Dongle Pro Plus Started GQRX; Opened the Device DropList; Attached the Funcube Dongle Pro Plus; Clicked on Device Scan button on the Bottom ( there is no Device scan in the Device DropList; Please which terminal window you mean i have to see messages? The Devices listed in the pull down menu of the device tab are:

Complex Sampled (IQ) File E1371/ES1373 /Creative Labs CT 2518 (Audio PCI64V/128/5200/ Creative CT4810/CT5803/CT5806 [Soun Blaster PCI]) FUNcube Dongle V2.0 FUNcube Dongle V2.0 RFSPACE Cloud-IQ Receiver RFSPACE NetSDR Receiver RFSPACE SDR-IP Receiver RFSPACE SDR-IQ Receiver RTL-SDR Spectrum Server Red Pitaya Transceiver Server Other...

Thanks

dl1ksv commented 1 year ago

You install gqrx from the repository of your linux distro. But what distro are you using? Ubuntu, Debian, Fedora ...? You have to start gqrx in a terminal window to get more error messages.

It's strange that you see the Funcube Dongle twice.

You can try to download the official release. Don't forget to make the downloaded file executable ( chmod +x )

I tested this executable and it works for me though it reports the libusb warnings you have seen.

ik8ozv commented 1 year ago

@dl1ksv Please Apologies if I forgot to Mention the distro I am using. It is UBUNTU 23.04 I am not to familiar with Linux so I ask you please if you can tell me how to unistall the actual version I have. Thanks.

Also please can you tell me the command to make the downloaded file executable?

Finally i gave rhe command Gqrx in the terminal and got:

QSocketNotifier: Can only be used with threads started with QThread gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.5.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp xtrx Resampling audio 96000 -> 48000 BandPlanFile is /home/enzo/.config/gqrx/bandplan.csv BookmarksFile is /home/enzo/.config/gqrx/bookmarks.csv [INFO] [UHD] linux; GNU C++ version 12.2.0; Boost_107400; DPDK_22.11; UHD_4.3.0.0+ds1-4build2 libusb: warning [libusb_exit] device 2.1 still referenced libusb: warning [libusb_exit] device 1.5 still referenced libusb: warning [libusb_exit] device 1.4 still referenced libusb: warning [libusb_exit] device 1.3 still referenced libusb: warning [libusb_exit] device 1.2 still referenced libusb: warning [libusb_exit] device 1.1 still referenced gr-osmosdr 0.2.0.0 (0.2.0) gnuradio 3.10.5.1 built-in source types: file fcd rtl rtl_tcp uhd hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp xtrx Using FUNcube Dongle V2.0 (hw:1) Funcube Pro+ :info: Start init fcdpp Funcube Pro+ :info: Audio device hw:1 opened fcdpp_control :info: FunCube Dongle V2.0 initialized. fcdpp_control :info: Dongle: FCDAPP 20.03 fcdpp_control :info: LNA gain enabled fcdpp_control :info: Mixer gain enabled fcdpp_control :info: IF gain set to: 15 fcdpp_control :info: Set Frequency to: 150000 Hz fcdpp_control :info: LNA gain enabled fcdpp_control :info: Mixer gain enabled fcdpp_control :info: IF gain set to: 15 fcdpp_control :info: Set Frequency to: 144800000 Hz

I hope it helps you to understand the problem. Please pay attention at the first line that i get also when i run any grc fie Thanks for your efforts

73’s de Enzo IK8OZV

dl1ksv commented 1 year ago

To make a file executable use a terminal window: cd "directoryname" The directoryname is the name of the directory that contains the file.

Then chmod + x filename

Now you can execute the file by

./filename

To test the downloaded file you don't have to uninstall anything.

No idea why you get the QSocketNotifier message. The output itself looks good. The dongle is initialized and it is set to 144800 kHz. Up to here there seems to be no error. The next step would be to start the device from the gui. I get the libusb warnings when I run the appimage , too, but the dongle works.

ik8ozv commented 1 year ago

@dl1ksv

when i give

./Gqrx-2.16-x86_64.AppImage

After done the comans:

chmod +x Gqrx-2.16-x86_64.AppImage

i get:

./Gqrx-2.16-x86_64.AppImage dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information

Thanks

dl1ksv commented 1 year ago

You have three options:

  1. Follow the recommendations given in the link above
  2. Run ./Gqrx-2.16-x86_64.AppImage --appimage-extract which builds a new directory. Switch to that directory and run ./AppRun
  3. Report a bug to Ubuntu
ik8ozv commented 1 year ago

@dl1ksv When i go to open the program i get always the warning:

Failed to set input device audio_alsa_source Please select another device.

In this version i can see just one Funcube called:

FUNCube Dongle V2.0

Please what to do? maybe the driver is not installed correctly. Any way to check if installed correctly? Thanks

73's de Enzo IK8OZV

dl1ksv commented 1 year ago

Seeing only FUNCube Dongle V2.0 is OK. You can try to run grc and there one of the examples using gr-funcube.

ik8ozv commented 1 year ago

I have tried the fmfcdpp one but i hear the audio with a lot of vibrations. Any hint please? Thanks

dl1ksv commented 1 year ago

So the driver is availabe and working.