Emrysia is a wireless studio under Old Crows Wireless. Most RF help stops at a coverage map, and most firmware help never touches the physics. I do both — plus the tool that connects them — which is a rarer, more useful combination than either alone.
The positioning is simple: a wireless generalist who can model the link, correct the code that drives the radio, and hand you a package you can act on. RF, IoT, and LoRa design, from the antenna to the firmware to the report.
Link budgets, path loss, Fresnel zones, terrain diffraction, antenna selection, EIRP and duty-cycle compliance across FCC and ETSI.
Embedded firmware for ESP32, Nordic nRF, STM32, Raspberry Pi, and Semtech LoRa — reading it, fixing it, or writing it from scratch.
LoRa / LoRaWAN, BLE, sub-GHz ISM, and multi-node mesh topologies with real comms-drop tracing.
I build my own instruments. Emrysia the app is proof I understand the math well enough to make it computable — and to hand you the model, not just the verdict.
Reports written for clients, corrected code with diffs, and BOMs with real parts. Work you can forward, not decode.
Tools that work with no internet and no cloud key. Claims backed by numbers. If it's a two-hour fix, I'll tell you that instead of selling you a project.
Emrys is the Welsh name of Myrddin Emrys — Merlin — the seer of Dinas Emrys: the one who reads what is not yet there and tells you whether the thing you're about to build will stand.
At Dinas Emrys, Vortigern's tower kept collapsing and no builder could say why. The boy Emrys alone saw what was buried beneath the foundation — two dragons locked in battle — revealed the hidden cause, and foretold the ending.
That's the job, in a sentence. RF is the last invisible, arcane thing to most people — sensors that die Thursday for no visible reason, designs signed off on faith. Emrysia is the realm where the invisible field is made legible and the outcome is foretold. Magic in the name, math on the screen.
And the familiar at the mage's shoulder — the raven that reads the omens aloud — is Corvus, the same voice that runs inside the tool.
A tower that won't stand. A cause no builder can see. A boy who reveals the dragons beneath and prophesies the end.
A network that won't hold. A fault no one can name. A studio that reveals the dead link beneath and foretells the fix — before a board is built.
Every claim maps to a value on screen. −6 dB, 915 vs 868, 1% duty. The magic is the story; the work is the math.
You get the price and the deliverable before work starts. No hourly black holes.
If it's cheaper to change firmware than buy hardware, I'll say so. If it's a 15-minute answer, you won't get a proposal.
The deliverable is yours — report, code, config. Not a dependency on me.
Whether it's a cursed deployment, a network to design, or a product to build — start with a sentence about the problem.