This document serves as a guide to configure and use the Honeywell Spyder Tool. The Honeywell Spyder Tool is an add-on module to the existing Niagara framework modules. It provides a graphical environment to program Honeywell Spyder Controllers.
It provides the following features:
The following enhancements have been made for the Honeywell Spyder release:
SIO4022, SIO6042, SIO12000, Sylk Actuator and Sylk Sensor (C7400S)
"Node Disabled alarm" occurs when function block engine stops. It is supported only for Lon Spyder Relay devices."
The following enhancements have been made for the Honeywell Spyder release:
Spyder Lon Relay model - PUL6438SR and Spyder BACnet Relay model - PUB6438SR
Lon Spyder Relay devices support a maximum of 300 function blocks while 200 is the number of function blocks a Bacnet Spyder Relay device supports.
The number of jar files required has been reduced to 9. The only jar files required are:
A new Logarithm function block has been added. This function block takes either the natural logarithm (loge(x) = ln(x)) or logarithm base 10 (log10(x)) of the input, depending on the configuration setting eOR10. Y = loge(X) or Y = log10(X).
The following function blocks have the TailOperation to specify output value based on one of four configurable property values:
The Divide function block has the DivOperation to specify the output of division based on either Modulo or Divide property. The result of the division is: for Modulo, the output is the remainder of the division; for Divide, the output is the quotient.
The Error Configuration View now displays 7 alarms with the addition of the Control Execution alarm. This alarm is reported if the execution of application takes more than one second per cycle.
You can configure Custom Sensor properties only if Data Type selected is Custom Sensor. You can configure the following Custom Sensor Configuration items:
Any digital inputs in Lon Spyder Relay models can be configured as Pulse meter, counter, or momentary inputs.
You can now configure SyncEdgeTrigger output in Floating Motor Configuration and trigger the motor point at any point in time using one of the following values:
You can now import Custom NVs from a file location or from any device within the same Station.
File: Enables you to select a custom NV that was created and saved regardless of the Station or device. Click the File option and click the Browse button; navigate to and select the .bog file. From the Select Type list, select the custom NV within the .bog file (a single .bog file may contain multiple custom NVs).
Station: Enables you to select a custom NV that was created and saved only within any device belonging to the same Station. Click the Station option and select the device where the custom NV was created and saved. From the Select Type list, select the custom NV you are looking for.
You can also export multiple custom NVs to a file to be reused later.
Spyder tool is now enhanced to track the application changes done at the controller through other sources (e.g. Zio). The tool shall give a warning to user during the download process, if the revision number of the application in the controller does not match with revision number in the station database. This way user can decide whether or not to overwrite the changes already done at the controller. Batch download operation is also enhanced to skip or overwrite the controllers that are updated by other sources.
The Temperature Setpoint Calculator block is introduced new in this release to calculate the effective heat setpoint and effective cool setpoint based on Effective occupancy current state, Scheduled next state, Center/offset setpoint, Manual override state, Recovery heat ramp rate, Recovery cool ramp rate.
| Acronym | Expansion |
| JACE | Java Application Control Engine |
| NRE | Niagara Runtime Environment |
| JVM | Java Virtual Machine |
| NV | Network Variables |
| Term | Definition |
| JACE | Java Application Control Engine. The Tridium-manufactured controller that runs the core runtime Niagara software in a JVM, providing a station with direct support for field device integration and enterprise LAN connectivity. |
| Fox | This is the proprietary protocol of Tridium for communication between workbench and the station. |
| Host | The hardware platform or machine on which the Niagara software runs. Niagara can run on a PC or a JACE controller. |
| Station | The Niagara station is a JVM that hosts the running of objects. |
| Commission | This is the process of downloading the application (program logic and network image) to the Honeywell Spyder controller. |
| Functional blocks | Functional blocks are the atomic program objects that define a specific function. |
| Macros | Macros are a set of functional blocks that define a specific functionality. |
| Wiresheet | Wiresheet is the view in the Niagara workbench that allows you to drag and drop functional blocks and macros to define application logic. |
| Programming environment/Graphical environment | A wiresheet view that allows you to define your application logic for the Honeywell Spyder controller. |
| Application | Application is a group of function blocks that are interconnected to form a control logic. This application is then downloaded to the controller to run the control logic in the controller. |