rtl_map, FFT-based visualizer for RTL-SDR [Project]

Show off any of your RTL-SDR or cheap SDR related projects.
Post Reply
Posts: 2
Joined: Sun Jan 27, 2019 10:48 pm

rtl_map, FFT-based visualizer for RTL-SDR [Project]

Post by KeyLo99 » Mon Jan 28, 2019 10:17 am

I'm a RTL-SDR researcher and DSP learner currently working on a project for properly figuring RTL2832 and I/Q fundamentals out. The project is about reading raw I/Q samples, processing samples and creating FFT graph from them. I tried to explain what I'm doing in detail with comment lines. I'm hoping that I will be helpful to RTL-SDR beginners with this rtl_map [C] project. Another purpose of the rtl_map project is making a frequency scanner application for signal security researches.
Another information about the project, installation instructions and example usages exist at the GitHub repository.
I'd be thankful for comments about the project, contributions with pull requests and new ideas.
Have a good day : )

Posts: 1
Joined: Sat Sep 07, 2019 11:54 pm

Re: rtl_map, FFT-based visualizer for RTL-SDR [Project]

Post by RichardKCollins » Sun Sep 08, 2019 12:38 am

You code is clearly written, but it is not at all clear what else is required to run this program, and how to get to where it will run.

I downloaded the three pieces,


This comes to 745 files in 128 folders. And there is no clear description of the dependencies of the other two pieces.

The simplest would be if you could compile the other two parts (ffrw3 and librtlsdr) and include them with your program as dlls. Don't be lazy and say "Oh just download all those pieces, it is in there somewhere." Give the specific pieces needed to use the tool you wrote.

Yes, I know it is important to give credit, and to link people back to the groups. I hope they can be convinced to keep current libraries for the different platforms. Or you will while you are interested in this tool. Perhaps this is available. The projects and packages I have looked at use a scattering of conventions, and most people do not take them too seriously.

Could you include an html page in the folder that links to a current dll (or the equivalent for Linux and other environments), and gives credit to the groups by name, and by linking to their main page. If you want to do more, keep it clean and lean, but don't leave anything out.

A few minutes of your time to give the pieces for immediate execution will save hours, days or weeks.

My main point is you currently are suggesting, without saying it exactly, that everyone should deal with the source code of every one of your dependencies. I say that can be done by you keeping the executables available.

A person new to SDR can probably modify your code. They have no reason to rewrite FFT or SDR core tools. If they want to do that, they can get involved, and you will just post the version that works with what you have. It is not perfect, but I am trying to find a way to shorten the horrendous and nasty process in place now. Try to use one small useful piece from AstroPy and you have to load 2039 files, 338 folders and 134 MegaBytes of stuff.

Is any of this making sense?

I would like to write some basic tools for recording SDR data at what are intended to be permanent stations world-wide. These will record some aspects of the electromagnetic field at each location - for comparisons, correlations, and basic research. My models are the superconducting gravimeter, seismometer, magnetometer, astronomical, radio telescope, VLBI, gravitational, meteorlogical, satellite,GPS/GNSS, cosmic ray, and many many other similar global networks that record basic data intended to be available for the coming decades.

I am trying to set up a global network of three axis, high sampling rate correlating gravimeters. These are intended to scan the earth, its surface, interior and environment. But to work at the levels of sensitivity required, means finding, identifying and characterizing all the electromagnetic sources in the solar system. As a start.

Richard Collins, The Internet Foundation

Post Reply