|
Smart
ways to use SDR Console for FM DXing
jamesf_uk on groups.io: I use console
extensively for FMDX and rely heavily on the RDS logging/database combination.
I've discovered that, when used in DX mode there seems to be a trade-off
between logging weaker decodes and red herrings, if you see what I mean.
When I'm scanning all possible frequencies from an IQ recording I'll end
up with A LOT of spurious decodes which have no match in the database,
these are easy to discount and discard, of course. I filter these out
quickly using "DB Browser for SQLite" which is very good at manipulating
the database entries.
This will leave me with a whole load of "Yes" entries... I've found over
time that most entries which have a PI Code count of less than 3 can also
be discarded, leaving me with a list of what are almost always genuine
decodes. Occasionally I may throw away something genuine but I can cross-check
the recording for audio and it's usually spot on.
Believe me, DB Browser is your friend in these situations and saves a
lot of wading through false decodes to get to the good stuff!
Jim Smith G0OFE on groups.io:I usually
export my RDS logfile to a CSV nd open it in LibreOffice Calc.It's easy
then to manipulate the data by using filters and sorting. This enables
me to:
* Discard the false decodes ( "no" in Db column, only one or two decodes
of that PI)
* Spot any decodes that are not in the Frequency Database, but are nevertheless
genuine.
By exporting my Frequency Database to CSV, careful arrangement of columns
to match the same output as the RDS database, one can quickly cross check
entries that way too.. handy in a busy Sporadic E opening here in Europe.
I found exporting to a spreadsheet easier and more versatile than using
DB Browser for SQlite.
Hope this gives you some food for thought.
jamesf_uk on groups.io: Interesting
point about the use of spreadsheets instead of DB Browser... I used to
do it that way as well but because I mainly work with IQ files I've found
that updating the database directly reflects the changes in the SDRC RDS
log. Once the data has been exported it's a bit of a process to get it
back into SDRC.
My (far too many terabytes of) archives from Es openings consist of the
IQ files, data analyser files and the RDS database, all self-contained
in one folder.
That way I can go back whenever I want to review some special catches,
all within the one piece of (marvellous!) software.
Personal preference plays a big part in how we all enjoy our hobby, I've
just found this works best for me.
|
|