echoes / Discussion / Troubleshooting: Echoes 0.50-1 on Raspberry Pi4B "Mismatched dongle" error

Hi!
I'm trying to get work Echoes 0.50-i on my RPi 4B 4GB running Rpios 11 (bullseye). Echoes is installed successfully after found the needed libsoapysdr0.8. I have a "Bus 001 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T" device (reported by lsusb command).
But as i try to run Echoes i get the error message popup: "Mismatched dongle in configuration file".
Here the line i have there:
"Device=0:rtlsdr Generic RTL2832U OEM :: 00000001 SN00000001"
I also tried with RTL2838U but no luck.
rtl_test output is:

pi@echoes:~/echoes $ rtl_test
Found 1 device(s):
  0:  Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4    43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode...
Allocating 15 zero-copy buffers
lost at least 32 bytes
^CSignal caught, exiting!

User cancel, exiting...
Samples per million lost (minimum): 0

And here lsusb:

pi@echoes:~/src $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I'm trying to use the AUTO_GRAVES.rts config file (attached)

Please help me. Thanks!!

AUTO_GRAVES.rts

gmbertani - 2022-07-25

Hi Laszlo,
it's normal if you get that message, because my AUTO_GRAVES.rts has been made in my station so the "Device=" string matches MY dongle, you simply have to close the warning by clicking on OK button and select another device clicking on "Device" drop down. There you should see the correct ID of YOUR dongle, click on it then press Save to store it permanently in AUTO_GRAVES.rts, it's all.

If instead you can't see your dongle in the drop down list, that could be really a problem to investigate.

ps see also the manual http://www.gabb.it/echoes particularly the page http://www.gabb.it/echoes/gui.html

Looking forward for updates.

Giuseppe

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-26
  
  Thanks, but the problem is, that in the dropdown list i have only the "Test Patterns" option. However my Pi sees my USB dongle, also the installed SDR++ software can use it, as you can see in attached pic. Don't know what the problem could be.
  
  sdrok.jpg
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-26

ok, you should then send me a log file. Just restore AUTO_GRAVES.rts as the original file, then run echoes from command line:

echoes -v -n4 -s AUTO_GRAVES > log.txt

then press OK to the mismatched dongle dialog . After that, quit the program and send me the log here, thanks.

Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-26
  
  Hmm, doesn't work (same error with sudo, but i think it should run without root):
  
  pi@echoes:~/echoes $ echoes -v -n4 -s AUTO_GRAVES > log.txt +++GUI application+++ qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted pi@echoes:~/echoes $
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-26

huh... in alternative you can collect the echoes-related messages stored in the journal, with

sudo journalctl -n10000 | grep echoes

in this way you'll get log messages with verbosity level is 3, and I'm not sure if it is enough to be useful - but let's see.

Giuseppe

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-26
  
  Attached the output.
  
  journalctl_out.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-26

ah I see you named your machine "echoes" so to get a shorter log, the command must be
sudo journalctl -n10000 | grep -a 'echoes echoes'

Anyway, if the unique device you see in the dropdown list is testpatterns, might be you missed to install the soapy support library for your dongle, the sopaysdr0.8-module-rtlsdr library.

If this is the case, you can find it in my repository
https://download.opensuse.org/repositories/home:/astronopteryx/

Giuseppe

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-26
  
  The package libsoapysdr0.8_0.8.1-2_armhf.deb was installed. Without that i could not install Echoes. But i installed now the soapysdr0.8-module-rtlsdr_0.3.0-4_armhf.deb package. After that When i start Echoes, i can select my device, but it gaves an error. See attached image and txt.
  
  Last edit: Laszlo Balogh 2022-07-26
  
  journal220726_2155.txt
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Laszlo Balogh - 2022-07-26
    
    And the error screen:
    
    rtlsdr.jpg
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-26

naah... I'd need the log file at level 4, really you can't run the program from a terminal command line? Are you working at console, so with a keyboard connected to the PI and HDMI screen
or via ssh and Xserver like I'm doing now? BTW I have a PI3+ and I have no problems with my command line.

For now I have nothing else to suggest except:

1- delete the default.rts and relaunch Echoes, just in case the previous attempts could have corrupted the file content and confuse the software while reading it.

2-I've seen your PI hostname is echoes, the user is echoes and the program to run is echoes... in a perfect world this should not be a problem, but it's not our world.
In your place I'd try to change temporarily the hostname and/or the user name and run the program, just to be sure that this coincidence is irrelevant.

3-Try to run the program by selecting "test patterns" - this will produce a simulated radio spectra and if you select the automatic mode, it generates also fake events to test the screen capture. This is not necessary to check, if you can see the spectra it's ok and we can be sure the problem is really related to dongle acquisition

looking forward for feedbacks

Giuseppe

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-27
  
  Thanks a lot! I did all the three steps, i don't know which helped, but it seems to be working now.
  See attached image. But i think something is wrong, as the levels are too low. What settings do i need to use in Device, FFT, Output, etc tabs?
  When i load AUTO.GRAVES settings, and start it, it says only "Acqusition running automatic mode", but nothing happens on the waterfall window.
  
  echoes001.jpg
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Laszlo Balogh - 2022-07-27

Here the auto.graves "running".

echoes002.jpg

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-27

