@joey-uson
When I post this issue I'm using Chrome and when I change to FireFox the problem disappear. No Idea what causing Chrome to hinder multiple addition in a folder

Hi @mattfox ,

Actually I'm studying right now AngularJS and starting to understand the Model,View and Controller . Most of the time I learn by inspecting the code and running it to see the results. What actually the face plate has are as follows:

1. Setpoint, 2 Minimum Limit, 3. Maximum Limit (limits are used for setting the low and/or high limit alarm), 4. Override bits (set to manual or Automatic mode). Basically all those points can be define as virtual points so it practically take the points after selecting the data source.

Hope you could share the pop up panel and I'll try to work on it.

Thanks

Joey

@thomaseinasto

Yeah I think this is the right solution, unfortunately I come from Siemens Automation background and need to study the AngularJS as you mention in your comment., If you could share a simple example would be great.

These Alarm categories are actually builtin in the BACnet Controller and I think it is practical to leave it in the controller and just influence the bits beside most of the control logic are locally defined in the controller. CraigWeb suggestion is logical, thanks

Dear CraigWeb,

It is during the drag and drop that it becomes -2 in red color, but if you drag only 1 item it is okay (Im using mangoEs 3.4.5)

If I select only one points I can drag to PX folder and it turn green while if multiple points selected and drag and drop in PX folder it does accept the points.

In old Siemens Desigo we called it Genie and superGenie while in PLC they call it face plate. The face plate is a pop up window that embodied the override command, Alarm status, acknowledgment and rest, and possible some setpoint if the devices under monitor has multiple aggregates. Once you click outside of the floating face plate it will close automatically. In this way we able to hide the details to make the graphics neat and clean and once needed can be expose by the user by clicking the graphic item in the GUI screen. Hope this be consider in the next release of Mango Automation.

In our current system we have 3 categories for Alarms as follows:
1.Simple Alarm - display and reset automatically (exist with MangoEs - as information, warning) and with reset / auto reset when certain value occur.
2. Advance Alarm - will require to acknowledge (exist with MangoEs)
3. Extended Alarm - will stay even the alarm return to normal but require the user to execute reset to enable the system to function again (does not exist with MangoEs- mainly we use this for Critical, safety and urgent alarm type) .

I completed converting our graphics elements in GIF and imported to MangoES and shown above I created a demo AHU for a project and found out latter that I have to go now and then to events to check and acknowledge all alarm that may appear in the GUI page. It would be better to have to have an individual alarm acknowledgement as additional to the pop-up beside (datapoints details, quick view chart, +Alarm acknowledgement), mean I don't have to go back and forth between events and GUI.

Just tested today and I would like only to inform you that it is working , thanks for the support

@phildunlap

Thanks for the explanation and scripts, I'll test on Sunday

Reason behind is I would like to have control to enable/activate the datasource (putting it online or offline) or change the parameters of the network ( i.e. ip address, bring online or offline) in order to install two identical MangoEs for the purpose of redundancy. One is label as Master and the other is Slave. My Idea is the Master will publish a continuous pulse which the slave will continuously monitor at certain interval and once the time period elapse and there is no pulse coming from the Master the Slave MangoEs will enable the datasource and possibly redefine the IP address to effectively replace the Master when it fail. I know this is a poor mans solution but may work. Calling the script will be define in the event handler or through Script datasource.

A better alternative would be integrating in the MAngoEs code itself. Any idea please...

Scenarios

1. A time scheduler created that trigger on every hour and trigger off after 10 minutes.
   
2. An event under scheduler define with as shown below.
   note: the target should not be needed if execution by script but the program required to put some parameter so I put other datapoints. When test the script if shows success false but the on trigger always executed properly except the inactive event.

I tried also to use set to static value and define additional context but in this case only the target is changing in on event.

3.Here the virtual datasource and point use in the simulation

Note that I make sure that it is settable

4. Monitor the datpoints details and it trigger on every hour (4:00pm (Set point handler) but never executed the trigger off / inactive value script.