Writing an Array to a flag tag in crimson 3.0

[Taintd]

Hi, I'm having an issue in crimson 3.0 when I create a programme using a case statement referencing a fault word that each bit needs to change the state of a flag tag so that it comes up in the alarm banner how do I configure the flag tag, as my script shows that it's ok syntaxes is fine but when I input the corresponding value into a setpoint no alarms come up, asked my tutor but he hasn't been much help.

 

[OkiePC]

Can you share your crimson file?

I typically set up alarms like this at the tag level. If each bit represents a different fault, I reference the word from the field device in one tag, and the bits as flag tags with the data source referencing that integer tag treated as a bit array and specifying a bit number.

If the tag is a code, I just make it a multi-state object and put all the faults as states, and on the alarm tab Event Name use an expression including the tag value.AsText. That way, your event viewer and alarm banner will show a unique alarm for each value with no need for separate complex expressions or programs with case statements.

 

[Taintd]

Can you show me an example of that?

 

[OkiePC]

Can you show me an example of that?

Here's one example of bit of word alarming. This system had two pumps so I use a symmetrical folder and tag structure for each and widgets for the display. I use a memory string tag called Title for the name of the pumps, because often, the end users want something besides "Pump 1" and "Pump 2". In this case, they wanted "West" and "East". Since I reference that title everywhere in the other tags and alarms, widgets, etc. I only had to change the data source of the Title tag to get the naming they preferred. I actually have another Title tag nested inside this one that points at the Title tag in the root folder. Sometimes it looks like I get carried away with indirection, but the payoff is the entry of the strings in the alarms and status words is easier to type out by doing that.

 

[Taintd]

I am.able to do that but when I write an interger value using a memory tag in crimson to write it doesn't make logical sense as using bit end means I need to write 2,4,8,16,32 to bring up the correct alarm, where as I need to input into the fault word as say 3 it bring its fault_3 flag tag alarm.

Here's one example of bit of word alarming. This system had two pumps so I use a symmetrical folder and tag structure for each and widgets for the display. I use a memory string tag called Title for the name of the pumps, because often, the end users want something besides "Pump 1" and "Pump 2". In this case, they wanted "West" and "East". Since I reference that title everywhere in the other tags and alarms, widgets, etc. I only had to change the data source of the Title tag to get the naming they preferred. I actually have another Title tag nested inside this one that points at the Title tag in the root folder. Sometimes it looks like I get carried away with indirection, but the payoff is the entry of the strings in the alarms and status words is easier to type out by doing that.

 

[OkiePC]

I am.able to do that but when I write an interger value using a memory tag in crimson to write it doesn't make logical sense as using bit end means I need to write 2,4,8,16,32 to bring up the correct alarm, where as I need to input into the fault word as say 3 it bring its fault_3 flag tag alarm.

That is different than your original post, and I am unable to follow what you have stated here. What is the source and data type of the alarm?

The last example I gave was one where each bit represented a different condition, and multiple conditions could be true at once (therefore generating multiple alarm events).

The other common example is a fault code where each unique value in an integer register represents a different (single) fault condition. You can program those in Crimson with a multi-state format and put the fault description in each state Text field. Then on the alarm tab, you can pick event mode Data Mismatch (assuming zero means no alarm) and put 0 for the Value and for the event name, reference the value of the tag.AsText Then, the alarm will display the text from the format tab in the alarm banner and alarm list objects.