Question about standard muxed and standard non-muxed property names
Question ariesed during discussion of the PPOS Property API together with @a.walter, @b.peter and @r.hari
For devices, there is often the situation that they can be either operated multiplexed, triggered by Timing-Events or non-multiplexed, triggered by some manual-move property or in local mode.
This creates the need of having both, multiplexed and non-multiplexed Setting and Acquisition Properties.
For PowerSupply e.g., there is Acquisition
(muxed) and DCValueAcq
(non muxed)
For PPos we are currently planning to have Setting
(muxed) and SettingDirect
(non muxed)
Since the use-case actually is the same for probably many more devices, it would be nice to use some standard-naming convention for these properties. (E.g. always call them AcquisitionMuxed
and AcquisitionNonMuxed
?)
This seems to collide with the wish to always have one setting property, called Setting
, to be used by LSA. (Maybe we should have SettingLSA
instead?)
Edit: For Acquisition properties, it actually seems to be possible to only use a single, multiplexed Acquisition Property for both, multiplexed and non-multiplexed values (Here a demonstrator Fesa class and its DU). Though the problem remains for the property Setting
for which that is not possible (a muxed setting prop throws an error when called with non-muxed context). And in any case, standardization is required for this issue.