It's a lot of fun though. Diving into SDR really opens up a new dimension of reality to you and lays bare the magic that can happen when you are able to directly apply complex mathematical constructs to real data coming out of a wire attached to, well, nothign.

I got a little obsessed with it actually and had to step away from it for a while lol.

Same here. I burnt a ton of time just scanning for voice communications and analyzing ADS-B. Once you start playing around in GNU Radio and decoding more exotic stuff, you really start going down the RF rabbit hole. It's an amazing hobby for learning about electronics.

Do you have any tips or resources on how to get to a competency level where you get to decode arbitrary digital signals you find from a scan?

I've read through all the GNU Radio documentation, along with the examples on their wiki and have even written my own blocks but keep finding that opening a grc file that someone else authored, there will be a critical block I've never seen before (and likely, never see again) which hampers experimentation. As soon as I attempt to decode a real-life signal, it feels like I dove in too fast -- there's too many unknowns, since the end result is [presumably] not going to be a nice, human-readable string. However, occasionally, I find challenges like [1] which are great, since you have the expectation that the signal _can_ be decoded; it's just that I've found examples like these to be quite rare.

[1] https://www.gnuradio.org/blog/2018-02-21-gnu-radio-challenge...

It's one thing to demodulate some manchester encoded OOK/FSK signal from some ISM-band hardware monitor vs. 64-QAM or GMSK. At some point it, to me, becomes indistinguishable from magic. Fluency in DSP is, IMHO, mandatory to be broadly effective with GNU Radio.

A plain C/C++ implementation is often so much clearer than a flow graph built in python.

Like any hobby?

Anyway, I'm a licensed HAM and I've played with electronics since forever. I was thinking to get a small SDR module to tinker with.