Schneider Electric Process Expert System 4.3 Foundation Library User Guide

PDF

Dokument

Annonce

Process Expert

EIO0000002403 06/2017

Process Expert

Foundation Application Templates

User Guide

06/2017 www.schneider-electric.com

The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information contained herein. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us.

No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of Schneider Electric.

All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components.

When devices are used for applications with technical safety requirements, the relevant instructions must be followed.

Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results.

Failure to observe this information can result in injury or equipment damage.

EIO0000002403 06/2017

Safety Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About the Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Foundation Application Templates . . . . . . . . . . . . . . . . . . . . . . . . . . .

Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Foundation Application Templates . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 Signal Conditioning and Processing . . . . . . . . . . . . . . . .

2.1 Signal Conditioning - Hardware Abstraction Layer . . . . . . . . . . . . . . .

$AISignal_UL - Analog Input Signal Conditioning . . . . . . . . . . . . . .

$AOSignal_UL - Analog Output Signal Conditioning. . . . . . . . . . . . .

$CounterSignal_UL - Counter Signal Conditioning . . . . . . . . . . . .

$DISignal_UL - Digital Input Signal Conditioning. . . . . . . . . . . . . . .

$DOSignal_UL - Digital Output Signal Conditioning . . . . . . . . . . . . .

2.2 HART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

$AHISignal_UL - HART Device Signal Mapping . . . . . . . . . . . . . . .

$AISignalHART_UL - HART Input Signal Conditioning (M580) . . . .

2.3 Time Stamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

$TSDInput - Time Stamped Information of Field Signals . . . . . . . . .

2.4 Peer to Peer Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Owner/Consumer Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data In/Data Out Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5 STAHL Control Module Templates . . . . . . . . . . . . . . . . . . . . . . . . . . .

$STAHLAI8 for STAHL 8-channel Analog Input Modules. . . . . . . . . .

$STAHLAO8 for STAHL 8-Channel Analog Output Modules . . . . . . . .

$STAHLDI16 for STAHL 16-Channel Digital Input Modules . . . . . . . .

$STAHLDO8 for STAHL 8-Channel Digital Output Modules . . . . . . . .

$STAHLAI8HART for STAHL 8-channel Analog Input Modules with

HART Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 Using STAHL Control Module Templates . . . . . . . . . . . . . . . . . . . . . .

Use Case Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Instantiation and Application Links . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

33

34

35

22

25

27

29

15

16

19

21

13

14

5

9

49

53

54

56

36

39

40

58

60

62

65

66

68

69

EIO0000002403 06/2017

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Finalizing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Logical Control Participant Project . . . . . . . . . . . . . . . . . . . . . . . .

STAHL Remote I/O System Configuration. . . . . . . . . . . . . . . . . . . . . .

Chapter 3 Special Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Special Card Application Templates Approach . . . . . . . . . . . . . . . . . .

$QEHC10500 - Quantum High Speed 5-Channel Counter Module . . .

$QEHC20200 - Quantum High Speed 2-Channel Counter Module . . .

$QERT85410 - Quantum Expert Time Stamp Module . . . . . . . . . . . . .

$QERT85420 - Quantum Expert Time Stamp Module . . . . . . . . . . . . .

$TUnsignCptBmx - M340 High Speed Counter Module UnSign . . . .

$TSignCptBmx - M340 High Speed Counter Module Sign . . . . . . . .

$EPITesysUAS - Advantys Special Module for Handling TeSys U

Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

$BMXEHC - M580 and X80 High Speed Counter Module . . . . . . . . . .

98

100

Chapter 4 Variable Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101

Elementary Variable Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

87

89

90

91

73

75

76

79

92

94

96

97

Array Variable Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reference Data Type Variable Templates . . . . . . . . . . . . . . . . . . . . . .

107

Chapter 5 Using HART Analog I/O Signals. . . . . . . . . . . . . . . . . . . .

109

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

102

105

Configuration Stage (Topology Explorer). . . . . . . . . . . . . . . . . . . . . . .

Instantiation Stage (Application Explorer) . . . . . . . . . . . . . . . . . . . . . .

Project Definition Stage (Project Explorer). . . . . . . . . . . . . . . . . . . . . .

Deployment Stage (Topology Explorer) . . . . . . . . . . . . . . . . . . . . . . . .

Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110

111

116

118

119

121

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

123

EIO0000002403 06/2017

Safety Information

Important Information

NOTICE

Read these instructions carefully, and look at the equipment to become familiar with the device before trying to install, operate, service, or maintain it. The following special messages may appear throughout this documentation or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.

EIO0000002403 06/2017

PLEASE NOTE

Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel. No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material.

A qualified person is one who has skills and knowledge related to the construction and operation of electrical equipment and its installation, and has received safety training to recognize and avoid the hazards involved.

BEFORE YOU BEGIN

Do not use this product on machinery lacking effective point-of-operation guarding. Lack of effective point-of-operation guarding on a machine can result in serious injury to the operator of that machine.

WARNING

UNGUARDED EQUIPMENT



Do not use this software and related automation equipment on equipment which does not have point-of-operation protection.

Do not reach into machinery during operation.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

This automation equipment and related software is used to control a variety of industrial processes.

The type or model of automation equipment suitable for each application will vary depending on factors such as the control function required, degree of protection required, production methods, unusual conditions, government regulations, etc. In some applications, more than one processor may be required, as when backup redundancy is needed.

Only you, the user, machine builder or system integrator can be aware of all the conditions and factors present during setup, operation, and maintenance of the machine and, therefore, can determine the automation equipment and the related safeties and interlocks which can be properly used. When selecting automation and control equipment and related software for a particular application, you should refer to the applicable local and national standards and regulations. The

National Safety Council's Accident Prevention Manual (nationally recognized in the United States of America) also provides much useful information.

In some applications, such as packaging machinery, additional operator protection such as pointof-operation guarding must be provided. This is necessary if the operator's hands and other parts of the body are free to enter the pinch points or other hazardous areas and serious injury can occur.

Software products alone cannot protect an operator from injury. For this reason the software cannot be substituted for or take the place of point-of-operation protection.

Ensure that appropriate safeties and mechanical/electrical interlocks related to point-of-operation protection have been installed and are operational before placing the equipment into service. All interlocks and safeties related to point-of-operation protection must be coordinated with the related automation equipment and software programming.

EIO0000002403 06/2017

NOTE: Coordination of safeties and mechanical/electrical interlocks for point-of-operation protection is outside the scope of the Function Block Library, System User Guide, or other implementation referenced in this documentation.

START-UP AND TEST

Before using electrical control and automation equipment for regular operation after installation, the system should be given a start-up test by qualified personnel to verify correct operation of the equipment. It is important that arrangements for such a check be made and that enough time is allowed to perform complete and satisfactory testing.

WARNING

EQUIPMENT OPERATION HAZARD



Verify that all installation and set up procedures have been completed.

Before operational tests are performed, remove all blocks or other temporary holding means used for shipment from all component devices.

Remove tools, meters, and debris from equipment.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Follow all start-up tests recommended in the equipment documentation. Store all equipment documentation for future references.

Software testing must be done in both simulated and real environments.

Verify that the completed system is free from all short circuits and temporary grounds that are not installed according to local regulations (according to the National Electrical Code in the U.S.A, for instance). If high-potential voltage testing is necessary, follow recommendations in equipment documentation to prevent accidental equipment damage.

Before energizing equipment:



Remove tools, meters, and debris from equipment.



Close the equipment enclosure door.

Remove all temporary grounds from incoming power lines.

Perform all start-up tests recommended by the manufacturer.

EIO0000002403 06/2017

OPERATION AND ADJUSTMENTS

The following precautions are from the NEMA Standards Publication ICS 7.1-1995 (English version prevails):



Regardless of the care exercised in the design and manufacture of equipment or in the selection and ratings of components, there are hazards that can be encountered if such equipment is



 improperly operated.

It is sometimes possible to misadjust the equipment and thus produce unsatisfactory or unsafe operation. Always use the manufacturer’s instructions as a guide for functional adjustments.

Personnel who have access to these adjustments should be familiar with the equipment manufacturer’s instructions and the machinery used with the electrical equipment.

Only those operational adjustments actually required by the operator should be accessible to the operator. Access to other controls should be restricted to prevent unauthorized changes in operating characteristics.

EIO0000002403 06/2017

About the Book

At a Glance

Document Scope

This document describes the Foundation templates, and the Control services that they provide.

For a more detailed description of their associated Control services and its parameters, refer to the user guides mentioned in this document.

This document is for users with knowledge of Process Expert, and its Control and Supervision

Participants.

Validity Note

This document is valid for Process Expert 4.3 or later. It supersedes any previous version.

Chapter 1 Overview

What Is in This Chapter?

This chapter contains the following topics:

Topic

Foundation Application Templates

Naming Convention

List of Foundation Application Templates

Page

EIO0000002403 06/2017

Overview

Foundation Application Templates

Description

The Process Expert Foundation library provides resources that have been pre-configured and tested by Schneider Electric. Foundation application templates provide standardized elementary resources that are used in control module templates of the General Purpose library. It also provides additional services that are required to manage data transmission within a system.

The resources provided by Foundation application templates are encapsulated in facet or composite templates. You can customize the services provided by these templates at the instance level.

You can link Foundation application templates to compatible process and device templates.

Foundation Application Template Services

Foundation application templates provide the following services:

