Communication Protocol

DeviceNet™
for Capacitance Diaphragm Gauge

CDG045D, CDG100D,
CDG160D, CDG200D

tira51e1(2009-01)1

General Information

CautionCaution: data transmission errors
Any attempt to simultaneously operate the gauge via the RS232C
Serial Interface and a Fieldbus interface (DeviceNet or Profibus) or the
diagnostic port may result in incorrect data and data transmission
errors.
Therefore, it is inadmissible to simultaneously operate the gauge via
the RS232C Serial Interface and DeviceNet, Profibus, or the diagnostic port.

Intended Use

This Communication Protocol contains instructions for operating DeviceNet interfaces (slaves) together with a master.
This manual describes the functionality of DeviceNet for programming
purposes. For more information →"DeviceNet Specifications" of theOpen DeviceNet Vendor Association (ODVA).
For safety information, specifications and operation instructions of thevacuum gauges refer to the appropriate documents (→[1], [2], [3]).

DeviceNet–Interface

The following description of the DeviceNet interface is compliant to the DeviceNet
specification of the Open DeviceNet Vendor Association and to the"Interface
Guidelines for DeviceNet Devices On Semiconductor Manufacturing Tools".
This manual describes the functionality of a DeviceNet group 2 only slave and supports explicit messaging and the I/O connections change of state/cyclic and polling.
We reserve the right to make technical changes without prior notice.

Product Identification

In all communications with INFICON, please specify the information on the productnameplate. For convenient reference copy that information into the space provided
below.

Model:
PN:
SN:
V

2

W

tira51e1(2009-01)

CDGxxxD.cp

Validity

This document applies to products of the temperature controlled CDG045D,
CDG100D, CDG160D and CDG200D series with DeviceNet interface.
Part numbers of standard products are indicated below. OEM products have otherpart numbers and different parameter settings (e.g. factory setting of setpoint) as
defined in the corresponding ordering information.
Sensor temperature C ⇒ 45°
D ⇒ 100°
E ⇒ 160°
F ⇒ 200°

3Cx1-xxx-2310
FlangeUnit

Measurement range(F.S.)

1 ⇒ DN 16 ISO-KF
3 ⇒ DN 16 CF-R
9 ⇒ 1/2" tube
E ⇒ 8VCR female
5 ⇒ Torr (x 133 Pa; x 1.3 mbar)
6 ⇒ mbar (x 100 Pa)
3 ⇒ 0.1
4 ⇒ 0.25
5 ⇒ 0.56⇒1
7⇒2
8⇒5
9 ⇒ 10A ⇒ 20B ⇒ 50C ⇒ 100
D ⇒ 200
E ⇒ 500
F ⇒ 1000 (Torr only)G ⇒ 1100 (mbar only)

The part number (PN) can be taken from the product nameplate.
If not indicated otherwise in the legends, the illustrations in this document correspond to CDG045D gauges with the DN 16 ISO-KF vacuum connection. They apply
to other vacuum connections and to the other gauges by analogy.
We reserve the right to make technical changes without prior notice.

TrademarkDeviceNet™

Patents

EP 1070239, 1040333
US Patents 6528008, 6591687, 7107855, 7140085

tira51e1(2009-01)

CDGxxxD.cp

Open DeviceNet Vendor Association Inc.

3

Contents
General Information
Intended Use
DeviceNet–Interface
Product Identification
Validity
TrademarkPatents

2
2
2
2
3
3
3

Contents

4

1 Technical Data

5

2 Interface Connection

7

3 Operation
3.1 Introduction
3.2 Front View
3.3 Indicators and Switches
3.3.1 Module Status LED
3.3.2 Network Status LED
3.3.3 Node Address Switch
3.3.4 Data Rate Switch
3.4 Abbreviations

8
8
8
9
9
9
9
10
10

4 Object Structure
4.1 Connection Object
4.1.1 Vendor-Specific Object Extension on Instance 2 Poll Connection
4.2 Identity Object
4.2.1 Class Attributes
4.2.2 Instance Attributes
4.3 S-Device Supervisor Object
4.3.1 Class Attributes
4.3.2 Instance Attributes
4.3.3
Semantics
4.3.4 S-Device Supervisor Object States
4.3.5 S-Device Supervisor Common Services
4.3.6 S-Device Supervisor Object Specific Services
4.4 S-Analog Sensor Object
4.4.1 Class Attributes
4.4.2 Semantics
4.4.3 Instance Attributes
4.5 Trip Point Object
4.5.1 Class Attributes
4.5.2 Instance Attributes of Trip Point Objects Instance 1 & 2
4.5.3 Semantics
4.5.4 Common Services
4.6 Discrete Output Point Object
4.6.1 Class Attributes
4.6.2 Instance Attributes of Instance 1 & 2
4.6.3 Common Services

11
11
11
12
12
12
13
13
13
14
17
17
18
19
19
19
19
27
27
27
28
28
29
29
29
29

5 I/O Assembly Object
5.1 I/O Assembly Object Instance Data Attribute Format

30
30

Appendix
A: Conversion of a Floating Number According to IEEE 754
B: Typical Start-Up Procedure
C: Literature

31
31
32
35

For cross-references to other documents, the symbol (→4[XY]) is used.

tira51e1(2009-01)

CDGxxxD.cp

1 Technical Data

Further technical data →Supply voltage

CDG045D
Supply voltage at the DeviceNet connector
Power consumption
while being heated
at operating temperature[1], [2], [3].

24 V nominal (11 … 25 V)
≤12 W
≤10 W

CDG100D, CDG160D, CDG200D
The temperature controlled CDG100D, CDG160D and CDG200D
gauges with DeviceNet interface require an additional, separate power
supply.
Supply voltage for gauge at D-sub
connector→[2], [3]Supply voltage for DeviceNet transceiver at micro style connector
24 V nominal (11 … 25 V)
Power consumption<2 W

DeviceNet interface

Fieldbus nameStandard applied
Communication protocol, data format
Interface, physicalData rate (adjustable via "RATE"
switch)Node address (MAC ID)(Adjustable via "ADDRESS", "MSD","LSD" switches)
DeviceNet connector
Cable

Cable length, system wiring

tira51e1(2009-01)

CDGxxxD.cp

DeviceNet
→

[5]

