Hi i have now tried it on S1 and I also got confused by this since i had an frequency error 13khz and ppm didnt work, finally i found this blog
Its been 3 years now, any idea if it can get fixed, I have an easy solution, just disable the tuning within the waterfall in the sourcecode
And add that as a parameter so it can be used when you start gqrx, would be fine, otherwise you forget this and you wonder why frq is totally wrong
//Chris

Thanks very much to you too, removing that file got mine working as well.
I'm so pleased - I was trying to get the Elad SW2 software to work in VirtualBox and it was too laggy really, this is much more snappy.

I wonder if I could get this working on Slackware as well?  Would I have to recompile or something?

Kevin.

Hi all,

I have used the wrapper with GQRX on a raspberry pi 4 with attached 7" screen, this produces a great FFT/waterfall. End use will be for my 10G /P system where the Elad FDM DUO is the IF transceiver. The system will run for more than a day connected to a USB power bank with 4 X 18650's in it. Photo below shows what it looks like, this is wht the FDM DUO tuned somewhere on shortwave.



As mentioned, the tuning control from GQRX works once at start, where it sets the radio to 14. something MHz but after that you cannot control the FDM DUO from the GQRX software, no major hassle for my application though.

Thanks to Giovanni for the wrapper, its really great!

regards,

Paul M0EYT.

Thank to Steve Knell,
I've found a bug that arises in gqrx wrapper when the tuning is done clicking on the waterfall.
The problem is related to the fact that gqrx uses a channel differential frequency to not move the hardware frequency.
This is perfect, not gqrx problem, but from TCP/IP socket only "real" frequency is avalable, and the wrapper uses this frequency to set the Center frequency on the device (DUO; S1, S2).
The tuning works well if youj don't use the "clik on the fft" to set frequency, in other words when the differential channel frequency is zero.
I've cheduled to change the communication between wrapper and gqrx using I/Q channel two way (as gqrx do with devices), but it takes time and effort, so I ask to be patient: even if it is not visible I'm working on this.
Regards,
Giovanni - HB9EIK

I'm very glad you succedeed in using the wrapper.

Giovanni

It's working now!!!  I removed this file ~/.config/gqrx/default.conf and all good.  MANY THANKS for this - very cool.

Hi Giovanni,

It's doing something now.  I'm now using 'sudo -E' to preserve those debug environment settings.  It did change the FDM-DUO's frequency to 14.200, but there is no audio in GQRX?

What's it trying to connect to and the end of the log (attached)?

Thanks,
Steve

Hi steve,
from the ldd command it seems that the programs are in the correct fornat and all the needed libraries are ok.
Also fhe environment variables are well configured.
The problem seems to be those environment variables are not seen fron program.
Could you please launch the program as
./elad-gqrx 2>/tmp/log.txt
and attach the  /tmp/log.txt file to the answer ?

Regards,

Giovanni

Hi Giovanni,

% ldd ./elad-gqrx
    linux-vdso.so.1 =>  (0x00007fff455df000)
    libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007f62fe1ba000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f62fdeb1000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f62fdc94000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f62fd8ca000)
    libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f62fe7bd000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f62fe5e1000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f62fd6c2000)

% ldd ./elad-firmware
    linux-vdso.so.1 =>  (0x00007fffcedd0000)
    libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007f48f09f2000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f48f0628000)
    libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f48f191a000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f48f040b000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f48f173d000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f48f0203000)

% echo $ELAD_DEBUG
1

% echo $GQRX_DEBUG
1

% sudo ./elad-gqrx

[no output]
When I do a strace on the PID, I see this: 

strace: Process 5226 attached
open("/tmp/elad", O_WRONLY

Any ideas, please?

Thanks,
Steve

Hi steve,
what is the output of ldd ./elad_gqrx ?

what is the output of ldd ./elad_firmware ?

to set GQRX_DEBUG and ELAD_DEBUG, have you used
export GQRX_DEBUG=1
export ELAD_DEBUG=1
or something different ?

before launching sudo ./elad_gqrx what is the result of
echo GQRX_DEBUG
and
echo ELAD_DEBUG
?

Sorry to have only questions, but hope the answers can help to trace the problem.

Regards,

Giovanni - HB9EIK

Hi Giovanni,

I would like to use this wrapper also, on my Linux Mint 18.3 host.  I have followed the installation instructions, but 'sudo ./elad_gqrx' just hangs and setting GQRX_DEBUG and ELAD_DEBUG don't produce any output either.

Is this because my machine has an amd64 chip set?

Thanks,
Steve

Giovanni,

Last update.. You were correct, the problem wasn't with the wrapper. Part of the reason for the problem was my limited linux abilities, the other was that the wrapper called up error when run as root. Another was that the system took a couple re-boots for the added text lines to be recognized. All is well now, thank you for your help to resolve this issue.

Update...
I have deleted the created elad.rules folder and simply added the text lines into the rules.d folder, which was (probably?) your intended advice. I now can run gqrx but still have the libusb errors showing in terminal.

Giovanni,

I created a folder called elad.rules within the folder rules.d
In the elad.rules folder, I added the three lines of text.
I always ran the wrapper with sudo and got the pulseaudio error.
With the added lines, I still get the pulseaudio error if trying to run as root.
I don't get the pulseaudio error when running the wrapper not as root.
However, I now get this error:

libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/001/004: Permission denied
libusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.
libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/001/004: Permission denied
libusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.

Sometimes gqrx will start up, sometimes not. If it comes up, it crashes as soon as I click to start the dsp.

Ken,
thanks for the follow-up.
Do you launch gqrx and/or wrapper as root or as your user ?
Try to launch gqrx as root: the problem exists?
Try to launch wrapper as non root, and see if the problem is solved.
Launching the wrapper as non root can have problem with device permissions.
If this is the case you have to add some rules to your system udev:
it could be necessary to add in  /etc/udev/rules.d/elad.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1721", ATTRS{idProduct}=="0610", MODE:="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1721", ATTRS{idProduct}=="061a", MODE:="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1721", ATTRS{idProduct}=="061c", MODE:="0666"
Hope this helps,

Giovanni - HB9EIK

Giovanni, I can start gqrx without the wrapper and it gives no error message about pulseaudio. If pulseaudio is running as root, I don't know how to change that so it doesn't.

Alberto, I tried to use your method but got this error message:

E: [pulseaudio] main.c: Failed to kill daemon: No such process

I fear that this issue is not related to wrapper. but it should be realated to the user.
In my experience some times pulseaudio has troble if used by root.

The first command I issue both when starting Debian Buster on the PC or Raspbian on the Raspberry Pi3 B is :

 pulseaudio --kill

from then on the audio behaves as it should....

Hi Ken,
I fear that this issue is not related to wrapper. but it should be realated to the user.
In my experience some times pulseaudio has troble if used by root.
Do you obtain the same error message if you start gqrx (no wrapper) as root or as your normal user ?
Regards,

Giovanni - HB9EIK

Hello,

I am using the wrapper and it works well in Ubuntu 18.04. I have a fresh install of Kubuntu 19.10 on another partition and when I attempted to run the wrapper on that newer update, I received an error message:

pulseaudio error: connection refused

GQRX is not brought up and the operation simply halts. I am mentioning this hoping someone else will confirm/examine this problem. I am not a linux expert, so I will let others decide if the wrapper needs to be modified for the newer linux or if the situation is something I must take care of with my Kubuntu install.

Hi Ken,
happy to know this :-)
Regards,

Giovanni - HB9EIK