Connectivity
BLE and Connected Device Firmware
Kyros Engineering develops Bluetooth Low Energy firmware for connected and battery-powered products — GATT and service design, connection reliability under real-world interference, power budgeting that survives the actual duty cycle, secure over-the-air update, and radio integration that will pass FCC and CE rather than surprise you at the test house.
Scope this with usBLE demos easily and ships hard. The gap is almost always one of three things: a power budget built from datasheet numbers instead of measured behaviour, a connection strategy that assumes a quiet RF environment, or an update path added after the architecture was frozen.
We design against the deployed condition — the enclosure, the battery, the interference, and the phone on the other end that will behave differently across OS versions.
Power budgets that hold in the field
Battery life claims fail on the details, and the details are measurable.
- Current profiled across the real duty cycle, including advertising, connection and radio-off states
- Connection interval and latency negotiated against actual application needs, not left at defaults
- Sleep current measured with the full board populated, where the leak usually is
- Wake sources audited — an unnecessary periodic wake can dominate the average
- Battery chemistry and temperature range folded into the estimate rather than assumed nominal
Reliability in a noisy world
The environment that matters is a hospital corridor, a factory floor or a pocket — not a bench with one central and one peripheral. We design reconnection, bonding and error recovery as explicit behaviour, and we test against the interference and range conditions the product will actually meet.
Secure update, designed in
An OTA path that was not planned for is the single most common reason a connected product cannot be fixed after launch.
- Flash partitioning and rollback decided before the memory map is committed
- Signature verification and secure boot, sized to the threat model rather than to fashion
- Interrupted-update behaviour defined and tested, including power loss mid-write
- Update over the phone app and over a service tool treated as one design, not two
- Field diagnostics so a failed update is reconstructable rather than mysterious
When to call
You probably want this if…
Frequently asked
Can you improve battery life on a product that already ships?
Often substantially, and the first step is measurement rather than optimisation. Profiling the real duty cycle usually finds one or two dominant contributors — an unnecessary wake, a connection interval left at default, or a sleep current leak on the populated board — that account for most of the gap.
Do you build the phone app as well?
We design and build the device side and the protocol between them, and we work directly with your app team or app vendor on the interface. Where a program needs the app built too, we scope it with a named developer rather than implying we have an app studio in-house.
How early should regulatory come into a BLE design?
At antenna placement, which is usually earlier than teams expect. Module choice, ground plane and enclosure material determine most of your radiated performance, and all three get expensive to change once mechanical is committed.
Connected product not behaving outside the lab?
Tell us the environment it fails in. That is usually the whole diagnosis.