pod: the HARDWARE RIO on COM1 (L4CONTROLS=RIO:COM1,KEYBOARD)

The real cockpit board now drives the cab instead of PadRIO, frozen in the
profile so all five tester launchers get it.  Nothing above the seam changed
-- the 109-mapping L4 control table installs exactly as on a desktop, and the
cab keeps the GLASS display stack.  BT_PLATFORM=pod is NOT the way to this;
that would drag in the 1995 gauge path.  RIO:COM1 -> \.\COM1 at 9600 8N1.

Evidence the link is real, not just "the port opened":
  RIO successfully initialized!
  FAILURE.LOG: 4 missing boards (Slot 3:0, 3:2, 4:0, 5:0), 16 dead lamps
  [ctrlmap] push stick x=0.0595238 y=0   <- physical stick outside deadband
A specific 4-of-many board inventory is the proof: a dead serial line reports
the WHOLE address space missing.  Reproduced after deleting FAILURE.LOG.  The
dead lamps are the boards this partial crash cart does not have.

Banner honesty: "GLASS (PadRIO ...)" was hardcoded, so a wired cab reported
PadRIO on the very line you read to check which device won.  It now names the
resolved one -- GLASS (hardware RIO; plasma off [L4PLASMA]).

Recorded in pod-hardware.md, including that RIO and PAD are mutually exclusive
(both assign rioPointer, last token wins) and that a CENTRED stick reads x=0,
which is indistinguishable from no data -- so the by-hand check of stick,
throttle, pedals, buttons and the Ranger calibration is still outstanding.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rw7No5wLTpkaUgA3ANbtZZ

scratchpad/pod/podprofile.ini

@@ -37,6 +37,18 @@ BT_START_INSIDE=1
 # Main view fills its 800x600 panel (DISPLAY3, the primary) with no border.
 BT_FIT=1
 
+# THE REAL COCKPIT BOARD.  RIO:COM1 -> \\.\COM1 at 9600 8N1 (L4SERIAL); the
+# stock control path above the seam (mapper, lamps, streamed .CTL mappings)
+# runs unchanged -- PadRIO was only ever standing in for this.
+#   * RIO and PAD are MUTUALLY EXCLUSIVE: both assign rioPointer in the
+#     L4CONTROLS parser, so the last token wins.  This turns the XInput pad
+#     off on this machine.  To get it back for a session, override in the
+#     launcher: set L4CONTROLS=PAD,KEYBOARD  (the real environment wins).
+#   * KEYBOARD stays in the list as the fallback.  It does NOT demote the RIO
+#     (it only sets a flag), and a silent total loss of input would be
+#     indistinguishable from a hang.
+L4CONTROLS=RIO:COM1,KEYBOARD
+
 # No 128x32 marquee wired on this cart -- and the glass profile would
 # otherwise default L4PLASMA to SCREEN and drop a plasma window on the glass.
 L4PLASMA=NONE

scratchpad/pod/runpod_rio.bat

@@ -0,0 +1,24 @@
+@echo off
+REM BT411 pod -- HARDWARE RIO test.  Same frozen glass/RGB rig, but the input
+REM device is the real cockpit board on COM1 instead of PadRIO.
+REM   L4CONTROLS=RIO:COM1 -> RIO opens \.\COM1 at 9600 8N1 (L4SERIAL).
+REM   KEYBOARD stays in the list so the cab is still playable if the board is
+REM   dead -- a silent loss of all input would be indistinguishable from a hang.
+setlocal
+set ROOT=C:\bt411
+set INSTALL=
+for /f "delims=" %%d in ('dir /b /ad /o-d "%ROOT%\BT411_*" 2^>nul') do (
+    if not defined INSTALL set INSTALL=%ROOT%\%%d
+)
+if not defined INSTALL goto noinstall
+powershell -NoProfile -ExecutionPolicy Bypass -File "%ROOT%\podkit.ps1" -Content "%INSTALL%\content" >nul
+cd /d %INSTALL%\content
+set L4CONTROLS=RIO:COM1,KEYBOARD
+set BT_CTRLMAP_LOG=1
+set BT_GLASS_LOG=1
+set BT_LOG=podrio.log
+start "" ..\build\Release\btl4.exe -egg PODTEST.EGG
+exit /b
+:noinstall
+echo No BT411_* folder found under %ROOT%.
+exit /b 1