I’m currently deep in the guts of a 2P nanosatellite, stitching together M17 and codec protocols on STM32—the kind of work where datasheets become bedtime stories and logic analyzers tell the truth when humans won’t. My north star is collaboration with ISRO, Dhruva Space, and serious space-tech players who build hardware that actually flies, not just pitches.
I speak fluent embedded. I’ve worked across AVR, Arduino, Raspberry Pi, ESP32, and now I’m firmly at home with STM32—from bare-metal firmware to RF payload logic. GPS modules, soil sensors, LCDs, relays, cameras—if it has pins and timing constraints, I’ve probably wrestled with it. I’m currently learning the next layer deeper (you know the drill), so feel free to ask me about satellite telemetry, APRS, SSTV, RF protocols, or why watchdog timers are therapy.
I build in public.
Projects like OrbitRadio—a UHF APRS telemetry payload hosted on MOI-1, transmitting satellite health data at 435.248 MHz using AFSK/FM and AX.25 at 1 W—are proof that I don’t just simulate space, I talk to it. Along the way, I’ve worked on SSTV decoders and denoisers, CubeSat-class amateur radio payloads, embedded AI applications, face detection on Raspberry Pi, smart irrigation systems, and full-stack platforms when hardware needed a backend brain.
I’m not here for buzzwords. I care about robust protocols, power budgets, failure modes, and signals that survive noise. If it can survive launch vibration, thermal cycles, and peer review, I’m interested.
Fun fact: I trust radios more than people—radios at least tell you exactly how bad the link budget is.
Still learning. Still building. If it flies, transmits, or refuses to crash at 3 a.m., I want in.
