Indeed.

I concede that my wording could be open to interpretation.

Yes

It’s likely not difficult to actually do, just determining what’s required and permitted.

Your club is a good starting point.

Be aware that the laws and requirements for grounding (and associated lighting protection) vary across the globe and within a country, to the point where something required in one location is illegal in another.

I’ve been attempting to quantify this in a podcast episode for years, but it’s currently beyond my resources to adequately document, let alone explain succinctly.

In my opinion your best bet is a locally licensed electrician or better yet, one who is also an amateur.

Fair warning, this rabbit hole goes deep … very deep!

This is not NSFW and tagging it thus makes it less effective, eventually meaningless.

Hi Kristoff,

Thanks for the heads-up on the empty data file. I think that the GitHub web interface was “helping” when I initially created the repo - since I still cannot create those from my cli. Now fixed.

I’ve added your interpretation with the sync bits to the documentation for the file. It’s a really interesting observation. I don’t know if there are more than one different types of packet, since my earlier attempt to record the data using a WebSDR failed for some unknown reason. I do know that others have also heard this signal on-air, so perhaps it’s still happening and others might share their recording.

I’d love to learn how to use the differential signal to remove noise to see if they’re actually all the same packet, or if they are actually different. I don’t particularly want to start manually flipping bits, but then there’s only 1,461 of them, so it’s doable in a pinch.

The timing of the signal is also interesting. According to inspectrum, the baud rate is 91.81, which isn’t any standard rate, which also makes me wonder if there is any actual information being transmitted here, other than a fixed timing signal.

73 de Onno VK6FLAB

Thank you, that link was very helpful.

Very interesting! I’ve installed it and attempted to look at the mystery signal, but I cannot make inspectrum show anything other than red. I think it’s sampled at 225144, but that’s speculation based on the filename. Any thoughts?

Source file: https://github.com/vk6flab/signals/tree/main/recorded

Edit: Update, once I played with the file format, testing c8, c16 and c32, I finally got something worth looking at. It appears to be c16 and there look to be 4 bits per symbol.

Edit 2: If I use URH, 2500 samples per symbol, I can decode bits as FSK and get the following string:

7cdc5d32a92284d1f5a53f01b512f2c4663860ec2b273abfdb3c6b90f77a0816f9b8ba65524509a3eb4a7e036a25e588cc70c1d8564e757fb6746b90f77a002df37174caa48a1347d694fc06d44bcb1198e183b0ac9ceaff6cf1ae43dde8205be6e2e9954914268fad29f80da897962331c307615939d5fed9e35c87bbd040b7cdc5d32a92284d1f5a53f01b512f2c4663860ec2b273abfdb3c6b90f77a0816f9b8ba65524509a3eb4a7e036a25e588cc7

Edit 3: Outputting only bits I get the following that seems to repeat (with some decoding errors) every 255 bits:

011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011101000110101110010000111101110111101000000000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111000011000001110110000101011001001110011101010111111110110110011110001101011100100001111011101111010000010000001011
011111001101110001011101001100101010100100100010100001001101000111110101101001010011111100000001101101010001001011110010110001000110011000111

The lack of transparency within the various bodies within our community is disturbing. It’s not that the information is there, waiting to be found, instead it seems clear to me that it’s been withheld for reasons nobody has ever even attempted to articulate let alone justify, and frankly I think it’s harmful to the well-being of the entire pursuit of amateur radio.

A search engine?

QSL … thank you.

Just to make sure, you’re not an ARRL member?

Are you an active LoTW user?

Very interesting! I just recorded a sample using your WebSDR, much appreciated.

Edit: Hmm … that’s odd. I just managed to check the file, two days later, and it’s essentially empty. It doesn’t appear to have saved the .mp3 file at all.

That’s very interesting. I thought it was a once-off, but you appear to be saying that it’s ongoing. I currently don’t have HF capabilities, so I reported on a recording made by a fellow amateur.

As far as figuring out where it comes from, the direction finding can be pretty rudimentary. Use any directional antenna and determine the direction of the strongest signal. Document it somewhere, get multiple people across the globe to do it, job done.

Feel free to record them here, seems like as good a place as any.

https://github.com/vk6flab/signals

There is a lot of hype in this article and precious little in the way of verifiable facts.

Does anyone have any links to something more credible?

Universal Radio Hacker playlist:

https://youtube.com/playlist?list=PLa4O03wp0ulCTXGiy7H05ljv_1qb8saBP

I’d recommend you explore https://qrm.guru/ to determine exactly where the noise is coming from and what to do about it.

Orca Slicer is open source and as far as I know a fork of Prusa Slicer. I suspect that you can compile from source with whichever version of OpenGL you want … if any.

Disclaimer: I’ve only just started looking at it for a different use-case, but it seems like it will do what I’m suggesting.

• https://daily.hamweekly.com/2025/05/arrl-influence-reduced-iaru-restructuring/
• https://daily.hamweekly.com/2025/05/iaru-considers-consolidation/
• https://www.iaru-r2.org/wp-content/uploads/2025/04/IARU-Consultation-on-Proposed-Restructuring_march_2025.pdf