Echoes: An RTL-SDR Tool for Meteor Scatter Detection
Thanks to "gmbertani" for letting us know about his recently released RTL-SDR compatible software called "Echoes". Echoes is a Windows, Linux and Raspberry Pi/Arch compatible tool that can be used together with an RTL-SDR and appropriate antenna to monitor for meteor scatter detections.
Meteor scatter works by receiving a distant but powerful transmitter via signal reflections off the trails of ionized air that meteors leave behind when they enter the atmosphere. Normally the transmitter would be too far away to receive, but if its able to bounce off the ionized trail in the sky it can reach far over the horizon to your receiver. Typically powerful broadcast FM radio stations, analog TV, and radar signals at around 140 MHz are used. By listening to these signal blips it can be possible to estimate the number of meteors falling.
Below we paste the official description and feature list of Echoes, and at the end is a video demonstrating Echoes in action:
Echoes it's a radio spectral analysis software for RTL-SDR devices, designed for meteor scattering purposes.
Echoes doesn't demodulate neither decode any human-made signal. Its main goal is to analyze and record the total power of natural signals and generate screenshots and tabular data (CSV, GNUplot) output in presence of particular peaks in a selected narrow range of frequencies. Since there is no demodulation, there is no provision for audio listening, except for a notify sound when an event has been recorded.
Features
- Captures waterfall spectra as PNG screenshots and statistics data files.
- Optionally generates GNUplot data files
- Multiple instances can manage separate dongles plugged in the same computer
- Three operating modes: continuos (records data only), periodic (captures data and screenshot every X seconds) and automatic (record data and screeshot each time a customizable (S-N) treshold is exceeded)
- HTML report production
- Installers ready for Windows7++ and RPMs / SRPMs for Linux
- xz binary package for Raspberry PI / Arch distro
- It can run headless, recording GNUplot and statistic data only
Max,
Are you still updating the software?
If so, are you open to some paid support to help me get setup and understand properly how to configure, what equipment works best and find a proper location to use this against in USA.
Hi Trevor,
sure. Latest release is 0.32 available
Being located in Italy, I couldn’t help you much in finding good radio sources for meteor scatter. You should find help from local radio amateurs. For any other question about the program
click at the project “discussion” tab. There is also a Facebook page (search for [email protected]) so you can write me messages. Please use one of these ways to ask further questions about the project,
thank you!
PS: on SourceForge there is also the updated manual, click on the “Wiki” tab.
Cordially
I definitely should never use html in these messages :s
Very new to this. Have made a DIY aerial and want to track meteors via Graves. I have purchased a NESDR SMArt v4 SDR and hope to use Echoes to capture and display results. Grateful if someone can give me a step by step guide on how to get this running on my laptop running Windows 10.
PS I am not anything approaching an expert on PCs and software, so a simple explanation would be welcome.
Thanks Al
Hi Alec,
This is a quickstart guide about the latest release of the software – 0.27 – that has been released yesterday, so take the newest binary before all.
1-The first step is install the Zadig driver as explained .
This step is common also for many other windows-based sdr receiver softwares around (HDSDR, SDR# etc…)
so you can find also videos explaining how to do that.
2-Once the driver is installed and the NESDR is plugged in, click on the Echoes desktop icon to start the program.
3-Click to load a sample configuration file, for instance c:\program files\gabb\echoes\TEST_CONTINUOUS.rts.
4-Press the Start button to make the waterfall flow.
Please note:
a-the program runs even without dongle plugged in, when a virtual device called TEST PATTERNS generates some noise
and peaks for software testing purposes. If your dongle has been detected, the DEVICE box in the little window should
display a test containing RTL SDR and various other letters and numbers.
Otherwise what yoy’re watching doesn’t come from your dongle!
b-each time you change the sample rate or the bandwidth, the waterfall view is restored to the default zoom value (1=no zoom)
and the tuned frequency is at the center of waterfall, resulting in a strong vertical line in the center of the spectra.
That line is the DC component of the spectra and its peak power is always 0 dBfs. In the sample configuration files, there is
always some amount of zoom and offset in order to slide that DC-peak away from the screen. For this reason, the tuned frequency
should be set some kHz above or below the interested frequency range.
c-please read the online wiki and ask further questions in the discussion forum
, thanks.
Giuseppe Massimo Bertani
(REPOST)
Hi Alec,
This is a quickstart guide about the latest release of the software – 0.27 – that has been released yesterday, so take the newest binary before all.
1-The first step is install the Zadig driver as explained here: https://sourceforge.net/p/echoes/wiki/install.md
This step is common also for many other windows-based sdr receiver softwares around (HDSDR, SDR# etc…)
so you can find also videos explaining how to do that.
2-Once the driver is installed and the NESDR is plugged in, click on the Echoes desktop icon to start the program.
3-Click to load a sample configuration file, for instance c:\program files\gabb\echoes\TEST_CONTINUOUS.rts.
4-Press the Start button to make the waterfall flow.
Please note:
a-the program runs even without dongle plugged in, when a virtual device called TEST PATTERNS generates some noise
and peaks for software testing purposes. If your dongle has been detected, the DEVICE box in the little window should
display a test containing RTL SDR and various other letters and numbers.
Otherwise what yoy’re watching doesn’t come from your dongle!
b-each time you change the sample rate or the bandwidth, the waterfall view is restored to the default zoom value (1=no zoom)
and the tuned frequency is at the center of waterfall, resulting in a strong vertical line in the center of the spectra.
That line is the DC component of the spectra and its peak power is always 0 dBfs. In the sample configuration files, there is
always some amount of zoom and offset in order to slide that DC-peak away from the screen. For this reason, the tuned frequency
should be set some kHz above or below the interested frequency range.
c-please read the online wikihttps://sourceforge.net/p/echoes/wiki/main.md and ask further questions in the discussion forum
https://sourceforge.net/p/echoes/discussion (choose a topic) thanks.
cordially GMB
Does Echoes work with the Funcube Pro+ dongle? (under Windows 10)
I have downloaded Echoes and it doesn’t see the Funcube
Sorry Alastair,
Echoes is based on librtlsdr.
The librtlsdr is for RTL2832U based DVB-T dongles. The Funcube Dongle has no RTL2832U chip.
OK thanks – I should probably have realised this!
Echoes does look interesting and I might give it a try with one of my spare 2832 based SDR dongles.
Good day
I am using a i7 and Win7 64bit, when I run Echoes I get a error that the PLL is not locked. I am using a 820T2 and a
NEW GEN RTL2832 with the 828 tuner. Both dongles gives me the same error, then I can use any other SDR software and both dongles work fine.
Any one that can help me.
Regards
Danie
Hi Danie,
Echoes uses librtlsdr to interface the dongle and that message is produced by that .
I always see that message when I start my program but it still works despite that. Maybe your don’t?
I just tried now, this is what I get when I start Echoes, in the console window:
————————————-
echoes(17:29:37)Info: Main thread:0x54b36e0 Reinitializing radio…
echoes(17:29:37)Info: Main thread:0x54b36e0 Found 1 device(s):
echoes(17:29:37)Info: Main thread:0x54b36e0 “0: Realtek RTL2838UHIDIR SN: 00000001”
echoes(17:29:37)Info: Main thread:0x54b36e0
echoes(17:29:37)Info: Main thread:0x54b36e0 Opening device “0: Realtek RTL2838UHIDIR SN: 00000001” :
echoes(17:29:37)Info: Main thread:0x54b36e0 Generic RTL2832U OEM
Found Rafael Micro R820T tuner
echoes(17:29:37)Info: Main thread:0x54b36e0 Opening successful.
echoes(17:29:37)Info: Main thread:0x54b36e0 AGC turned off.
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked! <===========
echoes(17:29:37)Info: Main thread:0x54b36e0 Sample rate set to 250000 Hz
echoes(17:29:37)Info: Main thread:0x54b36e0 FFT flags: 64
echoes(17:29:37)Info: Main thread:0x54b36e0 Window set to RECTANGLE
—————
so, if you see the program not working, it should be caused by something other, the "PLL not Locked" message is distracting you from finding the real problem.
Cordially
Giuseppe
Hi Giuseppe
This is all I get in the console window.
Log level: 4Found Rafael Micro R828D tuner
[R82XX] PLL not locked!
Danie
I get the same thing (PLL not locked) for a “R820T” Tuner. Is this a fatal error or just a nuisance not affecting desired functionality/operation?
Thanks much – Grant
Issues on startup. I’m using Windows7, I7 8 core, 32GB Ram, SSD 480GB. I have issues when I start up Echoes from a saved config file for my frequency. Everything seems to be OK, real time graph, power graph and water fall but its deaf. I’m using a signal generator to check for a received signal. After the buffer time its still not there. If I load the default settings and change them all to what I need and overwrite my setting file then it works most of the time. I also make sure that collection dates are correct. If I check the hardware using SDR# its working. I’m using the R820T original and now also V3. Great program! I’ve learned a lot. Thanks.
Thanks Luc,
could you explain if you load the .rts file by the means of “open” button or directly, by passing its pathname on the command line?
Cordially
Giuseppe
Sorry about the long delay. I start the program and “open” the .rts file using the program. I found a post that mentions a quirk in the program. Just click on +10KHz then -10KHz to get back to the same frequency and it works fine. Verified. That works every time.
Luc
French meteor scatter
http://www.free-sky.fr/meteor-scatter-graves-radar/
If anyone else is interested I have compiled qt5 for Raspberry pi which I finally got working on my pi 2.
worked for me and I hope it solves a few frustrations for others. This took 4 hours or so to fully compile on my i7 laptop so would have taken long long time on the pi itself
Well, i guess you mean for Raspbian, since I successfully ran the app on PI2 under Arch last spring. I’ve chosen Arch since it was the unique distro at that time that included QT5 and QT5charts. But ok, if you found a way to make it run under Raspbian, I’ll post your link on Echoes discussion forum and its Facebook page.
I’m struggling to get this working on a Raspberry pi in headless mode. This is a pi2 running latest stretch all up to date
I installed the dependencies and QT5 using this script to build https://github.com/chschnell/build-qt5-rpi
$ /usr/bin/console_echoes -c
QXcbConnection: Could not connect to display
Aborted
I rebooted and it ran!
🙂 nice to know. Good luck!
我的电脑是win10 64位系统，为什么无法运行您的软件？
早上好，
目前的图像
是在Linux Opensuse Leap64和Windows 10上制作的。
你能给我更多的细节吗？
这个程序是不是开始，还是收购不起作用？
你有没有安装Zadig驱动程序？
早上好，
目前的图像
https://sourceforge.net/projects/echoes/
是在Linux Opensuse Leap64和Windows 10上制作的。
你能给我更多的细节吗？
这个程序是不是开始，还是收购不起作用？
你有没有安装Zadig驱动程序？
您好，我打开软件后提示我无法打开rtlsdr，“Log level: 4usb_open error -12
critical echoes(0.219)Critical: Main thread:0x32736a0 ERROR: Failed to open rtlsdr device “0: ???\u0006 \u0001 SN: \u0002”
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application’s support team for more information.”
zadig驱动我以安装，SDR#和HDSDR都可以正确运行
昨天另一个人写信告诉我他也有这个问题，试着看看这个页面是否有用：
https://www.rtl-sdr.com/forum/viewtopic.php?f=7&t=1797
参考您发的网页，问题已经解决，谢谢您
Hi Max,
I introduced the periodic mode because it’s the simplest and dumbest way to take screenshots. Simplest because it does not need to set signal thresholds (automatic mode) and dumbest because in this way you record a big amount of data that must be manually selected afterwards. This is also a way to learn about how to set the thresholds for automatic mode.
The “shot x sec after peaks” control (manual fig.8) does exactly what you’re thinking. The best value should be equal to the time coverage of the waterfall minus 1..2.
The time coverage depends on the “time interval” control (see manual fig.7). Increasing this value, the waterfall slows down.
Don’t take in count the “shot duration” control, because it is not about screenshots but about the plot data files.
Thanks for your feedback.
Massimo
Hi Max,
I introduced the periodic mode because it’s the simplest and dumbest way to take screenshots. Simplest because it does not need to set signal thresholds (automatic mode) and dumbest because in this way you record a big amount of data that must be manually selected afterwards. This is also a way to get an idea about how to set the thresholds for automatic mode.
So, the delay you mean – “shot x secs after peaks” (see manual 6.3.4) – must be exactly what you’re asking for. Its best value is equal to the total waterfall coverage in seconds, minus 1..2. Notice that you can increase the refresh interval (6.3.3) to make the waterfall browsing slower.
Remember, the “shot duration” is meaningful only when you record plot files, not screenshots. If you don’t plan to use GNUplot, forget about it.
Thanks for your feedback.
BTW. in future, it’s better mail me directly since I get no notifications if someone writes a comment here. Today I’ve seen your post and the post above almost casually, since I didn’t know yet about the article 🙂
Hi Giuseppe, thanks for the explanation. I write here in case you want to clarify this for the public. For delay in automatic mode I did not mean the shot duration but the delay from the moment when a customizable (S-N) threshold is exceeded and when the recording starts. We want zero delay but some delay is probably caused from both software and hardware.
In other words, when a threshold is reached the portion of the signal before the threshold is not saved but also a portion after the threshold is not saved if the recording is slow to start. The only way is see to avoid this delay is to have a buffer and save the data starting from let’s say 1-2 sec. before the threshold is reached.
uhm… yes I understand, it’s not the shot duration. In the following video,
recorded in December 2017, under Geminids you can see how the automatic mode looks like
(I should rotate it 90° someday… )
Once installed the program, under “c:\program files\GABB\echoes” there is the configuration file (“geminidi 2017.rts”) I used in the video.
The results have been loaded in on GABB’s FB page:
You can see, when the echo appears on the top, nothing seems to happen but the peak has been detected.
The “shots X sec after peaks” has been set to 15sec, so after 15 secs since it started appearing, the echo is about in the middle of the screen and the shot is taken (ping…)
If another echo appears in the meantime, a new timer is started and enqueued, so each peak will get its shot.
In the second half of you message, you probably mean plot data recording, since it has no sense with screenshots.
Data recording works continuously, even when no events are detected. The data records (scans) are stored in a FIFO buffer in memory, its length is fixed and covers the number of seconds specified by “shot duration”; records becoming too old are forgotten. When a new event is detected, the countdown
(“shots X sec after peaks”) starts and when it expires, the screenshot is triggered and the entire content of the FIFO is flushed on disk (.dat files , see manual page 32) so the data loss you said can’t happen since the recording algorythm starts when acquisition starts.
Massimo
what’s wrong in my HTML?? :O
Thank you for the clarification, now everything is clear. I thought that it worked like an audio recorder, starting recording only after a peak as i have seen previous solutions based on the audio. I did not understand that it works like any other SDR software displaying the waterfall continuously. So reading again your previous explanation it is even more clear. As far as concerning the screenshot it does the same thing that we would do standing in front of a pc with a software like SDR#. Very interesting, i am going to test it soon. Thanks for your work!
I am a newbie with SDR, so not sure I fully understand how this ECHOES works.
Does it mean that it only receives reflected waves from GRAVE radar that transmits the waves?
So it receives the waves at the same frequency as the GRAVE radar transmits?
Thank you for for explanation
Hi,
no no, Echoes can be tuned on any frequency supported by your dongle, it’s not GRAVES-centric. The examples in the manual use the GRAVES because in Europe it’s the best source of radar signals for meteor scattering purposes, since it works 24h (except in maintenance stops).
You should find something similar source located at about 1000…3000 km from your site (looking at the hour you wrote your message, it seems you’re somewhere in America) it could be also an analog TV station – if they still exist there – working in VHF bands I..III . Some says that frequencies below 80MHz give the best results, but I only heard about, never checked.
If you contact a radio-amateur club I think they can give you much more help in setting up your station. There is also much material available online.
Thanks for you feedback
Massimo
Regarding the 3 operating modes, i don’t think the periodic one is usable because reflecttions can last from less than 1 sec to more than 20sec but most of them are about 1 sec. only. I would like to understand what is the delay in automatic mode before it starts recording to make sure that very short reflections are not cut significantly at the beginning. However the automatic mode is interesting for particular times of the year with high number of reflections most of them lasting over 2 sec. like the Perseids in August