ControlProgram Terminal Assignment View

This view provides a layout of the physical arrangement of the pins on the controller. Use this view to view or modify the configuration of inputs or outputs of the selected controller. According to the selected controller model, you can select which inputs or outputs must be assigned to the pins. The IO pins for Spyder I, Spyder II, and Spyder Bacnet  models are:

The inputs or outputs you have used to build the application logic along with invalid IO points are available as options for UI, DI, AO, and DO. You can choose  the inputs or outputs that are used to build the application logic, to be assigned to the physical pins of the controller. You can choose invalid IOs and reassign them to valid terminals.

Note: UI 0 and UI 7 for Spyder I, Spyder II, and Spyder Bacnet models are not shown on the Terminal Assignment View.

Example:

Let us say you have used four Modulating Inputs named Modulating Input 1, Modulating Input 2, Modulating Input 3, Modulating Input 4 and two Binary Inputs named BinaryInput 1 and BinaryInput2. On the Terminal Assignment View, for each Universal Input (UI 0 to 7), you  have the option to choose Modulating Inputs 1 to 4 or Binary Inputs 1 to 2.

The IO pins for Spyder Micro models are:

The input pin UI1 is fixed for Pulse_Meter or Counter type sensors, or Momentary type binary input. If the pin is not available or is currently assigned to another point, the tool creates the point as an invalid point.

To view the Terminal Assignment View of the controller:

  1. On the Nav palette, browse to Station > Config > Drivers > LonNetwork > LonSpyder.
    or
    Browse to Station > Config > Drivers > BacnetNetwork > BacnetSpyder.
  2. Right-click LonSpyder or BacnetSpyder.
    or
    Expand LonSpyder or BacnetSpyder and select ControlProgram. Right-click ControlProgram.
  3. Select Views > Terminal Assignment View. The view appear on the right side of the screen.
  4. Assign all the inputs and outputs and click Save to save the details or Reset to revert to the last saved changes.

Note: If you change the device model , the physical IOs continue to retain the IO pins previously assigned except in the following scenarios:

  1. If a custom IO has been assigned a pin that is fixed in the target model, HoneywellSpyder assigns a free pin, if available. If no free pin is available, the IO becomes an invalid IO.

  2. If there was a fixed pin assigned to a fixed IO in the source model and is different in the target model, Honeywell Spyder reassigns the fixed pin in the target model to that IO. But if the fixed pin is already in use in the target model, Honeywell Spyder converts the IO to the nearest custom type and reassigns a valid pin available. If there is no valid pin available the IO becomes unassigned.

  3. If the target model supports less number of IOs than the source model, Honeywell Spyder unassigns the pins for the IOs that are in excess in the target model.

  1. If target model supports more number of IOs than the source, Honeywell Spyder assigns available free pins to any invalid IOs present.

Note: The UI0 pin is not displayed on the Terminal Assignment View.

A report of all actions taken is generated.

If the name of a custom NV or Object clashes with a fixed NV or Object name in the target model, Honeywell Spyder generates a new unique name for the custom NV or Object and creates the new fixed NV or Object.

Sylk Device Support

Sylk Accessory Model Support

Sylk accessory model support and how to use them ( i.e Zeleny and Zelix support) Additional Sylk devices like actuators and the C7400S enthalpy sensor are now supported in all models of Spyder shipped from the factory after date code 1220 (Spyders that pre-date this can be re-flashed to support these new devices). To configure these devices, Go to the Terminal Assignment view and click the Add Sylk Device button and choose the appropriate device from the pulldown. Then drop the PhysicalPoint on the wiresheet (AO for an output value like an actuator, UI for an input value like a sensor) and then configure that block for a type of FixedSylkInput or FixedSylkOutput:


The tool will then automatically assign that physical point to a Sylk pin and the block will now show that information on the block, and the terminal assignment view will also show that point which can also be re-assigned if the default assignment is not desired.

The screen above is arranged to show information that is an input to the Spyder on the left and information that is an output to the Spyder on the right. In other words, points on the left are information the Spyder receives from the Sylk device, points on the right are things that Spyder uses to command the Sylk device.

Calibration and Diagnostics is not available for physical I/O that has been assigned a type of FixedSylkInput or FixedSylkOutput


Sylk IO Model Support

There are three models of Sylk I/O:

  1. SIO6042 (6 Univeral Inputs, 4 Analog Outputs, 2 Digital Outputs)
  2. SIO4022 (4 Univeral Inputs, 2 Analog Outputs, 2 Digital Outputs)
  3. SIO12000 (12 Univeral Inputs)
Configuring the I/O on these devices is done by dropping the desired PhysicalPoints on the wiresheet and then using the Terminal Assignment view to add a Sylk device and then assigning the points to the terminals on the Sylk I/O device.

Currently the only Spyders capable of supporting Sylk I/O devices are the Spyder with relay devices (PU*6438SR)

Below is a wiresheet with more physical points than a Spyder has (note the tool allows the user to drop an unassigned I/O, denoted by the red circle and slash.                  


The Terminal Assignment view now allows you to add a Sylk device. A new tab will be created and the user can select which type of Sylk device to add (in this case the user would select an SIO6042) and then a terminal assignment screen similar to the Spyder will be available to assign those unassigned points:



When the model of Spyder is changed and Sylk devices have been configured, the associated Sylk devices may be affected since some Spyders support Sylk devices which others do not (for example PUL6438S does not support Sylk I/O, but a PUL6438SR does). After the model has been changed, the tool will automatically remove any unsupported Sylk devices and any points previously configured for that device will be shown as unassigned in the wiresheet. If a Sylk device model has been changed, then any points not supported on the new model will be shown as unassigned in the wiresheet.

HoneywellSylkDevices.jar is intended for newly released Sylk devices for which the users currently installed Spyder tool does not support.

Related Topics

Sylk Advanced Properties