Create and use a custom palette file to store any Spyder object application, macro, device, FBs, IOs from a station. You can use this file to share it across Stations and among multiple users. This custom palette file acts only as a repository but you can not configure an object that exists in the palette.
You can later copy and paste or drag these objects from the custom palette to the station.
To create a custom palette file:
Note: You can double click the folder on the wiresheet and drag the UnrestrictedFolder object from the Palette palette on to the wiresheet. This has the effect of nesting folders within the palette file. This enables you to categorize objects that are stored in the palette file. For example, you can drag an UnrestrictedFolder from the Baja palette (Palette palette with Baja module selected) on to the wiresheet of the palette file and name it Applications. You can then double-click the Applications folder on the wiresheet and drag another UnrestrictedFolder object from the Baja palette and name it VAV Applications. This creates the VAV Applications folder under the Applications folder in a tree structure in the custom palette file you are creating.
To add any Spyder object such as a macro, application, IO, Function block to the custom palette:
To close the custom palette file, right-click the custom palette file and click Close.
Note: If you close a custom palette file without saving the contents of the custom palette file or close the Workbench without saving the contents of the custom palette file, the newly added contents are not saved and is not available when you access this folder the next time.
You can reuse components from the custom palette file in any application logic you create by dragging the desired object from the custom palette file to the wiresheet of the ControlProgram.
Adding a device to the custom palette file is similar to adding a Spyder object but it has some specific steps you have to perform additionally. To add a device to the Custom palette file:
Note: The Enable Saving ControlProgram option
makes the ControlProgram under device non-transient so that it can be saved to the bog
file. If this option is not invoked or before invoking this option, you close the bog file
or the workbench, the device looses the ControlProgram configuration in the custom palette
file. This option appears on device only when device is in the custom palette and the
ControlProgram under the device is transient. Once you invoke the option, the next time
onwards the same device option does not appear on the that particular device object. This
option appears only when required. If it does not appear, it means the ControlProgram of
the device is already in a non-transient state. This may happen when
copy-pasting/duplicating a saved device within/across palettes occurs or when you
copy-paste device object from the Spyder library to the custom palette folder.
Right-click the custom palette file and select Save.
The device is saved under the folder in the custom palette file.