We did not implement alarms the way you describe mainly because previous versions of the iPhone OS did not allow apps running in the background. With iOS4, applications in some categories are allowed to do so, but unfortunately ScadaMobile does not fit in any of them, and will only be allowed to run in the background for less than 10 minutes. We will anyway implement it to at least let users keep connections alive while temporarily switching to other apps, but this is not still optimum for implementing a true alarming system.
Something that some users are doing is to use built in features on the PLCs being monitored to send an e-mail or short SMS when an alarm condition is triggered. Then they can use the "Lookup" table feature in ScadaMobile to actually display a meaningful text to the user. The Lookup technique is shown in the StylesExampleEIP_PCCC.csv and StylesExampleModb.csv examples.
To some extend
We did not implement alarms the way you describe mainly because previous versions of the iPhone OS did not allow apps running in the background. With iOS4, applications in some categories are allowed to do so, but unfortunately ScadaMobile does not fit in any of them, and will only be allowed to run in the background for less than 10 minutes. We will anyway implement it to at least let users keep connections alive while temporarily switching to other apps, but this is not still optimum for implementing a true alarming system.
Something that some users are doing is to use built in features on the PLCs being monitored to send an e-mail or short SMS when an alarm condition is triggered. Then they can use the "Lookup" table feature in ScadaMobile to actually display a meaningful text to the user. The Lookup technique is shown in the StylesExampleEIP_PCCC.csv and StylesExampleModb.csv examples.
Joan