Control Includes core services plus additional, optional services, which you can activate if needed.

Function blocks and variables are the resources that are encapsulated in these templates to provide such services.

Exposed Interfaces

Foundation application templates expose interfaces that allow you to make the following types of connections:



To topological instances (mapping interfaces)

To other application instances (application interfaces)

Exposed interface can have the following roles:

Ref Role receiving data from the linked object. This role is represented graphically as male.

Def Role providing data to the linked object. This role is represented graphically as female.

CO Is used from the application templates representing communications objects (CO) that receive the data provided from the system configuration. This role is represented graphically as male.

DO Is used from the application templates representing device objects (DO) that receive the data provided from the system configuration. This role is represented graphically as male.

HO Is used from the topological template (also called hardware objects (HO)) to expose the information provided by the hardware (for example, topological addresses, slave number, and so on) to the project facets. This role is represented graphically as female.

SO Is used from the application templates representing the signal objects (SO) or I/O module objects that receive the data provided from the system configuration. This role is represented graphically as male.

EIO0000002403 06/2017

Naming Convention

Prefix

The $ character is used as prefix for templates made by Schneider Electric.

Suffixes

The following suffixes are used to identify types of templates:



No suffix: Control module template (composite).



UC : Control composite template.

UL : Control facet template.

Overview

EIO0000002403 06/2017

Overview

List of Foundation Application Templates

List of Families

The templates described in this document are grouped by family.

The table lists the control module templates of each family:

Family name

Signal conditioning -

Hardware Abstraction

Layer (HAL)

Time stamping

Unity Peer to Peer

Templates

$AISignal_UL

( see page 22 )

$AOSignal_UL

( see page 25 )

$DISignal_UL

( see page 29 )

$TSDInput_UL

( see page 36 )

$DOSignal_UL

( see page 31 )

$AHISignal_UL

( see page 34 )

$AISignalHART_UL

( see page 35 )

$CounterSignal_UL

( see page 27 )

(

$TSDInput see page 36

$TSDInput8

)

( see page 36 ) ,

$TSDInput16

( see page 36 ) and

$TSDInput32

( see page 36 )

Data In/Data Out

( see page 49 )

Owner/Consumer

( see page 40 )

Description

Analog input signal conditioning

Analog output signal conditioning

Digital input signal conditioning

Time stamped information of field signals

Digital output signal conditioning

HART device signal mapping

HART input signal conditioning

(M580)

Counter signal conditioning

Time stamped information of field signals

Data In/Out templates

Owner/Consumer templates

EIO0000002403 06/2017

Family name

STAHL

Unity Special In Rack

Cards

Variable templates

Templates

$STAHLAI8

( see page 54 )

$STAHLAO8

( see page 56 )

$STAHLDI16

( see page 58 )

Description

For STAHL 8-channel analog input modules

For STAHL 8-channel analog output modules

For STAHL 16-channel digital input modules

$STAHLDO8

( see page 60 )

$STAHLAI8HART

( see page 62 )

$QEHC10500

( see page 90 )

$QEHC20200

( see page 91 )

$QERT85410

( see page 92 )

For STAHL 8-channel digital output modules

For STAHL 8-channel analog input modules with 4 or 8 HART signals.

Quantum high speed 5-channel counter module

Quantum high speed 2-channel counter module

Quantum expert time stamp module

$QERT85420

( see page 94 )

$TUnsignCptBmx

( see page 96 )

$TSignCptBmx

( see page 97 )

$EPITesysUAS

( see page 98 )

Quantum Expert Time Stamp Module

M340 high speed counter module

UnSign

M340 high speed counter module

Sign

Advantys special module for handling

TeSys_U information

$BMXEHC ( see page 100 ) M580 and X80 high speed counter module

Unity Elementary variables ( see page 102

Unity Array variables

( see page 105 )

Unity REF_TO Variables

( see page 107 )

)

Elementary variable templates

Array variable templates

Reference data type variable templates

Overview

EIO0000002403 06/2017

Overview

Location of Templates

Templates of the following families are located at the path indicated in the table:

Template family

Signal conditioning

STAHL templates

Hart

Peer to peer communication

Unity Special In Rack Cards

Path

Global Templates/Foundation Library/Application/Control

Modules/Unity/Unity Signal Conditioning

Global Templates/Foundation Library/Application/Control

Modules/STAHL

Global Templates/Foundation Library/Application/Control

Modules/Unity/Unity Signal Conditioning

Global Templates/Foundation Library/Application/Control

Modules/Unity/Unity Peer to Peer

Global Templates/Foundation Library/Application/Control

Modules/Unity/Unity Special In Rack Cards

EIO0000002403 06/2017

Process Expert

Signal Conditioning and Processing

EIO0000002403 06/2017

Signal Conditioning and Processing

Chapter 2 Signal Conditioning and Processing

Overview

This chapter describes the functionality of Foundation application templates for signal conditioning and processing, and their composition.

These templates do not reflect any specific installation.

WARNING

LOSS OF CONTROL



Perform a Failure Mode and Effects Analysis (FMEA) of your application, and apply preventive and detective controls before implementation.

Provide a fallback state for undesired control events or sequences.

Provide separate or redundant control paths wherever required.

Supply appropriate parameters, particularly for limits.

Review the implications of transmission delays and take actions to mitigate.

Review the implications of communication link interruptions and take actions to mitigate.

Provide independent paths for control functions (for example, emergency stop, over-limit conditions, and fault conditions) according to the safety analysis and applicable codes, and regulations.

Apply local accident prevention and safety regulations and guidelines. 1

Test each implementation of this library for proper operation before placing it into service.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

1 For additional information, refer to NEMA ICS 1.1 (latest edition), Safety Guidelines for the

Application, Installation, and Maintenance of Solid State Control and to NEMA ICS 7.1 (latest edition), Safety Standards for Construction and Guide for Selection, Installation and Operation of

Adjustable-Speed Drive Systems or their equivalent governing your particular location.

What Is in This Chapter?

This chapter contains the following sections:

Section

2.1

2.2

2.3

2.4

Topic

Signal Conditioning - Hardware Abstraction Layer

HART

Time Stamping

Peer to Peer Communication

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

Section

2.5

2.6

Topic

STAHL Control Module Templates

Using STAHL Control Module Templates

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

Signal Conditioning - Hardware Abstraction Layer

Section 2.1

Signal Conditioning - Hardware Abstraction Layer

Overview

This section explains the basic functionality of the hardware abstraction layer (HAL) templates

(signal objects) and their composition.

Hardware abstraction layer is a mechanism that emulates access to hardware resources to maintain an application device-independent. These HAL templates generate elementary digital or analog Control Participant variables, which represent the value and/or quality of hard-wired signals.

You can use these variables in the program and map them to the hardware that is configured in the topology. The mapping generates the corresponding topological addresses automatically.

What Is in This Section?

This section contains the following topics:

Topic

$AISignal_UL - Analog Input Signal Conditioning

$AOSignal_UL - Analog Output Signal Conditioning

$CounterSignal_UL - Counter Signal Conditioning

$DISignal_UL - Digital Input Signal Conditioning

$DOSignal_UL - Digital Output Signal Conditioning

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

$AISignal_UL - Analog Input Signal Conditioning

Description

The $AISignal_UL hardware abstraction layer facet template creates variables and elementary function blocks (EFBs) to model the value, and optionally, the quality of analog input signals.

Alternatively, the template can process an external variable of Int or Real data type in which case it acts as a pass-through without generating encapsulated constituents.

Parameters

The table describes the parameters of the $AISignal_UL facet template that you can configure.

Type Default value Description Name

Configuration

Type Boolean

AISignalName

ChannelDataType

String

Enum

False (check box cleared)

Blank

Int

Select this parameter to process signal quality in addition to signal value.

NOTE: The parameter is selected by default when ChannelDataType is Real.

Enter a name to be used for the generated EFB and variables.

Select the data type of the signal to be acquired:



Int



Real

The table describes the logic generated by the facet template depending on its parameter configuration.

Value of the Type parameter

Value of the

ChannelDataType parameter

Int

Generated logic

AISignalCond1 EFB is generated along with a variable.

False (check box cleared)

True (check box selected)

False (check box cleared)

True (check box selected)

Real

AISignalCond1 EFB is generated along with variables

( SIGNALVALUE , ERROR , COMSTATUS , MODULESTATUS , and

NOTMODULESTATUS ) to provide signal quality information.

AISignalCondReal1 EFB is generated along with variables

( SIGNALVALUE , ERROR , COMSTATUS , MODULESTATUS , and

NOTMODULESTATUS ) to provide signal quality information.

NOTE: During the build, the number of variables created varies depending on the hardware to which the facet template is mapped.

EIO0000002403 06/2017

Signal Conditioning and Processing

Analog Signal Acquisition and Transmission

The table describes the interfaces exposed by the facet template to acquire an analog input signal depending on the signal type that is configured and the signal source.

Signal type

Int

Real

Signal from an I/O channel

AIChannel: Mapping interface to be used in the Hardware

Mapping Editor.

Acquires signal with or without signal quality.

AIChannelReal: Mapping interface to be used in the

Hardware Mapping Editor.

Acquires signal with or without signal quality.

Variable from another instance



IntVar: Application interface to be used in the Links Editor.

Acquires signal value only.

Type/role: $Int / Ref

When the interface is connected, the template serves only as a pass-through and no logic is generated from it.

