Alarm

The inputs that can be provided to this function block are Value, High Limit, Low Limit, Preset Time, Disable. The Alarm Status is given at the output. This function creates an alarm based on the value of the input compared to the high and low limits. You may create up to 32 alarm function blocks that map to nvoError. From iteration to iteration, the function block keeps track of the alarm status and delay timer. On power up or reset, these are cleared. It is NOT necessary to connect the output of this Function Block to the input of another for this function block to work. The Alarm Function Block is different because it also sets/resets a bit in nvoError.

Logic Inputs

Input Name Input Value Logic Value Description
Disable unconnected 0 Set Disable = False
  invalid 0 Set Disable = False
  0 0 Disable is False
  VAL != 0.0 1 Disable is False

Analog Inputs

  Range    
Input Name Low High Input Value Description
Value >=- infinity <+ infinity unconnected Value = invalid
      invalid Value = invalid
High Limit >=- infinity <+ infinity unconnected High Limit = invalid
invalid High Limit = invalid
Low Limit >=- infinity <+ infinity unconnected Low Limit = invalid
invalid Low Limit = invalid
Preset Time 0 32767 unconnected Preset Time = 0
(sec) invalid Preset Time = 0
Post Time 0 32767 unconnected Post Time = 0
(sec) invalid Post Time = 0

Output

Output Name Range Description
ALARM_STATUS False (0) / True (1) Alarm status

Operation

If the Value is greater than the High Limit or less than the Low Limit continuously for the Preset Time, the Alarm Status is TRUE. Once the alarm is set TRUE, it remains TRUE for at least the Post Time. If at the end of the Post Time the Value is still outside of the limits, the alarm remains. If the Value is within the limits and the post time expires, the Alarm Status is set to FALSE.

If the Value is Invalid (open, short, or not connected) or the Disable input is TRUE, the Alarm Status and timers are cleared.

Note: If a universal input is open or shorted, it generates an alarm ID configured to do so. (By adjusting the UI limits, you can choose when a UI is open or shorted.)

Alarms on Digital Values

The Alarm function block can be used to alarm on digital values by setting the high and low limits to zero (0.0). When Value equals FALSE (0), Alarm status is  FALSE. When Value is any other value, the Preset Time starts.

The Preset and Post Time values are limited to 0 to 32767 seconds (9.1 hours).

When the Alarm Status is TRUE, the configured bit in nvoError is set. When the Alarm Status is FALSE, the configured bit in nvoError is reset.

Alarm1.gif (7731 bytes)

Alarm State Value Timer Action Comment
False Outside limits < Preset Time Increment Timer. Insure alarm is valid for the preset time before issuing the alarm.
False Outside limits >= Preset Time Set Alarm Status = TRUE;
Clear Timer
The preset time has been met, post alarm and clear the timer so it can count the post time.
False Inside limits Do not care Clear Timer Value is inside the limits and there is no prior alarm, so clear the timer so it is ready to count the preset time when the value goes outside [again].
True Outside limits < Post Time Increment Timer Insure that we post the alarm for at least Post Time seconds regardless of what the value does with respect to the limits.
True Outside limits >= Post Time Stop Timer The alarm has been issued for at least the Post Time. The alarm is now allowed to return to normal as soon as the value goes back within the limits.
True Inside limits < Post Time Increment Timer Value has gone back inside the limits after posting the alarm. Wait until the timer expires before issuing the return to normal.
True Inside limits >= Post Time Clear Alarm Status;
Clear Timer
The alarm has been issued for at least the Post Time. Clear the alarm because the conditions are no longer present

View Alarms

To view the alarms that are generated, right-click LonSpyder or BacnetSpyder in the Nav palette and select Views > Alarms View.

The Alarms View is displayed.

There are 5 categories of alarms in Honeywell Spyder:

Alarm Type Description
Sensor Alarms Generated for all sensors configured in the logic. All input blocks assigned to pins UI0 to UI6 are listed in this category.
Invalid Configuration Alarms Occurs if there is an error in the configuration that was downloaded.
Network Communication Alarms Occur ONLY for NVIs and Object Inputs configured as fail detect. The network variable or object input names are listed in this category. In the LonSpyder I, Spyder II, and Bacnet Spyder models, you may define upto 32 input network variables with fail detect.

On detection of an alarm condition, the LonSpyder I, Spyder II, and BacnetSpyder models fill a number between 16 and 47.

In the Spyder Micro models, you may define upto 150 input network variables with fail detect. Spyder Micro models fill a number between 48 and 197.

Control Alarms All the alarm blocks configured in the logic are listed in this category. If an alarm block does not have any incoming link then the status is always NORMAL. You may define upto 32 alarm function blocks in LonSpyder I, Spyder II, Spyder Micro, and BacnetSpyder models.

On detection of an alarm condition, the LonSpyder I, Spyder II, and BacnetSpyder models fill a number between 48 and 79.

Spyder Micro models fill a number between 16 and 47.

S-BUS WM Fail Detect Alarms Shown only for LonSpyder II,   Spyder Micro, and BacnetSpyder models. These alarms occur for the linked outputs of the SBusWallmodule. All the linked outputs are listed in this category. In the LonSpyder II, and BacnetSpyder models, you may define upto 168 alarm function blocks.

On detection of an alarm condition, the LonSpyder II, and BacnetSpyder models fill a number between 80 and 247.

In the Spyder Micro models, you may define upto 50 alarm function blocks. Spyder Micro models fill a number between 198 and 247.

Note: It is not necessary that two consecutive bits are filled during two consecutive alarm conditions. The tool allocates any bit position within the specified range. For example, in case of S-Bus WM Fail Detect Alarms in Spyder Micro, it is not necessary that the bit position 198 is filled and then 199 and so on. Honeywell Spyder allocates any bit position between 198 and 247.Similarly is the case for all the models in Network Communication Alarms, Control Alarms, and S-Bus WM Fail Detect Alarms.

The nvoError bit number 48 onwards (byte no 7 onwards) indicate if any alarm blocks are in alarm.The bits are set based on the execution order of the alarm block, that is, the first bit (bit 48) is set for the alarm block with the lowest execution order. The next bit (bit 49) is set for the alarm block that has the next higher execution order.

View the Alarms View of the controller to see the nvoError status and the alarms. Additionally, this information is displayed at the bottom of the alarm configuration screen itself.

A message indicating the nvo Error bit for that particular alarm is displayed. The nvo Error Field name and the bit in that particular field where the alarm is read is also displayed as shown in the following figure.

Alarms View