-
Notifications
You must be signed in to change notification settings - Fork 16
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
K1 Optics encdiff stats #144
Conversation
All three are running with a buffer of a thousand right now, but do you think there is any benefit to them being larger? |
Left this running over night and it never exceeded cycle time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
);*) | ||
); | ||
|
||
fMR1K1PiEncoderPosDiff := M16.nEncoderCount - (M16.Axis.NcToPlc.SetPos - M16.stAxisParameters.fEncOffset) / 0.00244; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nrwslac can you double check with me that I am using the correct denominator here before I merge? I got it from the Scaling Factor Numerator for the stage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Confirmed 0.00244 is the MR1K1 Bend Pitch Scaling Numerator.
I thought I might get lower RMS over a longer interval; it wasnt the case, so no, I think 1000 is good. |
Description
Changed m_pi buffer size to 1000 and uncommented
Added encdiff stats for M1K1
Motivation and Context
https://jira.slac.stanford.edu/browse/ECS-6173
How Has This Been Tested?
Running on rixs-optics, haven't seen any errors related to going over cycle time
Where Has This Been Documented?
Screenshots (if appropriate):
Pre-merge checklist
Always Newest
pre-commit
(alternativelypre-commit run --all-files
)