Electronics & embedded systems · Power, battery & diagnostics
Senior engineering across power, battery and diagnostics.
Power conversion that doesn’t behave under load. Battery systems that need monitoring and protection, not just cells. Measurements that need to be trusted, not just taken. 1722 provides independent, vendor-neutral engineering across power electronics, battery and energy-storage systems (BMS), precision measurement and instrumentation, and diagnostics, condition monitoring and failure analysis — scoped as a project, delivered directly, and the IP is yours.
You commission the work, we deliver the output, you own it. A mutual NDA is offered as standard before any technical detail is shared.
What is engineered
Four disciplines, engaged individually or together.
Most real problems sit across more than one of these — a battery system needs conversion, monitoring and diagnostics working as a whole, not as separate line items.
- 01
Power electronics
DC–DC conversion, voltage regulation, power sequencing, protection circuits (over-current, over-voltage, reverse-polarity), thermal management and low-power design for battery-run and mains-fed systems alike.
- 02
Battery & energy-storage systems (BMS)
Cell-to-system monitoring, cell balancing and protection logic for battery and energy-storage systems, engineered with IEC 62133 and UN 38.3 in view from the schematic stage.
- 03
Precision measurement & instrumentation
Sensor interfaces, signal conditioning and filtering for measurements that need to hold up under noise, temperature drift and long duty cycles.
- 04
Diagnostics, condition monitoring & failure analysis
Instrumentation and analysis to characterise how a system behaves in the field and why a unit failed — root-cause failure analysis on real hardware, not simulation alone.
When you need it
The situations that bring this work in.
| A design misbehaves under load | Conversion efficiency drops, regulation is unstable, or protection circuits trip (or fail to trip) under real operating conditions. |
|---|---|
| A battery or energy-storage design needs system-level monitoring | Cells exist, but balancing, protection and system-level monitoring logic don’t yet. |
| A measurement can’t be trusted | Sensor readings drift, are noisy, or don’t hold across the operating temperature range. |
| Units are failing and the cause isn’t known | Field or test failures need root-cause failure analysis rather than a guess and a respin. |
| In-house capability is thin at senior level | The design work needs a senior engineer for a defined period, not a permanent hire. |
What you get
Deliverables you own.
Every engagement ships concrete artefacts your team keeps and can act on — never advice alone.
- Schematics & design files for the power, battery-management or measurement circuitry
- Design rationale & calculations — component selection, tolerances, thermal and protection margins
- Test & verification records — bench data, waveforms and pass/fail criteria against the spec
- Diagnostic & failure-analysis reports — root cause, evidence and recommended design response
- DFM & production-transfer notes so your chosen manufacturer can take it from there
- Handover pack — documentation in a form your team owns and can act on without us
Standards & scope
Design discipline, stated plainly.
Battery and energy-storage work is engineered with IEC 62133 and UN 38.3 in view from the schematic stage, not bolted on afterwards. Board-level and system work accounts for EMC/EMI and CE/UKCA requirements as design disciplines throughout, so formal compliance testing at an accredited test house is a confirmation step, not a rebuild. No certification is claimed by 1722 — only the design discipline that makes external certification achievable.
Out of scope — contract manufacturing, production-line operation, ongoing field support and formal compliance certification testing (arranged separately with an accredited test house). This is design and engineering time against a written scope of work.
Point us at the circuit, the cell, or the failure.
A short discovery call, a mutual NDA if needed, then a scoped plan.
FAQ
Power, battery & diagnostics, answered.
What does "power, battery & diagnostics engineering" cover?
Four related disciplines, engaged individually or together: power electronics (conversion, regulation, protection); battery and energy-storage systems including battery management (BMS); precision measurement and instrumentation (sensor interfaces, signal conditioning); and diagnostics, condition monitoring and failure analysis. Most engagements touch two or three of these at once — a battery system needs power conversion, monitoring and diagnostics to function as a whole.
Do you make batteries, or a specific battery product?
No. This is general-purpose power electronics, battery-system and diagnostics engineering applied to whatever hardware a client is developing — industrial equipment, mobile devices, energy-storage installations, test rigs. We do not sell or productise any finished device or product, and we do not discuss client applications by name or sector; each engagement is scoped from your requirements on the discovery call.
Do you hold ISO or other certifications?
No certifications are claimed. What is offered is the design discipline: battery work is engineered with standards such as IEC 62133 and UN 38.3 in view from the schematic stage, and board-level work accounts for EMC/EMI and CE/UKCA requirements early rather than as a late-stage surprise. Formal compliance testing and certification are arranged separately with an accredited test house. A mutual NDA is standard before any technical detail is shared.
Who owns the IP from the engagement?
You do. You commission the work, we deliver the output, and the design IP — schematics, firmware, test data, analysis — is yours on delivery. A mutual NDA is offered as standard before any technical discussion begins.
Is this the same as PCB or embedded firmware design?
It overlaps but is scoped separately. This line covers the power, battery and diagnostics engineering — circuit topology, cell-to-system monitoring, sensor and measurement design, failure analysis. Schematic capture, PCB layout and firmware/driver development sit on the PCB & circuit design line and are commonly engaged alongside it.
Do you provide ongoing production support or manufacturing?
No. This is design and engineering time against a written scope of work, not contract manufacturing, production-line operation or ongoing field support. Design-for-manufacture (DFM) review and production-transfer documentation are included as deliverables so your chosen manufacturer can take it from there.
How is work priced and scoped?
Day-rate, time-and-materials, retainer or fixed-scope against a written statement of work with named deliverables and acceptance criteria — never a subscription or a fixed-price product build. Start with a short discovery call to establish scope.
Who typically commissions this work?
CTOs, Heads of Engineering, Product/Innovation Directors and R&D or Quality Managers at hardware and product-development teams who need senior power, battery or diagnostics engineering without carrying it on permanent headcount.