→
[5]
CAN bus125 kBaud
250 kBaud
500 kBaud (default)"P" (125 kBaud, 250 kBaud, 500 kBaud
programmable via DeviceNet
0 … 63dec (default = 63dec)"P" (0 … 63 programmable via
DeviceNet)
Micro style, 5 pins, male
Shielded, special DeviceNet cable,
5 conductors(→  7 and[4])according to DeviceNet specifications(→[4], [5])

5

10.8

Dimensions [mm]

16.5

82

ST
A

2
SP

TU
S

1
SP

6

tira51e1(2009-01)

CDGxxxD.cp

2 Interface Connection
Making a DeviceNet interface
cable

For operating the temperature controlled CDGxxxD gauge via DeviceNet, aninterface cable conforming to the DeviceNet standard is required.
If no such cable is available, make one according to the following indications.

Cable typeA shielded special 5 conductor cable conforming to the DeviceNet standard has tobe used (→[4] and [5]).

Proceduren Make the DeviceNet interface cable according to the following indications:
1
2

4
3

Pin 1
Pin 2
Pin 3
Pin 4
Pin 5

5

Micro style, 5 pins,(DeviceNet)female, soldering side

Drain
Supply+24 VDC
Supply common GND
CAN_H
CAN_L

Pin assignment of the D-Sub 15-pins sensor connector according to therespective operating manual (→[1], [2], [3]).

o Plug the DeviceNet (and sensor) cable connector into the gauge.
DeviceNet cable
Sensor cablep Lock the DeviceNet (and sensor) cable connector.

tira51e1(2009-01)

CDGxxxD.cp

7

3 Operation
3.1 Introduction

Via the DeviceNet interface, the following and further data are exchanged in thestandardized DeviceNet protocol:•

Pressure reading•

Pressure unit (Torr, mbar, Pa)•

Zero adjustment•

Status and error messages•

Status of the switching functions

CautionCaution: data transmission errors
Any attempt to simultaneously operate the gauge via the RS232C
Serial Interface and a Fieldbus interface (DeviceNet or Profibus) or the
diagnostic port may result in incorrect data and data transmission
errors.
Therefore, it is inadmissible to simultaneously operate the gauge via
the RS232C Serial Interface and DeviceNet, Profibus, or the diagnostic port.

3.2 Front View

3
1

7

2

Position

8

4 5 6Function1

Address Switch × 10, decimal

2

Address Switch × 1, decimal

3

DeviceNet connector

4

Data Rate Switch

5

Network Status LED

6

Module Status LED

7"Sensor cable" connector(Power, analog I/O, RS232C I/O
and Relay contacts)tira51e1(2009-01)

CDGxxxD.cp

3.3 Indicators and Switches
3.3.1 Module Status LED

Device State

LED State

Power Off

Dark

Device Self-Test

Flashing
green/red

Device Operational

Green

Device is operating normally.

Red

Device has detected an unrecoverable fault

Unrecoverable Fault
Recoverable Fault

3.3.2 Network Status LED

Description
No power applied to device
Device is in self-test

Flashing red Device has detected a recoverable fault,
e.g. missing DeviceNet power supply

The network status LED indicates the status of the DeviceNet communication link.
State
Not Powered/not online

Online, not connected

Link OK online, connected

LED state To indicate
Dark

Flashing
green

Green

Device is not online.
•

The device has not completed the
Duplicate MAC_ID test yet.

•

The device may not be powered,look at Module Status LED.

Device is online but has no connectionsin the established state.
•

The device has passed the
Dup_MAC_ID test, is online, but
has no established connections toother nodes.

•

The device is not allocated to amaster.

The device is online and has connections in the established state.
•

3.3.3 Node Address Switch

The device is allocated to a master.

Connection time out

Flashingred

One or more I/O Connections are in thetimed out state.

Critical link failure

Red

Failed communication device. The
device has detected an error that has
rendered it incapable of communicatingon the network (Duplicate MAC ID, or
Bus–off).

During device initialization, the node address switches are read by the device firmware. If the switches specify a valid DeviceNet MAC ID, i.e. a value from 0 … 63,
this value is used as the device MAC ID. If the specified MAC ID differs from thevalue stored in the device’s non-volatile RAM (NVRAM), the new MAC ID will besaved in NVRAM. If the switches specify an invalid DeviceNet MAC ID, i.e. a value
greater than 63, the current value stored in the device’s NVRAM is used as thedevice MAC ID.
2
4
Example: Value of the DeviceNet MAC ID = 63:

tira51e1(2009-01)

CDGxxxD.cp

6
P
MSD

LSD

9

3.3.4 Data Rate Switch

A single, rotary switch is provided for configuring the data rate of the device. The
switch has three valid positions for the DeviceNet data rates, 125, 250, and500 kBaud, where:
RATE
5
P

1 ≙ 125 kBaud

2
1

2 ≙ 250 kBaud
5 ≙ 500 kBaud

Example: Data rate = 250 kBaud:All remaining switch positions specify software selection of the data rate.

3.4 Abbreviations

Abbr.

Meaning

NV

Nonvolatile; attribute value is maintained through power cycles

V
USINT

10

Volatile
Unsigned short integer value (Range 0 … 255)

INT

Integer value(Range –32767 … 32768)

UINT

Unsigned integer value(Range 0 … 65635)

UDINT

Unsigned double integer value

FLOAT

Floating point value(Range according to IEEE 754)

(Range 0 … 4'294'967'295)

XXh

Hexadecimal number(Radix = 16)

XXd

Decimal number(Radix = 10)

XXb

Binary number(Radix = 2)

tira51e1(2009-01)

CDGxxxD.cp

4 Object Structure
4.1 Connection Object

Class Code 05h = 05d
The connection class allocates and manages the internal resources associatedwith both I/O and explicit messaging connections. The specific instance generated
by the connection class is referred to as a connection instance or a connection
object.
The following Instances of the connection object are supported:•

Instance 1: Explicit messaging•

Instance 2: I/O polling•

Instance 4: I/O change of state/cyclic I/O connection

Please refer to the DeviceNet specification for further information.

4.1.1 Vendor-Specific Object
Extension on Instance 2
Poll Connection

For the selection of the active input assembly the following vendor specific attributecan be used.

Vendor specific extension:
Attribute
ID
100

Access NV/ Name
rule
V
Get/Set

NV Poll produce
assembly
instance

DeviceNet
Data type
USINT

Description of attribute

Semantics

Contains the instance num- 1, 2 (default), 3, 4, 5, 6,
ber of the assembly used by 8, 9, 10, 11, 12, 13, 14
this connection to send data

This vendor-specific attribute facilitates the configuration of the data assembly, thetemperature controlled CDGxxxD will send to the DeviceNet master as poll
response. It offers the possibility to select a (predefined) data assembly via aconfiguration tool + EDS file (→[6]). Attribute 100 allows the user to configure
the poll IO data assembly via EDS even if the poll connection of the temperature
controlled CDGxxxD is in the established state. The assembly number is stored
non volatile. Modifications of the poll produce assembly instance will take effectonly after a reset of the temperature controlled CDGxxxD.
Thus, definition of the temperature controlled CDGxxxD data assembly can bedone in various ways:
1) Standard method (without using attribute 100):
The DeviceNet master configures the "Produced Connection Path" attribute of
the poll connection (connection instance 2) when establishing communication to
the temperature controlled CDGxxxD. This requires a master to support
expanded explicit messaging capabilities.
2) Directly setting attribute 100 e.g. by a configuration tool(e.g. RS networks) + device reset

tira51e1(2009-01)

CDGxxxD.cp

114.2 Identity Object

Class Code 01h = 01d

4.2.1 Class Attributes

This object provides identification of and general information about the device.

Attribute ID

Access rule

Name

DeviceNet Description of attributedata type

Semantics of values

1

Get

Revision

UINT

Revision of this object.
Note: All class definitions are
required to include this classattribute.

The current value assigned to this
attribute is one (01). If updates that
require an increase in this value are
made, then the value of this attributeincreases by one.

2

Get

Max instanceUINT

Maximum instance number ofan object currently created inthis class level of the device.

