LOCUS · Room Live

Tilt 90°

Turn 0°

LOCUS error–

Plain trilateration–

Height (est · true)–

Anchors heard–

How is the dot moved?

Sync phone ↔ laptop

Phone page: phone.html (scan the QR in the corner of the view). Walk with the phone, watch the big 3D view here. Direct device-to-device link; settings sync both ways, each device keeps its own camera angle.

Not connected.

Phone sensors need HTTPS (this GitHub Pages link is). Same Wi-Fi is the most reliable; across different networks the link may fail (no relay server).

Space

Width (m) 5.0Depth (m) 4.0

Ceiling height (m) 2.7

Partition wall with door (NLOS test)

Anchors 5

Phone height

Held at 1.30 m

System knows the height

The engine solves position on the floor plane, so it converts every 3D range to a horizontal one using the height difference. If the assumed height is wrong the error grows — turn System knows the height off to see it. With ≥4 anchors at different heights LOCUS also estimates your height (shown top-left of the view).

Anchors (tap to select · drag in Top/Angled view to move)

Radio model

Noise model Noise level4 dB Packet loss 10%

RSSI @ 1 m (dBm)Path-loss n

Trust scorer

Inject faults

Select an anchor in the Space tab or tap one in the view, then:

LOCUS median–

Trilateration–

Kalman–

LOCUS 95%–

Trilat. 95%–

Samples0

Error against the phone's own dead-reckoned path (the "truth" here). Phone drift is not counted — see the honesty notes below.

Anchor	RSSI	Range	Trust

What is real and what is not. The motion of the dot is real (your phone's step counter and compass). The radio signal is synthetic: LOCUS computes the RSSI the anchors would hear from the phone's true position, adds noise, and the engine localises from that. "Truth" is dead-reckoned from the phone, so it drifts over minutes; use short walks, press Align often. Real BLE hardware is the Staff app's Live BLE tab.