Hello,
I am currently using a UR7e robot with Polyscope 5.25.0 in remote_control mode.
My workflow involves powering on the robot, releasing the brakes, and then loading and playing programs using Dashboard Interface commands. Concurrently, I have a primary interface client connected to listen for all messages returned by the robot.
I’ve observed an issue where the primary interface sometimes fails to send the A0C0 PROGRAM_XXX_STARTED message when a program begins execution.
Similarly, when the robot stops, particularly when a halt popup appears (e.g., a error message), the primary interface occasionally does not send the A0C0 PROGRAM_XXX_STOPPED message.
These primary messages are critically important for my application. I rely on them to accurately determine when the robot has started or stopped, which in turn dictates whether I need to collect electrical data via RTDE for predictive maintenance purposes.
Is this a bug?