Материал: m013500e_x06

Внимание! Если размещение файла нарушает Ваши авторские права, то обязательно сообщите нам

136 • DeviceNet

Configuration / Parametering with the Object Model

5.6.2.2.16Class 172 (0xAC) Output Fieldbus Variable UDINT

PLC output byte 1..128

Max. instance: 128

5.6.2.2.17Class 173 (0xAD) Output Fieldbus Variable UDINT

PLC output byte 1..128 Max. instance: 128

Starts with 2 bytes offset

(the 2nd and 3rd UINT (class168 / instance 2 and 3)

=1st UDINT (class173 / instance 1) etc.)

5.6.2.2.18Class 100 (0x64) - Attribute 44/100/101

Attribut ID

Used in Coupler

Access rule

Attribute

Data type

Brief description of the attribute

 

 

 

name

 

 

44

Specific

Get/Set

BK_SAVE_

UINT

Save dynamic created instances in non

(0x2C)

 

 

DYN_ASS_

 

volatile memory (after power up all

 

 

 

INST

 

saved instances are automatically

 

 

 

 

 

created )

 

 

 

 

 

0: save no dynamic instances

 

 

 

 

 

1: save dynamic instances

100 (0x64)

Specific

Get/Set

BK_FBINP_

UINT

Defines the number of bytes from the

 

 

 

VAR_CNT

 

PLC-fieldbus-variables (inputs) which

 

 

 

 

 

will be added to the assembly object

 

 

 

 

 

(this count will be added to the consu-

 

 

 

 

 

med path – assembly instances 1..3)

101 (0x65)

Specific

Get/Set

BK_FBOUT

UINT

Defines the number of bytes from the

 

 

 

_VAR_CNT

 

PLC-fieldbus-variables (outputs)

 

 

 

 

 

which will be added to the assembly

 

 

 

 

 

object (this count will be added to the

 

 

 

 

 

produced path – assembly instances

 

 

 

 

 

4..9)

Example:

The example comes from the DeviceNet Coupler point of view:

-> Configuration Coupler:

input process image 12 byte,

 

output process image 10 byte

-> BK_FBINP_VAR_CNT = 0;

BK_FBOUT_VAR_CNT = 0

poll connection: -> 12 byte produced -> 10 byte consumed

-> BK_FBINP_VAR_CNT = 4; BK_FBOUT_VAR_CNT = 3 poll connection:

-> 15 byte produced

(12 byte input process image + 3 byte PLC output fieldbus variables) -> 14 byte consumed

(10 byte output process image + 4 byte PLC input fieldbus variables)

5.6.2.2.19Identity Class 1 (0x01)

Instance 1:

Attribut ID

Used in Coupler

Access rule

Attribute name

Data type

Description of the attribute

Default

 

 

 

 

 

 

Value

10 (0x0A)

required

Get/Set

Heartbeat

USINT

Interval between 2 Heartbe-

0

 

 

 

Interval

 

at messages in seconds

 

WAGO-I/O-SYSTEM 750

DeviceNet

DeviceNet • 137

Configuration / Parametering with the Object Model

5.6.2.2.20Connection Object (0x05)

Description of the instances:

Instance ID

Description

1

... 4

...

5

 

 

6

 

References dynamic Connection

7

 

8

 

 

9

 

 

10

 

11

References I/O Connection

12

13

 

14

 

5.6.2.2.21Additional Assembly Instances 10 and 11

In addition to the (static) assemblies (1 ... 9) that are permanently preprogrammed in the device, the Controller has the assembly instances 10 and 11.

These simplify and speed up the transmission of the input and output image of the PFC variable from the fieldbus Controller to the master.

Description of the instances:

Instance

Description

ID

 

1 ... 9

....

10

References to the process image containing PFC output variables.

11

References to the process image containing PFC input variables.

Instance 10:

Attribute

Used in

Access

Name

Data type

Description

Value

ID

buscoupler

rule

 

 

 

 

3

optional

get

PFC

Array of

process image, collection of all

 

 

 

 

output

Byte

PFC output variables

 

 

 

 

variables

 

 

 

Instance 11:

Attribute

Used in

Access

Name

Data type

Description

Value

ID

buscoupler

rule

 

 

 

 

3

optional

get

PFC input

Array of

process image, collection of all

 

 

 

 

variables

Byte

PFC input variables

 

(For PFCs with software version before SW 01.06): PFC Output (I/O Assembly Instance 10):

Only the PFC output variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 101 (BK_FBOUT_ VAR_CNT).

WAGO-I/O-SYSTEM 750

DeviceNet

138 • DeviceNet

Configuration / Parametering with the Object Model

PFC Input (I/O Assembly Instance 11):

