Equipment Help in SA Templates

Hi Chris,


Yep, OK, then I would definitely go with the approach of using a custom meter template, with the default PV being your "SEL". Given your statements above, this would bind to the controller itself, as you have complex logic dictating its behaviour. A and B can just be additional signals, and I would take advantage of the prefix feature so its easy to bind up to meters. It looks like Practical range and Optimal range would be the same for all signals, so you could define the extra ones for your A and B signals as calculated variables and just point them to your main PV's OR and PR's -to save any need for configuration.
You can set up individual fault alarms on APV and BPV, and there is no problem putting a high diff alarm either on PV. These will all show up in the Info Zone etc. You could also set up a bit to indicate which is active source for SEL and put that on the faceplate.

The trickiest part I see here is the alarm limits on SEL. Are they dynamic? Or is it a case that one instance would use LL, L and another instance H, HH? If they are not dynamic, then you can either create two template types - or override per instance.
If they are dynamic, then I think that might be a trickier, mainly at the presentation layer of the composite genies. In general the limit markers are driven from the configuration of the workspace DefaultPLCLimits parameter or the PLCLimits equipment runtime parameter. Eq runtime params cannot be override at runtime. The one thing I would point out is that if you only need, say, upper alarm limits, then use the value of -1 to stubb out the lower limits. This is currently not documented, but we fixed that for 2018 R2. For PLC Alarm Limits, we have re-written the help for this topic for 2018 R2 as we found people were struggling with it.

In terms of parameters for workspace (SA) projects checkout the topic : Parameters > Parameter Reference > Template Parameters > Situational Awareness Parameters.

Cheers,

bradley

Hi Chris,


Yep, OK, then I would definitely go with the approach of using a custom meter template, with the default PV being your "SEL". Given your statements above, this would bind to the controller itself, as you have complex logic dictating its behaviour. A and B can just be additional signals, and I would take advantage of the prefix feature so its easy to bind up to meters. It looks like Practical range and Optimal range would be the same for all signals, so you could define the extra ones for your A and B signals as calculated variables and just point them to your main PV's OR and PR's -to save any need for configuration.
You can set up individual fault alarms on APV and BPV, and there is no problem putting a high diff alarm either on PV. These will all show up in the Info Zone etc. You could also set up a bit to indicate which is active source for SEL and put that on the faceplate.

The trickiest part I see here is the alarm limits on SEL. Are they dynamic? Or is it a case that one instance would use LL, L and another instance H, HH? If they are not dynamic, then you can either create two template types - or override per instance.
If they are dynamic, then I think that might be a trickier, mainly at the presentation layer of the composite genies. In general the limit markers are driven from the configuration of the workspace DefaultPLCLimits parameter or the PLCLimits equipment runtime parameter. Eq runtime params cannot be override at runtime. The one thing I would point out is that if you only need, say, upper alarm limits, then use the value of -1 to stubb out the lower limits. This is currently not documented, but we fixed that for 2018 R2. For PLC Alarm Limits, we have re-written the help for this topic for 2018 R2 as we found people were struggling with it.

In terms of parameters for workspace (SA) projects checkout the topic : Parameters > Parameter Reference > Template Parameters > Situational Awareness Parameters.

Cheers,

bradley