search

krakenrf / gr-krakensdr

GNU General Public License v3.0
55 stars 15 forks source link

Ethernet Connection Failed when running script #4

Open galkinb opened 1 year ago

galkinb commented 1 year ago

When running the example GNUradio scripts such as FFT display, I'm getting "Ethernet Connection Failed, Error: <class 'ConnectionRefusedError'>

Running this on a Raspberry Pi 4 using the provided SD card image and GNUradio 3.11 installed on the Pi. Verified that the krakensdr_doa program appears to run without errors, so assuming its not a power supply or cable issue. Observing the same issue on a laptop running Ubuntu 22.04.

cesarnr21 commented 1 week ago

@galkinb I am running into that same issue, did you ever find a solution?

galkinb commented 1 week ago

@cesarnr21 If I remember correctly, I wasn't able to get it working when the same RPi was running the krakensdr_doa code as the GNUradio script. One workaround that I think worked (I'm trying to jog my memory now) was separating out the functionality, as the readme says "Alternatively, you can run the heimdall code on a networked device, but you will need a fast Gigabit and possibly direct network connection to ensure the network throughput is sufficient to handle the five channels." I basically had one RPi running the Heimdall code with the preconfigured SD card image, had that connect via a short ethernet cable directly into a second RPi, and that second RPi could then run the GNUradio script with the input block configured to listen to the IP address of Pi 1.

Using two devices ended up being too cumbersome a solution so in the end I just looked at the doa script here https://github.com/krakenrf/krakensdr_doa/blob/main/_sdr/_signal_processing/kraken_sdr_signal_processor.py and wrote my signal processing code into it directly, without using GNUradio. If that's an option for you maybe give that a shot. Let me know if you manage to get something working, it would be good to be able to use GNUradio.

cesarnr21 commented 2 days ago

@galkinb I found that the issue was some invalid bash syntax in one of the scripts of in the heimdall_daq firmware. I made a PR for it here. Applying these changes fixed the issue for me.