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
Note: currently no version appears to have the looping working, with the motion platform appearing to glitch out for traces >= 5 minutes long. Functionality is still good for traces shorter than 300 seconds long. This is a separate issue, but in current operation this issue may also be made worse with issue #44 as the robot tends to crash if the UrScript file is not completely generated.
Update - most recent commit bc16b34 has resolved this for 6DoF robot only - so when 6DoF robot is used you can now run traces >5 minutes. Note there is an unavoidable time gap between these 5 minute segments as the next packet of information is sent to the robot controller.
No description provided.
The text was updated successfully, but these errors were encountered: