Concept illustration—not a photograph of ArmSoM hardware.
A kiosk can show a perfect image and still fail its first real interaction: the touch coordinates may be rotated, the application may not start after reboot, or the interface may become unusable when its server is offline.
The ArmSoM Sige3 documentation identifies the board as an RK3568B2 platform with HDMI and MIPI DSI display interfaces. These provide options for evaluating a compact interface terminal, but the selected panel and software still need their own validation.
1. Document two connections, not one
Record the display interface and the touch-controller interface separately. A display cable does not necessarily carry touch input.
For an embedded panel, verify the exact connector, pin assignment, power requirements and image support before connecting it. Follow the hardware documentation and remove power before changing internal connections. Do not assume that another board’s panel configuration applies unchanged.
2. Validate the screen before the kiosk application
Use a simple test screen with clearly marked corners and a readable grid. Confirm resolution, orientation and legibility at the intended viewing distance.
Then test touch input at the center, edges and corners. If you rotate the display, verify the input coordinates again: image rotation and touch mapping should be checked independently.
3. Exercise the complete user journey
Test the actual interface rather than only a desktop demonstration:
- Does it launch automatically after a normal reboot?
- Can users reach every important control?
- What happens when a backend request fails?
- If screen blanking is enabled, does input recover correctly afterward?
- Can a technician exit to a documented maintenance path?
Avoid putting administrative credentials into a public kiosk session. Separate routine operation from maintenance access.
4. Define acceptance in user terms
Record startup time, response to a typical touch action and behavior during the intended operating period. State the image, display, touch controller and application version alongside those observations.
Are you evaluating Sige3 for a local equipment panel or a browser-based kiosk? Share the display model and connection method first; they help narrow the integration questions.