Hi,
About the details of settings, they are explained in the manual, anyway that AUTO_GRAVES file is the same running on my station that is not a RPI but Lenovo Thinkcentre Core I5 with Opensuse Tumbleweed. Might be you'll have to increase the time interval in "Output" tab, I don't have a RPI4 but I think 10ms is a too small value, try to increase it to 100ms then decrease it in successive steps until you get the optimal speed for your hardware. Even the thresholds could need some tuning but first of all, the waterfall should display a spectra! What it seems looking at your screenshot is that Echoes isn't getting samples from the dongle. But don't be afraid. When working on a RPI it can happen that you launch Echoes and get strange transient errors. Then you try a second time and a third... until it runs without apparent changes... not really deterministic I know.

The same happened yesterday here, while I was trying to replicate your problem. My RPI is 3+ that means even less resources than your. Normally I don't use it with Echoes, except when I'm about to release a version and want to check how works with RPI.
So after 3 months I wanted to start Echoes on my RPI and it refused to run for 3 consecutive times. At fourth, it started and never stopped anymore until I turned it off a couple of hours later.

In your place I would investigate about why Echoes doesn't run when launched from command line because it will be useful to detect the cause of this and future problems. Echoes can run even without X server at all, in headless mode, but it needs to be launched from a terminal.

Giuseppe

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-27
  
  I launched echoes a lot of times, rebooted a lot the RPi. Nothing. However my dongle is working fine in a Windows laptop with SDR and Spectrumlab.
  I attach the config file. When i poress on start it says: "Acquisition running automatic mode". But nothing happens on the waterfall window. :(
  I don't know what the problem is, maybe simple it will not work on RPi. I cannot install a laptop for 7/24 mode, so if it will not work with RPi, than i have to pass this kind of job after years of uploading datas to RMOB. :(
  
  SDR01.jpg
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Laszlo Balogh - 2022-07-27
    
    Here my config:
    
    AUTO_GRAVES_MCLL.rts.txt
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Laszlo Balogh - 2022-07-27
      
      This also not works:
      
      pi@rmob:~/echoes $ echoes -v -n4 -s AUTO_GRAVES > log.txt +++GUI application+++ qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted pi@rmob:~/echoes $
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - gmbertani - 2022-07-27
        
        Sorry for asking again but you didn't answer: are you working on RPI thru a direct connection to graphic console, i.e. you have a HDMI monitor and USB keyboard plugged in the RPI or are you acceding it remotely through a SSH terminal and a X server on yourPC?
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Laszlo Balogh - 2022-07-27
        
        Ah sorry, i forgot it to answer.
        No, i use it remotely through VNC, but also have SSH access to it. No monitor, mouse or keyboard is attached directly to the RPi. Only PSU, LAN cable and the dongle is attached (to USB 3 slot... maybe i should replug it to USB 2 slot?).
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-27

Bingo!
I loaded your rts in my RPI3 and the problem appeared also here.
Essentially, AUTO_GRAVES.rts works on a PC but besides the interval speed there is also another parameter that must be changed: under Preferences, you should uncheck "Use direct buffers when available" - that option is good for PC only

Giuseppe

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-27
  
  And YESSSS! That was the problem! Echoes is running now, and receiving datas.
  
  And now the next question. :) How can i upload the hits to the RMOB site? Like it was in Windows with Spectrumlab.
  
  echoes_ok.jpg
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

gmbertani - 2022-07-27

How can i upload the hits to the RMOB site?

Sincerely I never did before so I don't know exactly what kind of data format RMOB expects.

Echoes collects the daily counts in a CSV file called daily_<config name="">.csv, in my case
daily_AUTO_GRAVES.csv (attached). There, day by day and hour by hour are collected the complessive events counts, that is split in overdense, underdense and fakes.
This file gets updated once a day and the maximum number of days it can store depends of the parameter "data lasting" under Preferences. </config>

When the maximum number of days has been reached, an automatic report HTML is generated and along with a colorgramme-like diagram where the counts displayed are the overdense+underdense (fakes aren't included). More details and pics can be found in the manual.
I attached also my fixed rts file, where I set to zero the event joining time, since I recently found a bug about that and enabled the help balloons - at the beginning they are useful but after some time you'll disable them again - I won't be offended :)

Giuseppe

AUTO_GRAVES_MCLL.rts

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Laszlo Balogh - 2022-07-27
  
  I loaded the rts file modified by you previously, and get the following picture. Its like the level is too low. Or is it okay?
  
  echoes_ok2.jpg
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - gmbertani - 2022-07-27
    
    yes I simply set the zoom to 1 to let you see all the 5 tracks in the historic graph, at right. If you increment the zoom slider, one or more tracks can go out from the viewport and you should operate on offset slider to see them again.
    Giuseppe
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Laszlo Balogh - 2022-07-29

So, echoes is now running, but till now there are no hits. Here my current settings, maybe you can see something why. Antenna and dongle is ok, connections ok.

AUTO_GRAVES_MCLL2.rts.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Echoes 0.50-1 on Raspberry Pi4B "Mismatched dongle" error

Echoes is a radio spectral analysis software for SDR devices

Forums

Help

Echoes 0.50-1 on Raspberry Pi4B "Mismatched dongle" error

Echoes 0.50-1 on Raspberry Pi4B "Mismatched dongle" error

Echoes is a radio spectral analysis software for SDR devices

Forums

Help

Echoes 0.50-1 on Raspberry Pi4B "Mismatched dongle" error document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Echoes 0.50-1 on Raspberry Pi4B "Mismatched dongle" error