You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seen on several new robots - the runstop button when using the web interface is extremely flaky, works probably less than half the time, and when it fails usually freezes the robot. Notably, cycling the physical runstop button on and off again resolves the issue and the interface becomes usable again almost always.
Failures can be triggered in many different ways
Clicking too fast usually causes a failure
Seems possibly more reliable on localhost and less reliable on a mediocre wifi connection
Often (but not always) you can hear the motor whine turn off, as it would when runstopped; but neither the physical button nor the interface button indicate a runstop. Interface becomes unresponsive and comes back after the physical runstop is cycled.
The text was updated successfully, but these errors were encountered:
Seen on several new robots - the runstop button when using the web interface is extremely flaky, works probably less than half the time, and when it fails usually freezes the robot. Notably, cycling the physical runstop button on and off again resolves the issue and the interface becomes usable again almost always.
Failures can be triggered in many different ways
The text was updated successfully, but these errors were encountered: