Device Modules

What are Device Modules

Device Modules are application code templates that provide a quick and efficient way to integrate field devices such as variable speed drives (VSD) or servo drives in the Logic Builder project. The Device Modules are implemented on function templates, a mechanism within Logic Builder to recall predefined application program contents.

Each Device Module contains the required application objects and the corresponding program code to control the field device to monitor its status, and to handle errors that are detected. It includes a separate global variable list to access the different device functionalities available to the entire Logic Builder project.

Device Modules are available for many field devices, either connected to the control system via fieldbus or hardwired. In addition, functional components that are directly associated to field devices are also contained within the Device Modules.

How to Work with Device Modules

Device Modules are represented in Logic Builder within a function template library.

All Device Modules described in this document are available within the Logic Builder development environment under Tools > Template Repository > Function Templates. For more information, refer to the Managing Function Templates online help.

Device Modules can become integrated into the application by drag-and-drop in one step. To achieve this, open the Software Catalog in the EcoStruxure Machine Expert Logic Builder. From the tab Macros in the Software Catalog, you can drag the desired Device Module from the respective Function Template library and drop it on the Applications tree. As a result, the Add Function From Template dialog box opens where you can perform the respective settings for adding the Device Modules.

Each Device Module provides a set of application objects. For a clear separation within the project, all Device Module application content inserted appears grouped in the Application tree:

The Program (PRG) as part of a Device Module is added automatically to the task configuration of the project.

The variables (interface) of the Device Modules are declared in a global variable list (GVL). They are accessible in the project as described in the following example.

To access to the variable which indicates the communication state of the Altivar 320 with the assigned instance name Drive1_ATV320, you can write the following code:

IF NOT(GVL_Drive1_ATV320.xConnectionOkay)THEN
(*your program code*);
END_IF

Typically Device Modules include a field device. Such a field device is added under the associated fieldbus manager. This assumes that the respective fieldbus manager has been configured in the project before you can instantiate a Device Module. For example, the Device Module ATV320_EtherNetIP requires a configured EtherNetIP Scanner.