Update:
I have gotten around my immediate problem, by reverting to using the secondary control interface to send scripts, rather than using the dashboard server to ‘play’ (the same) programs.
I keep the dashboard port open, which works well for detecting when the program (or script) has finished.
I still don’t understand why ‘play’ often returns ‘Failed to execute: play’ when I use the latter technique.
If the robot is off it will cause the failure, but since the secondary client interface works that is not your issue.
No program loaded is anothet
If the current program is undefined could cause the issue you are facing.
I have experienced that if your program require a Automove before starting, and your current pose is “far away”(probably closer to another inverse kinematic solution), the Play was failing. Avoiding this can be done by having a relative Waypoint as the first thing in your program.
Thanks. I wondered about that “Automove”… when I start a program with Polyscope, I always have to move to home first…
Is there a setting for that?
Interesting, that I do have one short program that seems to work usually, and it just backs the tool along it’s Z axis by 100mm, using a relative move.