← All professional work

Professional work

Engineering / bench stage

Radar Relay IoT

Embedded firmware, Azure services and commissioning tools for remote radar health monitoring and controlled power recovery.

My role

Device, cloud & desktop development

Focus

Embedded systems / Azure IoT / Device operations

Read the story
Radar Relay fleet dashboard showing grouped sites and controller statusView full size ↗
Actual dashboard running in fixture mode with a simulated fleet. Counts illustrate the interface, not a deployed fleet.
01

Device identity and provisioning

02

Telemetry and controlled power recovery

03

Desktop commissioning and signed releases

Built with

  • C++
  • Azure
  • TypeScript
  • React
  • Terraform
  • Python

A closer look

Radar Relay controller detail with telemetry charts and device state
Controller detail brings telemetry and device state together. Shown with fixture data.

Context

A remotely deployed radar may need a physical power cycle even when its network connection is unreliable. The surrounding control system needs to make that action deliberate, observable and recoverable.

What I built

  • Controller firmware: relay state, watchdogs, telemetry and hardware abstractions for Opta and ESP32 development.
  • Cloud services: device inventory, assignment, provisioning and command lifecycle APIs using Azure Functions and Cosmos DB.
  • Operator tools: a React dashboard and a Python-backed desktop commissioning application.
  • Delivery tooling: infrastructure definitions, signed firmware artifacts and repeatable installation workflows.

Design decisions

A controller, its network address and the radar it serves are separate identities. That allows hardware to move or be replaced without rewriting its history.

Commands also have a lifecycle. Requesting a power cycle, receiving an acknowledgement and observing completion are different facts. The UI preserves those differences instead of presenting a successful request as a completed physical action.

Project overview

This project joins embedded software, cloud architecture and the practical steps required to put a device into service. It began with a local Ethernet/relay prototype and expanded into provisioning, fleet views, desktop installation and engineering release management.

Recent work includes ESP32 Ethernet/Wi-Fi failover and signed firmware update paths. Hosted and bench progress is documented, while field acceptance remains staged. The system’s central design requirement is that loss of the controller or cloud connection must not remove radar power. Hardware qualification and broader rollout are separate milestones from implementing the software.