The largest Instance number of acreated object at this class hierarchy
level.

4.2.2 Instance Attributes
Attribute ID

Access rule

NV/ NameV

DeviceNet data type

Description of attribute1

Get

NV Vendor ID

UINT

Manufacturer identification
Value: 633 (INFICON AG) (default)

2

Get

NV Device type

UINT

1Ch = Vacuum pressure gauge
14 (default)

3

Get

NV Product code

UINT

4

Get

NV Revision

STRUCT

5

Get

NV Status

WORD

6

Get

NV Serial number

UDINT

7

Get

NV Product nameSHORT STRING

CDG045D, CDG100D, CDG160D,
CDG200D

The products with different product names only differ in the temperature at which
the sensor element is heated up. Different fullscale values of the gauges exist
within the same product name. The product code is always 14.

Services

12Service CodeName

Description

5 (05h)Reset

0 = last installation,
1 = default installation

14 (0Eh)

Get_Attribute_Single

tira51e1(2009-01)

CDGxxxD.cp

4.3 S-Device Supervisor
ObjectClass Code 30h = 48d4.3.1 Class Attributes
Attribute ID

Accessrule

Name

DeviceNetdata type

Description of attribute

Semantics of values

1

Get

Revision

UINT

Revision of this object

The current value assigned to this attribute is one (01). If updates that require
an increase in this value are made, thenthe value of this attribute increases by
one.

2

Get

Max
instance

UINT

Maximum instance number of an The largest Instance number of a created object at this class hierarchy level.
object currently created in thisclass level of the device.

4.3.2 Instance Attributes
Attribute ID

Access rule

NV/ NameV

DeviceNet data type

Description of attribute

3

Get

NV

Devicetype

SHORT STRINGASCII Text, "VG" (vacuum gauge)

4

Get

NV

SEMI standard
revision level

SHORT STRING

Specifies the revision level of the SEMI
S/A network standard to which the device
complies (for example "E54-0997").

5

Get

NV

Manufacturer’s nameSHORT STRING"INFICON AG" (default)

6

Get

NV

Manufacturer’s model
numberSHORT STRINGASCII text, manufacturer specified

7

Get

NV

Software revision level

SHORT STRINGASCII text, for example "010000"

8

Get

NV

Hardware revision
level

SHORT STRINGASCII text, for example "010000"

9

Get

NV

Manufacturer’s serial
numberSHORT STRINGASCII text

10

Get

NV

Device configuration

SHORT STRING

Depending on device:
Examples: 1000 Torr, 100 C
0.1 Torr, 200 C

11

Get

V

Device status

USINT→ "Semantics" section below.

12

Get

V

Exception status

BYTE→ "Semantics" section below.

13

Get

V

Exception detail
alarm

STRUCT of:

A structure of three structures containing
a bit mapped representation of the alarmdetailCommonexception detail

STRUCT of:Size 2

USINT

Number of common detail bytes

Detail 0

ARRAY of:→ "Semantics" section below.

Detail 1

BYTE→ "Semantics" section below.

Device exception
detailSTRUCT of:Size 2

USINT

Detail 0→ "Semantics" section below.

Detail 1

tira51e1(2009-01)

CDGxxxD.cp

Number of device detail bytes→ "Semantics" section below.

Manufacturer
exception detail

STRUCT of:Size 1

USINT

Number of manufacturer detail bytes

Detail 0

ARRAY of:

Manufacturer Specified

13

Attribute ID

Access rule

NV/
V

Name

DeviceNet data type

Description of attribute

14

Get

V

Exception detailwarning

STRUCT of:

A structure of three structures containing
a bit mapped representation of thewarning detail

Common exception
detailSTRUCT of:Size 2

USINT

Number of common detail bytes

Detail 0

ARRAY of:→ "Semantics" section below.

Detail 1

BYTE→ "Semantics" section below.

Device exception
detailSTRUCT of:Size 3

USINT

Number of device detail bytes

Detail 0

BYTE→ "Semantics" section below.

Detail 1

BYTE→ "Semantics" section below.

Detail 2

BYTE→ "Semantics" section below.

Manufacturer
exception detail

STRUCT of:Size 1

USINT

Number of manufacturer detail bytes = 1

Detail 0

ARRAY of:

Manufacturer specified

15

Set

NV

Alarm enable

BOOL→ "Semantics" section below.

16

Set

NV

Warning enable

BOOL→ "Semantics" section below.

101

Get

NV

Software revisionbase unit

SHORT STRINGASCII text, for example "010000"

102

Get

V

Run hours

UINT

1 = 1 hour

4.3.3 Semantics
Device status

This attribute represents the current state of the device. Its value changes as thestate of the device changes. The following values are defined:
Attribute value

State

0

Undefined

1

Self testing

2

Idle

3

Self-test exception

4

Executing

5

Abort

6

Critical fault

In case of a self-test exception restart the device with a reset out of the box(identity object class 1, instance 1, service 5, service target value: 1).

Exception status

14

A single byte attribute whose value indicates the status of the alarms and warnings
for the device. The device supports the expanded mode.
For the expanded mode, bit seven of exception status attribute is set to one;
exceptions are reported through the communication of this exception status attribute, formatted as specified in the table below. In addition, the exception detail
attributes are supported. The exception status bits are determined by a logical"OR" of the related exception detail bits, as indicated.

tira51e1(2009-01)

CDGxxxD.cp

Exception status bitmap

1)

Exception detail alarm andexception detail warning

Bit

Function0

ALARM / device-common 1)

1

ALARM / device-specific2

ALARM / manufacturer-specific3reserved, set to 0

4

WARNING / device-common 1)

5

WARNING / device-specific6

WARNING / manufacturer-specific7

1 ≙ Expanded Method

The alarm or warning is not specific to the device type or device type manufacturer.

The formats of these two attributes are identical. Therefore, they are described
together:
Attributes that relate the detailed status of the alarms or warnings associated withthe device. Each attribute is a structure containing three members; these threemembers, respectively relate the detailed status of exceptions that are common(i.e., not device-specific), device-specific but not manufacturer-specific, and manufacturer-specific. The common and device-specific detail are defined below. A
manufacturer-specific detail has a length of 1 byte. A SIZE value of one indicatesthat one byte detail is defined for the associated exception detail structure.
Each of the three structure members is defined as a structure containing an ordered list (i.e., array) of bytes of length SIZE, and an unsigned integer whose value
is SIZE. Each of the bytes in each array has a specific mapping. This mapping isformatted as 8 bits representing 8 independent conditions, whereas a value of 1
indicates that the condition is set (or present), and a value of 0 indicates that thecondition is cleared (or not present). Note that if a device does not support an
exception detail, the corresponding bit is never set. The bitmaps for alarms andwarnings in the corresponding attributes are structured in parallel so that a condition may have either alarm or warning set depending on severity. If a condition
inherently cannot be both alarm and warning, then the parallel bit position corresponding to the other state will remain "0".
The existence of an exception detail variable structure is dependent on the value of
the Exception Status Attribute; the existence of an exception detail variable
structure is only required if bit seven of the Exception Status attribute is set to 1
(indicating Expanded method reporting) and the bit (among bits zero through six) of
the Exception Status attribute corresponding to the particular exception type is also
set to 1.

