Controlling Alarm Values ​​from Mimic

[abdullah123456789]

Hello. I'm using the November 2024 version of Geo Scada Expert 2023 and have a question. I have some field data I retrieve via ODBC, and I also include this live field data in calculations within Scada.

I want to set alarm values ​​within the mimic page to which this calculation data is assigned. However, I definitely don't want to do this from the signal's Properties screen, but rather with a command embedded within the Mimic. To do this, I created a Text Box and assigned the signal to it using the Method method within the Pick Action. However, the Tune Alarm Limits method I chose for this operation doesn't seem to be working properly. The options I used in the Text Box assignment are as shown in the images below.

           

 

For example, let's say my signal's HighLimit value is 4. I enter the HighLimit value as 3 using this button. I don't receive any errors or warnings; the value is still 4 in the Tune Alarm Limits screen. However, when I check the signal's Properties screen, I see that there's still no change. 

When I checked the help page in the link below, I saw that the values ​​I entered here were only temporary, not permanent. Can you help me with this? So, is the transaction I perform with this method actually saved temporarily? Or is there a better way to perform the transaction I mentioned? Thank you in advance.

https://tprojects.schneider-electric.com/GeoSCADAHelp/Geo%20SCADA%202021/Content/DriversGuide/TuneAl...

[tfranklin]

What you're looking at is tuned alarm limits.  When you use alarm tuning, the base alarm config remains in place and the "tuned" value is effectively an override for that limit value until a user releases the tune.  Tuning is useful for situations where you've fully rationalized your alarms in a system and don't want users changing them, but want to give them the ability to bump them temporarily in the event a transmitter is at the edge of a limit and it's continuously re-triggering alarms.  

If you're wanting to change the actual configured alarm value, you'd need to do so with a script or query.  The user also will require the Configure permission to do so.  

set obj = server.findobject("someobject.path.here.to.analog.point")

obj.interface.highhighlimitstd = 123

obj.interface.highlimitstd = 50

This complicates a few things though because now you have to script in some kind of validation of the entered values.  Meaning -- if the user enters a HH value that is lower than the H limit, you'll get an error on the tag.  So instead, you'll want to do some error handling in the script.  This is all natively done for you with alarm tuning though.  If you're not keen on scripting I'd probably recommend the tuning route if you're comfortable with how it works.  

[abdullah123456789]

Thank you for your response. A few quick questions about Alarm Tuning: When does a tuning release occur besides manual release or system restart? Can tuned values be applied automatically after a restart? Is manual release done via a script or method, and how can I implement it? While tuning is active, does the system use the tuned values until release? Any example scripts or documentation would be helpful.