softMotorTf.db

[nmarks99]

I like the ability softMotor.db gives you to configure a "Soft Channel" motor record at runtime, however I find it very limiting on its own since calcout records are used which can only write their outputs to a single PV. For example, say I wanted the soft motor to drive three other motors together. There is no way to tell the soft motor to write its output to three different PVs.

Here I propose softMotorTf.db as an alternative to softMotor.db which uses transform records instead of calcout records for the $(P)$(SM)CalcFrwd and $(P)$(SM)CalcStop calculations. It also removes the additional scalcout records in softMotor.db which are used to copy links to the underlying calc records in favor of having the user configure the records directly. To configure an instance of softMotorTf.db the user must configure the readback(calcout), moving(calcout), output(transform), and stop(transform) calculations.

Screens for MEDM and CaQtDM are also included which are slight variations of the softMotor screens. The transform and calcout screens are used from the calc module.

[keenanlang]

Would you mind running

phoebus -main org.csstudio.display.converter.medm.Converter softMotorTFConfig.adl
phoebus -main org.csstudio.display.converter.medm.Converter softMotorTFs10.adl

And putting the resulting files in stdApp/op/bob/autoconvert ?

[nmarks99]

Done 57d1f37