Set brick to calculate velocity profile #395
Merged
tomtrafford merged 1 commit intomasterfrom Feb 11, 2026
Merged
Conversation
…otion Program 4.0
coretl
approved these changes
Feb 10, 2026
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
2 participants
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.
These changes set the PV {BRICK}:ProfileCalcVel to YES, so the brick creates the Velocity profile based off the provided VelocityMode profile.
(Bluesky testing has been setting this to NO, and has then messed up motion for Malcolm scans).
This PV was added in pmac 2-6-0 and will become a minimum requirement for Malcolm with this change.
This change also stops Malcolm raising warnings about an incompatible motion program, when using Motion Program 4.0