fix realtive movement#1174
Open
kuh0005 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request enhances the
AxoCmmtAsdrive control logic by improving how the end position of relative moves is tracked and validated. The main changes involve adding a new process variable for the expected end position and tightening the position-reached condition to ensure the axis is within the configured window.Drive move logic improvements:
MC_MoveRelativeEndPosition_PVto store the expected end position for relative moves in theAxoCmmtAsclass.MC_MoveRelativeEndPosition_PVto the sum of the current position and the move distance when initiating a relative move, ensuring accurate target tracking. [1] [2]InPositionWindowofMC_MoveRelativeEndPosition_PV, improving move accuracy and safety.