The cdsRampMuxMatrix part, which is new to RCG 2.8 (and updated in 2.8.3), allows for pre-writing a new matrix and then loading it with a specified ramp time from the current values to the new ones.
This part has been swaped into the PD_DOF_MTRX position in the main LSC library part in:
USERAPPS/lsc/common/models/lsc.mdl
The h1lsc model was rebuild/installed/restarted, and has been tested and seems to be working as expected.
The channel interface to the matrix has now changed. The readback channel retains the same form as the non-ramping matrix, but new channels are added to write the new matrix:
|
LSC-PD_DOF_MTRX_ |
current setting readback |
|
LSC-PD_DOF_MTRX_SETTING_ |
new setting value |
|
LSC-PD_DOF_MTRX_RAMPING_ |
indicator that element is ramping |
| LSC-PD_DOF_MTRX_TRAMP | ramp time |
| LSC-PD_DOF_MTRX_LOAD_MATRIX | load new values |
Scripts/guardian will need to be modified to write new matrix values accordingly.
The MEDM screens for the input matrix were updated with a new interface for the matrix. The updates screens are (screenshots below):
USERAPPS/lsc/common/medm/LSC_CUST_PD_DOF_MTRX_VAC.adl
USERAPPS/lsc/common/medm/LSC_CUST_PD_DOF_MTRX_AIR1F.adl
USERAPPS/lsc/common/medm/LSC_CUST_PD_DOF_MTRX_AIR2F.adl
USERAPPS/lsc/common/medm/LSC_CUST_PD_DOF_MTRX_CM.adl
Each matrix element is split vertically, with the readback of the current value at the top, and the new value at the bottom. The boxes are colored to indicate the state:
- new different setting not yet applied
- ramping to new value
- current setting is non-zero
The "Kissel buttons" on the main LSC_OVERVIEW screen did not have to be modified since the readback channel did not change.
