I have changed the driver for the NESDR Smart dongle using Zadig successfully I think, Then downloaded the Echoes software. All seemed fine.
With the dongle inserted (with no cable or antenna connected) in the laptop I started Echoes. The Console window opens with the message +++GUI application+++ Log level4
The devices window and the Waterfall both are also open.
However when I look in the Devices window the only device indicated is 1. Test Patterns
Clicking start and the waterfall produces lines of data
Should I be seeing the NESDR in the Device window? Any help appreciated
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When you check the plugged-in USB devices in Windows system tray, your NESDR should be listed and the same name you should see listed in the Echoes device window.
Could you please
1- re-run Zadig (version 2.5 the latest) -
2-check the options "advanced mode" and "list all devices"
3-reinstall the device
4-press save log and send me the file - it's quite short so you can copy and paste its content directly answering this message.
Take the latest package that suites your machine, 32 or 64 bit
These utilities are based on the same librtlsdr library used by Echoes. In this way we can understand better what is causing problems. There is a very simple utility called "rtl_test" that can be run from command line.
If that program runs, it means that Zadig drivers have been correctly installed so the problem is in Echoes. Looking forward for your feedback
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I followed your feedback and re-installed the driver again and the log is
attached. I also ran the osmocom utility as you suggested and the screen
shot of the result is also attached. Look forward to hearing from you in
due course.
When you check the plugged-in USB devices in Windows system tray, your
NESDR should be listed and the same name you should see listed in the
Echoes device window.
Could you please
1- re-run Zadig (version 2.5 the latest) -
2-check the options "advanced mode" and "list all devices"
3-reinstall the device
4-press save log and send me the file - it's quite short so you can copy
and paste its content directly answering this message.
Take the latest package that suites your machine, 32 or 64 bit
These utilities are based on the same librtlsdr library used by Echoes. In
this way we can understand better what is causing problems. There is a very
simple utility called "rtl_test" that can be run from command line.
If that program runs, it means that Zadig drivers have been correctly
installed so the problem is in Echoes. Looking forward for your feedback
the driver must be ok, our rtl_test outputs look similar.
The next step is to prepare a simple batch file with the following content:
cd \"program files"\GABB\echoescmd /k "echoes -v -n4"
in this way you start echoes and enable a verbose log output that ends in a file
named echoes.log . The file is placed in the following directory
C:\users\*your-user*\echoes\echoes.log
start the batch file and try clicking on the Device control, just to check if you
still see only the test device. Then press Exit and send me echoes.log.
I hope this will be enough to let me understand what's happening.
In 0.27 the code behind the Device control has been partially rewritten and might
be you found a new bug.
If you like, in the meantime you could try to install the older release,
the 0.26 because it has been released about 18 months ago and nobody reported
about dongles not recognized (except a user who tried to connect an AirSpy dongle
that is not a plain RTL-SDR).
Thanks for your patience.
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the driver must be ok, our rtl_test outputs look similar.
The next step is to prepare a simple batch file with the following content:
cd \"program files"\GABB\echoescmd /k "echoes -v -n4"
in this way you start echoes and enable a verbose log output that ends in
a file
named echoes.log . The file is placed in the following directory
C:\users*your-user*\echoes\echoes.log
start the batch file and try clicking on the Device control, just to
check if you
still see only the test device. Then press Exit and send me echoes.log.
I hope this will be enough to let me understand what's happening.
In 0.27 the code behind the Device control has been partially rewritten
and might
be you found a new bug.
If you like, in the meantime you could try to install the older release,
the 0.26 because it has been released about 18 months ago and nobody
reported
about dongles not recognized (except a user who tried to connect an AirSpy dongle
that is not a plain RTL-SDR).
I tried to attach the file but sourceforge refuses the attachment of executable files for safety purposes, so I had to attach it with a different name. Get this file and save it on your desktop, then rename it as ECHOES.BAT
I tried to attach the file but sourceforge refuses the attachment of
executable files for safety purposes, so I had to attach it with a
different name. Get this file and save it on your desktop, then rename it
as ECHOES.BAT
I understood what's happening.
The rtl_sdr library linked into Echoes is 2 years old and your NESDR was not supported, but we're sure now it is, because rtl_test works.
So it makes no sense to try with rel.0.26 since the rtl_sdr library is the same.
I plan to release the fix within a couple of weeks. There are also 2 other bugs I fixed (see Known Bugs in Discussions) and are waiting for release.
Thank you
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi GiuseppeI now have Echoes running with the dongle connected to an
aerial, it seems to be working as different frequencies give different
traces. Just a couple of issues. Under Output, no options are given for
setting the Acquisition Mode, see attached screen shot. Am I missing
something? Secondly, if I want reports presumably I need to download
GNUPLOT? Currently if I enable this in the Main Window, the programme
crashes.
I tried to attach the file but sourceforge refuses the attachment of
executable files for safety purposes, so I had to attach it with a
different name. Get this file and save it on your desktop, then rename it
as ECHOES.BAT
The default window size is wrong - it will be fixed. You can simply enlarge vertically the window and the output controls will appear.
GNUplot is NOT essemptial. You can produce the report even without GNUplot. Anyway, if you check the box to generate GNUplot output, the program will produce a data file for each shot. These files can be later rendered with GNUplot or other data plotting program (i.e. Matlab, Veusz etc.)
You should be careful about disk space because data files tend to take lot of space, depending of the data dump coverage you set. The longer this value, the bigger will be the dat file. And in continuous mode, the dat file grows until you stop the acquisition.
The crash you experimented can be replied? if yes, could send me the default.rts file?
C:/Users/celan/echoes/default.rts
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many thanks Giuseppe, apologies for the question, with such a simple
answer. Followed your suggestion to stretch the box and the options
appeared. Now set to Auto to only produce plots when something detected.
Also when I clicked on gnuplot this time program did not crash. Hope to set
up tomorrow and hope for a meteor in the near future. Very many thanks yet
again. Best wishes Alec
The default window size is wrong - it will be fixed. You can simply
enlarge vertically the window and the output controls will appear.
2.
GNUplot is NOT essemptial. You can produce the report even without
GNUplot. Anyway, if you check the box to generate GNUplot output, the
program will produce a data file for each shot. These files can be later
rendered with GNUplot or other data plotting program (i.e. Matlab, Veusz
etc.)
You should be careful about disk space because data files tend to take lot
of space, depending of the data dump coverage you set. The longer this
value, the bigger will be the dat file. And in continuous mode, the dat
file grows until you stop the acquisition.
The crash you experimented can be replied? if yes, could send me the
default.rts file?
1- In Device tab, set the minimum sample rate (226000), Tune frequency about 10khz away from 143.050.000, let's say 143.040.000 or 134.060.000 and maximum gain 49
2-In FFT, check downsampler bypass and resolution 32768 or higher (the higher you set, the slower will be the waterfall)
3-in Output tab, set PERIODIC mode, set 100ms of refresh interval , set a nonzero value as stop after, say 1000, both thresholds to zero and dump data coverage set to 30sec (no matter if you use GNUplot or not, in periodic mode this field indicates the time between sequential shots).
4-in waterfall window, set Freq. zoom at about 10khz and Freq.offset to +/-10khz depending of your tune frequency, to reach the Central freq of 143.050.000.
Start the acquisition and wait about a minute to read the waterfall coverage on waterfall window.
Stop the acquisition and set the number of seconds of waterfall coverage in dump data coverage
In this way the program will produce sequential screenshots. If data dump coverage is 30s it means 120 shots per hour. If you run it for at least a couple of hours you should be able to catch at least some sporadic events and see their noise N and peak S levels, these data will be useful later to set in AUTOMATIC mode the appropriate thresholds for your station.
Good luck,
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1- In Device tab, set the minimum sample rate (226000), Tune
frequency about 10khz away from 143.050.000, let's say 143.040.000 or
134.060.000 and maximum gain 49
2-In FFT, check downsampler bypass and resolution 32768 or higher
(the higher you set, the slower will be the waterfall)
3-in Output tab, set PERIODIC mode, set 100ms of refresh interval , set
a nonzero value as stop after, say 1000, both thresholds to zero and dump
data coverage set to 30sec (no matter if you use GNUplot or not, in
periodic mode this field indicates the time between sequential shots).
4-in waterfall window, set Freq. zoom at about 10khz and Freq.offset
to +/-10khz depending of your tune frequency, to reach the Central freq
of 143.050.000.
Start the acquisition and wait about a minute to read the waterfall
coverage on waterfall window.
Stop the acquisition and set the number of seconds of waterfall coverage
in dump data coverage
In this way the program will produce sequential screenshots. If data
dump coverage is 30s it means 120 shots per hour. If you run it for at
least a couple of hours you should be able to catch at least some sporadic
events and see their noise N and peak S levels, these data will be useful
later to set in AUTOMATIC mode the appropriate thresholds for your station.
Hi Giuseppe Apologies for having to come back again. Followed your
instructions, but probably got it wrong. Waterfall is running and saving a
dump every 40 sec. But the screen looks odd, not sure why, obviously I have
something wrong? See attached screenshot.
Regards Alec
1- In Device tab, set the minimum sample rate (226000), Tune
frequency about 10khz away from 143.050.000, let's say 143.040.000 or
134.060.000 and maximum gain 49
2-In FFT, check downsampler bypass and resolution 32768 or higher
(the higher you set, the slower will be the waterfall)
3-in Output tab, set PERIODIC mode, set 100ms of refresh interval , set
a nonzero value as stop after, say 1000, both thresholds to zero and dump
data coverage set to 30sec (no matter if you use GNUplot or not, in
periodic mode this field indicates the time between sequential shots).
4-in waterfall window, set Freq. zoom at about 10khz and Freq.offset
to +/-10khz depending of your tune frequency, to reach the Central freq
of 143.050.000.
Start the acquisition and wait about a minute to read the waterfall
coverage on waterfall window.
Stop the acquisition and set the number of seconds of waterfall coverage
in dump data coverage
In this way the program will produce sequential screenshots. If data
dump coverage is 30s it means 120 shots per hour. If you run it for at
least a couple of hours you should be able to catch at least some sporadic
events and see their noise N and peak S levels, these data will be useful
later to set in AUTOMATIC mode the appropriate thresholds for your station.
Hi alec,
take a look on FFT tab, you have a resolution of only 8 points, too low. Press the minus button to shrink the point's size, increasing the nunber of points. It should be at least 16384 for the settings I suggested
Giuseppe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Giuseppe, I mistook your info, and set the resolution Hz at the high
figure and not the FTT points. Now reset and the window looks better. It
must seem worse than teaching a child, dealing with me! I have the set up
now running and hope to see a blip or two.
Best wishes
Alec
Hi alec,
take a look on FFT tab, you have a resolution of only 8 points, too low.
Press the minus button to shrink the point's size, increasing the nunber of
points. It should be at least 16384 for the settings I suggested
Giuseppe
Evening Giuseppe. Made the changes and ran for over 300 pages of the
waterfall, but alas nothing was seen on the recording. Hopefully due to
there being no activity. Screenshot attached. One thing I noticed was that
each of the dumped waterfall images had the same time stamp on them, is
this normal? They did each have a separate individual image number.
Hi alec,
take a look on FFT tab, you have a resolution of only 8 points, too low.
Press the minus button to shrink the point's size, increasing the nunber of
points. It should be at least 16384 for the settings I suggested
Giuseppe
1-the central frequency should be 143050000, you are 1650hz out. Since there are no relevant meteor showers in this period, most of echoes are quite small and not frequent.
Just to give you a taste of numbers, today since midnight my station catched 53 events and my antenna is pointed quite badly because is out of a window looking the south, while for my position on the earth (near Milan) the best would be point toward west/southwest.
A friend who helped me testing Echoes in a station out in the country closer to France, can catch about 150-200 events per day (without showers) hah... I envy him! :D
2-The waterfall completely blue. Did you try to increase brightness and contrast? Your image doesn't show those sliders. Take a look of my two screenshots and try to set the same values. Otherwise send me the rts file so I can take a look.
Hi Giuseppe, good that the problem has been found and can be sorted. Presumably I wait until you confirm that you have released the fix?
Thanks for your efforts and patience.
Alec
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I need the USB identifier number of your NESDR. You can find it by left-clicking on Windows start button and launching the "Device manager" as showed in the attached screenshot, where the red box indicates the number I'm interested in.
The NESDR device should be listed under "USB devices" when it's plugged in.
Right-click on the device to display the popup menu and click "Properties" to show the number.
The number is in fact composed by a 4-digits pair, called VID and PID separed by ampersand. It's a hexadecimal number so besides 0..9 there are letters from A to F. My number is 0BDA 2832.
I expect your number is different from mine, otherwise it means Echoes is going nuts for a different reason than the one I tought.
Hi Giuseppe, sorry about the delay getting back to you.
had a look and the dongle gives 2 items under USB (simply called Bulk-In,
Interface) see attached. I have copied the Driver properties info for each.
I think they are identical.
Hope this helps
Regards
Alec
I need the USB identifier number of your NESDR. You can find it by
left-clicking on Windows start button and launching the "Device manager" as
showed in the attached screenshot, where the red box indicates the number
I'm interested in.
The NESDR device should be listed under "USB devices" when it's plugged
in.
Right-click on the device to display the popup menu and click "Properties"
to show the number.
The number is in fact composed by a 4-digits pair, called VID and PID
separed by ampersand. It's a hexadecimal number so besides 0..9 there are
letters from A to F. My number is 0BDA 2832.
I expect your number is different from mine, otherwise it means Echoes is
going nuts for a different reason than the one I tought.
Mmmm.... your VID/PID are the same of my R820T dongles (I have three R820T and a Terratec E4000) so the problem should not be due to librtlsdr version.
Instead, I've found a bug in the dongle detection code. I'm not sure if it causes the problem you found, but anyway I generated a pre-0.28 that fixes that bug and the other two listed in KNOWN_BUGS topic.
Excellent, Echoes can now see the dongle. Very many thanks for all your
efforts and patience in dealing with a newbie. The next issue I have of
course is to get some sort of understanding of how to get Echoes working!
I have looked through the user manual and understand bits and pieces, but
it is a steep learning curve. Is there a crib sheet to simply set Echoes
up to get signals from the Graves transmitter?
Thanks ever so much for your efforts.
Take care
Alec
Mmmm.... your VID/PID are the same of my R820T dongles (I have three R820T
and a Terratec E4000) so the problem should not be due to librtlsdr version.
Instead, I've found a bug in the dongle detection code. I'm not sure if it
causes the problem you found, but anyway I generated a pre-0.28 that fixes
that bug and the other two listed in KNOWN_BUGS topic.
Hi Giuseppe !
I'm Marta a new subscriber in this forum.
I recently installed Echoes but I have a problem.
When I open Echoes software, I attach my SDR to the USB connection and when I start to run echoes, it doesn't detect any SDR. I see a message saying that echoes cannot detect the SDR.
I use ubuntu studio on Linux and I'm using SDR (HackRF One).
I want to use echoes for my sound project, detection of meteor echoes with the use of Graves radar.
Could you please help me with this issue ? ? what can I do?
I started a few months ago to use SDR and I'm super new to using Echoes software.
Also any PDF version of a manual ,how to use Echoes for beginners ?
Thanks for your help,
Best Marta
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi as a complete newbie, need help already.
I have changed the driver for the NESDR Smart dongle using Zadig successfully I think, Then downloaded the Echoes software. All seemed fine.
With the dongle inserted (with no cable or antenna connected) in the laptop I started Echoes. The Console window opens with the message +++GUI application+++ Log level4
The devices window and the Waterfall both are also open.
However when I look in the Devices window the only device indicated is 1. Test Patterns
Clicking start and the waterfall produces lines of data
Should I be seeing the NESDR in the Device window? Any help appreciated
Hi Alec,
yes you should see a rtl-sdr device .
When you check the plugged-in USB devices in Windows system tray, your NESDR should be listed and the same name you should see listed in the Echoes device window.
Could you please
1- re-run Zadig (version 2.5 the latest) -
2-check the options "advanced mode" and "list all devices"
3-reinstall the device
4-press save log and send me the file - it's quite short so you can copy and paste its content directly answering this message.
another thing you can do is to test your dongle with the rtl_sdr windows utilities from osmocom
https://ftp.osmocom.org/binaries/windows/rtl-sdr/
Take the latest package that suites your machine, 32 or 64 bit
These utilities are based on the same librtlsdr library used by Echoes. In this way we can understand better what is causing problems. There is a very simple utility called "rtl_test" that can be run from command line.
If that program runs, it means that Zadig drivers have been correctly installed so the problem is in Echoes. Looking forward for your feedback
Giuseppe
Afternoon Giuseppi, thanks for your feedback.
I followed your feedback and re-installed the driver again and the log is
attached. I also ran the osmocom utility as you suggested and the screen
shot of the result is also attached. Look forward to hearing from you in
due course.
Best regards
Alec
On Tue, 23 Feb 2021 at 12:38, gmbertani gmbertani@users.sourceforge.net
wrote:
Hi Alec
the driver must be ok, our rtl_test outputs look similar.
The next step is to prepare a simple batch file with the following content:
in this way you start echoes and enable a verbose log output that ends in a file
named echoes.log . The file is placed in the following directory
C:\users\*your-user*\echoes\echoes.logstart the batch file and try clicking on the Device control, just to check if you
still see only the test device. Then press Exit and send me echoes.log.
I hope this will be enough to let me understand what's happening.
In 0.27 the code behind the Device control has been partially rewritten and might
be you found a new bug.
If you like, in the meantime you could try to install the older release,
the 0.26 because it has been released about 18 months ago and nobody reported
about dongles not recognized (except a user who tried to connect an AirSpy dongle
that is not a plain RTL-SDR).
Thanks for your patience.
Giuseppe
Giuseppe I'm not too computer savvy, can you explain simply how I make a
batch file?
Regards Alec
On Tue, 23 Feb 2021, 21:02 gmbertani, gmbertani@users.sourceforge.net
wrote:
I tried to attach the file but sourceforge refuses the attachment of executable files for safety purposes, so I had to attach it with a different name. Get this file and save it on your desktop, then rename it as ECHOES.BAT
Morning Giuseppe, Tried to follow your instructions. Well out of my comfort
zone here!
Hopefully the file I have attached is what is required. Many thanks for
your patience.
Best wishes Alec
On Tue, 23 Feb 2021 at 23:00, gmbertani gmbertani@users.sourceforge.net
wrote:
Hi Alec,
I understood what's happening.
The rtl_sdr library linked into Echoes is 2 years old and your NESDR was not supported, but we're sure now it is, because rtl_test works.
So it makes no sense to try with rel.0.26 since the rtl_sdr library is the same.
I plan to release the fix within a couple of weeks. There are also 2 other bugs I fixed (see Known Bugs in Discussions) and are waiting for release.
Thank you
Giuseppe
Hi GiuseppeI now have Echoes running with the dongle connected to an
aerial, it seems to be working as different frequencies give different
traces. Just a couple of issues. Under Output, no options are given for
setting the Acquisition Mode, see attached screen shot. Am I missing
something? Secondly, if I want reports presumably I need to download
GNUPLOT? Currently if I enable this in the Main Window, the programme
crashes.
Thanks for your help, kind regards
Alec
On Tue, 23 Feb 2021 at 23:00, gmbertani gmbertani@users.sourceforge.net
wrote:
Hi Alec,
The default window size is wrong - it will be fixed. You can simply enlarge vertically the window and the output controls will appear.
GNUplot is NOT essemptial. You can produce the report even without GNUplot. Anyway, if you check the box to generate GNUplot output, the program will produce a data file for each shot. These files can be later rendered with GNUplot or other data plotting program (i.e. Matlab, Veusz etc.)
You should be careful about disk space because data files tend to take lot of space, depending of the data dump coverage you set. The longer this value, the bigger will be the dat file. And in continuous mode, the dat file grows until you stop the acquisition.
The crash you experimented can be replied? if yes, could send me the default.rts file?
C:/Users/celan/echoes/default.rtsGiuseppe
Many thanks Giuseppe, apologies for the question, with such a simple
answer. Followed your suggestion to stretch the box and the options
appeared. Now set to Auto to only produce plots when something detected.
Also when I clicked on gnuplot this time program did not crash. Hope to set
up tomorrow and hope for a meteor in the near future. Very many thanks yet
again. Best wishes Alec
On Sun, 28 Feb 2021, 22:07 gmbertani, gmbertani@users.sourceforge.net
wrote:
Hi Alec,
To start with GRAVES you should:
1- In Device tab, set the minimum sample rate (226000), Tune frequency about 10khz away from 143.050.000, let's say 143.040.000 or 134.060.000 and maximum gain 49
2-In FFT, check downsampler bypass and resolution 32768 or higher (the higher you set, the slower will be the waterfall)
3-in Output tab, set PERIODIC mode, set 100ms of refresh interval , set a nonzero value as stop after, say 1000, both thresholds to zero and dump data coverage set to 30sec (no matter if you use GNUplot or not, in periodic mode this field indicates the time between sequential shots).
4-in waterfall window, set Freq. zoom at about 10khz and Freq.offset to +/-10khz depending of your tune frequency, to reach the Central freq of 143.050.000.
Start the acquisition and wait about a minute to read the waterfall coverage on waterfall window.
Stop the acquisition and set the number of seconds of waterfall coverage in dump data coverage
In this way the program will produce sequential screenshots. If data dump coverage is 30s it means 120 shots per hour. If you run it for at least a couple of hours you should be able to catch at least some sporadic events and see their noise N and peak S levels, these data will be useful later to set in AUTOMATIC mode the appropriate thresholds for your station.
Good luck,
Giuseppe
Many thanks Giuseppe for all your help and suggestions. I will let you know
how it goes. Best wishes Alec
On Mon, 1 Mar 2021, 06:53 gmbertani, gmbertani@users.sourceforge.net
wrote:
Hi Giuseppe Apologies for having to come back again. Followed your
instructions, but probably got it wrong. Waterfall is running and saving a
dump every 40 sec. But the screen looks odd, not sure why, obviously I have
something wrong? See attached screenshot.
Regards Alec
On Mon, 1 Mar 2021 at 06:53, gmbertani gmbertani@users.sourceforge.net
wrote:
Hi alec,
take a look on FFT tab, you have a resolution of only 8 points, too low. Press the minus button to shrink the point's size, increasing the nunber of points. It should be at least 16384 for the settings I suggested
Giuseppe
Thanks Giuseppe, I mistook your info, and set the resolution Hz at the high
figure and not the FTT points. Now reset and the window looks better. It
must seem worse than teaching a child, dealing with me! I have the set up
now running and hope to see a blip or two.
Best wishes
Alec
On Mon, 1 Mar 2021 at 14:17, gmbertani gmbertani@users.sourceforge.net
wrote:
Evening Giuseppe. Made the changes and ran for over 300 pages of the
waterfall, but alas nothing was seen on the recording. Hopefully due to
there being no activity. Screenshot attached. One thing I noticed was that
each of the dumped waterfall images had the same time stamp on them, is
this normal? They did each have a separate individual image number.
Getting there slowly, thanks for your efforts
Regards Alec
On Mon, 1 Mar 2021 at 14:17, gmbertani gmbertani@users.sourceforge.net
wrote:
Hi Alec,
1-the central frequency should be 143050000, you are 1650hz out. Since there are no relevant meteor showers in this period, most of echoes are quite small and not frequent.
Just to give you a taste of numbers, today since midnight my station catched 53 events and my antenna is pointed quite badly because is out of a window looking the south, while for my position on the earth (near Milan) the best would be point toward west/southwest.
A friend who helped me testing Echoes in a station out in the country closer to France, can catch about 150-200 events per day (without showers) hah... I envy him! :D
2-The waterfall completely blue. Did you try to increase brightness and contrast? Your image doesn't show those sliders. Take a look of my two screenshots and try to set the same values. Otherwise send me the rts file so I can take a look.
Giuseppe
Last edit: gmbertani 2021-03-01
This is the output of rtl_test on my pc, with dongle connected:
Hi Giuseppe, good that the problem has been found and can be sorted. Presumably I wait until you confirm that you have released the fix?
Thanks for your efforts and patience.
Alec
Could I ask for another information?
I need the USB identifier number of your NESDR. You can find it by left-clicking on Windows start button and launching the "Device manager" as showed in the attached screenshot, where the red box indicates the number I'm interested in.
The NESDR device should be listed under "USB devices" when it's plugged in.
Right-click on the device to display the popup menu and click "Properties" to show the number.
The number is in fact composed by a 4-digits pair, called VID and PID separed by ampersand. It's a hexadecimal number so besides 0..9 there are letters from A to F. My number is 0BDA 2832.
I expect your number is different from mine, otherwise it means Echoes is going nuts for a different reason than the one I tought.
Cordially
Giuseppe
Hi Giuseppe, sorry about the delay getting back to you.
had a look and the dongle gives 2 items under USB (simply called Bulk-In,
Interface) see attached. I have copied the Driver properties info for each.
I think they are identical.
Hope this helps
Regards
Alec
On Wed, 24 Feb 2021 at 22:06, gmbertani gmbertani@users.sourceforge.net
wrote:
Mmmm.... your VID/PID are the same of my R820T dongles (I have three R820T and a Terratec E4000) so the problem should not be due to librtlsdr version.
Instead, I've found a bug in the dongle detection code. I'm not sure if it causes the problem you found, but anyway I generated a pre-0.28 that fixes that bug and the other two listed in KNOWN_BUGS topic.
https://drive.google.com/file/d/1ZUzLTT6hbuvNK_EO5Ced8rn3Ma7yGTaP/view?usp=sharing
this is the link to my google drive. Let me know if it works, and I'll publish it as 0.28 official
Thanks
Giuseppe
Morning Giuseppi
Excellent, Echoes can now see the dongle. Very many thanks for all your
efforts and patience in dealing with a newbie. The next issue I have of
course is to get some sort of understanding of how to get Echoes working!
I have looked through the user manual and understand bits and pieces, but
it is a steep learning curve. Is there a crib sheet to simply set Echoes
up to get signals from the Graves transmitter?
Thanks ever so much for your efforts.
Take care
Alec
On Sat, 27 Feb 2021 at 08:07, gmbertani gmbertani@users.sourceforge.net
wrote:
Hi Giuseppe !
I'm Marta a new subscriber in this forum.
I recently installed Echoes but I have a problem.
When I open Echoes software, I attach my SDR to the USB connection and when I start to run echoes, it doesn't detect any SDR. I see a message saying that echoes cannot detect the SDR.
I use ubuntu studio on Linux and I'm using SDR (HackRF One).
I want to use echoes for my sound project, detection of meteor echoes with the use of Graves radar.
Could you please help me with this issue ? ? what can I do?
I started a few months ago to use SDR and I'm super new to using Echoes software.
Also any PDF version of a manual ,how to use Echoes for beginners ?
Thanks for your help,
Best Marta