PYTHON · NUMPY

The reporting record

Nine fields separate a reproducible robot energy figure from a bare number. How many of them do the existing standards already supply?

Build an energy report a reviewer can check, using what the existing standards already supply.

01Challenge

Nine fields separate a reproducible energy figure from a number. Fill them in, and say for each one which standard supplies it and which leaves it to you.

Predict firstNine fields separate a reproducible robot energy figure from a bare number. How many of them do the existing standards already supply?

02Model

One method now exists and it arrived in June 2026: ISO/TS 25213 specifies how to measure the energy consumption of a six-axis articulated industrial robot, the conditions for the measurement, and how to present the result. Read its edges before you lean on it. It is a voluntary specification, so it obliges nobody; it is paywalled; it excludes service, medical, SCARA, autonomous mobile and delta robots by name; and humanoids are not mentioned. This course did not read its clauses, so treat what it fixes internally as unread rather than as settled. What no method yet supplies is a task denominator. ISO 9283 measures accuracy and contains no power measurement at all, though its cube is where datasheet figures come from. IEC 61800-9-2 measures drive losses at eight fixed operating points and treats the duty profile as an input assumption. ISO 20140 defines efficiency as a ratio and leaves both terms to the user. What does exist and is fully open is OPC 34100 / PROFIenergy: separate import and export counters at every level, so regeneration is never silently netted, and a machine-readable accuracy class travelling with every value. No academic robot-energy paper reports an accuracy class.

03Guided practice

Run the cell, read which fields are unfilled, then fill them for a measurement you could actually take on a bench you have access to.

04Feedback

PASS WHEN You have a reporting record that states its plane, its model, and its uncertainty.

If your run fails, check:

Adopt OPC 34100's contract rather than inventing one: separate import/export counters and a declared accuracy class.
VDMA 34179's productive/unproductive split matters because integrating a trajectory silently drops the idle term.
Compute energy belongs in the same ledger; no standard puts it there yet.
ISO/TS 25213 (June 2026) covers six-axis industrial arms only, is voluntary, and excludes AMRs by name. For every other body the fields you just filled in are the method.

05Retrieve & space

Which two fields must you state because no standard fixes them?
What does OPC 34100 supply that no robot-energy paper currently reports?
Why is 'energy per cycle' insufficient as a denominator?
As of 2026, which robot morphologies have a published energy-measurement method, and who is obliged to use it?

06Mastery & project

Publish an energy figure that another lab can reproduce, and name the standard behind each field.

Write the record for one measurement on real hardware. Where you cannot fill a field, state why and what instrument would.

GO FURTHER · THE LIVE PLAYGROUND

Open the instrument ↗ · Two axes on a shared DC link. Move the meter, slide the phase, watch the number change.

← 1/T³ and 1/T Back to course →

PYTHON · NUMPY

The reporting record

Complete the record and count what a reviewer cannot check.

You read

the arrays and values already in scope

You change

the code you write in each cell

Fixed

the dataset and the checks that grade you