Common exception detailtira51e1(2009-01)

CDGxxxD.cp

This structure relates exception conditions (i.e. alarms or warnings) which arecommon to all devices within the Hierarchy of Semiconductor Equipment Devices.
The Detail element of the structure is an ordered list (i.e., array) of bytes of length[SIZE] which is the value of the structure element Size. For each byte in the Detailfield, all bits which are not identified are reserved for future standardization.
The first byte in this attribute is CommonExceptionDetail[0]. Additional exception
details, if provided, are named CommonExceptionDetail[1], …
CommonExceptionDetail[SIZE]. The specific exception associated with each of thebitmaps is given in the table below. The SIZE for this revision is two (2).

15

Device exception detailThis structure, similar in form to common exception detail, relates exception conditions which are specific to individual devices on the network and are defined in
the following. The detail element of the structure is an ordered list (i.e. array) ofbytes of length [size = 2] which is the value of the structure element size.

Manufacturer exception
detailThis structure, similar in form to Common Exception Detail, relates exception conditions which are specific to the manufacturers of individual devices on the network.
There is one byte manufacturer exception details defined. The Detail element of thestructure is an ordered list (i.e. array) of bytes of length [size = 1] which is the valueof the structure element size.

Exception detail alarm
Data component

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Common exception detailalarm size

0

0

0

0

0

0

1

0

Common exception detailalarm 0

0

0

0

Data
memoryNonvolatilememoryCodememory00Common exception detailalarm 1

0

0

0

0

0

0

0

0

Device exception detailalarm size

0

0

0

0

0

0

1

0

Device exception detailalarm 0S-Analog sensor instance 1, sensor alarm byte 0

Device exception detailalarm 1

S-Analog sensor instance 1, sensor alarm byte 1

Manufacturer exception
detail alarm size

0

0

0

0

0

0

0

1

Manufacturer exception
detail alarm 0

0

0

0

0

0

0

0

SerCom
Alarm

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Common exception detailwarning size

0

0

0

0

0

0

1

0

Common exception detailwarning 0

0

0

0

Data
memoryNonvolatilememoryCodememory00Common exception detailwarning 1

0

0

0

0

0

0

0

0

Device exception detailwarning size

0

0

0

0

0

0

1

1

Exception detail warning
Data component

Device exception detailwarning 0

S-Analog sensor instance 1, status extension

Device exception detailwarning 1

S-Analog sensor instance 1, sensor warning byte 0

Device exception detailwarning 2

S-Analog sensor instance1, sensor warning byte 1

Manufacturer exception
detail warning size

0

0

0

0

0

0

0

1

Manufacturer exception
detail warning 0

0

0

0

0

0

0

0

SerComWarning16

tira51e1(2009-01)

CDGxxxD.cp

Alarm enable and warning
enable4.3.4 S-Device Supervisor
Object States

These boolean attributes are used to enable (1) or disable (0) the S-Device supervisor object’s process of setting exception bits. When disabled, corresponding bits
are never set; and, if they were set, disabling clears them. Also, alarm and warningstates are not retained; when enabled, bits will be set only if the corresponding
condition is true.
The default state for these enable attributes is enabled (1).

Power Applied, orReset Request from any state except CRITICAL FAULT, or
Perform Diagnostics Request from any state except CRITICAL FAULT or ABORT

Self-Test Failed
SELF-TESTING

Self-Test
PassedRecover Request or
Exception Condition
ClearedSELF-TESTEXCEPTION

Abort Request
Abort Request
IDLE

Stop Request
Connection Timeout
or Release Master/
Stave Connection
Set

Recover Request

Start
RequestABORTCRITICAL FAULT
Abort Request

EXECUTING
Critical Fault
from any state

Abort - Used to transition the device application objects to the aborted state. This
service request may be (and generally will) originated internally, from application
objects.
Recover - Used to transition the device application objects, out of the abort state,
to the idle state. This service request may be originated internally, from application
objects.
Perform_Diagnostics - Used to instruct the DS object to perform a diagnostic test.

4.3.5 S-Device Supervisor
Common Services

Service
Code

Service Name

Description of Service

0Eh

Get_Attributes_Single

Returns the contents of the specified
attribute.

10h

Set_Attributes_Single

Modifies an attribute value.

05h

Reset

Resets the device to the Self-Testing state.

06h

Start

Starts the device execution.

07h

Stop

Moves the device to the Idle state.

The device transitions from the IDLE state to the EXECUTING state by a
START Request (Service Code 06h) or by the receipt of the first valid I/Odata.
You will not get any valid measurement values from the device until thisservice has been requested or the I/O-poll message has been received.

tira51e1(2009-01)

CDGxxxD.cp

174.3.6 S-Device Supervisor
Object Specific Services

Explanation toService code 4Eh

Service
Code••

Service Name

Description of Service

4Bh

Abort

Moves the device to the Abort state

4Ch

RecoverMoves the device out of the Abort state

4Eh

Perform_Diagnostics

Causes the device to perform a set of
diagnostic routines

DS Object Service Parameter dictionary
Parameter

Form

Description

TestID

USINT

Type and possibly detail of diagnostic test to be
performed

TestID parameter
The following values are defined for the TestID parameter for the
Perform_Diagnostics Service Request:
Attribute Value
0

State
Standard

Type "Standard" is specified if there is only one type of diagnostic defined or if
there are more than one including a type standard.

18

tira51e1(2009-01)

CDGxxxD.cp

4.4 S-Analog Sensor Object

Class Code 31h = 49d

4.4.1 Class Attributes
Attribute ID

Accessrule

Name

DeviceNetdata type

Description of attribute

1

Get

Revision

UINT

Revision of this object Note: All class definitions are The current value
required to include this class attribute.
assigned to this attribute is one (01).

2

Get

Max
instance

UINT

Maximum instance number of an object currently
created in this class level of the device.

94

Get

Activevalue

Is used by assemblies to produce this class-level
INT orspecified by attribute, instead of the value (attribute ID 6) of the
S-Analog sensor instances.
data type

95

Get

Activeinstance
numberUINT

Identifies the object instance that is providing thevalue which is copied into the active value for all
input assemblies and the alarm/warning exception
details for the S-Device supervisor object.

Semantics of values

The largest Instancenumber of a createdobject at this classhierarchy level.

Default = 1→ Behavior section.
96

Get

Number ofgaugesUSINT

Identifies the number of gauge instances present in
the device.

99

Get

Subclass

UINT

Identifies a subset of additional class attributes,
services and behaviors.

1 ≙ Instance selector

4.4.2 Semantics
Active value

Assemblies or connections may produce this class-level attribute, instead of thevalue (attribute ID 6) of the active S-Analog sensor instance. The S-Analog sensor
class-level attribute active instance number identifies the object instance that iscurrently active and providing the value to the active value class-level attributewhich is, in turn, produced by the input assemblies that have active value as amember.

Active instance number

The device internally modifies this attribute, as required, to identify the S-Analog
sensor object instance providing the value member which is copied into the active
value for all input assemblies and the alarm/warning exception details for the
S-Device supervisor object.
→ Behavior for more information on the mechanism.

