BuildIoT Lab
BuildIoT Lab
contact@buildiotlabs.com

Services

Connected products need hardware, firmware and software that work together. We design the electronics, develop the embedded systems, build the supporting applications and document the handover.

IoT Hardware R&D & Design

An electronics design you can explain, build and test.

We turn a connected-product idea into a system architecture and a circuit design: sensor interfaces, power, radios and protection. Low-power design is a speciality: we budget where the charge goes in each state and change the design until the budget holds.

CurrentTimeAwake 1.4 sAsleep 298.6 s15 µAOne report every five minutes. Waking costs more thansleeping, so how often you wake decides the battery life.
Fig. 1. A duty-cycled node: short, expensive wakes and long, cheap sleeps.

Scope and examples

  • System architecture and block design
  • Circuit design and sensor interfaces
  • Power budgets, deep-sleep and regulator choices
  • Design review and optimisation of an existing design
  • Component recommendations with alternatives

Expected deliverables

  • Architecture diagram
  • Schematics and component recommendations
  • Design notes with the reasoning behind each choice

Tools and platforms

ESP32 family, STM32, Sensor interfaces (I²C, SPI, UART, ADC), Li-ion and LiPo power, Low-quiescent regulators

Custom PCB Design

Board files a fabrication house can build from.

Schematic capture, 2- to multilayer layout, stack-up, design-for-manufacture review and component selection. We supply the digital output a board house or assembler needs; we do not run manufacturing or assembly ourselves.

MCUIllustration only: the layers a layout covers, from footprints torouting and edge connectors. Not a client board.
Fig. 2. An illustrative board: footprints, routed copper, vias and edge pads.

Scope and examples

  • Schematic capture and component selection
  • 2-layer and multilayer layout
  • Stack-up and impedance planning where needed
  • Design-for-manufacture (DFM) review
  • Revision of an existing board

Expected deliverables

  • Editable CAD source files
  • Gerber and drill files
  • Bill of materials
  • Fabrication and assembly data, when in scope

Tools and platforms

Schematic and layout CAD, Multilayer stack-ups, DFM checks, Gerber and drill output

Embedded Firmware

Devices that recover on their own.

Firmware in C and C++ for ESP32 and STM32, with FreeRTOS where the job needs it. We design for the bad day: a brownout, a dropped link, a sensor that stops answering, an update that fails halfway.

SensorNetworkUpdateIdleWatchdogEvery task feeds the watchdog. One that hangs stops the feed,and the chip restarts into a known state.
Fig. 3. Tasks on a FreeRTOS timeline, with the watchdog fed at every checkpoint.

Scope and examples

  • Architecture and task design
  • Drivers for sensors and peripherals
  • BLE, Wi-Fi, MQTT and LoRa connectivity
  • Over-the-air updates with rollback
  • Power management and reliability: watchdogs, brownout handling, safe restarts

Expected deliverables

  • Source repository
  • Build and flashing instructions
  • Firmware binaries
  • Test notes against the agreed behaviour

Tools and platforms

ESP-IDF, STM32Cube HAL and LL, FreeRTOS, C, C++17, BLE, Wi-Fi, MQTT, LoRa

IoT Software & Cloud

Data that arrives in order and survives a dropped link.

From the device to the screen: web dashboards, mobile apps, backend and APIs, MQTT and cloud services, telemetry pipelines and device management. Reliable delivery is a speciality: buffering on the device while the link is down, ordered ingestion, and alerts people will act on.

Sensor nodeMQTT brokerDatabaseDashboardLink downBuffer on the nodeWhen the link drops, readings wait on the node and go outin order when it returns. Nothing is lost, nothing is duplicated.
Fig. 4. Store and forward: readings queue on the node while the link is down.

Scope and examples

  • Web dashboards and mobile apps
  • Backend and API design
  • MQTT broker and cloud setup with access control
  • Telemetry storage with retention rules
  • Device management and monitoring

Expected deliverables

  • Source code
  • API documentation
  • Deployment guide
  • Configuration files and tests

Tools and platforms

MQTT, TLS, Mosquitto, EMQX, InfluxDB, Grafana, Node.js, Docker

Technical Consulting & Remote Engineering

A clear next engineering step, before you spend on the wrong one.

Feasibility checks, architecture advice, debugging of a design that misbehaves, prototype guidance and remote support for your own team. Everything is done remotely, with the work and the findings written down.

Enclosure baseBattery and chargerESP32 boardSensor moduleEnclosure lidBuilt from standard modules, so every part on the bill ofmaterials can be sourced again.
Fig. 5. An exploded prototype: enclosure, module, board and battery, each one documented.

Scope and examples

  • Feasibility studies
  • Architecture and technology choices
  • Debugging and root-cause analysis
  • Prototype guidance and remote test assistance
  • Remote engineering support for your team

Expected deliverables

  • Feasibility report
  • Design review
  • Roadmap
  • Issue findings
  • Agreed milestone outputs

Tools and platforms

Design reviews, Bench measurement guidance, Remote debugging sessions

Not sure which you need?

Describe the device and the problem. We’ll tell you which of these applies, or that a review is the cheaper first step.

Deliverables are subject to the agreed scope and test criteria. “Manufacturing-ready files” means digital PCB output; we do not offer manufacturing or assembly.

Start a Project