Skip to content

P2Engineering ecosystems

Three ecosystems, each with its own way of going wrong.

A generic supplier database treats every category the same. It cannot, because the parameter that decides a motor and the parameter that decides a cell are not the same kind of number, and neither fails in the same way.

Ecosystems

0

Drone, robotics, battery and energy

Component categories

0+

Each with its own parameter set

Companies mapped

0+

Role recorded, not merged

01The ecosystems

DOM-01

Drone components

Propulsion, control, navigation, and payload for unmanned aircraft.

Airframe decisions are coupled decisions. Motor, ESC, propeller, and pack form one system, and selecting any of them in isolation is the most common way a UAV programme loses endurance it can never get back.

Published categories

What breaks here

  • Endurance targets set from thrust tables measured on a different prop
  • ESC ratings that do not survive the enclosure they are mounted in
  • Pack selected last, after the mass budget is already spent

Motor · ESC · propeller · pack are selected as one set.

DOM-02

Robotics components

Actuation, motion control, sensing, and embedded compute.

Robotics sourcing fails on integration, not on parts. A specification met on the bench and a specification met inside a duty cycle, at temperature, across a fieldbus, are different specifications.

Published categories

What breaks here

  • Torque specified without the duty cycle it was measured at
  • Fieldbus support claimed in marketing and absent in the toolchain
  • Compute modules that throttle to a fraction of their benchmark

Actuator · drive · encoder · controller share one control loop.

DOM-03

Battery & energy components

Cells, packs, management, power electronics, and test.

Energy systems are where claimed numbers and delivered numbers diverge most. Capacity at C/5 and capacity at the discharge rate your system actually draws are not the same number, and the gap is rarely on the datasheet.

Published categories

What breaks here

  • Capacity quoted at C/5 and consumed at 3C
  • Rewrapped cells purchased as manufacturer stock
  • Certificates whose scope excludes the configuration being shipped

Cell · BMS · pack construction · charger are one qualification.

02Cross-domain

Most real systems sit across two of these.

A mobile robot carries its own pack. A drone is a robotics problem with a mass budget. When a requirement crosses domains we structure it as one system rather than running three separate exercises that later contradict each other.

Worked example

An inspection UAV with a 45-minute endurance target is not a motor decision. It is a coupled decision across propulsion, control, and pack — and the endurance number is settled by whichever of the three is specified last.

Start with the application

Building in one of these ecosystems?

Send the application and the operating conditions. We structure it, map the landscape, and validate what the suppliers claim.