search

equinor / iec63131

Other
9 stars 8 forks source link

Create an Alarm class in the library for SFCs #45

Closed LeonHanke closed 2 years ago

LeonHanke commented 2 years ago

In order to transfer a holistic SFC, it would be helpful to introduce an Alarm object in the AML Library. This way the corresponding Alarms could be transferred during im-/export of SFCs.

AlexTxen commented 2 years ago

In SCD's some (PLC related) alarm parameters (priorities, limits, etc.) are stored in attributes on corresponding function blocks and terminals. No separate alarm objects are used. If separate Alarm object would be created for SFC's, then this approach will be inconsistent with SCD's. Also separate Alarm object could be something much more "bigger", since it could be mapped with alarm classification data. But it doesn't seem to be in the scope of iec63131 AML library at current moment.

Proposal to solve the issue is to use same approach, as for FB alarms mapping and add necessary attributes on "SequenceFlowTimeout" external interface.

Given the proposed approach, which attributes are needed for alarm information? 'Priority', else?

ipi-equinor commented 2 years ago

Please see comment on issue #49 regarding alarm attributes. Unfortunatlly the standard have not defined terminal codes for the sequence chart symbols but the AML requires a firm definition of terminal names. This issue will be taken into the revision work of the standard. The commitee agrees that the sequence Step block alarm should be handled the same way as for the MB block, one will have a fixed name (SequenceFlowTimeout) on the terminal while having three display alternativs (blank,A,W) to be used on the diagram.

cdenisey commented 2 years ago

Alarms for SFCs have been added in AML version accordingly to the answer from the committee.