▲ 155 r/morsecode+1 crossposts

I made a Morse code app for Flipper Zero and it got slightly out of hand

I made a Flipper Zero app for Morse code. It started as "can I make the orange brick do telegraphy properly?" and then got slightly out of hand.

The first trick is Flipper-to-Flipper Morse: send from one Flipper, receive on another. Pocket secret-message machine. Utterly unnecessary, which is half the charm.

It is also useful if you want to get better at ARG games, beat the timer in escape rooms without crawling back to the Morse lookup table, become suspiciously useful at Keep Talking and Nobody Explodes, get through scouting signal-badge stuff, or just finally understand what that random bit of Morse in cartoons and old films is actually saying. Or maybe you want to become a ham radio operator: low quality voice chat where the ionosphere decides what medical conditions you'll talk about next.

What it does:

  • Flipper to Flipper Morse
  • listen-and-repeat exercises
  • straight-key timing practice
  • sending drills
  • real telegraphic key or paddle over GPIO
  • USB telegraphy adapter mode for specialised practice sites and games (keyboard, mouse, and MIDI output modes)
  • smooth audio out on P2 if the buzzer starts doing your head in
  • built-in help/manual for learning without memorising Morse as dot-and-dash inventory
  • ham radio field mode with canned messages, rig keying, PTT, and logging

The first hardware adapter is just a 6.5 mm jack soldered to header pins. No PCB, no ceremony, just a small ugly hack that works annoyingly well. You can use the Flipper buttons, but a real key feels much better and is more fun to build.

BENS BEST BENT WIRE is a common telegraphy test phrase: the Morse equivalent of scribbling loops and those suspiciously round capital-A shapes when testing a pen.

Video attached, code and release here:

https://github.com/yo3gnd/morse-flipper

u/yo3gnd — 3 days ago
▲ 16 r/HamRadioBeginner+1 crossposts

SSBTrainer.com - a serious SSB simulator for DXing and contesting

Since SSB trainers seem to be popular lately, I thought I’d share the one I started building back in early January: https://ssbtrainer.com

It’s a ham radio SSB trainer with realistic generated voices, HF background noise modeled from technical recommendations, QRM, pileups, DX-style pileups, auroral and QRO effects, plus a waterfall display. Did I mention it also throws at you all the annoyances you find in a pileup - the ionosondes, whistling, the OTH radar and people yelling ola ola over your dx?

The voices are generated, but I took extra care to make it fun. The DXes can get annoyed if you QRZ too much, if you send repeat partials. Some might be nice and slow down for you, some will show their annoyance in various ways.

You can practice digging callsigns progressively deeper into the noise, with modes for things like non-NATO callsigns, accents, and other harder copy scenarios.

There’s also a not-so-secret CW mode hidden in the pileups: decode the first CW callsign and you’ll find it. The server has been sort of hammered lately. It works great on any device, even cheap phones, since everything happens server side.

It's still in an early stage, feedback is welcome.

AI disclosure: some parts were LLM-supervised. Mostly the UI, voice triage, voice rendering, and a bit of backend plumbing. The DSP is hand-rolled and tuned by ear.

ssbtrainer.com
u/yo3gnd — 10 days ago

A rough little tool for waking up unknown POCSAG pagers: pocsag-probe

Ever ended up with a POCSAG pager that has only a partial RIC on the sticker and, if you are lucky, a vague rumour about where it might be tuned? I had one of those charming little problems and did not particularly fancy building yet another programming interface just to ask the thing what it already knows. So I wrote pocsag-probe.

It throws messages through a HackRF or rpitx, sweeps frequencies, walks RIC ranges, reads candidate RICs from a file, and expands partial patterns like 0118 or 3xx21x into valid POCSAG addresses. The point is not elegance. The point is to automate the dull detective work until the pager finally admits what it is listening for. It's not really a prober, it's a bruteforcer. It works. Eventually.

github.com
u/yo3gnd — 2 months ago

June 2026 is near, are you still using your hamclock on esp8266? I'm considering maintaining it.

The folks working on open-hamclock-backend/OHB have rebuilt a backend that speaks the HamClock protocol, which is very good news for keeping older installs useful after the original CSI service goes away.

For Linux/Raspberry Pi-style builds, switching backend is relatively painless because the client can be started with a different backend host. For ESP8266 units, I do not think we get that luxury: depending on the exact build, this likely means DNS/hosts-file trickery somewhere on the network, or rebuilding/flashing a client that points at the new backend. I can do that work, publish a build, and possibly keep it maintained if there is actually an audience for it.

What I am trying to figure out is how many people would benefit from an upgrade path beyond the old ESP8266 3.10 line. The initial goal would be deliberately boring: not a rewrite, not a new product, not “HamClock but better”; just a functional build that lets existing devices keep working past June 2026.

Pics of working setups would be lovely.

reddit.com
u/yo3gnd — 2 months ago