You can add devices, macros, Sbus wall modules and/or applications to a library.
To add a new Macro, Device, SbusWallModule, ControlProgram, or Application to a library:
To add a new Macro, Device, Application, ControlProgram, or SBusWallModule to a library:
Note: The Library list displays all libraries in the Parent folder. The
Parent folder is indicated by the Parent Folder Path.
The Save to Library function is possible only in the Engineering mode and applies to
macros, applications, devices, SBusWallModules, and control programs.
You can add or modify devices, applications, SBusWallModules, or macros to a library. Items such as Applications and macros are saved to the Application(s) folder in a library while a new device or changes to a device are added to the Device(s) folder in a library. Once you have done all the changes to a library, you must save them so that they are available for subsequent use.
Note: You do not have the option to save these items to a different library.
The Save to Library function is possible only in the Engineering mode and applies to macros, applications, devices, and control programs.
To save the changes you have made to a library:
- Overwrite the existing version, type or select:
- Description: A brief description of the application with the changes made.
- Type: Select the Application Type.
- Version: This is auto-updated. You cannot change the version number.
- Attachment: Click Add to browse through and attach a document(s). The path of the document you are attaching is displayed in the Attachment field. Select an attachment or click Remove to remove an attachment.
- Save as a new application, enter or select:
- Name: Type a name for the items you are saving.
- Description: A brief description of the application with the changes made.
- Type: Select the Application Type.
- Version: This is auto-updated. You cannot change the version number.
- Attachment: Click Add to browse through and attach a document(s). The path of the document you are attaching is displayed in the Attachment field. Select an attachment and click Remove to remove an attachment.
Alternatively, you can save a device/macro/application/SBusWallModule that you have created from the Nav palette. For additional information, refer to From the Nav Palette section of this topic.
Note:
When an Application folder is saved to a library, all network variables/Bacnet objects created on that folder are also saved.
When an Application folder is saved to a library, an NV/Object whose
field(s) is(are) exposed on the same folder as point(s) is saved to the library in such a
way that:
The network variable/object is saved.
The fields are exposed as points the same way as in the application being saved (that is,
NV/Object fields remain exposed and the NV/Object configuration screen indicates that the
fields of the NV/Object are exposed on the same folder level.
When an Application folder is saved to a library, an NV/Object whose
field(s) is(are) exposed on a different folder other than the current one as points is
saved in such a way that:
The network variable/object is saved.
The fields exposed as points are saved as unexposed fields. The NV/Object configuration
view indicates those fields as unexposed
Fields exposed as points on the same folder are saved as exposed points
When an Application folder with exposed point(s) whose associated NV/Object is present in other folders other than the current folder and its child Application folders, is saved to a library, the associated NV/Object is also copied along with that folder.
When an Application folder is saved to a library, the physical points (I/O points) in the logic are saved along with their assigned terminal IDs.
When an Application folder is saved to a library, only the NVs/Objects created in that folder and its child Application folders are saved. No additional Fixed NVs/Objects are saved along with it. (This implies that the tool does not do any thing in the background to make the application being saved a complete application based on the model because the application is independent of the model.)
When an Application is saved to the library, all the fixed NVs/Objects and fixed IOs become of the type custom in the library and they can be modified/deleted.
When a physical IO is added to an application under Applications category in the library, the physical point is not assigned any pin. It is in an unassigned state.
When an application is created under Applications category in the application library, the tool does not warn users of the application going out of limits (This is because the application (in the absence of the device) is independent of the model and model based restrictions). You can create as many NVs/Objects, and IOs and drag as many FBs as you wish.
When an application is created under a device in the library, the tool warns you when the application goes out of limits based on the model selected.
You can also add SBus wall module to your application logic and load the same to a library only if you are using the LonSpyder II, Spyder Enhanced, Spyder Micro, or BacnetSpyder models.
PX files created on the library item being saved are also saved to the library automatically.