The one thing that makes remote support possible
A stable network path to the processor. Not to the screen, to the controller. If the controller is on a network we can reach, we can see the input status, the mapping, the brightness settings, and the receiving card status. That covers roughly 70 percent of the faults we get called about.
What we ask the client to prepare at install time
- A fixed IP or a DDNS name for the processor.
- A VPN or a port-forward for one specific port, documented.
- A phone on a tripod pointing at the wall, for the duration of the call.
- The commissioning photos and the cabinet numbering plan.
What we cannot fix remotely
Anything that requires touching a module, a cable, or a power supply. A dead pixel cluster, a loose ribbon, a burnt connector. Those need hands. What we can do is make sure the hands are sent with the right part and the right instruction, so it is one visit instead of three.
A real example
A wall in West Africa showed a horizontal band of flickering cabinets. Remote access showed the receiving cards were fine and the input was stable. The pattern moved when we changed the refresh setting, which pointed to a cable. We shipped one cable and a spare card. The client's own electrician swapped it in twenty minutes with our engineer on a video call.
The limits to be honest about
Remote support depends on the client's network, and some sites will not allow inbound access. In that case, plan for a local partner who can be trained once. Training a local technician for two days is cheaper than two flights, and it builds a relationship that lasts.
What this changes commercially
It changes the spare parts strategy. If you can diagnose remotely, you can hold fewer spares locally and ship the exact part. That is why we recommend a small kit plus remote access rather than a large stock that sits unused.