Number of gaugesThis attribute is used to determine the size of all input assemblies within a node.
→ respective device profile for its usage within a device type.

4.4.3 Instance Attributes

tira51e1(2009-01)

CDGxxxD.cp

Two S-Analog sensor instances (instance 1 and instance 2) are available. Instance
1 represents the physical sensor reading of the capacitance diaphragm gauge.
Instance 2 represents the physical sensor reading of the atmosphere pressure
sensor.

19

4.4.3.1 Instance Attributes ofInstance 1

Following is the instance 1 with the subclass extension of the capacitance manometer (diaphragm gauge) part of the gauge. Many different types of gauges areavailable. The behavior of all gauges is the same, but the fullscale value isdifferent.

Attribute
ID

Access rule

NV/ NameV

DeviceNet data
type

Description of
attribute

Semantics of values

3

Set /Cond.
→ below

NV Data type

USINT

Determines thedata type of value
and all related
attributes as specified in this table.

→ "Semantics" section below.
Int≙ C3h [default]

4

20

Set
→ below

NV Data units

UINT

Determines theunits context ofvalue and all related attributes.

float

≙ CAh

→ "Semantics" section below.
Supported Values:
Counts ≙ 1001h [default]
mbar≙ 1308h

Torr≙ 1301h

Pascal≙ 1309h

5

Get

V

Reading valid

BOOL

0 = invalid
Indicates that thevalue attribute con- 1 = valid
tains a valid value. (invalid: e.g., not warmed up
yet)

6

Get

V

Value

INT or specified
by data type

Analog input value

The corrected, converted, calibrated final value of the sensor.
→ "Semantics" section below.

7

Get

V

StatusBYTE

Alarm and warningstate of this object
instance.

→ "Semantics" section below.

8Set

NV Alarm enable

BOOL

Enables the setting 0 = disable [default]of the alarm status 1 = enable
bits

9

Set

NV Warning enable

BOOL

Enables the setting 0 = disable [default]
1 = enableof the warning
status bits

10

Get

NV Full Scale

INT or specified
by data typeThe value of fullscale for the sensor.

The value of attribute value
corresponding to the full scalecalibrated measurement of thesensor.
[default] = maximum allowablevalue for the data type

11

Get

NV Offset-A data type

USINT

Determines thedata type of
attribute offset-A[default] = INT (C3h)

12

Set

NV Offset-A

Specified byattribute 11

An amount addedprior to gain toderive value

This value could be read at themeasurement device itself after
execution of zero adjust service.
0 = [default]

17

Set

NV Alarm trip point
high

Determines thevalue above whichan alarm condition
will occur[default] = Maximum value forits data type.

18

Set

NV Alarm trip point low INT or specified
by data type

Determines thevalue below whichan alarm condition
will occur[default] = Minimum value for its
data type.

19

Set

NV Alarm hysteresis

Determines theamount by which
the value must
recover to clear an
alarm condition[default] = 0

INT or specified
by data typetira51e1(2009-01)

CDGxxxD.cp

Attribute
ID

Access rule

NV/ NameV

DeviceNet data
type

Description of
attribute

21

Set

NV Warning trip pointhigh

INT or specified
by data type[default] = Maximum value for
Determines thevalue above which its data type.
a warning condition
will occur

22

Set

NV Warning trip pointlow

INT or specified
by data type[default] = Minimum value for its
Determines thevalue below which data type.
a warning condition
will occur

23

Set

NV Warning hysteresis NT or specified
by data type

Determines theamount by which
the value must
recover to clear awarning condition

25

Set

NV Safe state

USINT

Specifies the be→ "Semantics" section below.
havior for the value [default] = 0
for states otherthan execute

26

Set

NV Safe value

INT or specified
by data typeThe value to be
used for safe state= safe value→ "Semantics" section below.
[default] = 0

32

Get

NV Overrange

INT or specified
by data typeSpecifies the highest valid value

The value above which attributereading valid is set to invalid.
[default] = maximum allowablevalue for the data type

33

Get

NV Underrange

INT or specified
by data typeSpecifies thelowest valid value

The value below which attributereading valid is set to invalid.
[default] = minimum allowablevalue for the data type

93

Get

V

Sensortemperature

RealThe temperature in
Celsius at which
the sensor has
warmed up

94

Get

V

Sensor warning

Struct of byte

Bit definitions of
sensor warnings

0 = [default]

Bit definitions of
sensor alarms

0 = [default]95

tira51e1

Get

V→ "Semantics" section below→ "Semantics" section below

0 = [default]
Bit-mapped byte
providing additional → "Semantics" section below
status bits of an SAnalog sensor
instance.

NV Subclass

UINT

Identifies a subset
of additional instance attributes,
services and behaviors.

Set

NV Offset vendor
specific

INT or specified
by data type

Customer specified
offset which will be
added to the offsetA value from zeroadjust service

Set

NV Filter

USINT

Get

V

99

Get

100

101

CDGxxxD.cp

Struct of byte

[default] = 0

BYTE

96

(2009-01)

Sensor alarm

Semantics of values

Status extension

3 = Capacitance Manometer

0 = Dynamic [default]
1 = Fast
2 = Slow21

4.4.3.2 Semantics
Data type

All Data Type attributes use the enumerated values integer or float.
The Data Type value will be set automatically based upon the first valid I/O connection established by the device.
If no established I/O connections exist, which include an attribute from this object,then the Data Type attribute is settable provided that the object is in the Idle State.
Note: Using data type integer in combination with a pressure unit (mbar, Torr or Pa)
will obviously not produce reasonable values below 1.

Data unit

The Data Unit is only settable in the IDLE state.

Value

An S-Analog sensor object instance derives a reading from a physical analog sensor. The reading is converted to the data type and units specified for the value
attribute.

StatusA bit mapped byte which indicates the Alarm and Warning Exception status of theobject instance. The following definition applies:

Safe state

Bit

Definition

0

High Alarm Exception:

0 = cleared1

Low Alarm Exception:

0 = cleared

1 = set2High Warning Exception: 0 = cleared

1 = set3

Low Warning Exception:

1 = set4

Reserved

5

Reserved

6

Reserved

7

Reserved

0 = cleared

1 = setThis attribute specifies what value will be held in value for states other than executing. The purpose of this mechanism is to allow other devices, who may be using
this value to transition to (or remain in) a safe state in the event of this device
transitioning to a FAULT, IDLE, or ABORT state. The following values are defined:
Attribute value

State

0

Zero

1

Full scale

2

Hold last value

3

Use safe value

Safe value

For safe state set to use safe value, this attribute holds the value to which the value
attribute will be set for object instance states other than executing.

Sensor alarm

16 Bits are used as sensor faults. Sensor alarm byte 0 is mapped to the device
exception detail alarm 0, sensor alarm byte 1 is mapped to the device exception
detail alarm 1.

Data component

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Sensor alarm byte 0

0

0

0

0

0

0

0

0

Sensor alarm byte 1

High alarm
exception

Low alarm
exception

0

0

0

0

Electronics
failure0

22

tira51e1(2009-01)

CDGxxxD.cp

Sensor warning

