These come first because the next step asks what your display shows — which columns, in what order, in what units, and what each identification colour means. Those are far easier to get right when the display itself is on the table, so the screenshots are read alongside your answers rather than only afterwards.
They are evidence about the display, not authority about the system. A screenshot shows one moment: where it disagrees with what you write, what you write wins, and the disagreement is written down rather than quietly resolved.
Euro_AD has 4. The console is copied from these — with only a few views the copy is a guess in the gaps.
- 19e3e12a-79ef-475f-b92a-6de2706caf42-IMG_4559.jpg
- 6f6bb79f-02cd-4164-bad0-6bae6ab7f30b-IMG_4558.jpg
- b0715ebb-6047-4e11-8fd9-9ba585dfe19b-IMG_4561.jpg
- c6b4aa67-908a-44db-8f69-5019a5857651-IMG_4560.jpg
Add more views of the real console
The console a trainee sits at is copied from these — layout, proportions, palette, borders, typography. Send as many as you can, up to 20: different views show different panels and states, and a colour that only appears during an alert cannot be copied from a screenshot taken when nothing was happening.
- — the whole screen, at least once — the layout is taken from this
- — each panel close up, so the type and the borders are readable
- — the display with tracks on it, and with none
- — a track selected, and an alert state if the system has one
- — any menu, key or legend the operator reads
Identifying content is not carried across: no vendor names, unit markings or real call signs. Only the appearance is copied.