Only the PFC input variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 100 (BK_FBIN_ VAR_CNT).

(For PFCs from software version SW 01.06):

PFC Output (I/O Assembly Instance 10):

Only the PFC output variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 104 (BK_FBOUT_ PLCONLY_VAR_CNT).

The first PFC transfer byte is defined by the value in class 100 / instance 1 / attribute 105 (BK_FBOUT_STARTPLC_VAR_CNT).

PFC Input (I/O Assembly Instance 11):

Only the PFC input variables are transmitted via the corresponding I/O message connection. The data length is equivalent to the value in class 100 / instance 1 / attribute 102 (BK_FBINP_PLCONLY_ VAR_CNT).

The first PFC transfer byte is defined by the value in class 100 / instance 1 / attribute 103 (BK_FBIN_STARTPLC_VAR_CNT).

WAGO-I/O-SYSTEM 750

DeviceNet

Application in Explosive Environments • 139

Foreword

6 Application in Explosive Environments

6.1 Foreword

Today’s development shows that many chemical and petrochemical companies have production plants, production, and process automation machines in operation which use gas-air, vapor-air and dust-air mixtures which can be explosive. For this reason, the electrical components used in such plants and systems must not pose a risk of explosion resulting in injury to persons or damage to property. This is backed by law, directives or regulations on a national and international scale. WAGO-I/O-

SYSTEM 750 (electrical components) is designed for use in zone 2 explosive environments. The following basic explosion protection related terms have been defined.

6.2 Protective Measures

Primarily, explosion protection describes how to prevent the formation of an explosive atmosphere. For instance by avoiding the use of combustible liquids, reducing the concentration levels, ventilation measures, to name but a few. But there are a large number of applications, which do not allow the implementation of primary protection measures. In such cases, the secondary explosion protection comes into play. Following is a detailed description of such secondary measures.

6.3 Classification Meeting CENELEC and IEC

The specifications outlined here are valid for use in Europe and are based on the following standards: EN50... of CENELEC (European Committee for Electrotechnical Standardization). On an international scale, these are reflected by the IEC 60079-... standards of the IEC (International Electrotechnical Commission).

6.3.1 Divisions

Explosive environments are areas in which the atmosphere can potentially become explosive. The term explosive means a special mixture of ignitable substances existing in the form of air-borne gases, fumes, mist or dust under atmospheric conditions which, when heated beyond a tolerable temperature or subjected to an electric arc or sparks, can produce explosions. Explosive zones have been created to describe the concentrations level of an explosive atmosphere. This division, based on the probability of an explosion occurring, is of great importance both for technical safety and feasibility reasons. Knowing that the demands placed on electrical components permanently employed in an explosive environment have to be much more stringent than those placed on electrical components that are only rarely and, if at all, for short periods, subject to a dangerous explosive environment.

WAGO-I/O-SYSTEM 750

DeviceNet

140 • Application in Explosive Environments

Classification Meeting CENELEC and IEC

Explosive Areas Resulting from Gases, Fumes or Mist:

Zone 0 areas are subject to an explosive atmosphere (> 1000 h /year) continuously or for extended periods.

Zone 1 areas can expect the occasional occurrence of an explosive atmosphere (> 10 h 1000 h /year).

Zone 2 areas can expect the rare or short-term occurrence of an explosive atmosphere (> 0 h 10 h /year).

Explosive Areas Subject to Air-borne Dust:

Zone 20 areas are subject to an explosive atmosphere (> 1000 h /year) continuously or for extended periods.

Zone 21 areas can expect the occasional occurrence of an explosive at-

mosphere (> 10 h 1000 h /year).

Zone 22 areas can expect the rare or short-term occurrence of an explosive atmosphere (> 0 h 10 h /year).

6.3.2Explosion Protection Group

In addition, the electrical components for explosive areas are subdivided into two groups:

Group I: Group I includes electrical components for use in fire-damp endangered mine structures.

Group II: Group II includes electrical components for use in all other explosive environments. This group is further subdivided by pertinent combustible gases in the environment. Subdivision IIA, IIB and IIC takes into account that different materials/substances/gases have various ignition energy characteristic values. For this reason the three sub-groups are assigned representative types of gases:

IIA – Propane

IIB – Ethylene

IIC – Hydrogen

Minimal Ignition Energy of Representative Types of Gases

Explosion Group

I

IIA

IIB

IIC

 

 

 

 

 

Gases

Methane

Propane

Ethylene

Hydrogen

 

 

 

 

 

Ignition Energy (µJ)

280

250

82

16

 

 

 

 

 

Hydrogen being commonly encountered in chemical plants, frequently the explosion group IIC is requested for maximum safety.

WAGO-I/O-SYSTEM 750

DeviceNet