AINPUTSignalExt: Application interface to be used in the

Links Editor. Acquires signal value with signal quality.

Type/role: $AINPUTSignal / HO

To enable the interface, select to acquire also signal quality by setting the Type parameter to true.

RealVar: Application interface to be used in the Links Editor.

Acquires signal value with or without signal quality.

Type/role: $Real / Ref

When the interface is connected, the template serves only as a pass-through and no logic is generated from it.

NOTE: Connecting an application interface disables the other application interfaces as well as the corresponding mapping interface. For example, if the signal type is Int and the Type parameter true, connecting the IntVar interface disables the AINPUTSignalExt interface and the AIChannel mapping interface.

The table describes the interfaces exposed by the facet template to transmit an analog input signal depending on the interface that receives the signal and the type of the signal.

Signal transmission interface

AISignal

Type/role

/ Def

Description

AINPUTSignal

AISignalReal

AINSPUTSignalReal

/ DO

/ Def

/ DO

Transmits the name of the variable holding the signal value when the signal is acquired by using the IntVar interface.

Transmits the names of the variables holding the signal value and signal quality when the signal is acquired by using the AINPUTSignalExt or

AIChannel (mapping) interfaces.

Transmits the name of the variable holding the signal value when the signal is acquired by using the RealVar interface.

Transmits the names of the variables holding the signal value and signal quality when the signal is acquired by using the RealVar or AIChannelReal

(mapping) interfaces.

EIO0000002403 06/2017

Signal Conditioning and Processing

Composition

The template encapsulates the AISignalCond1 and AISignalCondReal1 EFBs, which provide the core Control services.

Control Resource Description

Refer to the AISignalCond1 and AISignalCondReal1 - Analog Input Signal Conditioning

(see Process Expert , Foundation Control Services User Guide) for more details.

EIO0000002403 06/2017

Signal Conditioning and Processing

$AOSignal_UL - Analog Output Signal Conditioning

General Description

The $AOSignal_UL hardware abstraction layer facet template creates variables to model the value, and optionally the quality of analog output signals.

Alternatively, the template can process an external variable of Int data type in which case it acts as a pass-through.

Applying the Analog Signal

The table describes the options offered by the facet template to apply an analog output signal:

Hardware mapping Links Signal applied to

I/O Channel

Signal quality no yes

Variable no yes

AOChannel/SO mapping interface

–

IntVar PO interface: Signal value only

AOUTPUTSignalExt PO interface: Signal quality

IntVar and AOSignal interfaces. Signal value only.

IntVar and AOSignal interfaces: Signal value only.

AOUTPUTSignalExt and AOUTPUTSignal interfaces: Signal quality

NOTE: Using a PO interface disables the mapping interface.

Parameters

The table describes the parameters of the $AOSignal_UL facet template that you can configure:

Type Default value Description Name

Configuration

Type Boolean 0

AOSignalName

ChannelDataType

String

Enum empty

Int

Select this parameter to process signal quality in addition to signal value.

Enter a name to be used for the generated DFB and variables.

Select the data type of the signal to be acquired:



Int



Real

EIO0000002403 06/2017

Signal Conditioning and Processing

The table describes the logic generated by the facet template depending on the Include Signal

Quality and Conditioning parameter configuration:

Type value Generated logic

False

(check box cleared)

A variable and AOSIGNALMOVE DFB are generated.

True (check box selected)

AOSIGNALCOND DFB is generated along with variables

( SIGNALVALUE , ERROR , COMSTATUS , MODULESTATUS , and

NOTMODULESTATUS ) to provide signal quality information.

NOTE: During the build, the number of variables created varies depending on the hardware to which the facet template is mapped.

Composition

The HAL template encapsulates the AOSIGNALCOND and AOSIGNALMOVE DFBs, which provide the core Control services.

Control Resource Description

Refer to the AOSIGNALCOND - Analog Output Signal Conditioning (see Process Expert ,

Foundation Control Services User Guide) for more details.

EIO0000002403 06/2017

Signal Conditioning and Processing

$CounterSignal_UL - Counter Signal Conditioning

General Description

The $CounterSignal_UL hardware abstraction layer facet template creates variables to model the value, and optionally the quality of counter signals.

Counter Signal Acquisition

The table describes the options offered by the $CounterSignal_UL facet template to acquire a counter signal depending on the channel data type as shown below:

Signal acquired from

Variable

Channel Data

Type

UDINT

Hardware mapping Links

UINT

CounterChannelUDINT/SO mapping interface

CounterSignalUDINT and

CounterSignal interfaces:

Signal value only.

CounterSignalUDINTExt and CounterSignal interfaces: Signal quality

CounterSignalUINT and

CounterSignal interfaces:

Signal value only.

CounterSignalUINTExt and CounterSignal interfaces: Signal quality

Counter Channel

( BMXEHC0200/BMXEHC0800/

BMXERT1604T/140QEHC10500

/140QEHC20200 )

UDINT

Counter Channel

( 140QEHC10500/

140QEHC20200 )

UINT CounterChannelUINT/SO mapping interface

EIO0000002403 06/2017

Signal Conditioning and Processing

Parameters

The table describes the parameters of the $CounterSignal_UL facet template that you can configure:

Type Default value Description Name

Configuration

CounterSignalName String Empty

ChannelDataType Enum UDINT

Enter a name to be used for the generated EFB and variables.

Selects the channel data type of the signal to be acquired

 UDINT

 UINT

NOTE: During the build, the number of variables created varies depending on the hardware to which the facet template is mapped.

Composition

The HAL template encapsulates the CounterSignalCondUDInt and CounterSignal-

CondUInt EFBs, which provide the core Control services.

Control Resource Description

Refer to the CounterSignalCondUDInt and CounterSignalCondUInt - Counter Signal

Conditioning (see Process Expert , Foundation Control Services User Guide) for more details.

EIO0000002403 06/2017

Signal Conditioning and Processing

$DISignal_UL - Digital Input Signal Conditioning

General Description

The $DISignal_UL hardware abstraction layer facet template creates variables to model the value, and optionally the quality of digital input signals.

Alternatively, the template can process an external variable in which case it acts as a pass-through without generating encapsulated constituents.

Digital Signal Acquisition

The table describes the options offered by the facet template to acquire a digital input signal depending on the signal source:

Hardware mapping Links Signal acquired from

I/O Channel

Signal quality no yes

Variable no yes

DIChannel/SO mapping interface

–

BoolVar PO interface: Signal value only

DINPUTSignalExt PO interface: Signal quality

BoolVar and DISignal interfaces. Signal value only.

BoolVar and DISignal interfaces: Signal value only.

DINPUTSignalExt and DINPUTSignal interfaces: Signal quality

NOTE: Using a PO interface disables the mapping interface.

Parameters

The table describes the parameters of the $DISignal_UL facet template that you can configure:

Type Default value Description Name

Configuration

Negate

Type

DISignalName

Boolean

String

False

Empty

True = Negates the input or output signal.

Select this parameter to process signal quality in addition to signal value.

Enter a name to be used for the generated EFB and variables.

EIO0000002403 06/2017

Signal Conditioning and Processing

Name

TimeStamping

PLCHMIVar

Type

Enum

Boolean

Default value Description

None Sets the Time stamping variable providing the signal value.

Possible values:

 Both edges .



Rising edges .

Falling edges .

None .

attributes of the generated

False

NOTE: By default, Process Expert uses the System time stamping mode, which supports only the both

Edges setting.

The other values are supported by the Applicative time stamping mode. Refer to the topic describing

Unity Pro Settings (see Process Expert, Control

Participant Services, User Guide) .

Sets the HMI variable attribute of the generated variable providing the signal value.

NOTE: Set this parameter to True if you change the default value for TimeStamping ; otherwise, the Time stamping attribute of the generated variable is set to

None independently of your selection.

The table describes the logic generated by the facet template depending on the Include Also

Quality Signal parameter configuration:

Type value

False (check box cleared)

True (check box selected)

Negate value Generated logic

0 or 1 A variable and DISignalCond1 EFB are generated.

0 or 1

(

DISignalCond1

SIGNALVALUE ,

EFB is generated along with variables

ERROR , COMSTATUS , MODULESTATUS , and

NOTMODULESTATUS ) to provide signal quality information.

NOTE: During the build, the number of variables created varies depending on the hardware to which the facet template is mapped.

Composition

The HAL template encapsulates the DISignalCond1 EFB, which provides the core Control services.

Control Resource Description

Refer to the DISignalCond1 - Digital Input Signal Conditioning (see Process Expert , Foundation

Control Services User Guide) for more details.

EIO0000002403 06/2017

Signal Conditioning and Processing

$DOSignal_UL - Digital Output Signal Conditioning

General Description

The $DOSignal_UL hardware abstraction layer facet template creates variables to model the value, and optionally the quality of analog output signals.

Alternatively, the template can process an external variable in which case it acts as a pass-through.

Applying the Digital Signal

The table describes the options offered by the facet template to apply a digital output signal:

Signal applied to

I/O Channel

Variable

Signal quality no yes no yes

Hardware mapping Links

DOChannel/SO mapping interface

–

BoolVar PO interface: Signal value only

DOUTPUTSignalExt PO interface: Signal quality

BoolVar and DOSignal interfaces. Signal value only.

BoolVar and DOSignal interfaces: Signal value only.

