VR tracking · offline connection planning
Plan a documented base-station synchronization route
Build a logical Lighthouse 1.0 mode or 2.0 channel worksheet, distinguishing optical sync, approved sync cables and duplicate channels.
Your setup and observations
Use this for an already identified station generation. It produces logical synchronization requirements, not a room layout or coverage estimate. Only the first N channel fields apply to N active 2.0 stations.
Work through a concrete example
Example: for two documented 1.0 stations, declared unobstructed optical synchronization yields b/c; a declared approved sync-cable route yields A/b. For two 2.0 stations, entering channel 3 twice identifies a collision. Changing the second to an unused channel creates a logical channel plan, not a coverage guarantee.
Documented 1.0 consumer case
A single 1.0 station uses mode A. Two use b/c with unobstructed optical synchronization or A/b with an approved synchronization cable, as described in the linked HTC instructions. No three- or four-station 1.0 plan is supplied.
2.0 channels are not a sync cable
This worksheet supports up to four active 2.0 stations per consumer tracked set and requires distinct channel IDs from 1–16. The 1.0 route/cable/visibility fields are ignored for a 2.0 result. Actual tracked-device support remains a separate prerequisite.
No placement or safety certification
No room coverage, beam geometry, mounting, range or tracking-accuracy result is inferred. Do not open stations, inspect laser emissions or use their firmware port as a normal tracking-data route. Follow exact current manufacturer instructions.