# engineering · engineering.m
Embedded & IoT Builds
Embedded and IoT builds — sensor code, microcontroller firmware, and the wiring diagram.
Embedded coursework is marked on hardware behaviour, not just code that compiles — timing that's off by a few milliseconds or a sensor that was never calibrated shows up the moment it runs. We build and, where possible, test against real hardware, and include the wiring diagram so the setup is reproducible, not just the code.
What you get
- Firmware written for the exact board your course specifies
- Wiring diagram included, not just the code
- Sensor calibration handled, not assumed out of the box
- Power and timing constraints respected, not just "it compiles"
- Tested on real hardware where you can provide it, simulated where you can't
- Comments explaining any interrupt or timing-sensitive logic
What to send first
- The problem sheet and any equations, models or reference designs
- MATLAB / Simulink version and required toolboxes
- For embedded work: the board (Arduino, ESP32, STM32, Raspberry Pi) and sensors
- Whether you need a physical build, a simulation (Tinkercad, Proteus) or code only
How it runs
- 01
Send the spec
The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.
- 02
Scope and quote in writing
We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.
- 03
Build against the brief
Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.
- 04
Tested handover
A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.
- 05
Fixes and walkthrough
One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.
Embedded & IoT Builds: common questions
We write and test the firmware and provide wiring diagrams and a bill of materials. For physical builds we can work with the kit you have over a video call, or deliver a simulation if the brief allows it.
Tell us your release and toolboxes and we test against them. We avoid functions that only exist in toolboxes you do not have.
It depends on the scope of the brief, the stack and the deadline. Send the spec on WhatsApp and you get a fixed price and delivery date in writing before any work starts — no hourly meter.
Turnaround depends on scope and is agreed with the quote. Tell us the real deadline, including the timezone, and we will say honestly whether it is workable before you commit.
// related
Often paired with embedded & iot builds
./send-brief
Send your board.
Paste the embedded & iot builds brief into WhatsApp — the message already names the service. Scope and price come back in writing.