You can find these primitives located in the display pages section under System Primitives.įind the Alarm Viewer, Alarm Ticker, and Event Viewer and drag and drop them to a page. Not all actions will be available, depending on theĭisplay alarms in the Alarm Viewer, Ticker, and Event Viewer PrimitivesĪll alarms in the system when active will show up in the Alarm Viewer, Alarm Ticker, and Event Viewer. The On Accept, On Active, On Clear and On Event properties are used to specify actions to beĮxecuted when the change of state of the alarm occurs. Refer to the Using Services chapter for information on Mail To- specifies the email address book entry to which a message should be The lower the numerical value of the priority field, the nearer to the top the Priority - used to control the order in which alarms are displayed by Crimson’sĪlarm viewer. Edge triggered alarms must always be manually Time to run-up before the alarm is activated.Īccept - used to indicate whether the user will be required to explicitly acceptĪn alarm before it will no longer be displayed. The motor has been requested to start this property can be used to provide the motor with As an example, if anĪlarm is set to activate when a speed switch indicates that a motor is not running even when Subsequent reactivations will result in a further alarm being signaled. Specifies the amount of time for which the alarm condition must no longer exist before In the case of an edge triggered alarm or event, this property also Rather, an event will be logged to internal memory and optionally to the memory card.ĭelay- used to indicate how long the alarm condition must exist before theĪlarm will become active. In this case, the alarm will be edge triggered, but will not result in an alarm condition. This property can also be used to indicate that this alarm should be used as an event In the latter case, the alarm will remain in the active state while the condition The former case, the alarm will trigger when the condition specified by the event mode firstīecomes true. Trigger - is used to indicate whether the alarm should be edge or level triggered. Remember that the property always acts to maintain an alarm once the alarm isĪctivated, and not to modify the point at which the activation occurs. When the tag falls below the value by an amount greater than or equal to the alarm’s The alarm will become active when the tag exceeds the alarm’s value, but will only deactivate States when the process is near the alarm condition. Hysteresis - used to prevent an alarm from oscillating between the on and off The exact interpretation depends on the event mode as described above. Value - defines either the absolute value at which the alarm will be activated, theĭeviation from the setpoint value or the change in value that must occur since the alarm last For example-purposes, this tech note will select Active ON for the flag tag and Absolute High for the numeric tag.Īlarm Settings for Flag and Numeric tags:Įvent Name - The title of the alarm or descriptionĮnable- Set via an expression or tag to enable or disable this alarm from occurring even if the condition for it is true Select your appropriate event mode for your particular tag. Flag tags and numeric tags have different event modes. Set the Event mode to which ever trigger mode for your alarm will be. Under the alarm tab, you will see that each tag offers two alarms that you can configure per tag. Click on that tag and look in the center window. Go to your data tags section, create a new tag or find an existing tag to use. Note: Only data tags have an alarm tab feature so either mapped or internal tags must be used. Crimson has built-in alarm management objects called alarm viewer primitive, as well as an event viewer primitive for historical purposes. Numeric tags and flag tags mapped or internal support alarms and events to report issues and call actions. Red Lion Controls CR1000 Human Machine Interface (HMI), CR3000 HMI, Data Station Plus (DSPSX/GT/ZR), G3 HMI, G3 Kadet HMI, Graphite® Controller (GC), Graphite HMI, Modular Controller (MC), and ProducTVity Station™ (PTV), Fle圎dge Series (DA50A/DA70A Software Group 3 or higher), DataStation(DA30D)Ĭreating and utilizing numerical based alarms and events.Ĭrimson's display functionality has a built-in alarm system directly tied to each data tag that exists in the system. This document describes utilizing Alarms and Events in Crimson®.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |