IMAGES

Wiki Image Manifest

This is an internal working document (not a published wiki page — GitHub wiki ignores files it doesn't link, and nothing links to this). It tracks every image the wiki needs: which already have a placeholder reference in a page, which still need a reference added, the exact content each shot should show, and the manager state required to capture it.

Legend — Type:

• 📷 Screenshot — capture from the manager UI
• 🖥️ OS screenshot — Windows dialog (UAC, firewall, joy.cpl, DCS/BMS UI)
• 🔧 Photo — physical hardware photo
• ✏️ Diagram — illustration/wiring diagram (can be drawn, not captured)

Legend — Status:

• ✅ Referenced — the page already has an ![...](images/...) tag waiting for the file
• ➕ To add — image would help but no reference exists in the page yet

All files go in images/ and are referenced as images/<name>.png.

---

Already referenced in pages (✅ — these placeholders exist; drop the file in to fill them)

Home

File	Type	Status	What it shows	Capture conditions
home-overview.png	📷	✅	The manager open, ideally on the home page with boards connected and a clean layout — the "hero" shot	Boards online (real or mock); home/avionics page

Install the Manager

File	Type	Status	What it shows	Capture conditions
install-uac-prompt.png	🖥️	✅	Windows UAC prompt with Verified publisher: Invictus Machine LLC	Run the real signed installer .exe
install-wizard.png	🖥️	✅	Installer welcome / wizard screen	Run the real installer
install-firewall-prompt.png	🖥️	✅	Windows Defender Firewall prompt for AIM Cockpit Manager, Private networks checked	First launch on a machine that hasn't allowed it yet

Set Up the Cockpit Network

File	Type	Status	What it shows	Capture conditions
network-fix-banner.png	📷	✅	Network page alert: cockpit adapter missing 192.168.100.1, with the Fix button and adapter name	Launch with the cockpit adapter NOT carrying 192.168.100.1 (remove the IP first, or use a machine that's never been set up)

Add Your First Board

File	Type	Status	What it shows	Capture conditions
board-new-badge.png	📷	✅	Network page, a board row with a NEW badge	A freshly-booted, never-configured board on the network (or mock)
board-wizard-open.png	📷	✅	Board setup wizard, first screen	Open the wizard on a NEW/UNCONFIGURED board
board-wizard-name.png	📷	✅	Wizard board-name entry field	Wizard, name step
board-wizard-panels.png	📷	✅	Wizard panel-selection screen with cockpit zones + checkboxes	Wizard, panel-pick step
board-configured.png	📷	✅	Network page, a configured board with a green status dot and its name	A saved, configured board (or mock)

Assign Controls to Pins

File	Type	Status	What it shows	Capture conditions
pin-assign-panel-view.png	📷	✅	Panel control list with a pin field next to each control	Configured board → open a panel's pin-assignment view
pin-assign-autosuggest.png	📷	✅	The Auto-suggest button and resulting filled-in pin numbers	Same view, after clicking Auto-suggest
pin-assign-export.png	📷	✅	The Export Pin List button and a sample exported pin-list document	After exporting a pin list

Test and Calibrate

File	Type	Status	What it shows	Capture conditions
test-live-view.png	📷	✅	Live panel view: switch states + pot position bars	Live/Test view of a panel (real hardware ideal so values are real)
test-calibrate-pot.png	📷	✅	Right-click → Calibrate context menu + the calibration dialog with the live auto-capturing bar	Right-click a pot in live view, open Calibrate

Swap or Replace a Board

File	Type	Status	What it shows	Capture conditions
swap-export-config.png	📷	✅	Export Config button on a configured board's detail panel	Configured board detail view
swap-import-config.png	📷	✅	Import Config button on a NEW board's row	NEW/UNCONFIGURED board

Set Up DCS

File	Type	Status	What it shows	Capture conditions
dcs-setup-button.png	📷	✅	DCS Integration card listing detected DCS variants + install status	DCS installed + launched once (so Saved Games exists)
dcs-setup-dialog.png	📷	✅	DCS Integration card after a successful install, green per-variant status	After clicking Install
dcs-connected.png	📷	✅	DCS Integration card showing Connected status	⚠️ NOT YET IMPLEMENTED — Connected/Waiting status is Task #127. Capture only after the manager is updated.

Cockpit Displays in DCS

File	Type	Status	What it shows	Capture conditions
display-management-card.png	📷	✅	DISPLAY MANAGEMENT card on the home page	Home page
mfd-detected-displays.png	📷	✅	Multi-Display dialog, 1. DETECTED DISPLAYS list with FLASH buttons	Open the display dialog (multi-monitor PC shows best)
mfd-assign-roles.png	📷	✅	2. ASSIGN ROLES section, dropdown per role	Same dialog
dcs-monitor-options.png	🖥️	✅	DCS Options → System with AIM MFDs in the Monitors dropdown	In DCS after applying a layout

Set Up Falcon BMS

File	Type	Status	What it shows	Capture conditions
bms-keyfile-card.png	📷	✅	BMS KEYFILE card on the home page	Home page
bms-driver-ready.png	📷	✅	AIM GHOST JOYSTICKS status showing all devices ready	After driver install + create devices

---

Suggested additions (➕ — no reference in the page yet; add one if you want the shot)

What You Need

File	Type	What it shows	Notes
hw-sidewinder-board.png	🔧	Photo of a Sidewinder board, headers visible	Product photo
hw-phoenix-board.png	🔧	Photo of a Phoenix board	Product photo
hw-poe-switch.png	🔧	A small 802.3at PoE switch	Optional

Wiring Your Switches, Knobs, and Pots

File	Type	What it shows	Notes
wiring-switch.png	✏️	Switch → GPIO + GND diagram (replaces/supplements the ASCII art)	Diagram
wiring-3pos.png	✏️	3-position switch → 2 GPIO + common GND	Diagram
wiring-encoder.png	✏️	Encoder A/B/common wiring	Diagram
wiring-pot.png	✏️	Pot 3.3V / wiper / GND wiring	Diagram
wiring-jst-ph.png	🔧	A crimped JST PH connector / header	Optional photo

Install the Virtual-Joystick Driver

File	Type	What it shows	Notes
bms-driver-not-installed.png	📷	AIM GHOST JOYSTICKS status reading "Not installed" with Install driver button	Pre-install state
joycpl-ghost-joysticks.png	🖥️	Windows joy.cpl / Controllers list showing AIM Ghost Joystick 1, 2, …	After devices created

Load the Keyfile

File	Type	What it shows	Notes
bms-launch-without-override.png	🖥️	BMS Launcher with "Launch without any Setup override" selected	Critical-step illustration
bms-controllers-load.png	🖥️	BMS Setup → Controllers → Load, selecting Invictus AIM F-16.key	In BMS

Assign Axes in BMS

File	Type	What it shows	Notes
bms-axis-assign.png	🖥️	BMS Controllers screen binding an axis on an AIM Ghost Joystick	In BMS

Cockpit Displays in BMS

File	Type	What it shows	Notes
bms-apply-displays.png	📷	EXPORT section with APPLY BMS DISPLAYS button + BMS status line	Multi-Display dialog
rttclient-tray.png	🖥️	RTTClient running in the Windows system tray	After launching RTTClient

Update the Manager

File	Type	What it shows	Notes
update-banner.png	📷	The update banner across the top of the window	Requires an available update (or a forced/dev state)

Update Board Firmware

File	Type	What it shows	Notes
firmware-page.png	📷	Firmware page with board dropdown + drop area	Board connected
firmware-flashing.png	📷	Progress bar mid-flash	During an actual flash

Indicator and Caution Lights

File	Type	What it shows	Notes
wizard-step3-lamp-pins.png	📷	Wizard Step 3 with indicator lamp rows getting GPIO pins	Wizard on a board with a lamp panel
wizard-step2-caution-spi.png	📷	Wizard Step 2, Caution Panel checked, SPI channel dropdown	Wizard
caution-panel-lit.png	🔧	A physical caution panel lit up	Optional finished-build photo

UHF and CMDS Displays

File	Type	What it shows	Notes
wizard-spi-slot.png	📷	Wizard Step 2 SPI channel dropdown for UHF/CMDS	Wizard
uhf-display-lit.png	🔧	UHF 7-seg display showing channel/freq	Finished-build photo
cmds-display-lit.png	🔧	CMDS dot-matrix display showing counts	Finished-build photo

VFT5 Side-Stick

File	Type	What it shows	Notes
vft5-firmware-page.png	📷	Firmware page with the stick connected, version shown	VFT5 plugged in
vft5-profiles-page.png	📷	Profiles page, grip dropdown + "joy.cpl will show N buttons" preview	VFT5 connected
vft5-joycpl.png	🖥️	joy.cpl test panel showing the stick's buttons/POVs	VFT5 connected

Settings

File	Type	What it shows	Notes
settings-page.png	📷	The Settings page (full, or one shot per section)	Any time

Board Pin Reference

File	Type	What it shows	Notes
sidewinder-headers.png	🔧/✏️	Sidewinder with headers labeled (GPIO, P1–P8, SPI, I²C, backlight)	Annotated photo or diagram
phoenix-headers.png	🔧/✏️	Phoenix with headers labeled	Annotated photo or diagram

---

Capturing manager screenshots without hardware / a running sim

Summary: there is no single "mimic mode" flag. But the manager's board discovery is a plain TCP protocol, so a small helper script can make fake boards appear online — enough to capture most of the manager-UI screenshots with no real hardware. A few states genuinely can't be faked.

The fake-board helper

mock_boards.py (kept in C:\Users\Chris\Documents\aim-dev-tools\, outside this repo) connects to the running manager on 127.0.0.1:8888 and pretends to be one or more boards. Stdlib only — no install needed to run it.

Flow:

1. Launch the manager (any normal launch; add --dev to also un-hide the Debug log / Deadband / Factory pages — see below).
2. In a second terminal: python mock_boards.py (default preset = a NEW Sidewinder + NEW Phoenix + an UNCONFIGURED board).
3. Screenshot the Network-page states, open the wizard, etc.
4. For the green/configured look: python mock_boards.py --preset configured, then run the real wizard on each board and Save. The fake board acks the config push and "reboots," and the manager matches it to the registry entry it just wrote → the row turns green with the name you chose. This also lets you screenshot pin-assignment, auto-suggest, export, live view, and swap export/import — all the configured-board screens.

What each state needs

Image group	Fakeable?	How
Network: NEW / UNCONFIGURED badges	✅	mock_boards.py default preset
Network: green configured board	✅	--preset configured + run the real wizard
Board wizard (open/name/panels)	✅	Open the wizard on a fake NEW board
Pin assignment / auto-suggest / export	✅	After the wizard configures a fake board
Live / Test view (static)	✅	Configured fake board (switch movement would need the script to also send CTL: messages — not built yet)
Swap export/import config	✅	Configured fake board + a second NEW one
Display Management card + dialog	✅	Already works with no hardware; detected-displays list = your real monitors
DCS card: Installed / Update available	✅	Run the real install (just a file copy), or place an older copy for the stale state
Settings page	✅	Always available
Avionics panels / instruments	✅	Always renders the full F-16C catalog, no hardware
Home overview (hero)	✅	With fake boards online
Update banner	⚠️	Needs an actual newer release published (or a dev-forced state)
Firmware page (board)	✅	Fake board appears as a flash target; an actual flash needs a real board
BMS driver "devices ready" / joy.cpl Ghost Joysticks	❌	Needs the real EV-signed driver installed + devices provisioned (UAC). Not fakeable.
VFT5 stick connected (firmware version, apply)	❌	Needs a real VFT5 on USB. (The Profiles grip dropdown + preview do render with no stick.)
OS dialogs (UAC, firewall, DCS Options, BMS Launcher, RTTClient tray)	❌	Capture live during real install/use
Hardware photos / wiring diagrams	❌	Physical photos / drawn diagrams

Dev mode

Launch with --dev (or triple-click the logo in-app) to un-hide developer pages: Debug log, Deadband, Factory calibration. Dev mode does NOT inject fake hardware or fake sim/connection states — those still come from the real artifacts above. It's only useful if you want to document those dev pages.