Error View on LonSpyder Device

This view displays all the alarms generated by the Honeywell Spyder controller. There are 7 categories of alarms:

Note: The S-BUS WM Communication Alarm and the S-BUS WM Fail Detect Alarms are shown only for:

To view the Alarms View of a controller, right-click the Device Name in the Nav palette and select Views > Alarms View. The Alarms view is displayed on the right half of the screen. The Alarms view is static and you must refresh the view to get the latest update.

nvoError

The Honeywell Spyder tool provides a multi-byte network variable, nvoError, which indicates errors. You can access the nvoError map on the Property Sheet view of the controller. The nvoError map consists of 10 fields of one byte each. As each byte is 8 bits long, there are a maximum of 80 bits that are used to indicate errors. Each bit is mapped to an alarm.

There are 7 categories of alarms:

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, Spyder Enhanced, 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, Spyder Enhanced, 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 Enhanced, Spyder Micro, and BacnetSpyder models.

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

Spyder Micro models fill a number between 16 and 47.

S-BUS WM Communication Alarm These alarms occur when there is a communication break between the device and the wall module.
S-BUS WM Fail Detect Alarms Shown only for LonSpyder II, Spyder Enhanced,   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, Spyder Enhanced, and BacnetSpyder models, you may define upto 168 alarm function blocks.

On detection of an alarm condition, the LonSpyder II, Spyder Enhanced, 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.

Control execution alarm Shown only for LonSpyder Relay and Spyder Bacnet Relay models. This alarm is reported if the execution of application takes more than one second per cycle. As Spyder Relay models support more resources, execution time can exceed 1 second per cycle. This alarm is reported in such cases.

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.

To view the Alarms View of a controller, right-click the Device Name in the Nav palette and select Views > Alarms View. The Alarms view is displayed on the right half of the screen. The Alarms view is static and you must refresh the view to get the latest update.

The following table indicates the bit positions and the alarms they are used to represent:

Bit Position Alarm Type Description
0-7 Sensor Alarm Indicates error condition on Modulating inputs or outputs.
0 Sensor Alarm The on-board pressure sensor is open or shorted.
1 Sensor Alarm Universal Input 1 exceeds the user defined range, that is, it is open or shorted.
2 Sensor Alarm Universal Input 2 exceeds the user defined range
3 Sensor Alarm Universal Input 3 exceeds the user defined range
4 Sensor Alarm Universal Input 4 exceeds the user defined range
5 Sensor Alarm Universal Input 5 exceeds the user defined range
6 Sensor Alarm Universal Input 6 exceeds the user defined range
7 Sensor Alarm Universal Input 7 exceeds the user defined range
8-14 No mapping The on-board thermistor is open or shorted
15 Invalid Configuration Alarm The configuration downloaded to the controller is illegal. One or more file sections have a CRC error
16-47 Network Communication Alarm The input network variable represented by this bit is not being received within the fail detect time.
48-79 Control Alarm The alarm function block reporting the alarm represented by this bit.
80-247 S-BUS WM Fail Detect Alarms The output of the S-Bus Wallmodule represented by this bit is not being received within the fail detect time.

The range and bit positions differ for LonSpyder Micro. The following table indicates the bit positions for the Control Alarms, Network Communication Alarms, and S-Bus WM Fail Detect Alarms.

Bit Position Alarm Type Description
16-47 Control Alarm The alarm function block reporting the alarm represented by this bit.
48-197 Network Communication Alarm The input network variable represented by this bit is not being received within the fail detect time.
198-247 S-BUS WM Fail Detect Alarms The output of the S-Bus Wallmodule represented by this bit is not being received within the fail detect time.

Note: UI 0 is displayed only for models that support UI 0. UI 7 is not shown on the Alarms View.