IDEC WindMSG - Manual (Page 12)

12. Sign Key (+/-)
Used for signed data entry.
13. Sign Key (+/-) and 0
Single key used as a sign key as well as numeric key 0. If
this key is pressed immediately after data entry is initiated,
key is taken as sign key else it is taken as ‘0’ key.
14. Numeric Key 0
Enters a ‘0’ after data entry is initiated.
15. Numeric Key 1
Enters a ‘1’ after data entry is initiated.
16. Numeric Key 2
Enters a ‘2’ after data entry is initiated.
17. Numeric Key 3
Enters a ‘3’ after data entry is initiated.
18. Numeric Key 4
Enters a ‘4’ after data entry is initiated.
19. Numeric Key 5
Enters a ‘5’ after data entry is initiated.
20. Numeric Key 6
Enters a ‘6’ after data entry is initiated.
21. Numeric Key 7
Enters a ‘7’ after data entry is initiated.
22. Numeric Key 8
Enters a ‘8’ after data entry is initiated.
23. Numeric Key 9
Enters a ‘9’ after data entry is initiated.
24. Numeric Key A
Enters a ‘A’ after data entry is initiated.
25. Numeric Key B
Enters a ‘B’ after data entry is initiated.
26. Numeric Key C
Enters a ‘C’ after data entry is initiated.
27. Numeric Key D
Enters a ‘D’ after data entry is initiated.
28. Numeric Key E
Enters a ‘E’ after data entry is initiated.
29. Numeric Key F
Enters a ‘F’ after data entry is initiated.
30. Edit Bit On
A coil is turned on after data entry is initiated.
31. Edit Bit Off
A coil is turned off after data entry is initiated.
32. Acknowledge Alarm
Active alarm is acknowledged using this key.
33. Next Alarm
Next alarm from the container is displayed.
34. Previous Alarm
Previous alarm from the container is displayed.
* While defining double Tag operations, make sure both the tags
have same number of bytes. Else the task may lead to erroneous
results.
4.3 Alarms
Any tag can be continuously monitored by defining alarms for each bit
of that tag. To display an alarm on the screen as soon as it is
triggered, alarm object has to be placed on the screen. If the value of
the particular tag becomes nonzero, alarm is displayed in the alarm
object. An alarm is triggered for each bit in a tag. Total 256 alarms
can be defined in HG1X. HG1X stores the alarm information in an
alarm container. Maximum 64 alarms can be stored in the container.
First triggered alarm is on the top of the container. New alarm is
added from the bottom. Operator has to acknowledge each alarm by
using any key with definition ‘Acknowledge Alarm’. When alarm
condition is cleared and the alarm is acknowledged, the alarm is
deleted from the container. Alarm can also be printed on the serial
port. Printing is performed as soon as the alarm is triggered.
Two types of alarms can be defined in HG1X:
1. Consecutive Alarms
2. Discrete Alarms
1. Consecutive Alarms:
Consecutive alarms can be useful when user wants to monitor 16
consecutive tags. All the 16 consecutive tags should be defined in the
tag database. An alarm cab be defined for each bit. HG1X uploads all
16 tags in a single block. When any bit of 16 tags is found to be on
(‘1’) corresponding alarm is triggered. Triggered alarm is displayed in
the alarm object. Each alarm has to be acknowledged. User should
define a key to acknowledge alarms. User can also scroll through the
table of alarms using keys defined as ‘Next Alarm’ and ‘Previous
Alarm’. Acknowledged and inactive alarm is deleted from the
container. New alarm is added from the bottom of the container.
2. Discrete Alarms:
Discrete alarms can be useful when user wants to monitor tags which
are not in a sequence, discrete. An alarm is defined for each bit of
tag. When any bit of any tags is found to be on (‘1’) corresponding
alarm is triggered. Triggered alarm is displayed in the alarm object.
User should define a key to acknowledge alarms. User can also scroll
through the table of alarms using keys defined as ‘Next Alarm’ and
‘Previous Alarm’. Acknowledged and inactive alarm is deleted from
the container. New alarm is added from the bottom of the container.