DOUTPUTSignalExt and DOUTPUTSignal interfaces: Signal quality

NOTE: Using a PO interface disables the mapping interface.

Parameters

The table describes the parameters of the $DOSignal_UL facet template that you can configure:

Type Default value Description Name

Configuration

Negate

Type

DOSignalName

Boolean

String

False

Empty

True = Negates the input or output signal.

Select this parameter to process signal quality in addition to signal value.

Enter a name to be used for the generated DFB and variables.

EIO0000002403 06/2017

Signal Conditioning and Processing

The table describes the logic generated by the facet template depending on the Include Also

Quality Signal parameter configuration:

Type value

False

(check box cleared)

True

(check box selected)

Generated logic

A variable and DOSIGNALMOVE DFB are generated.

DOSIGNALCOND DFB is generated along with variables

( SIGNALVALUE , ERROR , COMSTATUS , MODULESTATUS , and

NOTMODULESTATUS ) to provide signal quality information.

NOTE: During the build, the number of variables created varies depending on the hardware to which the facet template is mapped.

Composition

The HAL template encapsulates the $DOSIGNALCOND and DOSIGNALMOVE DFBs, which provide the core Control services.

Control Resource Description

Refer to the DOSIGNALCOND - Digital Output Signal Conditioning (see Process Expert ,

Foundation Control Services User Guide) for more details.

EIO0000002403 06/2017

Signal Conditioning and Processing

HART

Section 2.2

HART

Overview

This section describes the functionality of HART templates and their composition.

What Is in This Section?

This section contains the following topics:

Topic

$AHISignal_UL - HART Device Signal Mapping

$AISignalHART_UL - HART Input Signal Conditioning (M580)

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

$AHISignal_UL - HART Device Signal Mapping

Description

The $AHISignal_UL facet template models the value and/or quality of signals of HART devices that are part of the Krohne instrumentation library. It allows mapping these signals to the four channels of an STBAHI8321 HART interface module, using one mapping interface.

You can also use this template together with the $AnalogInput or $AnalogInput1 templates to map signals of custom Krohne-like templates.

For more information, refer to the description of the various use cases (see Process Expert ,

Process Templates User Guide) .

NOTE: This facet template is referenced by templates of the Krohne instrumentation library.

Composition

The $AHISignal_UL template encapsulates the AHISIGNAL DFB (see Process Expert ,

Foundation Control Services User Guide) , which provides core Control services.

Interfaces

The template exposes the following interfaces:

Interface identifier

HARTChData

PAISignalReal

PAINPUTSignalReal

SAISignalReal

SAINPUTSignalReal

TAISignalReal

TAINPUTSignalReal

QAISignalReal

QAINPUTSignalReal

Type/role

$HARTChData/Def

Description

Channel data from AHISIGNAL to HART DFB.

$Real/Def

Provides the name of the primary variable.

$AinputSignalReal/DO Provides the name of the primary variable with signal quality.

Provides the name of the secondary variable.

$AinputSignalReal/DO Provides the name of the secondary variable with signal quality.

$Real/Def Provides the name of the tertiary variable.

$AinputSignalReal/DO Provides the name of the tertiary variable with signal quality.

$Real/Def Provides the name of the quaternary variable.

$AinputSignalReal/DO Provides the name of the quaternary variable with signal quality.

EIO0000002403 06/2017

Signal Conditioning and Processing

$AISignalHART_UL - HART Input Signal Conditioning (M580)

Description

The Hardware Mapping Editor of Process Expert allows you to map only 1 signal per channel of a supported HART analog I/O module, which is configured in the topology. The HART module is acting as a regular I/O module and the signal corresponds to the Primary Variable (PV). The other

HART signals, for example, Secondary Variable (SV), Tertiary Variable (TV), and/or Quarternary

Variable (QV), and so on are not available.

The $AISignalHART_UL facet template allows you to use all HART signals (including PV) coming from supported HART analog input and output modules by allocating manually state RAM addresses to variables representing these HART signals.

Parameters

The table describes the parameters of the $AISignalHART_UL facet template that you can configure:

Name

AISignalVar_Add

AISignalError_Add

Type

String

AISignalModStatus_Add String

AISignalName

Type

String

Boolean

Default value

Description

HART AI signal value address excluding %MW

HART Detected error in AI signal address excluding %MW

HART AI signal mod status address excluding

%MW

Enter a name to be used for the generated EFB and variables.

Select this parameter to process signal quality in addition to signal value.

Composition

The template encapsulates the following constituents, which provide the Control services:

 AISignalHart1



AISignalErrorBOOL

AISignalModStBOOL

AISignalVar

EIO0000002403 06/2017

Signal Conditioning and Processing

Time Stamping

Section 2.3

Time Stamping

$TSDInput - Time Stamped Information of Field Signals

General Description

The $TSDInput control module template receives time stamped information of field signals and passes this information on to alarm pages of the Supervision runtime.

NOTE:

Apart from the single-channel time stamping template, 8-, 16-, 32 channel time stamping templates are also available.

 $TSDInput8 : This template receives time stamped information from 8-channel time stamping



 modules.

$TSDInput16 : This template receives time stamped information from 16-channel time stamping modules.

$TSDInput32 : This template receives time stamped information from 32-channel time stamping modules.

The configuration of these templates is similar to the single-channel time stamping template.

EIO0000002403 06/2017

Signal Conditioning and Processing

Parameters

Configuration

The table describes the Configuration parameters that you can configure:

Element Name Name

Control Negate

Type

DISignalName

TimeStamping

Type

Boolean

String

Enum

Default value Description

False

True = Negates the input or output signal.

Refer to DISignal_UL ( see page 29 ) .

–

Both Edges

Enter a name to be used for the generated

EFB and variables.

Sets the Time stamping attributes of the generated variable providing the signal value.

Possible values:

 Both edges .



Rising edges .

Falling edges .

None .

NOTE: By default, Process Expert uses the

System time stamping mode, which supports only the Both Edges setting.

The other values are supported by the

Applicative time stamping mode. Refer to the topic describing Unity Pro Settings

(see Process Expert, Control Participant

Services, User Guide) .

Composition

The $TSDInput template references composite and facet templates, which provide the following services:

Control Includes core services input signal.

Supervision These services complement the Control services.Supervision Services are optional.

The table describes the services that are available from the $TSDInput control module and the corresponding facet, which implements the service:

Control

Services

Facet template Facet template

Control $DISignal_UL

Control service description

Refer to

$DISignal_UL

(see Process Expert

, Foundation Control

Services User Guide)

Associated

Supervision services

Corresponding facet template

Supervision $TSDISignal

_CD

Control

Services

Control $DISignal

_UL

EIO0000002403 06/2017

Signal Conditioning and Processing

The table describes the services that are available from the $TSDInput8 , $TSDInput16 ,

$TSDInput32 control module and the corresponding facet, which implements the service:

Control Services

( $TSDISignalx_UC )

Control TSDISignal

_1 to

TSDISignal

Facet template

$DISignal_

Control service description

Refer to

$DISignal_UL

(see Process

Expert ,

Foundation

Control

Services User

Guide)

Where x represents the number of channels (8, 16, or 32)

Associated Supervision services

($TSDISignalx_CS)

TSDISignal_CD1 to

TSDISignal_CDx

Corresponding facet template

$TSDISignal_CD

Interfaces

The time stamping templates expose the following application interfaces:

Interface identifier

DISignal

DINPUTSignal

Type/role

$Bool/Def

$DINPUTSignal/Def

Description

Provides the name of the parameter, which holds the digital input signal value.

Provides the name of the parameters, which hold the digital input signal value and signal quality.

NOTE: There are as many pairs of interfaces as there are channels.

EIO0000002403 06/2017

Signal Conditioning and Processing

Peer to Peer Communication

Section 2.4

Peer to Peer Communication

Overview

This section describes the functionality of peer to peer communication templates and their composition.

What Is in This Section?

This section contains the following topics:

Topic

Owner/Consumer Templates

Data In/Data Out Templates

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

Owner/Consumer Templates

Description

Owner-consumer templates allow you to exchange, using peer to peer communication, sets of data between two Control projects, one being the owner, the other the consumer communicate different data types.

(see Process Expert,

User Guide) , and the consumer template to the consumer project. Several templates exist to

The owner template is assigned to the owner project, which provides the data: Either physical I/O signals or external variables (logical signals).

The owner template gets data through the following ways:



Hardware mapping for physical I/O signals



Interface links with other instances (Links Editor) or refinement for logical signals

You can use only 1 type of link at once for each channel.

Both data value and detected failure value are transported between the owner and the consumer.

In addition to the detected failure value provided by the owner, you can configure it to also include the quality of the signal.

1 pair of owner/consumer templates exists for each of the following use cases:



Digital signals:



Exchange of up to 16 boolean input signals

Exchange of up to 16 boolean output signals



Analog signals:



Exchange of up to 8 integer input signals



Exchange of up to 8 integer output signals

NOTE: A typical use case for these templates is to implement distributed I/Os with the Modicon

M340 PRA module. In such use case, the Control project deployed to the PRA acts as owner, and the Control project executing the logic acts as the consumer.

Template Naming Convention

The templates follow a naming convention:

$<data type><amount of data><signal type>_<role>

Where:



<data type> is Bool or Int



<amount of data> is 8 or 16

<Signal type> is IN for inputs (from owner to consumer) or OUT for outputs (from consumer to owner)

