This view displays all the alarms generated by the Honeywell Spyder controller. There are 6 categories of errors:
Note: The S-BUS WM Communication Alarm and the S-BUS WM Fail Detect Alarms are shown only for:
Spyder II models: PVL6436AS, PVL6438NS, PUL6438S
Spyder Micro models: PVL4024NS, PVL4022AS, PUL4024S, PUL1012S, PVL0000AS
To view the Error View of a controller, right-click the Device Name in the Nav palette and select Views > Error View. The Alarms view is displayed on the right half of the screen. The Error view is static and you must refresh the view to get the latest update.
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 6 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 and
Spyder II models, you may define upto 32 input network variables with fail detect. On detection of an alarm condition, the LonSpyder I and Spyder II 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, and Spyder Micro
models. On detection of an alarm condition, the LonSpyder I and Spyder II models fill a number between 48 and 79. Spyder Micro models fill a number between 16 and 47. |
| Control Execution Alarm | These Control Execution alarms
are of following
types - Control Execution Spike Error: Controller execution time has overrun 100% (greater than 2 seconds). Control Execution Pulse Error: 5 overruns in a row of any duration (greater than 1 second). Control Execution Degrade Error:10% accumulated overrun time over a 1 minute window. |
| Node Disabled Alarm |
Description: This alarm occur when function block engine stops its
execution. (It occurs only for Lon Spyder Relay devices.) Resolution: Put the device to auto mode. |
| S-BUS WM Fail Detect Alarms | Shown only for LonSpyder II and Spyder Micro models. These alarms occur
for the linked sensors of the SBusWallmodule. All the linked sensors are listed in this
category. In the LonSpyder II models, you may define upto 168 alarm function blocks.
On detection of an alarm condition, the LonSpyder II 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. |
| S-BUS WM Communication Alarm | These S-BUS WM communication alarms
are of following
types - Alarm Type 1: "There is a communication break between the device and the wall module." Resolution: Check the wiring between spyder and wall module. Alarm Type 2: "There is an unexpected device at the address x." Resolution: 1. Disconnect the unexpected device at the address "x" from sylkbus. 2. Configure a sylk device having address "x" on the wire sheet and download to the controller. Alarm Type 3: "The device at the address "x" is not responding or incompatible with proxy file contents." Resolution: 1. Connect a sylk device at address "x". 2. If there is already a device connected at address "x", check if the device is working properly and has no configuration error. It is advisable to contact "Honeywell Tech Support" in this scenario. Note: All the above 3 alarms can happen simultaneously, but the tool still shows the one error at a time. The order to display the error is not determined. It can display in random order. |
Note: You can view alarms only in Engineering mode.
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 Error View of a controller, right-click the Device Name in the Nav palette and select Views > Error View. The Error view is displayed on the right half of the screen. The Error 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.