What problem does it solve? Engineers maintaining the HT9045 IC Test Handler struggle to interpret Shuttle 1/2 state machine behavior (Do_Auto_SHT1/Do_Auto_SHT2) when diagnosing jams, floating ICs, residual material, or sensor failures in the Borland C++ Builder codebase. ## Core Features & Use Cases - State Machine Reference: Maps every case value (1, 100, 200, 400, 2300, etc.) in AutoSHT1Task/AutoSHT2Task to left-move, right-move, barcode, floating, and retry branches. - Mode-Based Sub-Switches: Documents CheckShuttleOutputHasICError and CheckShuttleSensorBroken_1/_2 logic keyed on TestIF.iTestMode for residual IC and sensor-broken detection across 16+ test modes. - Debugging Entry Points: Provides a step-by-step diagnostic order for stuck shuttles, retry loops, and safety interlocks with InArm/OutArm/Index. - Use Case: When a Shuttle 2 right-move hangs, read AutoSHT2Task's live value, locate the case in the flow map, and follow the documented branch to identify whether the cause is a floating check, 2D barcode scan, or HTTP retry path. ## Quick Start Ask the AI to explain why Shuttle 1 is stuck at case 400 in Do_Auto_SHT1 and what retry path it follows.
