![]() Suspicious alarms (delayed activation and deactivation): The PmaAlarmGroup.onStateChange event is triggered for each change in state of each alarm in the PmaAlarmGroup object where the alarm is defined. It doesn't happens at alarms where the " Inactivate type" configurator is set to "2 = inactivation and automatic acknowledgement".Īn alarm that has been inactivated and if needed, the user has even acknowledged it. It doesn't happens at alarms where the " Acknowledgement type" configurator is set to "2 = acknowledgement and automatic inactivation".Īn alarm that has been inactivated but the user hasn't acknowledged it. By means of the alarm you can find out if the alarm is acknowledged.Įach alarm can find itself in one of the following states: Alarm state:Īn alarm that has been activated and no inactivation occurred nor the user acknowledged it.Īn alarm that has been activated, no inactivation occurred and the user acknowledged it. In the script by calling the PmaAlarmGroup.Acknowledge or PmAlarmItem.Acknowledge methods.Ĭaution: The user must have the " Acknowledge" permission. Basic panel parameters of registered viewer:Ģ. The basic parameters are added (only if not provided previously) into the parameters sParams of the Pm.CreateView method and then passed to the viewer ( PmaPanel object). The registered viewers are opened via PmaAlarmGroup or PmaEventGroup by additional suffix /#state or /#history. This is a preconfigured panel that can be freely modified by the designer. The viewer can be created separately at any time later. When creating a new alarm/event group, it is possible to choose to create the appropriate viewers. When you resize the viewer in runtime, it adapts its content (zooming, moving graphic objects), and also works on the Web. Therefore, the PROMOTIC system contains preconfigurations of all three basic viewers (alarm states, alarm history and event history). Registering the viewer into the group therefore makes it easier to open the viewer for such alarm/event group.Ĭreating a viewer panel is not a trivial matter. Opening the registered viewer (created by panel) of intermediated alarm/event group is much easier thank opening the viewer directly, because the group provides the viewer with all important parameters that have to be provided for opening. Registering the viewer into the alarm/event group allows it to intermediate the viewing of its alarms/events. The viewer is usually registered in the PmaAlarmGroup object or in the PmaEventGroup object. The object is usually located in the panel together with other utility objects (buttons, texts) and works as alarm state viewer, alarm history viewer, or event history viewer. The objects PmgAlarmStateViewer, PmgAlarmHistoryViewer or PmgEventViewer are designed for viewing alarms/events. The "Remote connection via the Web" type of storage is used - see the " Storage type" configurator. Remote group (client) - the case when the application displays alarms/events that arise and they are stored in another application (server) that can run on another computer. Local group (server) and remote group (client): All alarms/events can be viewed together, they can be stored in one file, etc. Thus you'll maintain these alarms/events with these objects but internaly they are "pointed" to the base object. Then you create required alarms/events in these objects. ![]() ![]() Then you create next PmaAlarmGroup objects on other relevat suitable places where you check the " Parent enabled" configurator and you set the path to the base object. ![]() You parametrize it accordingly but you don't need to create even single alarm/event in this object. you want to have one PmaAlarmGroup object for each boiler), then it can be done by the following process:Ĭreate one PmaAlarmGroup object which will serve as the base (root) for all further objects. If you want to have only one group of alarms/events (so that you could, for example, view all these alarms together) but you want to create it by more PmaAlarmGroup objects (e.g. Dynamic alarms/events: To avoid alarms/events to have to be defined in advance, then it is possible to define so-called template on the " Items" tab (see the " Template for dynamically created items" configurator) and then such alarms/events can be created dynamically in the script by the PmaAlarmGroup.RegisterNew or PmaAlarmGroup.ActivateNew methods. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |