Customizing an OPC DA Library

When configuring Desigo CC to connect to a third-party OPC server, if the device requires a custom object model and/or custom import rules, you will need to create an OPC library for the device and configure it appropriately.
To this purpose you must first create a customized OPC library, then you must import custom OPC object models into this library, and finally configure the import rules for the customized OPC library. For background information, see OPC DA Library.

To create an OPC library for integrating a third-party OPC device into Desigo CC instead of constructing the library manually you can use the customization feature to automatically create the required library structure. The following procedure describes how to create a new OPC library by cloning the structure of the Headquarter OPC library at a lower level. The customized library will be placed at the allowed customization level (for example, L4-Project).

You do not need to configure an OPC library if you plan to use default object model and the default import rules for the OPC device. In that case you can skip this section.

You are trained and authorized to work with system libraries. Also you are authorized to handle libraries for the specific customization level (L4-Project, L3-Country, or L2-Region) where you want to create the new library.

System Manager is in Engineering mode.

System Browser is in Management View.

Select Project > System Settings > Libraries > L1-Headquarter > Global > OPC.

In the Library Configurator tab, click Customize the entire library to a lower level .

Click OK to confirm.

The structure of the selected library is cloned under the allowed customization level (for example, L4-Project > Global > OPC). This structure already contains the blocks, such as import rules and object models that you must later configure.

To import custom OPC object models into the custom OPC library do one of the following:

If you plan to use default OPC object models skip this step.

If the object models provided in the default OPC library are not sufficient you must import custom object models from a configuration file. See Importing Custom OPC Object Models into the OPC Library.

When you import OPC items into an OPC network, the import rules determine how the OPC types in the CSV configuration file are mapped to the OPC object models of the OPC library. To configure import rules for a customized OPC library, do the following:
a. Select Project > System Settings > Libraries > L2-Region or L3-Country or L4-Project > Global > OPC > Import Rules.
b. Select the Import Rules tab where the Object and Properties expander displays the standard import rules inherited from the L1-Headquarter level.
c. (Optional) For each OPC Type, modify the standard mapping by selecting a different Object Model, and a different value from the following fields: Direction, Transformation Type.

OPC import rules

The import rules defined in the standard OPC library are optimal for OPC integration. When configuring import rules for a customized OPC library, even though you can freely modify the mapping, we suggest not changing the configuration inherited from L1-Headquarter which can be considered consistent and working with the majority of the OPC object models.