16 Bits are used as sensor warnings. Sensor warning byte 0 is mapped to thedevice exception detail warning 1, sensor warning byte 1 is mapped to the device
exception detail warning 2.

Data component

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Sensor warning byte 0

0

0

0

0

0

0

0

Not attemperature

Sensor warning byte 1

High
warning
exception

Lowwarning
exception

0

0

0

0

Electronics
warning

Status extension
Data component

0

8 Bits providing the current sensor alarm state of the instance. They are mapped todevice exception detail warning 0.
Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

0

0

0

0

0

Underrange
exceededOverrange
exceeded

Reading1)
invalid

Sensor alarm byte 01)

4.4.3.3 Common Services

Logical inversion of reading valid

The S-Analog Sensor Object provides the following common services:
Service Service Name
Code

4.4.3.4 Object–Specific
Services

Description of Service

0Eh

Get_Attribute_Single

Returns the contents of the specified attribute.

10h

Set_Attribute_Single

Modifies an attribute value.

The S-Analog Sensor Object provides the following common services:
Service Service Name
Code
4Bh

Zero_Adjust

Description of Service
Used to calibrate the zero pressure value.
2 = zero adjust

The Zero_Adjust service is used to cause the S-Analog sensor object device tomodify its Offset-A attribute value (instance 1) based upon manufacturer specificalgorithms. The target value specified in the service request represents the actual
parametric measurement that the physical sensor should be reporting at the time of
the request.
There are no state transitions associated with the invocation of this service. It is,therefore, incumbent upon the user to establish the device into the desired configuration prior to, and during, the execution of these services. This will generally
involve exposing the sensor to a known environment and treating the values read
during execution of the services accordingly.
A success service response indicates that the service was accepted and theapplication process started.

Zero adjust algorithm

Zero_Adjust request service
data field parameters

tira51e1(2009-01)

CDGxxxD.cp

To perform the Zero_Adjust Request pump down to a value 2 decades below theminimum pressure range of the gauge and then start the Zero_Adjust Request
Service with a target value of "0".

Parameter

Data type

Description

Semantics of values

Zero_Adjust
parameteror target
value

UINT or
FLOAT
depending ondata type

The target
value for thezero calibration

The value to which the attribute6, value, will be set (always 0).
If not specified, the default valueof zero is used.

23

4.4.3.5 Behavior
Data typeThe following behavior with respect to Data Type applies:
The data type value will be set automatically based upon the first valid I/O connection established by the device.
If no established I/O connections exist, which include an attribute from this object,then the Data Type attribute is settable provided that the object is in the Idle State.
The following example demonstrates this behavior:
A device specifies an instance of the S-Analog sensor object as well as two static
assembly object instances, both with data attribute components mapped to thisobject instance. Assembly object instance ID 1 specifies INT data types andassembly object instance ID 2 specifies REAL data types.
After the device is on-line, it is configured with an I/O connection to assembly
instance ID 2. When the connection transitions to the Established State, this object
instance attribute Data Type is automatically set with the value for REAL before
any data is communicated to, or from, the object instance. Any subsequent attempt
to connect to assembly instance ID 1 would then be rejected and result in an
INVALID ATTRIBUTE VALUE error with the additional error code indicating the IDof the offending attribute, which in this case would be the connection path.

24

tira51e1(2009-01)

CDGxxxD.cp

4.4.3.6 Instance Attributes ofInstance 2 / Atmosphere
Pressure Sensor
Attribute
ID

Access rule NV/ NameV

DeviceNetdata type

Description of attribute

Semantics of values

3

NV Data type→
"Semantics"

USINT

Determines the data typeof value and all related
attributes as specified inthis table.

→ "Semantics" section below[default] = INT

4

NV Data units→"Semantics"

USNIT

Determines the units context of value and all related
attributes.

[default] = Counts

5

Get

V

Reading
valid

BOOL

Indicates that the value
attribute contains a valid
value.

0 = invalid
1 = valid (always set)

6

Get

V

Value

INT or REAL

Analog input value.

The corrected, converted, calibrated
final value of the sensor.
→ "Semantics" section

7

Get

V

StatusBYTE

Alarm and warning state ofthis object instance.

=0

10

Get

NV Full scale

INT or REAL

The value of full scale forthe sensor.

[default] = maximum allowable value
for the data type

25

Set

NV Safe state

USINT

Specifies the behavior forthe value for states otherthan execute.

→ "Semantics" section below[default] = 0

26

Set

NV Safe value INT or specified by data
type

The Value to be used forsafe state = safe value→ "Semantics" section below[default] = 0

32

Get

NV Overrange INT or REAL

Specifies the highest valid
value.

The value above which attributereading valid is set to invalid.
[default] = maximum allowable value
for the data type

33

Get

NV Underrange

INT or REAL

Specifies the lowest valid
value.

The value below which attributereading valid is set to invalid.
[default] = minimum allowable value
for the data type

94

Get

V

Sensorwarning

Structure ofbyte

Bit definitions of sensor
warnings.

default = 0→ "Semantics" section below

95

Get

V

Sensoralarm

Structure ofbyte

Bit definitions of sensor
alarms.

default = 0→ "Semantics" section below

96

Get

V

Statusextension

Byte

Bit-mapped byte providing
additional status bits of an
S-Analog sensor instance.

default = 0→ "Semantics" section below

99

Get

V

Subclass

UINT

Identifies a subset of additional instance attributes,
services and behaviors.

3 = Capacitance Diaphragm Gauge

4.4.3.7 Semantics of S-Analog
Sensor Instance 2

tira51e1(2009-01)

Data type→ Instance 1

Data units→ Instance 1

Value→ Instance 1

Safe state→ Instance 1

Safe value→ Instance 1

CDGxxxD.cp

25

16 Bits are used as sensor warnings.

Sensor warning
Data component

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Sensor warning byte 0

0

0

0

0

0

0

0

0

Sensor warning byte 1

0

0

0

0

0

0

0

0

Sensor alarm
Data component

16 Bits are used as sensor faults.
Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

Sensor alarm byte 0

0

0

0

0

0

0

0

0

Sensor alarm byte 1

0

0

0

0

0

0

0

0

Status extension
Data component
Sensor alarm byte 0

8 Bits providing the current sensor alarm state of the instance
Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

Bit 2

Bit 1

Bit 0

0

0

0

0

0

Underrange
exceeded=0Overrange
exceeded=0

Reading1)
invalid=01)

4.4.3.8 Common Services of
S-Analog Sensor
Instance 2

4.4.3.9 User Atmosphere
Adjust Service

Logical inversion of reading valid

The S-Analog sensor object provides the following common services:
Service Service namecode

Description of service

0Eh

Get_Attribute_Single

Returns the contents of the specified attribute.

10h

Set_Attribute_Single

Modifies an attribute value.

Service Service Name
Code
32h

User Atmosphere
AdjustDescription of Service
Performs an Atmosphere Adjust for the ATMSensor

There are no state transitions associated with the invocation of this service. It is,therefore, incumbent upon the user to establish the device into the desired configuration prior to, and during the execution of this service. This will generally involve exposing the sensor to a known environment and treating the values read
during execution of the services accordingly.
A success service response indicates that the service was accepted and the application process started.
To perform the User Atmosphere Adjust Request vent the gauge to atmosphereand then start the User Atmosphere Adjust Service without any target value. The
pressure value of the atmospheric pressure sensor is then tracked to the value of
the CDG.

