With a channel access link via OMSL=closed_loop/DOL=OTHER:PV CPP (CA link that causes processing of the record), we can automatically couple non-TwinCAT/ads-ioc PVs to a TwinCAT PLC.
Proposing some new syntax:
pv: TWINCAT:PVNAME
link: OTHER:PV
Additional thought needs to go into how to deal with adding alarm severity information - to determine the validity of the value. A 'linked structure' provided in lcls-twincat-general could take care of it generically, but there'd have to be a structure for each type (ST_LinkedPV_Int, ST_LinkedPV_Float, etc.), I think... (thoughts, @ZLLentz @n-wbrown?)
With a channel access link via
OMSL
=closed_loop
/DOL
=OTHER:PV CPP
(CA link that causes processing of the record), we can automatically couple non-TwinCAT/ads-ioc PVs to a TwinCAT PLC.Proposing some new syntax:
Additional thought needs to go into how to deal with adding alarm severity information - to determine the validity of the value. A 'linked structure' provided in
lcls-twincat-general
could take care of it generically, but there'd have to be a structure for each type (ST_LinkedPV_Int
,ST_LinkedPV_Float
, etc.), I think... (thoughts, @ZLLentz @n-wbrown?)EPICS db example from @ghalym: