# NXSLED demonstration and validation kit

Reusable test scripts · Version 1.0 · 2026-09-12

Use on an authorized, isolated demonstration system. These protocols create evidence; they are not reports of tests already completed. Agree application-specific pass criteria with the customer and selected manufacturers before testing. Do not disable safety controls or disrupt production systems to produce a demonstration.

## Common test record

For every run record: project and test ID; date; operator and reviewer; exact display/processor/source models and serial references; firmware; cabling topology; resolution/frame rate; brightness settings; relevant software versions; viewing positions; environmental conditions; input content version; agreed pass criterion; observed result; evidence file; limitations; corrective action; retest result.

Allowed result values: **Not tested / Pass / Fail / Blocked / Not applicable with reason.** A customer preference is recorded separately from a measured hardware result.

## 1. Bring-your-content intake and privacy

1. Ask the customer for an approved, representative sample and one decision the demonstration should answer. Prefer synthetic or redacted material where possible.
2. Record content owner, permitted use, authorized attendees, access location, retention/deletion date and whether recording is allowed. Marketing reuse is a separate permission.
3. Do not request passwords by email or place credentials in presentation files. Use an approved authenticated sharing method when needed.
4. Check the file with the organization's approved security process before opening; do not bypass blocked macros or endpoint controls.
5. Use a segregated test source with notifications suppressed. Do not connect a public demo wall to live customer camera, healthcare, police or financial accounts.
6. Run the agreed task at the expected scale and seats. Capture only permitted evidence.
7. Return or remove content as agreed, including working copies, recordings and temporary exports. Record the action and any retained copy with its basis and restricted location.

**Intake fields:** content reference; owner; allowed display; allowed capture; marketing permission; deletion due; custodian; completion confirmation.

## 2. Daylight, legibility and comfortable output

**Question:** can the actual audience read the content and tolerate the appearance in the real room?

- Test approved slides, small text, gradients, dark scenes and natural imagery, not only vivid promotional video.
- Mark near, far and off-axis positions, including relevant seated/standing users.
- Repeat under measured/recorded available daylight, normal evening lighting and the intended shade settings; do not describe unlike conditions as a controlled comparison.
- Record display settings and any available calibrated measurement. If energy is measured, identify meter, interval and content; do not generalize a brief reading to an annual energy guarantee.
- Ask observers to read agreed content without prompting. Record errors, comfort feedback and the conditions where performance changes.
- Re-test the selected configuration after room finishes and lighting are installed.