26

tira51e1(2009-01)

CDGxxxD.cp

4.5 Trip Point Object

Class Code 35h = 53d
The Trip Point Object models the action of trip points (two relays) of the CDG(corresponding to physical outputs) (Discrete Output Object). A trip point value,
designated as a high or low trip point, is compared to the specified source value.
This trip point is intended to be used as a process control indicator.

4.5.1 Class Attributes
Attribute ID

Accessrule

Name

DeviceNet Description of attributedata type

1

Get

Revision

UINT

Revision of this object. Note: All class definitions
are required to include this class attribute.

2

Get

Max
instance

UINT

Maximum instance number of an object currently
created in this class level of the device.

4.5.2 Instance Attributes ofTrip Point Objects
Instance 1 & 2AttributeIDtira51e1

Access rule NV/ NameV

DeviceNetdata type

Description of attribute

Semantics of values

5

Set

NV Low trippoint

INT or based
data typeattribute

Defines the value at or below which a trip point condition will occur.

→ "Semantics" section below[default] = 0

6Get

NV Low trip
enable

BOOL

Enables the low trip point
setting.

[default] = 0

7

Get

V

BOOL

State of this object
instance.

0 = trip point condition does not exist(unasserted)
1 = trip point condition exists(asserted)

10

Set

NV Hysteresis

Same ashigh/low point
data type

Determines the amount bywhich the input must recover to clear a trip pointcondition.

→ "Semantics" section[default] = 0

12

Get

NV Destination

PackedEPATH

Path to attribute 3 of Instance 1 or 2
Specifies the path of thedestination attribute whose of DOP Object.
value will be set by output.

13

Get

V

OutputBOOL

Output of the object thevalue of which is sent todestination.

= Status of the relay

14

Get

NV Source

PackedEPATH

Specifies the path of thesource attribute whose
value is retrieved for Input.

Path to attribute 6 of instance 1 of Sanalog sensor object

15

Get

V

Input

INT or specified by datatype

Input to the object whose
value is retrieved fromsource.

Value of attribute 6 of instance 1 of Sanalog sensor object

16

Get

NV Data units

ENGUNITS

Units of input, trip point.

USINT

Status17

Get

NV Data type

Data type of input.

[default] = INT

101

Set

NV Percentage REAL
of ATM

Multiplier for ATM control.

If high trip point enabled, this value
will be multiplied with pressure value
from S-Analog sensor instance 2(ATM sensor) copied into trip point
high

102

Get

V

INT or based
data typeattribute

Defines the value at or
above which a trip pointcondition will occur.

[default] = 0

103

Get

NV High trip
enable

BOOL

Enables the high trip point
setting.

[default] = enabled(2009-01)

CDGxxxD.cp

High trip
point

27

4.5.3 Semantics
Setpoint function

If "Low Trip Enable" is set, the setpoint function is used (automatically attr. 101 is
set to zero and the functionality ATM detection is disabled).
Low trip point is compared to the input value to generate a trip point condition.
Status will be set if the input value is at or below the low trip point.
If the pressure increases above the low trip point and hysteresis, the status will bereset.

ATM detection

This functionality is used to compare the pressure measured by the CDG with theatmospheric pressure.
Attribute 101 is used to define a value "Percentage of Atmosphere". This value will
be multiplied with the pressure from the S-Analog sensor instance 2 (ATM sensor).
Then the result will be copied into attr. 102 = ATM high trip point. If a value iswritten to percentage of atmosphere, the low trip enable is set to zero.
Status will be set if the input value is at or above the high trip point.
If the pressure decreases below the high trip point - hysteresis, the status will bereset.

Hysteresis

The Hysteresis value specifies the amount by which the Input value must transitionin order to clear a trip point condition.
The following relationship demonstrates the logic for a Low Trip Point:
For Status not set:
For Status set:

4.5.4 Common Services

If (Input ≤ Trip Point Low)
Then set Status
If (Input > Trip Point Low +Hysteresis)
Then clear Status

The trip point object provides the following common services:
Service Service name
code

28

Description of service

0Eh

Get_Attribute_Single

Returns the contents of the specified attribute.

10h

Set_Attribute_Single

Modifies an attribute value.

tira51e1(2009-01)

CDGxxxD.cp

4.6 Discrete Output Point
ObjectClass Code 09h = 09d

4.6.1 Class Attributes
Attribute ID

Accessrule

Name

DeviceNet Description of attributedata type

1

Get

Revision

UINT

Revision of this object. Note: All class definitions
are required to include this class attribute.

2

Get

Max
instance

UINT

Maximum instance number of an object currently
created in this class level of the device.

4.6.2 Instance Attributes ofInstance 1 & 2Attribute
ID

Accessrule

Name

DeviceNetdata type

Description of attribute

Semantics of values

3

Get

Value

BOOL

Output point value.

0 = Off
1 = On (activated)

4.6.3 Common Services

The discrete output point object provides the following common services:
Service Service name
code
0Eh

tira51e1(2009-01)

CDGxxxD.cp

Get_Attribute_Single

Description of service
Returns the contents of the specified attribute.

29

5 I/O Assembly Object
Class Code04h = 04d

A collection of assembly objects allows the sending of attributes from different
application objects in one message (i.e. Polling I/O).

5.1 I/O Assembly Object
Instance Data Attribute
FormatThe S-Analog Sensor object definition specifies a behavior that modifies the Data
Type of certain attributes based upon the first valid I/O connection established toan Assembly Object instance. In order to maintain consistency, this device type will
only allow connections to either INT or REAL based Assembly instances. Once a
valid connection is established, attempts to configure connections, or otherwise
access data, to a different type of Assembly instance will return a RESOURCEUNAVAILABLE error.
The I/O Assembly DATA attribute has the format shown below:

Instance

Type

Byte

1

Input

0-1

Bit 7

Bit 6

Bit 5

Bit 4

Bit 3

INT Pressure Value

Bit 2

Bit 1

2
(default)

Input

0
1-2

Exception Status
INT Pressure Value

3

Input

0

Exception Status

Bit 0

0

Trip
StatusInst. 2

Trip
StatusInst. 10

Trip
StatusInst. 2

Trip
StatusInst. 10

Trip
StatusInst. 2

Trip
StatusInst. 10

Trip
StatusInst. 2

Trip
StatusInst. 1

1
0

0

0

0

0

2-3

INT Pressure Value

4

Input

0-3

REAL Pressure Value

5

Input

0
1-4

Exception Status
REAL Pressure Value

6

Input

0

Exception Status

1
0

0

0

0

2-5

REAL Pressure Value

8

Input

0

Exception Status

9

Input

0-1
2-3

Active Instance
INT Active Pressure Value

10

Input

0
1-2
3-4

Exception Status
Active Instance
INT Active Pressure Value

11

Input

0

Exception Status

1

0

0

0

0

0

2-3
4-5

Active Instance
INT Active Pressure Value

12

Input

0-1
2-5

Active Instance
REAL Active Pressure Value

13

Input