<role> is O for the owner side and C for the consumer side

EIO0000002403 06/2017

Signal Conditioning and Processing

Configuring the Communication Timeout

An internal mechanism is present in the templates to verify if the peer to peer communication is working correctly. A continuously increasing internal counter keeps sending the count value to the counterpart controller, which monitors this count value and detects whether the count value is stalled within a time-out value.

You can configure the Communication Time Out parameter in the instance of the consumer template, using the Properties window. Enter a value in seconds, depending on the architecture that is used.

List of Templates

The following owner/consumer templates are available:

Identifier

$Bool16INO

$Bool16INC

$Bool16OUTO

$Bool16OUTC

$Int8INO

$Int8INC

$Int8OUTO

$Int8OUTC

Description

Packs and exposes up to 16 boolean input signals from the owner project and exposes them to the consumer.

Unpacks and consumes up to 16 boolean input signals that are received from the owner project.

Packs and exposes up to 16 boolean output signals from the owner project and exposes them to the consumer.

Unpacks and consumes up to 16 boolean output signals that are received from the owner project.

Packs and exposes up to 8 integer input signals from the owner project and exposes them to the consumer.

Unpacks and consumes up to 8 integer input signals that are received from the owner project.

Packs and exposes up to 8 integer output signals from the owner project and exposes them to the consumer.

Unpacks and consumes up to 8 integer output signals that are received from the owner project.

EIO0000002403 06/2017

Signal Conditioning and Processing

$Bool16INO

The template exposes the following interfaces:

Name

Bool16InO

DISignalxx

DINPUTSignalxx

Type/role Description

$Bool16InData/Def Application interface to link to the related consumer template.

$Bool/Ref Application interface for digital signal value. This interface only provides the name of the variable holding the digital signal value.

Linking this interface disables the

DINPUTSignalxx interface for the channel.

$DINPUTSignal/Ref Application interface for external signal and detected failure value.

Linking this interface disables the DISignalxx interface for the channel.

NOTE: xx represents the channel number in the template, from 01 to 16.

$Bool16INC

The template exposes the following interfaces:

Name

Bool16InC

$DISignalxx

$DINPUTSignalxx

Type/role

$Bool16InData/Ref

$Bool/Def

$DInputSignal/Def

Description

Application interface to link to the related owner template.

Application interface for digital signal value.

Application interface for signal and detected failure value.

NOTE: xx represents the channel number in the template, from 01 to 16.

$Bool16OUTO

The template exposes the following interfaces:

Name

Bool16OutData

BoolVarxx

DOUPUTSignalxx

Type/role

$Bool16OutData/Def

$Bool/Def

$DOUTPUTSignal/PO

Description

Application interface to link to the related consumer template.

Application interface for digital signal value.

Application interface for external signal and detected failure value.

NOTE: xx represents the channel number in the template, from 01 to 16.

EIO0000002403 06/2017

Signal Conditioning and Processing

$Bool16OUTC

The template exposes the following interfaces:

Name

Bool16OutData

BoolVarxx

DOUTPUTSignalxx

Type/role

$Bool16OutData/Ref

$Bool/Ref

$DOUTPUTSignal/DO

Description

Application interface to link to the related owner template.

Application interface for digital signal value.

Application interface for signal and detected failure value.

NOTE: xx represents the channel number in the template, from 01 to 16.

$Int8INO

The template exposes the following interfaces:

Name

Int8InO

AISignalxx

AINPUTSignalxx

Type/role

$Int8InData/Def

$Int/Ref

$AINPUTSignal/HO

Description

Application interface to link to the related consumer template.

Application interface for analog signal value.

Linking this interface disables the

AINPUTSignalxx interface for the channel.

Application interface for external signal and detected failure value.

Linking this interface disables the

AISignalxx interface for the channel.

NOTE: xx represents the channel number in the template, from 01 to 08.

$Int8INC

The template exposes the following interfaces:

Name

Int8InC

$AISignalxx

$AINPUTSignalxx

Type/role

$Int8InData/Ref

$Int/Def

$AINPUTSignal/DO

Description

Application interface to link to the related owner template.

Application interface for analog signal value.

Application Interface for signal and detected failure value.

NOTE: xx represents the channel number in the template, from 01 to 08.

EIO0000002403 06/2017

Signal Conditioning and Processing

$Int8OUTO

The template exposes the following interfaces:

Name

Int8OutData

IntVarxx

AOUTPUTSignalxx

Type/role

$Int8OutData/Def

$Int/Def

$AOUTPUTSignal/PO

Description

Application interface to link to the related consumer template.

Application interface for analog signal value.

Application interface for external signal and detected failure value.

NOTE: xx represents the channel number in the template, from 01 to 08.

$Int8OUTC

The template exposes the following interfaces:

Name

Int8OutData

IntVarxx

AOUTPUTSignalxx

Type/role

$Int8OutData/Ref

$Int/Ref

$AOUTPUTSignal/DO

Description

Application interface to link to the related owner template.

Application interface for analog signal value.

Application interface for signal and detected failure value.

NOTE: xx represents the channel number in the template, from 01 to 08.

Reference Documents

Refer to Owner/Consumer more information.

(see Process Expert , Foundation Control Services User Guide) for

EIO0000002403 06/2017

Signal Conditioning and Processing

Using the Digital Input Owner/Consumer Templates

The following example explains how to use the digital input owner/consumer templates

( $Bool16INO / $Bool16INC ):

Step

Action

Instantiate $Bool16INO and $Bool16INC in the Application Explorer.

In the Links Editor, link the Bool16INO interface from the owner to the consumer.

Link BoolVar interface of $Bool16INO to a boolean variable in the Links Editor if required or else you can perform hardware mapping to actual digital input card in the Projects Explorer.

NOTE: You can link the channel only once. If you link the channel to a variable, the channel is not available anymore during hardware mapping.

Refer to the following figure.

You can link the consumer output interfaces DISignal to variables and

DInputSignal to DigitalInput instances, using the Links Editor. To link a

DigitalInput instance to a DInputSignal interface, set the Include also

Quality Signal parameter to 1.

Refer to the figures below.

Refer to the Peer to Peer Communication Through Modbus TCP (see Process

Expert, User Guide) for information on the other steps that you need to complete to implement peer to peer communication.

EIO0000002403 06/2017

Signal Conditioning and Processing

The following figure shows how to link to the DISignal01Var interface of an instance of Bool16INO interface of $Bool16INO to the MotorOP interface of an instance of $Motor and how to link the

$Bool16INO interface to the Bool16INC interface of an instance of $Bool16INC.

EIO0000002403 06/2017

Signal Conditioning and Processing

The following figure shows how to link the consumer output interface DINPUTDSignal01 to the

DINPUTSignalExt interface of an instance of $DigitalInput .

EIO0000002403 06/2017

Signal Conditioning and Processing

The following figure shows how include also signal quality by setting the Type parameter of the

DISignal element to true in the Instance Editor window of the Application Explorer.

EIO0000002403 06/2017

Signal Conditioning and Processing

Data In/Data Out Templates

Description

The Data In/Data Out facet templates allow you to exchange, by using peer to peer communication, scattered data between two or more Control projects, one being the owner, the others the consumer (see Process Expert, User Guide) . The Data Out template is assigned to the owner project and the Data In template to the consumer project. Several templates exist to communicate data of different data types between projects.

There are 2 different types of templates:



Data Out templates create a variable in the owner that can be accessed from 1 consumer.



Instantiate as many Data Out templates as there are consumers that need to access the shared data.

Data In templates create a network variable to receive data from the owner.

(see Process Expert, User Guide) in the consumer

Number of templates:



There are 11 Data Out templates and 11 corresponding Data In templates.



The 11 templates correspond to 11 different data types, which are Bool , Int , Dint , Word ,

