Published by Jinfan
What to bring to the review
- Exact battery, host and relevant charger revisions
- Confirmed requirements, proposed targets and unresolved questions kept separate
- A responsible owner and evidence location for each decision
6 records that turn a robot mission into a battery duty cycle
Use a row with field number, requirement, responsible party, revision, evidence link and decision. Keep the original measurements or documents available to the authorized project team. Mark missing evidence as open; do not replace it with an estimated pass.
- 1. Mission boundary: identify the start, end and required operational reserve.
- 2. Mode timeline: record idle, travel, turning, lifting or other actual states without inventing missing modes.
- 3. Battery traces: retain voltage, current and timestamps at a stated measurement boundary.
- 4. Concurrent loads: mark overlaps between drive, compute, sensors and auxiliary equipment.
- 5. Conditions: identify payload, route, temperature basis and pack condition for that run.
- 6. Outcome: record shutdown reason, host events, observed energy and unresolved findings.
Use the record to make a scoped decision
Integrate battery-side voltage multiplied by current over the documented timeline to obtain energy. Reconcile the mode durations with the complete mission duration before comparing runs. Keep peak events separate from total energy, and compare different payload or route conditions as distinct records.
Keep acceptance limits explicit
An average current cannot establish transient capability, and a mission estimate does not replace evaluation of the intended robot and pack.
Technical context and limits
TI describes measurement and verification in relation to battery characteristics and operating conditions. The proposed worksheet applies that need for an identified measurement context; it does not prescribe a universal application pass limit.
TI: Accuracy and Verification Methodologies for Advanced Fuel Gauges