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

Motor record does not process autosaved DIR/OFF properly on startup #73

Closed
ZLLentz opened this issue Mar 30, 2021 · 0 comments · Fixed by #76
Closed

Motor record does not process autosaved DIR/OFF properly on startup #73

ZLLentz opened this issue Mar 30, 2021 · 0 comments · Fixed by #76

Comments

@ZLLentz
Copy link
Member

ZLLentz commented Mar 30, 2021

This is usually not noticed, but causes a big issue if you've autosaved values for .DIR and .OFF.

What happens is that the displayed value is the unmodified raw value from the PLC after a boot. Your .DIR and .OFF fields display the autosaved values, but they are not applied to the .RBV field until the first record process. There are a few ways to process the record:

  • Request a move
  • Set a new (or the same) value to the .OFF field
  • Set 1 to the .PROC field

The first of which (request a move) results in very alarming behavior, where the motor position suddenly jumps in an instant!

I did a hacky fix at the bottom of ioc-lamp-motion's st.cmd for Adam:

dbpf("TMO:LAMP:MMS:01.PROC","1")
dbpf("TMO:LAMP:MMS:02.PROC","1")
dbpf("TMO:LAMP:MMS:03.PROC","1")
dbpf("TMO:LAMP:MMS:04.PROC","1")
dbpf("TMO:LAMP:MMS:05.PROC","1")
dbpf("TMO:LAMP:MMS:06.PROC","1")
dbpf("TMO:LAMP:MMS:10.PROC","1")
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 a pull request may close this issue.

1 participant