Home / JournalJournal

Power budgets need a mission profile

Average consumption alone can hide the parts that determine runtime.

Mission evidence illustrative scene

Describe the mission as a sequence of operating states: idle, sensing, moving, computing and communicating. Estimate how long each state lasts and which components run at the same time.

Keep the assumptions visible. A calculation is more useful when the team can change the duty cycle and inspect the effect than when it offers a precise-looking single runtime number.

Compare the budget with measured runs when those become available. Account for peak demand, reserve and the conditions under which the observations were made. Treat an early model as a planning aid rather than proof of endurance.

A clearer next step

Bring the question.
Let’s examine it.

Start a conversation ↗