Hey everyone,
I’m working on an automation cell layout where we are testing collaborative robots interacting directly with mobile device screens using soft-tipped stylus end-effectors. Part of our setup involves using a local browser view to test interface layouts and script-based triggers before deploying the physical robot paths.
The issue I’ve run into over the past couple of days is severe UI lag and sporadic lockups on our Teach Pendant’s interactive display. It seems to happen specifically when we pull external interactive scripts into the preview window. For instance, if I try to mirror a localized testing platform where users play game environments or execute custom automation script parameters, the background WebKit engine on the controller completely chokes. The interface stops responding to touch inputs for up to ten seconds, and occasionally it completely crashes the custom screen layer, forcing a hard restart of the PolyScope interface.
It feels like the embedded browser engine in the control box is heavily struggling with modern JavaScript executions or rapid frame-rate refreshes that are typical of touch-emulation test tools.
Has anyone else experienced system-wide lag or memory crashes when displaying highly dynamic, script-heavy web interfaces or interactive dashboards on their pendant? Are there any specific limitations on what the internal web view can execute without freezing the rest of the PolyScope UI thread, or is it better practice to host these dynamic environments completely on a separate client PC and communicate with the controller strictly via RTDE or socket connections?
Any troubleshooting advice or insights on handling embedded web interface stability would be awesome!