About the service
I write combat firmware for devices on ESP32, STM32, and Arduino, and lead projects from prototype to hardware ready for series production. My core work is that very low level that most prefer to avoid: sensor and actuator drivers over I2C, SPI, UART, and one-wire, interrupt handling, ADC digitization, PWM control, and neat state machines that keep the device predictable even when the network drops or power fluctuates.
On the connectivity side, I set up WiFi and BLE provisioning, telemetry over MQTT with proper QoS and last-will, TLS where needed, and OTA updates so you don't have to drive to the field with a laptop. I separately deal with power consumption: deep-sleep schedules, interrupt-based wake-up, duty cycles, and current measurement, because a sensor that lives three days is not a product. When a server component is needed, I assemble broker configuration, a lightweight data ingestion API, and a simple dashboard where telemetry can arrive.
I work in C and C++ under ESP-IDF, Arduino, and STM32 HAL/CubeMX, carefully read datasheets, and when the bus lies, I plug in a logic analyzer or oscilloscope. You get commented source code, reproducible builds, and instructions on how to flash and debug the device yourself.
What I typically do:
— Sensor and actuator drivers, interrupts, ADC/PWM, robust state machines
— WiFi/BLE provisioning, MQTT telemetry, TLS and OTA updates
— Low power consumption, deep-sleep, and battery life estimation
— Optional server component: broker, ingestion API, live dashboard
On the connectivity side, I set up WiFi and BLE provisioning, telemetry over MQTT with proper QoS and last-will, TLS where needed, and OTA updates so you don't have to drive to the field with a laptop. I separately deal with power consumption: deep-sleep schedules, interrupt-based wake-up, duty cycles, and current measurement, because a sensor that lives three days is not a product. When a server component is needed, I assemble broker configuration, a lightweight data ingestion API, and a simple dashboard where telemetry can arrive.
I work in C and C++ under ESP-IDF, Arduino, and STM32 HAL/CubeMX, carefully read datasheets, and when the bus lies, I plug in a logic analyzer or oscilloscope. You get commented source code, reproducible builds, and instructions on how to flash and debug the device yourself.
What I typically do:
— Sensor and actuator drivers, interrupts, ADC/PWM, robust state machines
— WiFi/BLE provisioning, MQTT telemetry, TLS and OTA updates
— Low power consumption, deep-sleep, and battery life estimation
— Optional server component: broker, ingestion API, live dashboard