Pixel-pitch guidance is a screening input, not a universal readability guarantee. [Planar viewing-distance reference](https://www.planar.com/media/439462/understanding-viewing-distance.pdf)

## 3. Podcast and camera compatibility

**Question:** does the complete camera-to-recording chain produce the required image in the planned framing positions?

1. Document camera, lens, focus distance, frame rate, shutter, exposure, sync, display settings and processor mode supported by the selected equipment.
2. Record a speaker with fine background detail, dark tones and motion at every intended camera angle and representative focal length.
3. Review recorded output for scanning/banding, moiré, skin tones, dropped frames and audio/video timing. The room's naked-eye appearance is insufficient evidence.
4. Repeat relevant conditions after any processor, camera, mode or firmware change. Keep a reproducible preset and a known-good sample.
5. Log limits: a pass applies to the tested chain and settings, not every future camera or shooting mode.

Camera shutter and LED refresh interaction is equipment-dependent; features such as ShutterSync have explicit supported hardware. Verify compatibility rather than promising every wall is camera-safe. [Brompton camera-timing reference](https://www.bromptontech.com/features/shuttersync/)

## 4. Gaming, simulation and multi-input performance

**Question:** is the entire signal path suitable for the intended interaction?

- Use the intended console or simulation computer and real application, display processor, switching path and controls.
- Record requested versus observed resolution/frame rate and any compromises caused by multiview, scaling, HDR or source switching.
- Use a documented measurement method for source-to-display response. Identify instrument, sample count and measurement limitations; manufacturer processor latency alone is not the total system latency.
- Test all intended simultaneous inputs, independent audio routes and user controls. Check four-player usability with actual participants, not only four visible windows.
- For two-sided systems, prove that each player's input and audio are independent. Validate physical support separately before suspending equipment or seating occupants beneath it.
- Compare results to the customer's written criterion. If no criterion or reliable method exists, record observed behavior without a numerical performance claim.

## 5. Operations incident and recovery

**Question:** can an operator identify the relevant condition and use the information to act?

1. Load synthetic multi-site camera/dashboard sources with a clearly identified test scenario.
2. Trigger a non-production event such as loss of one demo video input or a simulated network alert.
3. Ask the operator to identify the affected site, select relevant views and follow a documented escalation step.
4. Measure task completion and record missing/ambiguous information. Do not claim the display itself detects incidents unless that integration was built and tested.
5. Restore the input; confirm stale/frozen information is not mistaken for a current view.
6. Rehearse a permitted configuration restore on a test device with approved backup and rollback. Never erase a production controller to demonstrate recovery.

Public-safety, clinical and trading scenarios remain illustrative unless their authorized owners validate the complete operational system. This is not a certification for life-safety use.

## 6. Serviceability and operator handoff

- On de-energized or otherwise manufacturer-approved test equipment, a qualified technician performs an approved module/service task using the actual access approach.
- Record access equipment, tools, isolation method, time, personnel and any inaccessible item. Do not invent a replacement time from an unmounted sample.
- A different trained operator starts, switches and shuts down the system using the handoff card.
- Confirm approved configuration/firmware records and compatible spare references can be found without exposing credentials.
- Resolve documentation gaps before describing the procedure as repeatable.

## 7. Six short application scripts

| Application | Operator task | Evidence artifact |
|---|---|---|
| Boardroom | Start an authorized test call, share a real slide and return to default | Seat/readability record and control task result |
| Furniture | Change a fabric and save an approved product selection | Selection export checked against catalog |
| Remodeler | Revise a finish, show allowance effect from approved data and route approval | Versioned decision record; no invented price |
| Car dealer | Select valid options and hand off chosen configuration | Dealer-approved configuration export |
| Residential | Switch art → movie → sport → quiet/off without assistance | Operator task and comfort record |
| Production | Load scene, record sample, export and clear session | Recorded sample and deletion record |

For a 60–90-second published clip, show one complete task, disclose simulations, identify the tested configuration and obtain content/participant permissions. Editing must not hide a failed step or misrepresent elapsed time.

## 8. Specialty holds before demonstrations

**DJ lasers:** the requested four 6 W units remain a separately engineered and professionally operated option. Do not energize them for visitors until a qualified provider has verified product, show, venue and applicable approval requirements. FDA explains required reports and approval before higher-class laser shows may operate. [FDA laser-light-show guidance](https://www.fda.gov/radiation-emitting-products/home-business-and-entertainment-products/laser-light-shows)

**Sports:** use spatial mockups before live-ball use. Golf impact surfaces, basketball containment/padding and any exposed LED assembly require specialist review for the actual design.

**Pool lift:** use a dry, non-operating or manufacturer-approved demonstrator before offering a wet-area installation. Require coordinated mechanical, structural, electrical, drainage, weather and service reviews. A rendering is not a safety analysis.

**Exterior 90-degree display:** preserve the intended corner and show both target-viewpoint and off-axis behavior. Validate mounting, outdoor conditions, sign permissions and content rights before operation.

## Release checklist

- [ ] Defined question and pass criterion
- [ ] Authorized content and participants
- [ ] Equipment and settings identified
- [ ] Safe, non-production test environment
- [ ] Observed results retained, including failures
- [ ] Limitations visible in sales claims
- [ ] Customer feedback recorded separately
- [ ] Content handling completed
- [ ] Reviewer authorized the specific published claim