Hi colleagues !
What is the correct way to add secondary equipment parameters to primary equipment faceplate trend zone?
Hi Bradley !
To speak more precisely, our Meters and ControlValves are separate DFBs with separate DDT data structures at PLC level. This leads to create two equipment types: one for Meter with PV and SP items and one for ControlValve with OP and FB items.
What i'm trying to achieve is to combine two equipment types in one common faceplate. For tags i've used SecondaryEquipment association built-in selection adorner. For trends it seems to be more complicated since _InfoTrend_PALoadTask function doesn't support secondary equipment. Probably there is a trick how to create an alias to avoid direct cicode modification and also to avoid Meter and ControlValve binding at equipment database level.
Actually there was a nice feature in LibEquip, where we could configure an individual .pav file for each equipment, which would load if file exist.
BR
pf
Hi Bradley !
To speak more precisely, our Meters and ControlValves are separate DFBs with separate DDT data structures at PLC level. This leads to create two equipment types: one for Meter with PV and SP items and one for ControlValve with OP and FB items.
What i'm trying to achieve is to combine two equipment types in one common faceplate. For tags i've used SecondaryEquipment association built-in selection adorner. For trends it seems to be more complicated since _InfoTrend_PALoadTask function doesn't support secondary equipment. Probably there is a trick how to create an alias to avoid direct cicode modification and also to avoid Meter and ControlValve binding at equipment database level.
Actually there was a nice feature in LibEquip, where we could configure an individual .pav file for each equipment, which would load if file exist.
BR
pf