0
1-2
3-6

Exception Status
Active Instance
REAL Active Pressure Value

14

Input

0

Exception Status

1
2-3
4-7

30

0

0

0

0

0

0

Active Instance
REAL Active Pressure Value

tira51e1(2009-01)

CDGxxxD.cp

Appendix
A:

Conversion of a Floating
Number According toIEEE 754
General
Number received

AA BB CC DDh

1. Reverse the sequence ofthe HEX words

2. Separate into bytes

Legend:XXh

Hexadecimal number(Radix = 16)

XXd

Decimal number (Radix = 10)

XXb

Binary number (Radix = 2)

DDh

CCh

BBh

AAh

SEEE EEEEb

EMMM MMMMb

MMMM MMMMb

MMMM MMMMb

Sign

3. Calculate(4-Byte, floating format)

8-Bit exponent

23-Bit mantissa

S

EEEE EEEEb

MMM MMMM MMMM MMMM MMMM MMMMbØØØ⎛ MMM MMMM MMMM MMMM MMMM MMMM ⎞
b⎟
23
⎜
⎟
2
⎝
⎠

1+ ⎜

⎛ NNNNNd ⎞⎟⎝ 8388608 d ⎠= 1+ ⎜

Ø
Sign =

Exponent =Mantissa =

S

XYZd

RSTUVd-1

Converted number

tira51e1(2009-01)

CDGxxxD.cp

Sign × 2(Exponent-127) × Mantissa

31

Example
Number received

00 00 CA 42h

1. Convert sequence of the
HEX words

2. Separate into bytes

42h

CAh

00h

00h

0100 0010b

1 1 0 0 1010b

0000 0000b

0000 0000b

Sign

3. Calculate(4-Byte, floating format)

8-Bit exponent

23-Bit mantissa

01000 0101b

100 1010 0000 0000 0000 0000b

Ø

Ø

Ø

-10

⎛ 100 1010 0000 0000 0000 0000 ⎞
b⎟
1+ ⎜⎜
⎟⎟
23
⎜
2
⎝
⎠
⎛ 4849664 d ⎞⎟⎝ 8388608 d ⎠= 1+ ⎜

ØØ

Sign =

Exponent =Mantissa =1133

1.578125

Converted number

B:

Typical Start-Up
Procedure

Allocation process

1 × 2(133-127) × 1.578125 = 101

The start up of a device is divided into the steps:•

Allocation process•

Setting of the EPR attribute•

Choice of the input and output assemblies

Send an allocation string as defined in the DeviceNet specification to the device
you want to allocate.
Set the bits in the allocation choice byte to 1 for these connections you want to use.

32

tira51e1(2009-01)

CDGxxxD.cp

Example

Master MAC ID:
Allocation choice:Slave address:

0
Explicit, poll, bit strobe, COS
2⇒ Allocation string:
Slave’s explicit/unconnected response message:

416
413

00 4B 03 01 57 00
00 CB 00

Within the first allocation message the explicit connection has to beestablished.

Setting of the EPR attribute(expected packet rate)

After the allocation, the device activates an INACTIVITY WATCHDOG TIMER.
This timer has to be set for every single connection (connection object, attribute 9)
which is allocated in the allocation choice byte. This attribute defaults to 2500
(2500 milliseconds) within explicit messaging connections, and to zero within an I/O
connection. If the INACTIVITY WATCHDOG TIMER expires, the establishedconnection will be released. With every message the device receives, this timer isreloaded with the value specified in the according connection object and so it
doesn’t expire. The value zero deactivates the INACTIVITY WATCHDOG TIMER.
So in this step the inactivity watchdog timer has to be set. In testing mode you
could use the value 0 to deactivate the inactivity watchdog timer.
In the following you see the strings for setting the EPR attribute (addresses as
specified above):ID

Message body414

00 10 05 01 09 00 00

set EPR of the explicit connection to zero414

00 10 05 02 09 00 00

set EPR of the poll connection to zero414

00 10 05 03 09 00 00

set EPR of the bit strobe connection to zero414

00 10 05 04 09 00 00

set EPR of the COS/cyclic connection to zero

The responses of the slave are:

Choice of the input and output
assemblies

ID

Message body413

00 90 00 00

set EPR of the explicit connection to zeroYou can specify which of the several in a device predefined input/output assemblies should be used for every single connection.
Reading or setting of the input/output assemblies is possible only if thecorresponding connection (polling, change of state, bit strobe) has been
allocated in the allocation message.

Reading the configured
assemblies

If you want to read the number of the chosen assembly, you must read the attributes 14 and 16 in the corresponding Instance of the connection object (object ID 5).
For reading this value, the connection has to be established. The EPR attributemay be set.
Instance 2: Polling
Instance 3: Bit strobe
Instance 4: Change of state/cyclic

tira51e1(2009-01)

CDGxxxD.cp

33

Setting of assemblies

If you want to set the number of the chosen assembly, you must set the attributes
14 and 16 in the corresponding instance of the connection object.
For setting this value, the connection has to be allocated, but the EPR
attribute has not to be set to any value.

ExamplesRead a configured assembly (addresses as specified above)

Get single request:
ID

Message body

414

00 0E 05 02 0E

Get produced connection path (request for
input assembly by master).

Get single response:ID

Message body413

00 8E 20 04 24 05 30 03

Response from slave

The addressing format of the attribute values differ from the normal mode. A connection path attribute that specifies class 4, instance 5, and attribute ID 3 is illustrated below:
Class #420

04

Instance #5
2405

Attribute #3
30

03

The instance defines the assembly you want to use. This format has to be used by
the master in the request and is used by the slave in the response.
Set the input assembly 04 for a poll connection (addresses as specified
above)

Set single request:
ID

Message body414

80 00 10 05 02 10 20 04414

80 81 24 04 30 03

First fragment
Second fragment

Because the message body is greater than 8 bytes, the fragmented protocol has tobe used.
Set single response:

34

ID

Message body413

80 C0 00

Response on first fragment

413

80 C1 00

Response on second fragment

tira51e1(2009-01)

CDGxxxD.cp

C:

tira51e1

Literature(2009-01)

CDGxxxD.cp[1]

www.inficon.com
Operating Manual
CDG045D
tina51e1
INFICON AG, LI–9496 Balzers, Liechtenstein[2]

www.inficon.com
Operating Manual
CDG100D
tina52e1
INFICON AG, LI–9496 Balzers, Liechtenstein[3]

www.inficon.com
Operating Manual
CDG160D, CDG200D
tina53e1
INFICON AG, LI–9496 Balzers, Liechtenstein[4]

www.odva.org
Open DeviceNet Vendor Association, Inc.
DeviceNet™ Specifications[5]

Common Industrial Protocol (CIP™) Ed. 3.5 and DeviceNet™ Adaptionof CIP Ed. 1.6 (Open DeviceNet Vendor Association)[6]

www.inficon.com
Product descriptions and downloads
INFICON AG, LI–9496 Balzers, Liechtenstein35Original: English tira54e1 (2009-01)

t i r a54e1

LI–9496 Balzers
LiechtensteinTel +423 / 388 3111
Fax +423 / 388 3700
reachus@inficon.com
www.inficon.com