You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:.OFF
field.PROC
fieldThe 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:The text was updated successfully, but these errors were encountered: