The essentials
POI content-transition testing checks whether the intended content is selected, played, and stopped after a location event arrives. This is a plan that has not yet been executed. CubeSignP5 support and behavior on actual equipment have not been confirmed. The proposed sequence is to review the supplier interface, define playback rules with simulated events, and then verify them in a real robot environment.
Key takeaways
- This robot-display transition test plan has no measured results.
- Examine duplicate, delayed, and exit events as well as POI entry.
- Align the time reference of event logs and screen recordings before comparison.
Define the test scope first
The robot model, location interface, player version, and supported transition functions have not yet been selected. Safety verification of robot movement control is separate from content playback testing.
Agree on the expected screen behavior
The following playback rules are for discussion with the operator. Testing follows agreement on expected behavior; all results currently remain untested.
| Input | Expected behavior to agree on | Current result |
|---|---|---|
| POI entry | Select the assigned content | Not run |
| Repeated delivery of the same event | Determine whether to prevent duplicate restarts | Not run |
| POI exit | Define when to return to default information | Not run |
| Event past its validity period | Determine whether to ignore outdated events | Not run |
Keep event and screen records together
Plan to collect event occurrence, receipt, and playback times alongside screen recordings. Equipment details, logs, captures, and benchmarks are not yet available. Exclude internal implementation and customer-site information when publishing results.
What changes and where it applies
This plan examines playback rules for location events. Performance differences or improvements over earlier products have not been measured.
AI Cube’s perspective
Separating content-selection time from the time it appears on screen may help locate an issue in location detection, event delivery, or the player.
Technical considerations
Turn playback rules into test inputs and expected outputs, and specify how record timestamps will be aligned. This prepares a common basis for comparing events with screen changes.
Business and operations
Review both normal-operation demonstrations and operational tests that include exceptions. This plan can support discussions about site responses before delivery conditions are agreed.
Related products and solutions
Sources and reference dates
- MQTT Version 5.0 — reference for event delivery conditions ↗OASIS · Source date 2019-03-07 · Accessed 2026-09-10
Evaluating a deployment?
Tell us about your installation and operating conditions so we can discuss relevant products and the scope of a PoC.
Technical and PoC inquiries ↗