Real , Array[1..8] of Int , Array[1..100] of Int , Array[1..125

of Int ,

Array[1..8] of Real , Array[1..50] of Real , and Array[1..62] of Real .

NOTE: You can use a Data Out template only to link directly to the functional variable input pin of any instance assigned to the consumer project. In such case, you need to create the network variable in the consumer, using the Manage Network Variables dialog box (see Process Expert,

User Guide) .

List of Templates

The following Data In/Data Out templates are available:

Identifier

$DINBool_UL

$DOUTBool_UL

$DINInt_UL

$DOUTInt_UL

$DINDInt_UL

$DOUTDInt_UL

$DINReal_UL

$DOUTReal_UL

$DINWord_UL

$DOUTWord_UL

Description

Data In template for Bool data type.

Data Out template for Bool data type.

Data In template for Int data type.

Data Out template for Int data type.

Data In template for DInt data type.

Data Out template for DInt data type.

Data In template for Real data type.

Data Out template for Real data type.

Data In template for Word data type.

Data Out template for Word data type.

EIO0000002403 06/2017

Signal Conditioning and Processing

Identifier

$DIN8Int_UL

$DOUT8Int_UL

$DIN99Int_UL

$DOUT99Int_UL

$DIN124Int_UL

$DOUT124Int_UL

$DIN8Real_UL

$DOUT8Real_UL

$DIN49Real_UL

$DOUT49Real_UL

$DIN62Real_UL

$DOUT62Real_UL

Description

Data In template for Array[1..8] of Int data type.

Data Out template for Array[1..8] of Int data type.

Data In template for Array[1..100] of Int data type.

Data Out template for Array[1..100] of Int data type.

Data In template for Array[1..125] of Int data type.

Data Out template for Array[1..125] of Int data type.

Data In template for Array[1..8] of Real data type.

Data Out template for Array[1..8] of Real data type.

Data In template for Array[1..50] of Real data type.

Data Out template for Array[1..50] of Real data type.

Data In template for Array[1..62] of Real data type.

Data Out template for Array[1..62] of Real data type.

Data Out Interfaces

The $DOUTBool_UL template exposes the following interfaces:

Name

OUT

Type/role

$Bool/Ref

$Bool/Def

Description

Application Interface to link to any variable in the owner that is to be exchanged through the network, including pins of DFBs.

Application interface to link to the related DataIn instance, which will consume the variable or to the functional variable input pin of any other instance.

NOTE: Identical interfaces are present in the other 10 templates with the type changing according to their respective data types, which are Int , Dint , Word , Real , Array[1..8] of Int ,

Array[1..100] of Int , Array[1..125] of Int , Array[1..8] of Real , Array[1..50] of

Real , Array[1..62] of Real .

Data In Interfaces

The $DINBool_UL template exposes the following interfaces:

Name

Type/role

$Bool/Ref

Description

Application interface to link to the variable from the owner. It receives the name of the network variable that is created in the owner project.

EIO0000002403 06/2017

Signal Conditioning and Processing

Name

OutToVar

Out

Type/role

$Bool/Ref

$Bool/Def

Description

This interface is used to provide the name of a variable of same type to which the value coming from the owner project needs to be passed on.

Otherwise, link the Out interface to one or more instances assigned to the consumer project.

Application interface to link to 1 or more input pins of a DFB in the consumer. The interface provides the name of the variable.

NOTE: Identical interfaces are present for the remaining 10 templates with the role identifiers changing according to their respective data types, which are Int , DInt , Word , Real ,

Array[1..8] of Int , Array[1..100] of Int , Array[1..125] of Int , Array[1..8] of Real , Array[1..50] of Real , and Array[1..62] of Real .

Reference Document

Refer to Move_<type> DFBs more information.

(see Process Expert , Foundation Control Services User Guide) for

Using Data In/Out Templates

The following example explains how to use the Data In/Out templates

( $DINBool_UL\$DOUTBool_UL ) to exchange a boolean variable (represented by the $Bool_UL template):

Step Action

1 In the Application Explorer, instantiate $DINBool_UL , $DOUTBool_UL , Motor , and $Bool_UL .

2 Link the OUT interface of $DOUTBool_UL to the IN interface of $DINBool_UL .

Refer to the figure below.

3 In the Links Editor, link the IN interface of $DOUTBool_UL to the MotorOP interface of $Motor .

4 Link the OutToVar interface of $DINBool_UL to $Bool_UL .

5 Refer to the Peer to Peer Communication Through Modbus TCP (see Process

Expert, User Guide) for information on the other steps that you need to complete to implement peer to peer communication.

EIO0000002403 06/2017

Signal Conditioning and Processing

The following figure shows how to link the OUT interface of $DOUTBool_UL to the IN interface of

$DINBool_UL .

EIO0000002403 06/2017

Signal Conditioning and Processing

STAHL Control Module Templates

Section 2.5

STAHL Control Module Templates

Overview.

This section describes the basic functionality of the STAHL templates and their composition.

What Is in This Section?

This section contains the following topics:

Topic

$STAHLAI8 for STAHL 8-channel Analog Input Modules

$STAHLAO8 for STAHL 8-Channel Analog Output Modules

$STAHLDI16 for STAHL 16-Channel Digital Input Modules

$STAHLDO8 for STAHL 8-Channel Digital Output Modules

$STAHLAI8HART for STAHL 8-channel Analog Input Modules with HART Signals

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

$STAHLAI8 for STAHL 8-channel Analog Input Modules

General Description

The $STAHLAI8 control module template allows reading the analog input signal value and signal quality data from 8 input channels of a STAHL analog input module.

Parameters

Each instance of this template allows you to configure the offset between a range of values for the function block that it generates. If you configure offset parameter values incorrectly, a mismatch can occur between the field device and the generated function block, which leads to the exchange of incorrect information.

WARNING

LOSS OF CONTROL

1. Allow only qualified personnel to configure offset parameter values.

2. Conduct a safety analysis for the application and equipment installed.

3. Verify that the offset parameter values match the STAHL configuration values.

4. Verify the offset parameter values for each input pin of the function block that is generated by an instance of the template.

5. Validate offset parameter values under simulated conditions before deployment in the field.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Element

Name

Control

The table describes the Configuration parameters, which you can configure.

Name Type Default value Description

InputModuleDataOffset SHORT 0

InputModuleStatusOffset SHORT 0

Offset of input data in context of STAHL IS1 Remote

I/O system.

Offset of status data in context of STAHL

IS1 Remote I/O system.

EIO0000002403 06/2017

Signal Conditioning and Processing

Composition

The $STAHLAI8 template references composite and facet templates that provide the following services:

Control Core services.

The table describes the services that are available from the $STAHLAI8 control module and the corresponding facet, which implements the service:

Control services

Composite template

Corresponding facet template

Control service description

Associated

Supervision services

Corresponding facet template

Supervision service description

Core services

– – – – – $STAHLAI8_UL Refer to the

STAHLAI8CH DFB

(see Process Expert ,

Foundation Control

Services User Guide) .

The control module template exposes the following interfaces.

Interface identifier

VarName

AISignal01...AISignal08

Type/role

VarName/B

$Int/Def

AINPUTSignal01...AINPUT

Signal08

$AINPUTSignal/DO

Description

Receives the variable name.

Provides the analog input signal value of channels 0 to 7.

Provides the analog input signal value and diagnostic information of channels 0 to 7.

EIO0000002403 06/2017

Signal Conditioning and Processing

$STAHLAO8 for STAHL 8-Channel Analog Output Modules

General Description

The $STAHLAO8 control module template allows writing the analog output signal value to 8 output channels of a STAHL analog output module. It also reads the signal quality data from each channel.

Parameters

WARNING

LOSS OF CONTROL

1. Allow only qualified personnel to configure offset parameter values.

2. Conduct a safety analysis for the application and equipment installed.

3. Verify that the offset parameter values match the STAHL configuration values.

4. Verify the offset parameter values for each input pin of the function block that is generated by an instance of the template.

5. Validate offset parameter values under simulated conditions before deployment in the field.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Element

Name

Control

Configuration

The table describes the Configuration parameters, which you can configure.

Name

OutputModuleDataOffset

Type

SHORT

Default value

Description

OutputModuleStatusOffset SHORT 0

Offset of output data in context of STAHL

IS1 Remote I/O system.

Offset of output status data in context of STAHL

IS1 Remote I/O system.

EIO0000002403 06/2017

Signal Conditioning and Processing

Composition

The $STAHLAO8 template references composite and facet templates that provide the following services:

Control Core services.

The table describes the services that are available from the $STAHLAO8 control module and the corresponding facet, which implements the service:

Control services

Composite template

Corresponding facet template

Control service description

Associated

Supervision services

Corresponding facet template

Supervision service description

Core services

– – $STAHLAO8_UL – – – Refer to the

STAHLAO8CH DFB

(see Process Expert ,

Foundation Control

Services User Guide) .

The control module template exposes the following interfaces:

Interface identifier

VarName

AOSignal01...AOSignal08

Type/role

VarName/B

$Int/Ref

AOUTPUTSignal01...AOUTPUT

Signal08

$AOUTPUTSignal/DO

Description

Variable name.

Provides the analog output signal value of channels 0 to 7.

Provides the analog output signal value and diagnostic information of channels 0 to 7.

EIO0000002403 06/2017

Signal Conditioning and Processing

$STAHLDI16 for STAHL 16-Channel Digital Input Modules

General Description

The $STAHLDI16 control module template allows reading the digital input signal value and signal quality data from 16 input channels of a STAHL digital input module.

Parameters

WARNING

LOSS OF CONTROL

1. Allow only qualified personnel to configure offset parameter values.

2. Conduct a safety analysis for the application and equipment installed.

3. Verify that the offset parameter values match the STAHL configuration values.

4. Verify the offset parameter values for each input pin of the function block that is generated by an instance of the template.

5. Validate offset parameter values under simulated conditions before deployment in the field.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Element

Name

Control

Configuration

The table describes the Configuration parameters, which you can configure.

Name Type Default value Description

InputModuleDataOffset SHORT 0

InputModuleStatusOffset SHORT 0

Offset of input data in context of STAHL IS1 Remote

I/O system.

Offset of status data in context of STAHL

IS1 Remote I/O system.

EIO0000002403 06/2017

Signal Conditioning and Processing

Composition

The $STAHLDI16 template references composite and facet templates that provide the following services:

Control Core services.

The table describes the services that are available from the $STAHLDI16 control module and the corresponding facet, which implements the service:

Control services

Composite template

Corresponding facet template

Control service description

Associated

Supervision services

Corresponding facet template

Supervision service description

Core services

– – – – – $STAHLDI16_UL Refer to the

STAHLDI16CH DFB

(see Process Expert ,

Foundation Control

Services User Guide) .

The control module template exposes the following interfaces:

Interface identifier

VarName

DISignal01...DISignal16

Type/role

VarName/B

$Bool/Def

DINPUTSignal01...DINPUT

Signal16

$DINPUTSignal/Def

Description

Received the variable name.

Provides the digital input signal value of channels 0 to 15.

Provides the digital input signal value and diagnostic information of channels 0 to 15.

EIO0000002403 06/2017

Signal Conditioning and Processing

$STAHLDO8 for STAHL 8-Channel Digital Output Modules

General Description

The $STAHLDO8 control module template allows writing the digital output signal value to 8 output channels of a STAHL digital output module. It also reads the signal quality data from each channel.

Parameters

WARNING

LOSS OF CONTROL

1. Allow only qualified personnel to configure offset parameter values.

2. Conduct a safety analysis for the application and equipment installed.

3. Verify that the offset parameter values match the STAHL configuration values.

4. Verify the offset parameter values for each input pin of the function block that is generated by an instance of the template.

5. Validate offset parameter values under simulated conditions before deployment in the field.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Element

Name

Control

Configuration

The table describes the Configuration parameters, which you can configure.

Name Type Description

OutputModuleDataOffset SHORT

Default value

OutputModuleStatusOffset SHORT 0

Offset of output data in context of STAHL

IS1 Remote I/O system.

Offset of output status data in context of STAHL

IS1 Remote I/O system.

EIO0000002403 06/2017

Signal Conditioning and Processing

Composition

The $STAHLDO8 template references composite and facet templates that provide the following services:

Control Core services.

The table describes the services that are available from the $STAHLDO8 control module and the corresponding facet, which implements the service:

Control services

Composite template

Corresponding facet template

Control service description

Associated

Supervision services

Corresponding facet template

Supervision service description

Core services

– – $STAHLDO8_UL – – – Refer to the

STAHLDO8CH DFB

(see Process Expert ,

Foundation Control

Services User Guide) .

The control module template exposes the following interfaces:

Interface identifier

VarName

DOSignal01...DOSignal08

Type/role

VarName/B

$Bool/Ref

DOUTPUTSignal01...DOUTPUT

Signal08

$DOUTPUTSignal/DO

Description

Variable name.

Provides the digital output signal value of channels 0 to 7.

Provides the digital output signal value and diagnostic information of channels 0 to 7.

EIO0000002403 06/2017

Signal Conditioning and Processing

$STAHLAI8HART for STAHL 8-channel Analog Input Modules with HART Signals

General Description

The $STAHLAI8HART control module template allows reading the analog input signal value and signal quality data from 8 input channels of a STAHL analog input module HART. It also processes four or eight HART signals.

Parameters

WARNING

LOSS OF CONTROL

1. Allow only qualified personnel to configure offset parameter values.

2. Conduct a safety analysis for the application and equipment installed.

3. Verify that the offset parameter values match the STAHL configuration values.

4. Verify the offset parameter values for each input pin of the function block that is generated by an instance of the template.

5. Validate offset parameter values under simulated conditions before deployment in the field.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Element Name

Control.STAHLAI8

Control.STAHLHV4 InputModuleDataOffset

Control.STAHLHV8 InputModuleDataOffset

Control

Configuration

The table describes the Configuration parameters, which you can configure.

Name

InputModuleDataOffset

Type

SHORT

InputModuleStatusOffset SHORT

SHORT

InputModuleStatusOffset SHORT

Default value Description

0 Offset of input data in context of

STAHL IS1 Remote I/O system.

Offset of status data in context of

STAHL IS1 Remote I/O system.

Offset of input data in context of

STAHL IS1 Remote I/O system.

Offset of input data in context of

STAHL IS1 Remote I/O system.

Offset of status data in context of

STAHL IS1 Remote I/O system.

NOTE: You can only select either of the two elements.

EIO0000002403 06/2017

Signal Conditioning and Processing

Composition

The $STAHLAI8HART template references composite and facet templates that provide the following services:

Control Includes core services plus additional, optional services, which you can activate if needed.

The table describes the services that are available from the $STAHLHV4 control module and the corresponding facet, which implements the service:

Control services

Composite template

Corresponding facet template

Control service description

Core services

Control $STAHLAI8HART

_UC

$STAHLAI8_UL Refer to the

STAHLAI8CH DFB

(see Process Expert ,

Foundation Control

Services User

Guide) .

–

Optional services

Control $STAHLAI8HART

_UC

Associated

Supervision services

Corresponding facet template

Supervision service description

–

– $STAHLHV4_UL Refer to the

STAHLHARTVal4

DFB

(see Process Expert ,

Foundation Control

Services User

Guide) .

$STAHLHV8_UL Refer to the

STAHLHARTVal8

DFB

(see Process Expert ,

Foundation Control

Services User

Guide) .

–

– – –

The control module template exposes the following interfaces.

Interface identifier

VarName

AISignal01...AISignal08

Type/role

VarName/B

$Int/Def

AINPUTSignal01...AINPUT

Signal08

$AINPUTSignal/DO

Description

Receives the variable name.

Provides the analog input signal value of channels 0 to 7.

Provides the analog input signal value and diagnostic information of channels 0 to 7.

In addition, the control module template exposes the following interfaces, depending on the element selection.

EIO0000002403 06/2017

Signal Conditioning and Processing

When you select the STAHLHV4 element:

Interface identifier

HARTSignal01...HART

Signal04

Type/role

$Real/Def

When you select the STAHLHV8 element:

Interface identifier

HARTSignal01...HART

Signal08

Type/role

$Real/Def

Description

Provides the HART signal value of channels 0 to 3.

Description

Provides the HART signal value of channels 0 to 7.

EIO0000002403 06/2017

Using STAHL Control Module Templates

Section 2.6

Using STAHL Control Module Templates

Signal Conditioning and Processing

Example Use Case

Using an example, this section describes the steps to configure a IS1 Remote I/O system, which communicates with a Quantum controller through I/O scanning.

The implementation of this system requires both Process Expert and Unity Pro.

NOTE: This use case focuses on the configuration of the controller and the IS1 Remote

I/O system, and on the communication between the two. It does not describe the entire system engineering life cycle.

What Is in This Section?

This section contains the following topics:

Topic

Use Case Architecture

Instantiation and Application Links

Configuring Instances

Configuration

Finalizing the System

The Logical Control Participant Project

STAHL Remote I/O System Configuration

Page

EIO0000002403 06/2017

Signal Conditioning and Processing

Use Case Architecture

Physical Architecture Description

The architecture that is modeled in this use case consists of the following components:

Module/Hardware

Quantum CPU 651 50

STAHL IS1 remote I/O system CPU

DIM16

DOM8

8AIH

Particular configuration IP address

I/O scanner 192.168.10.68

– 192.168.10.30

Templates

Automatic selection through bottom-up process.

$GenericDevice (Application template)

$EGenericDeviceHW (Topological template)

$STAHLDI16

$STAHLDO8

$STAHLAI8

8AIH

Process Expert system server/engineering station

–

Configured as 8-channel analog input module.

Configured as 8-channel analog output module.

Configured as 8-channel analog input module with

4 HART values.

Process Expert and Unity

Pro installed

–

$STAHLAO8

$STAHLAI8HART

–

NOTE: The Quantum controller, STAHL IS1 Remote I/O system, and Process Expert workstation are connected to the Ethernet control network.

EIO0000002403 06/2017

Architecture Representation

Signal Conditioning and Processing

EIO0000002403 06/2017

Signal Conditioning and Processing

Instantiation and Application Links

Instantiating Templates

Instantiate the necessary STAHL templates and the $GenericDevice application template in the Application Explorer.

NOTE: The $GenericDevice application template is used to pass the input/output data variable name to the STAHL templates through the VarName interface.

The following figure shows instances of the necessary templates in the Application Explorer:

Linking Instances

Open the instance of the $GenericDevice template in the Links Editor and connect its VarName interface to the VarName interface of each STAHL template instance. After this process, the Link status of each STAHL template then becomes Valid.

EIO0000002403 06/2017

Signal Conditioning and Processing

Configuring Instances

Overview

Each instance of a STAHL control module template allows you to configure the offset between a range of values for the function block that it generates. If you configure offset parameter values incorrectly, a mismatch can occur between the field device and the generated function block, which leads to the exchange of incorrect information.

WARNING

LOSS OF CONTROL

1. Allow only qualified personnel to configure offset parameter values.

2. Conduct a safety analysis for the application and equipment installed.

3. Verify that the offset parameter values match the STAHL configuration values.

4. Verify the offset parameter values for each input pin of the function block that is generated by an instance of the template.

5. Validate offset parameter values under simulated conditions before deployment in the field.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

To be able to configure the STAHL template instances in the Properties window of the Application

Explorer, you need to calculate the value of the following parameters:



InputModuleDataOffset

InputModuleStatusOffset



OutputModuleDataOffset

OutputModuleStatusOffset

In addition, for the $STAHLAI8HART template instance, you need to calculate the value of the

InputModuleDataOffset parameter for HART data.

To be able to configure the $GenericDevice template instance in the Properties window of the

Application Explorer, you need to calculate the value of the following parameters:



Input Data Length

Output Data Length

Calculating STAHL Parameter Values

Two tables are used to calculate parameter values to configure the STAHL instances in the context of STAHL IS1 Remote I/O system:



Input/output module status offset: This table shows how to calculate the values to set the module status offset parameters.



Input/output module data offset : This table shows how to calculate the values to set the module data offset parameters.

EIO0000002403 06/2017

Signal Conditioning and Processing

This example shows the parameters of the STAHLDI16_1 instance that you need to configure:

Slot

Slot 1 - DIM 16

Slot 2 - DOM 8

Slot 3 - AI 8

Slot 4 - AO 8

Slot 5 - AI 8 +

4 HART

Slot 6 - Empty

Slot 7 - Empty

Slot 8 - Empty

Slot 9 - Empty

Slot 10 - Empty

Slot 11 - Empty

Slot 12 - Empty

Slot 13 - Empty

Modbus address Data

1013

1014

1015

1016

1017

1018

1019

1020

1021

1022

1023

1024

1025

Slot 14 - Empty

Slot 15 - Empty

1026

1027

Slot 16 - Empty 1028

CPU status register 1029–1031

Status (S15–S0)

CPU status

16–18

Input/output module status offset

EIO0000002403 06/2017

Signal Conditioning and Processing

Slot

Slot 1 - DIM 16

Modbus address

1032

1033

Slot 2 - DOM 8 32

1034

Slot 3 - AI 8

Slot 4 - AO8

1035–1042

1043

33–40

1044

Data

Data (DI31–DI0)

Status (S15–S0)

Data (DO31–DO0)

Status (S15–S0)

Data (AI7–AI0)

Status (S7–S0)

Data AO7–AO0)

