One system has several independent layers
A headset or accessory may appear in SteamVR without using base-station optical sensors. A USB socket, radio receiver, station channel and application body role each solve a different problem. Start with the exact manual and identify the affected device’s tracking technology. This guide concerns tracking connections, not a new wired-PCVR display/USB suitability calculator.
Optical generation is a declared capability
Base Station 1.0 and 2.0 do not form one combined optical setup. A 1.0-only tracked device does not gain 2.0 support from a different cable or receiver. A device supporting both can use a supported single-generation set. The generation checker identifies this intersection for one declaration; it does not maintain a complete headset database or validate a mixed-origin setup.
Radio channels are not USB ports
Count exact compatible receiver channels, then subtract channels already occupied within that total. Requested devices are additional demand. One multi-channel Tundra receiver can expose more than one channel, so a physical dongle count alone is misleading. Do not invent two spare headset channels without exact evidence, or unpair a working controller to make a count fit.
Do not combine receiver families
The bounded receiver worksheet keeps a classic-compatible pool separate from one Ultimate dongle. Ultimate uses camera-based tracking and its own supported radio route; spare capacity in that family cannot serve a classic optical tracker by arithmetic. Each pool needs its own exact device, receiver and runtime support evidence. A logical free-channel label is not a hardware address or pairing command.
Plan synchronization after identifying the stations
For the documented two-station 1.0 case, optical synchronization and approved-cable synchronization use different mode pairs. The 2.0 worksheet instead checks distinct active channel IDs. It is bounded to four station rows and does not turn sixteen channel identifiers into sixteen supported simultaneous stations. It never calculates room coverage, beam geometry, mounting safety or tracking accuracy.
Paired does not mean tracked or assigned
For a wireless receiver path, first record the manual-defined pairing indication, then runtime presence and valid pose, then application detection and the intended role. An unknown observation remains unknown. If a paired device is missing from the runtime, collect receiver/runtime evidence. If the runtime pose is valid but an app role is missing, changing optical hardware is not the next supported inference.
Coordinate alignment remains a runtime job
Independently tracked devices can use different coordinate spaces even while all local observations look valid. Free runtime tools such as SpaceCalibrator address specific alignment jobs; this site neither replaces them nor measures calibration. Stop relying on an unresolved tracking setup for movement, and follow the exact manufacturer/app guidance. Do not inspect laser emissions, open stations, disable protections or apply generic firmware/reset procedures.