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

ACU: more care when setting up go_to #768

Merged
merged 2 commits into from
Oct 14, 2024
Merged

Conversation

mhasself
Copy link
Member

@mhasself mhasself commented Oct 4, 2024

Description

ACU motion is initiated in a more carefully ordered way (clear_faults, start move in one axis, start move in next axis...).

Motivation and Context

This responds to odd errors seen on the LAT (a while ago) and on SATP1 (recently). Not clear that these fixes will resolve those issues, but it's quite possible.

How Has This Been Tested?

Tested on SATP1.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

This may explain some instances seen on LAT where a go_to leads to
"Irregularity during motion!" error.  The deeper symptom is that the
Preset position appears to not take effect (the "commanded position"
does not update).  So perhaps either an outstanding fault, or a side
effect of clear_faults, prevents the position from updating.
This is part (2) of trying to avoid errors where the http connection
is closed or does not reply, when initiating a move.
@BrianJKoopman BrianJKoopman merged commit 505a642 into main Oct 14, 2024
5 checks passed
@BrianJKoopman BrianJKoopman deleted the mhasself/acu-strict-order branch October 14, 2024 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants