This feature enables you to quickly load an application or a macro you might have stored in a library to an application or macro you are currently working with in the Nav palette.
Note: The Load From Library function is possible only in the Engineering mode and applies to macros, applications, and control programs only. 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 Micro, or BacnetSpyder models.
To load a library item to an application or macro in the Nav palette:
Note:
When an application is imported from a library:
The application is added as a subfolder at that level in the target.
The NVs/Objects with name clashes are removed and its exposed points if any, are converted to invalid points.
If the IO being imported has no pin assigned, the tool assigns a pin to the IO, if available. If no pin is available, the IO is imported as an invalid IO.
If the IO being imported has a pin already assigned, the tool retains the pin if it (the pin) is free on the target. If the pin has already been used on the target controller, the tool reassigns a pin to the IO, if available. If no pin is available, the tool unassigns the pin from the IO (the IO is converted to an invalid IO).
If the IO being imported has a fixed IO configuration, the tool assigns a fixed IO pin to the IO as per the target controller, if available. If not, the tool converts the IO to a custom type and reassigns a free IO pin, if available. If not available, the IO becomes an invalid IO.
When an application is imported from a library to an empty controller (fresh controller with no changes made to the logic), both the ControlProgram and the imported application folder get the same GUID (Universal Unique Identifier).
For the NVs/Objects whose NV/Object name, number of fields, field names
and network datatypes matches that of fixed NVs/Objects on the target controller, the tool
does the following:
If the target controller is a fresh device, the tool strips off the fixed NV/Object from
the ControlProgram/Application folder of the target controller. The matching NVs/Objects
on the target folder are marked as fixed.
If the target controller is not a fresh device, matching fixed NVs/Objects on the incoming
folder are stripped off. Any incoming fixed NV/Object points that are exposed on the
incoming folder are remapped to point to the fixed NVs/Objects on the target controller
logic (provided the fields configuration, including the value and the internal datatype
are matching).
If the target controller is not a fresh device and if any of the fixed NVs/Objects are
exposed on the wiresheet as points, the tool strips off matching NVs/Objects from the
incoming folder and the exposed points of those NVs/Objects are converted to invalid
state. There is no effect on the exposed fixed NV/Object points on the target controller.
The LonSpyder tool checks for UNVT name clashes. The tool generates a unique UNVT name for those incoming NVs whose structure matches with UNVT name clashes with existing NVs.
If the target controller is a fresh device, then analog output type (Current or Voltage) of the incoming AOs (if any) would be the default type. That is, any new AO that is dragged onto the wiresheet in the station has the analog output type set to be same as that set for incoming AOs.
When loading from a library, PX files are also copied to the Station and can be accessed in the Station.
Attachments can exist only in the library. They can not be created or loaded from the library in Station. If you try to load or drag the library item which contains an attachment, then the attachment is discarded from the library item automatically.