ProSoft Technology ProSoft i-View - Manual (Page 40)

Data Source Files ProSoft i-View ♦ Mobile Process Monitoring and Control Application
User Manual Version 2.0.2
Page 40 of 106 ProSoft Technology, Inc.
September 29, 2011
will trigger the alarm only when the value on the tag is above 100.
The default value for the Bounds attribute on alarm tags is bounds:={0, 0};. Therefore,
any non-zero value in a tag will trigger an alarm. This is especially relevant for BOOL tag
alarms, because by default they will become active when the tag goes to 1 (true) and
inactive otherwise, just as you would expect.
Example
The following rows in a source file represent the settings for the alarm tags that
generated the first and fourth rows on this page:
Alarm1 INT
HR1 label:="Group 1"; comment:="Weight Value went above 6
kg"; style:=alarm; bounds:={-inf,6};
Alarm4 BOOL C1
label:="Group 2"; comment:="Someone Manipulated the
Switch!"; style=alarm;
Performance Considerations
Unlike regular tags, alarm tags are continuously polled from PLCs even if they are not
shown on the screen. Also, ProSoft i-View may continue polling them while running in the
background. So it is recommended that special care be taken when deciding what tags
will be reserved for alarms. Particularly, it is highly recommended to group alarms in tags
as contiguously as possible, and to use boolean alarms instead of scalar value alarms as
much as possible. Arrays of BOOL are the best choice, if supported by the protocol.
Observing this recommendation will lead to shorter communication patterns and less
network overhead than if no special care was taken, ultimately improving the end user
experience.
3.1.11 Comments in Data Sources
You can comment Rows on Source Files for documental purposes or while you
are testing your project. To do so just start the row with the '#' character.
Examples:
# These are the lookup table entries for the style selection texts we are using
# This alarm checks for a value being too high on the statistics page
3.1.12 Specification of Communication Protocol
Starting with version 1.5 you can explicitly set the communication protocol on
source files, instead of having ProSoft i-View determining it by the kind of
addresses used in Column C as before. This feature has been provided to grant
future compatibility with a larger number of communication protocols, where
some addressing naming conventions could conflict or overlap existing ones.
To tell the actual communication protocol on a source file you must insert the
following comment as the first line.