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

decoupling st1k4 from st3k4 when st3k4 is out and tune im2k0 lag para… #122

Merged
merged 1 commit into from
Jun 18, 2024

Conversation

tongju12
Copy link
Contributor

…meter

TMO requests to decouple ST1K4 with ST3K4 while ST3K4 is OUT.
When ST3K4 IN, ST1K4 IN
When ST3K4 OUT, ST1K4 is free to be IN or OUT
IM2K0 has lag monitoring error, tune the parameter

Motivation and Context

TMIO requests it to use ST1K4 to block beam when ST3K4 is out

How Has This Been Tested?

Nick and I tested by toggling a boolean instance, ST1K4 is working as expected but not test with the real ST3K4 moving(ST3K4 is not working back then due to RP work.
IM2K0 moves around 10 times without error

Where Has This Been Documented?

(https://jira.slac.stanford.edu/browse/ECS-5586)

Screenshots (if appropriate):

Pre-merge checklist

  • Code works interactively
  • Code contains descriptive comments
  • Test suite passes locally
  • Libraries are set to fixed versions and not Always Newest
  • Code committed with pre-commit (alternatively pre-commit run --all-files)

@tongju12 tongju12 requested review from ZLLentz and NSLentz June 18, 2024 21:24
eEnumSet := ENUM_EpicsInOut.OUT;
END_IF
*} END_IF
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As always, it's ok to just delete these lines (we have version control to bring them back)

@@ -1464,7 +1464,7 @@ Drive Status 4 (manually linked):
</Drive>
<Controller Name="Ctrl" CtrType="2">
<CtrPara PriorControlFactor="1">
<PosDiffControl Range="1"/>
<PosDiffControl Range="1" Time="0.1"/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which parameter is this? Position lag monitoring time, changing from "default" to 0.1s?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it was 0.02s, now it is 0.1s

@@ -1462,7 +1462,7 @@ Drive Status 4 (manually linked):
</Drive>
<Controller Name="Ctrl" CtrType="1">
<CtrPara PriorControlFactor="1">
<PosDiffControl Range="0.1"/>
<PosDiffControl Range="0.2"/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't noted in the PR text but Tong has mentioned to me previously that this fails to complete a move once in a while with no obvious issues- widening the range here will probably mitigate this.

Copy link
Member

@ZLLentz ZLLentz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a quick note here: as implemented, ST1K4 will need to be manually pulled by TMO when ST3K4 is pulled. I assume they know this and have signed up for the responsibility.

Only small notes in the diff here, it would be ok to merge as-is I think.

@tongju12 tongju12 merged commit d5d7d34 into pcdshub:master Jun 18, 2024
9 checks passed
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

Successfully merging this pull request may close these issues.

2 participants