Equipment Help in SA Templates

Hi Chris,

A bit to digest there.

A couple of questions:
1. Is the RTD a single piece of equipment with 2 signals? Does each signal have (or need to have) more information such as practical range, optimal range, independent alarm limits etc?
2. Ideally how would you like it displayed to the operator on the screen?
3. Can each signal alarm? or just the synthesized average?

To give you an idea of what could be done, I'll make the assumptions of:
1. a single piece of equipment with two signals A and B and a synthesized Average signal - PV
2. Only the Avg signal has alarm limits and will alarm.

One technique you can do is create a custom meter template, based on our template. Use the PV item as your Average by changing it to a calculated variable and doing the avg between A and B. Create two additional variable items APV and BPV for your A and B signals. I name that to take advantage of the "prefix" feature of the meter composite genie templates. You can enable PLC based alarm limits for your PV (Average) if you don't want to use analog tag.
On a page you can drop down the standard meter, configure it as temp if you want. By default it binds to an item called PV. Alarms will trigger when the avg of A and B meet your defined limits of your PV variable. To get all 3 trends displaying I nthe info zone, configure the InfoZoneTrends parameter has Bas mentioned. InfoZoneTrends can be configured in 3 ways (the help only mentions 2 ways.. sigh) You can set it globally, by type or for a specific equipment instance. as the help describes how to do the fist two, I'll describe how to do it per equipinstance. Add a new Runtime Equipment Parameter via Citect Studio (System Model > Equipment > Runtime Parameters). Set the Cluster, Euipment field. For the name field specify "InfoZoneTrends", for the value specify "PV, APV, BPV" (no quotes). set "IsTag" to false.
You can then tailor a faceplate by adding all three values, or even set up meters on the faceplate for each signal . Use the prefix field on each composite to do that. (if you used the prefix pattern for your signals)

If you wanted to display the values of all 3 signals at once on a page, well you can consider using the meter_multiple composite genie. this is where item prefixing also is essential. Set every equipment field to the same value. Leave item prefix #1 blank. Set Item prefix #2 as A, and item prefix #3 as B. To do this though, without compilation warnings of missing tags, you will need to set up PRLow, PRHigh, TrackDsp and ORDsp tags for A and B, e.g. APRLow, BPRLow. The meters require these tags at minimum to operate nicely.

Cheers,

bradley

Hi Chris,

A bit to digest there.

A couple of questions:
1. Is the RTD a single piece of equipment with 2 signals? Does each signal have (or need to have) more information such as practical range, optimal range, independent alarm limits etc?
2. Ideally how would you like it displayed to the operator on the screen?
3. Can each signal alarm? or just the synthesized average?

To give you an idea of what could be done, I'll make the assumptions of:
1. a single piece of equipment with two signals A and B and a synthesized Average signal - PV
2. Only the Avg signal has alarm limits and will alarm.

One technique you can do is create a custom meter template, based on our template. Use the PV item as your Average by changing it to a calculated variable and doing the avg between A and B. Create two additional variable items APV and BPV for your A and B signals. I name that to take advantage of the "prefix" feature of the meter composite genie templates. You can enable PLC based alarm limits for your PV (Average) if you don't want to use analog tag.
On a page you can drop down the standard meter, configure it as temp if you want. By default it binds to an item called PV. Alarms will trigger when the avg of A and B meet your defined limits of your PV variable. To get all 3 trends displaying I nthe info zone, configure the InfoZoneTrends parameter has Bas mentioned. InfoZoneTrends can be configured in 3 ways (the help only mentions 2 ways.. sigh) You can set it globally, by type or for a specific equipment instance. as the help describes how to do the fist two, I'll describe how to do it per equipinstance. Add a new Runtime Equipment Parameter via Citect Studio (System Model > Equipment > Runtime Parameters). Set the Cluster, Euipment field. For the name field specify "InfoZoneTrends", for the value specify "PV, APV, BPV" (no quotes). set "IsTag" to false.
You can then tailor a faceplate by adding all three values, or even set up meters on the faceplate for each signal . Use the prefix field on each composite to do that. (if you used the prefix pattern for your signals)

If you wanted to display the values of all 3 signals at once on a page, well you can consider using the meter_multiple composite genie. this is where item prefixing also is essential. Set every equipment field to the same value. Leave item prefix #1 blank. Set Item prefix #2 as A, and item prefix #3 as B. To do this though, without compilation warnings of missing tags, you will need to set up PRLow, PRHigh, TrackDsp and ORDsp tags for A and B, e.g. APRLow, BPRLow. The meters require these tags at minimum to operate nicely.

Cheers,

bradley