Status (S7–S0)

Input module data offset

–

Output module data offset

–

22–29

–

2–8

–

Slot 5 - AI 8 +

4 HART

1045–1052

1053

1054–1060

Data (AI7–AI0)

Status (S7–S0)

HART data

32–39

41–48

–

Calculating STAHL HART Parameter Values

The following figure shows the STAHLAI8HART_1 instance and the two parameters of the

STHALAI8 element, which you calculate in the same way as for the STHALAI8_1 instance:

EIO0000002403 06/2017

Signal Conditioning and Processing

The following figure shows the InputModuleDataOffset parameter of the STHALHV4 element, which you calculate using the module data offset table:

Calculating the GenericDevice Instance Parameter Values

Calculate the value of the parameters of the $GenericDevice application instance as follows:



Input Data Length: Total number of read/input registers in the context of STAHL IS1 remote I/O

 system.

Output Data Length : Total number of write/output registers in the context of STAHL IS1 remote

I/O system.

NOTE: You have to enter the length of the input/output data variable greater than or equal to 2, to avoid detected errors in project build.

EIO0000002403 06/2017

Signal Conditioning and Processing

Configuration

Overview

The Quantum controller and the STAHL IS1 Remote I/O system communication through Modbus

TCP Ethernet implicit message by using the I/O scanner service of the controller. A generic

