Spyder Library Applications
The applications and macros created and saved to the library are stored
in the Application(s) folder in the library. Application(s) is
one of the default folders in every library.
To create a new application in the library:
- Click the options button in the Spyder Library sidebar. A list of
options appear.
- Select New > Application. The Application Name dialog
box appears.
- Type the name of the application in the Application Name dialog box.
- Click OK. An application with the given name is created in the Application(s)
folder in the library.
- Expand the Application(s) folder on the left pane to view the
application file of the application you just now created.
- Expand the application file under the Application(s)
folder on the left pane to view the application you just now created.
To add any Spyder object such as an application, macro, physical IO, software IO,
Function block to the application in the library:
- Browse to the application by clicking Station > Drivers > LonNetwork >
LonSpyder > ControlProgram
or
Station > Drivers > BacnetNetwork > BacnetSpyder > ControlProgram
in the Nav sidebar.
- Right-click any Spyder object such as application, macro, device, FB, or IO in the Palette
sidebar and select Copy.
- Right-click the application in the Spyder Library sidebar and select Paste.
or
Drag the object to the wiresheet of the application in the Spyder Library
sidebar. The application, macro, device, FB, or IO appears on the wiresheet of the
application.
Note:
When a software IO in Lon such as NVI, NCI, or NVO is added to the
wiresheet, an NV is created in the NV Configuration View. The corresponding backend object
is created in the Object Configuration View.
When a software IO in Bacnet such as Network Inputs, Network Setpoints,
or Network Outputs is added to the wiresheet, a backend object is created in the Object
Configuration View. The corresponding NV is created in the NV Configuration View.
When a Bacnet software input of type Constant is added to the wiresheet,
no backend object or NV is created.
When a physical input of type Modulating Input is added to the
wiresheet, a backend object -AI, as well as a reference object -UICalOffset are created in
the Object Configuration View. There is no NV created for the physical point in the NV
Configuration View.
When a physical IO such as Binary Input, Binay Output, or Modulating
Output is added to the wiresheet, a backend object is created in the Object Configuration
View. There is no NV created for the physical point in the NV Configuration View.
Application Conversion - Lon Applications to BACnet and vice-versa
Lon to BACnet
If an application created under Lon Spyder device is dropped onto a BACnet Spyder
device:
- Lon network interface will be removed and BACnet network interface will be added.
- All Lon Network Variables will be removed.
- BACnet objects will be created for all the points on the wiresheet
- If the point on the wiresheet is of type Modulating Input, a corresponding AI object and
an UICalOffset object will be created.
- If the point on the wiresheet is of type Network Setpoint and if it corresponds to a
field of nciUICalOffset, then the tool will do the following automatically:
- Create Modulating Input (MI) only if MI with the same terminal number as the exposed
point is not available in the BACnet device. If the BACnet device already has an MI with
the same terminal number, the tool will not create a new MI.
- Create the corresponding AI object and UICalOffset object for the newly created MI.
- If the point is of type Modulating Output, Binary Input, or Binary Output the
corresponding BACnet object will be created by the tool.
- If the point is of type Network Input and if it is attached to nviTimeSet, the tool will
automatically map the exposed point to the corresponding DEV_DeviceObject field.
- If the logic has a TemperatureSetpointCalculator block, 6 BACnet
objects will be created (only if the BACnet device does not already have one) representing
the setpoint values of the block.
Lon to Library Application
If an application created under Lon device is dropped onto the Library application:
- BACnet network interface will be added.
- BACnet objects will be created for all points on the wiresheet.
- If the point is of type Modulating Input (MI), AI and UICalOffset objects will be
created. If the BACnet device has any free terminal, MI added to BACnet device will be
assigned to that terminal. If the BACnet device does not have any free terminal, the MI
will remain unassigned.
- If the point is of type Network Setpoint and if it is attached to nciUICalOffset, the
tool will do the following automatically.
- Create Modulating Input (MI) only if MI with the same terminal number as the exposed
point is not available in the BACnet device. If the BACnet device already has an MI with
the same terminal number, the tool will not create a new MI.
- Create the corresponding AI object and UICalOffset object for the newly created MI.
- If the point is of type Modulating Output, Binary Input, or Binary Output, the
corresponding BACnet object will be created by the tool.
- If the point is of type Network Input and if it is attached to nviTimeSet, the tool will
automatically map the exposed point to the corresponding DEV_DeviceObject field.
- If the logic has a TemperatureSetpointCalculator block, 6 BACnet
objects will be created (only if the BACnet device does not already have one) representing
the setpoint values of the block.
BACnet to LON
If an application created under BACnet Spyder device is dropped onto the Lon Spyder
device:
- BACnet network interface will be removed and Lon network interface will be added.
- All BACnet objects will be removed.
- Lon objects will be created for all points on the wiresheet
- If the point is of type Network Setpoint and if it is attached to UICalOffset object,
the tool will automatically map the exposed NetworkSetpoint to the nciUICalOffset field
based upon the terminal number used by the corresponding Modulating Input.
- If the point is of type Network Input and if it is attached to DEV_DeviceObject, the
tool will automatically map the exposed point to the corresponding nviTimeSet field.
- If the logic has a TemperatureSetpointCalculator block, the
network variable nciTempSetpoints will be created (only if the Lon device does not already
have one) representing the setpoint values of the block.
BACnet to Library Application
If an application created under BACnet device is dropped onto the Library application:
- Lon network interface will be added.
- Lon objects will be created for all the points on the wiresheet.
- If the point is of type Network Setpoint and if it is attached to UICalOffset object,
the tool will automatically map the exposed NetworkSetpoint to the nciUICalOffset field
based upon the terminal number used by the corresponding Modulating Input.
- If the point is of type Network Input and if it is attached to DEV_DeviceObject, the
tool will automatically map the exposed point to the corresponding nviTimeSet field.
- If the logic has a TemperatureSetpointCalculator block, network variable
nciTempSetpoints will be created (only if the Lon device does not already have one)
representing the setpoint values of the block.
Viewing and Editing Bacnet Objects and Lon NVs
- Browse to the application in the Application(s) folder in the Spyder
Library sidebar.
- Right-click the application and select Views.
- Select NV Configuration View to view the Lon Network Variables
available on the wiresheet of the application.
or
Select Object Configuration View to view the Bacnet Objects available on
the wiresheet of the application.
The configuration properties of the physical and software IOs in the application
library now enables you to edit the points for both the network interfaces. The Advanced
option under Configure Properties contains the two tabs, Bacnet
Object and Lon NV.
To edit the physical and software IOs in the application library:
- Browse to application in the Application(s) folder in the Spyder
Library sidebar.
- Right-click the application and select Views.
- Select Wiresheet to view the Spyder objects such as application, macro,
device, FB, or IO in the Application Library.
- Right-click any physical IO or software IO on the wiresheet and select Configure
Properties. The Configure Properties dialog box appears.
- Click Advanced. The Advanced dialog box contains the
two tabs Bacnet Object and Lon NV.
Note: The version of the tool installed must support both Lon and Bacnet
to be able to view the two tabs in the Advanced dialog box.
If a Lon application is dragged onto the wiresheet of a Bacnet device then,
- All the Lon NVs that appear on the wiresheet are converted to the corresponding Bacnet
objects. During the conversion, the network datatype of all points are removed.
- The backend objects are created for the points on the wiresheet of the Bacnet device.
- The assignment of pins in the Terminal Assignment View are also
corrected. If the Bacnet device has fewer terminal, then the physical points are
unassigned.
If a Bacnet application is dragged onto the wiresheet of a Lon device then,
- All the software points that appear on the wiresheet of the Bacnet application are
converted to the corresponding Lon NVs. The physical points on the wiresheet are mapped to
the fixed NVs. During the conversion, the network datatype of all points are mapped to a
standard NV type (SNVT).
Note: For tools supporting both Lon and Bacnet ,
When you save an application to library from a Lon Network, backend
Bacnet objects are created for the points on the wiresheet. Backend objects are not
created for mandatory and fixed NVs.
When you save an application to library from a Bacnet network, the
points are shown as invalid in the NV Configuration View.
When a Lon NV is created in the NV Configuration View, the corresponding
Bacnet object is automatically created only when the Lon NV is shown on the wiresheet as
point.
When a Bacnet object is created in the Object Configuration View, the
corresponding Lon NV is automatically created only when the Bacnet object is shown on the
wiresheet as point.
When a point is added to the wiresheet, the corresponding Lon NV and
Bacnet Object is created with the default settings.
If the configuration details of the point on the wiresheet is
modified, the changes are applied to both Lon and Bacnet.
Changing Bacnet object details such as GPU, Fail Detect, Update Rate, or
Sen Delta does not affect the corresponding NV.
Related Topics
Open Spyder Library
Add Items to Library
Delete Library Items
Export Library Items
Import Items to Library
Load Library Items