Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looping not working - test different versions #50

Open
ChandrimaSengupta opened this issue Oct 15, 2024 · 2 comments
Open

Looping not working - test different versions #50

ChandrimaSengupta opened this issue Oct 15, 2024 · 2 comments

Comments

@ChandrimaSengupta
Copy link
Collaborator

No description provided.

@ChandrimaSengupta ChandrimaSengupta changed the title Looking not working - test different versions Looping not working - test different versions Oct 15, 2024
@akac0297
Copy link
Collaborator

akac0297 commented Nov 28, 2024

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.

@akac0297
Copy link
Collaborator

akac0297 commented Feb 4, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants