Most connected-equipment projects fail at the seams — the board talks, the cloud listens, and nobody owns what happens in between. We take the whole path, from the signal on the wire to the fleet tool your support team uses.
ESP32 and ESP32-S3 board design for equipment that has to survive a real site: sensing, power, I/O and the cable harness that connects it to the machine. Prototypes through to small-batch production, assembled and bench-tested before they ship.
C++ on ESP-IDF, written on our own HSYS framework: modular, message-based, with a hardware abstraction layer so the same code runs as a desktop simulator. Behaviour gets tested before a board is powered up, and products share one codebase.
Equipment that was never meant to be read usually still says something on a wire. We capture it, decode it, and build the tap that turns it into usable events — as we did for three different fuel dispenser display protocols.
HTTPS for telemetry, MQTT for the command and configuration path. Device identity, reconnection and local buffering handled on the board, so an unreliable link delays data rather than losing it.
Versioned update bundles delivered over MQTT or HTTP, applied in a safe order and rolled out in batches. Staged updates for multi-chip boards, where boot, partition and firmware must land in sequence.
The unglamorous half that decides whether a deployment is supportable: a support console for the fleet, remote config with snapshots and audit trail, factory flashing scripts, log collection, and test rigs that emulate the real equipment.
Scoped in stages, so you can stop at the end of any one of them with something usable in hand.
What the machine is, what it already emits, and what you need out of it. Often a short capture-and-decode exercise on a live unit before anything is committed.
A working board and firmware against a test rig or a real unit, proving the signal can be read reliably and the data lands where it should.
A small number of units installed and watched in production conditions — which is where the surprises actually surface.
Batch production, installation, and the tooling for whoever supports the fleet afterwards. Updates ship over the air from then on.
A short description of the equipment and what you want out of it is enough for us to say whether this is worth a conversation.