03 - Cockpit Broker & Nodes

Physical cockpit I/O, node synchronization, simulator mappings, broker placement and single-instance operation.

Kennis (1)Taken (2)

TAKENLIJST

2 taken

Create and qualify the XP12 Phenom 300 catalogue and mappings Open NORMAAL

The static audit (knowledge item 117) finds an Aerobask DA62/X-Plane starter catalogue in current broker configuration. Phenom 300 catalogue/mappings are missing or unverified. Broker XP12 autodetection alone does not qualify the aircraft profile. Inspect available catalogues and mappings before creating replacements. Define and implement the Phenom 300 controls/state needed by the current physical cockpit and planned startup/cold-and-dark workflow. Record gaps explicitly. Acceptance: catalogue identity and aircraft compatibility can be checked by preflight; required controls, feedback, node/output synchronization and agreed initial-state behavior are verified in a live XP12/Phenom session with version/build evidence. Keep nodes simulator-independent. Until proven, the integrated xp12_phenom300 profile must show an explicit block. Do not disable unrelated existing manual XP12 use. RadioBridge, WingRally and Instructor capabilities require their own separate qualification.

Correct broker readiness and expected-node reporting Open NORMAAL

Use static audit knowledge item 117. Broker .NET 8 build 0.0.1.353 exposes /v1/session/status on 8096. Defects: nodes.connected and nodes.total currently use the same counter; ready only means catalogue loaded. Implement truthful reporting for the profile's expected nodes versus connected nodes, identify missing nodes, and distinguish catalogue loaded, correct aircraft catalogue/mappings, simulator connection, and node/output synchronization. Define the resulting functional readiness contract with the launcher; preserve compatibility for existing API consumers or version the change. Acceptance: a missing expected node is visible; only connected nodes cannot be treated as the total expected set; a loaded catalogue with no simulator or unfinished synchronization does not produce cockpit-ready. Report unknown when evidence is absent. Confirm retained simulator-neutral node protocol on TCP 8099. Preserve the single-broker constraint. MSFS can use simulator/development-host broker; XP12 currently requires the local broker and loopback Web API. During read-only preflight, reject an incompatible host without moving/stopping/starting a broker. Phenom catalogue/mapping qualification remains a separate prerequisite.

Kennis

1 item

📝

Broker and node operating constraints

Source: user-supplied cockpit-Codex static audit, 18 September 2026. Source/configuration/deployment were inspected; live runtime qualification and rebuild validation remain pending. See knowledge item 117. The broker translates physical cockpit-node I/O into simulator functions and synchronizes nodes. Keep nodes simulator-independent. Only one active broker is allowed in the reported setup. MSFS can use a broker on the simulator PC or an alternate host. For X-Plane 12, the broker currently must run on the simulator PC because it uses X-Plane's built-in Web API at 127.0.0.1:8086; the alternate host cannot access that loopback endpoint directly. ESP nodes connect automatically. SimConnect is an integration interface, not a separate program to launch. ExtPlane and a separate X-Plane REST/WebSocket bridge are not required for the reported XP12 setup. ProSimBridge is outside the initial MSFS/XP12 scope. Cockpit Control may remain off during normal operation. Manager implications Check broker location as well as liveness. If an incompatible remote broker is already active when starting XP12, report the conflict and implement an explicit coordinated transition; do not silently start a second broker. Verify the real discovery and readiness mechanisms in code before relying on them. Distinguish node connection from successful synchronization. Concrete readiness defects and profile gap Broker is .NET 8 version 0.0.1.353. Runtime API/Sim Control uses HTTP+WS 8096; /v1/session/status is available. ESP nodes use TCP 8099. In the inspected code nodes.connected and nodes.total use the same counter. They cannot establish that all expected nodes are present. Define expected nodes per profile and report absent and connected nodes truthfully. The current ready flag means only that the control catalogue is loaded. It does not establish simulator connection, correct aircraft mappings, node synchronization or output synchronization. Do not use it as Cockpit ready. Current XP configuration uses an Aerobask DA62 starter catalogue. Phenom 300 catalogue/mappings are missing or unverified. XP12 broker support does not imply a qualified XP12/Phenom cockpit profile. ExtPlane port 51000 remains fallback/diagnostic context, not a normal-start dependency. In the first read-only preflight phase, a wrong broker host is reported/rejected without process mutations.