Modbus TCP I/O device entity (which is the counterpart of the generic device instance create in the Application) allows you to perform the communication mapping with the controller.

Configuring the Topology

Step

Action

In the Topological Explorer, create a Quantum controller entity and configure it with the I/O scanner enabled.

Configure the client memory properties with suitable values.

NOTE: The configuration of the STAHL IS1 Remote I/O system is performed outside of Process Expert.

Create a Modbus TCP I/O device entity by using the $EGenericDeviceHW template and configure its properties.

EIO0000002403 06/2017

Signal Conditioning and Processing

The following figure shows the properties of the generic Modbus TCP I/O device entity after configuring its parameters:

The parameters are calculated as follows in the context of the STAHL IS1 Remote I/O system:



ReadLength = Total number of read/input registers. The actual number is 49 but it is rounded

 off to 50.

WriteLength = Total no of write/output registers. The actual number is 8 but it is rounded off to

10.

For detailed information on ReadAddress and WriteAddress parameters, refer to the Operating_in structions_IS1_ModTCP manual .

Connecting to the Control Network

Create an Ethernet network and make a physical connection with the controller and the generic device entities.

EIO0000002403 06/2017

Signal Conditioning and Processing

Finalizing the System

To complete the system engineering life cycle, complete the following steps:

Step

Action

Create a Control project.

Assign facets of the $GenericDevice and STAHL instances to the Control project

Generate the project.

Create an executable and proceed with:



Service mapping.



Communication mapping: To configure data exchange between the controller and the STAHL IS1 Remote I/O system system by I/O scanning.

Hardware mapping: To map the application facet of the $GenericDevice instance to the toplogical facet of the generic Modbus TCP I/O device entity.

Build the project.

The following figure shows the communication mapping:

The following figure shows the hardware mapping:

EIO0000002403 06/2017

Signal Conditioning and Processing

The Logical Control Participant Project

The following figures show as an example FBD section to which a facet of two STAHL instances was assigned after generating it. It contains the DFB, which is encapsulated in each facet and logical references to the generic device data variables:

EIO0000002403 06/2017

Signal Conditioning and Processing

This figure shows the STAHLDI16CH DFB, which is encapsulated in the facet of the STAHLDI16_1 instance (digital input template):

EIO0000002403 06/2017

Signal Conditioning and Processing

This figure shows the STAHLDO8CH DFB, which is encapsulated in the facet of STAHLDO8_1 instance (digital output template):

EIO0000002403 06/2017

Signal Conditioning and Processing

STAHL Remote I/O System Configuration

Overview

You need to do the STAHL IS1 Remote I/O system configuration on a local Unity Pro application with the help of a DTM.

This topic describes the configuration of the STAHL IS1 Remote I/O system, which contains one

Modbus TCP interface and the five I/O modules.

Two configuration scenarios can be considered:



Scenario1: The STAHL IS1 Remote I/O system is connected to the network, the digital and

 analog modules are plugged on to the BusRail and an IP address is assigned to the STAHL

IS1 Remote I/O system CPU. In this case, the Unity Pro DTM Browser field bus discovery feature is used, allowing the appropriate modules to be automatically selected.

Scenario 2: The STAHL IS1 Remote I/O system is not reachable. In this case, the digital and analog I/O modules are manually selected by using the Unity Pro DTM Catalog.

Installing the STAHL IS1 Remote I/O System DTM

In any case, you need to install the STAHL IS1 Remote I/O system DTM on the PC on which you are running Unity Pro first. A DTM installs like traditional software.

You can download the STAHL IS1 Remote I/O system DTM from the STAHL http://www.rstahl.com

Updating the Unity Pro DTM Catalog

After the DTM is installed, you have to update the Unity Pro DTM catalog.

Refer to Updating the Unity Pro Hardware Catalog in the Unity Pro online help.

Configuring the STAHL IS1 Remote I/O System - Common Steps

The table describes the steps of the configuration that are common to both scenarios:

Step

Action

In the DTM Browser, right click the Host PC folder, and select Add to open the DTM catalog.

EIO0000002403 06/2017

Signal Conditioning and Processing

Step

Action

Select the 9441/1x-00-00 CPM Z1 24V Eth Modbus TCP/IP DTM, which corresponds to the selected CPU, and click Add DTM.

3 You can change the Alias name. In this guide IS1 is used as alias.

4 Double-click the IS1 instance to open the DTM.

EIO0000002403 06/2017

Step

Signal Conditioning and Processing

Action

Enter the selected IP address of the module in the Address field.

6 Click OK to apply the modifications and close the DTM.

EIO0000002403 06/2017

Signal Conditioning and Processing

Configuring the STAHL IS1 Remote I/O System - Scenario 1

For scenario 1, you have to be able to reach the IS1 module by using a ping command from the

PC on which Unity Pro is running.

The table describes the steps of the configuration that are specific to scenario 1:

Step

Action

In the DTM Browser, right click and select Connect.

NOTE: The field bus discovery service is available only when the DTM is connected to the corresponding physical device. For details refer to

DTM Browser in the Unity Pro online help.

EIO0000002403 06/2017

Step

Signal Conditioning and Processing

Action

Once connected, right click IS1 again and select Field bus discovery:

EIO0000002403 06/2017

Signal Conditioning and Processing

Step

Action

Select the slot number to discover. Start with the first slot, which corresponds to the first I/O module inserted in the BusRail. In this case, the D9470_3x_16_xx_DIM_16 DIM 16 STAHL module is inserted in

Slot01.

Click OK to launch the discovery. The Field bus discovery dialog box is displayed. It lists the scanned and matched devices.

From the Matched Devices pane, select the module and click the + button to add it to the selected devices pane.

Click OK to insert the module into the Unity Pro DTM Browser.

Repeat steps 2 to 6 for the remaining DTM/slot pairs.

Configuring the STAHL IS1 Remote I/O System - Scenario 2

For scenario 2, the field bus discovery feature cannot be used and you need to select the modules manually.

The table describes the steps of the configuration that are specific to scenario 2:

Step

Action

In the DTM Browser, right click IS1 and click Add… to open the DTM catalog.

Select the appropriate DTM and click Add DTM to validate. A window opens to select the slot number on the BusRail where the selected DTM is physically inserted.

EIO0000002403 06/2017

Step

Signal Conditioning and Processing

Action

Click OK to confirm the slot number. The Properties window opens. In this window, you can change the alias name.

Click OK to complete the DTM instantiation .

Repeat steps 1 to 5 for the remaining DTM slot pairs.

EIO0000002403 06/2017

Signal Conditioning and Processing

EIO0000002403 06/2017

Process Expert

Special Cards

EIO0000002403 06/2017

Special Cards

Chapter 3 Special Cards

Overview

This chapter explains the basic functionality of the special card templates and their composition.

These function blocks do not reflect any specific installation.