Start with a simulated room#
Open Lab administration → Interfaces. Select the room or global scope before editing. An interface instance combines a type/codec, transport and configuration. A room route selects where a channel’s output goes; creating an instance does not automatically route every channel to it.
Use the mock devices and browser outputs for a first rehearsal. All values in this application are simulated. The fictional examples do not qualify a physical device or its clinical measurements.
Configure and test an instance#
Choose New interface, select a type and give the instance a distinct ID and readable name. Set the transport and its required fields, then save. Review permissions and network policy before enabling a listener or remote destination. Start and test the instance using its controls; inspect live state and received/delivered frames.
If another administrator changes the saved configuration, a revision conflict can preserve your unsaved draft. Reload the saved configuration and explicitly discard or reapply the draft after comparing it. Do not assume the last click overwrote somebody else’s edit.
Pair a browser screen#
Create or select a monitor-screen instance and request its pairing code. Open the lab’s pairing page on the intended browser and enter the displayed six-digit code. Check that the screen is connected, then send an explicit simulated test output. Pairing does not sign the screen into the administrator account.
Pairing is tied to the selected host and instance. Revoke it when the screen changes role or leaves the lab. A QR/code shown on the administrator screen is sensitive access material; avoid including it in public screenshots.
Route channels#
Inspect the Site room’s output routes and the session setup compatibility view. Map each relevant channel to the intended screen, speaker, webhook or other configured output. Keep the deliberate console fallback visible when no destination is selected. A wildcard audit route may receive matching output in addition to a primary destination; it is not proof of physical delivery.
Test the actual destination before a learner session. A host accepting an output and an interface delivering it are separate outcomes. Read failures and live health in the console.
Extend a vendor format#
A declarative mapping is the smallest option when a bounded text/JSON format fits existing rules. Use a plugin when you need a new codec, transport or feature. The fictional Acme walkthrough implements the same small protocol as data and as a plugin, with exact simulated expectations.
Troubleshooting#
| Problem | Next action |
|---|---|
| Connected but no output | Check room scope, instance enabled state, primary channel route and the actual delivery report. |
| Network request denied | Inspect the administrator’s listener/egress policy and exact destination. A configuration field does not grant permission. |
| Browser pairing fails | Check code/host/expiry and whether the instance is still present; request a fresh code when needed. |
| Reading looks stale | Some simulated displays intentionally update only on a new reading. Test the declared device behaviour. |
| Mapping parses the wrong value | Verify parameter code, UCUM unit, message kind and literal sample timestamp. Connectivity alone does not validate a codec. |