Interface for Bayard-Alpert Capacitance Diaphragm Gauge
BCG450-SD
tira40e1 (2005-04)1
Intended Use
of this Document
This Communication protocol contains instructions for operating the vacuum gauges BCG450-SD (featuring DeviceNet interfaces) as slaves together with a
DeviceNet master.
This manual describes the functionality of DeviceNet for programming
purposes. For more information refer to the "DeviceNet specifications" of
the Open DeviceNet Vendor Association (ODVA) (→ [2]) and the corresponding european standard (→ [3]).
For specifications and operation instructions of the vacuum gauges refer
to the appropriate documents:
BCG450-SD → [1], [4], [5], [6]
DeviceNet Interface
Abbreviations
The following description of the DeviceNet Interface is compliant to the DeviceNet
specification of the Open DeviceNet Vendor Association.
This manual describes the functionality of a DeviceNet Group 2 Only Slave and
supports Explicit Messaging and the I/O Polling.
We reserve the right to make technical changes without prior notice.
Abbr.Meaning
NVNonvolatile; attribute value is maintained through power cycles
VVolatile
INTInteger value(Range –32767 … 32768)
UINTUnsigned integer value(Range 0 … 65635)
USINTUnsigned character value (Range 0 … 255)
FLOATFloating point value(Range according to IEEE 754)
XX
XX
XX
Hexadecimal number(Radix = 16)
h
Decimal number(Radix = 10)
d
Binary number(Radix = 2)
b
Trademarks
2tira40e1 (2005-04) BCG450SDv1.cp
DeviceNet™ Open DeviceNet Vendor Association Inc.
Contents
Intended Use of this Document2
DeviceNet Interface2
Abbreviations2
Trademarks2
1 Start-Up of the Slave4
1.1 Power Supply Requirements4
1.2 Front View of the BCG450-SD4
1.3 Connectors on the Device5
1.4 Side View of the BCG450-SD6
1.5 Indicators and Switches6
1.5.1 Module Status LED6
1.5.2 Network Status LED7
1.5.3 Node Address Switch7
1.5.4 Data Rate Switch7
1.5.5 Setpoint7
2 Object Structure8
2.1 Connection Object8
2.1.1 Vendor-Specific Object Extension on Instance 2 Poll Connection8
2.2 Identity Object9
2.2.1 Class Attributes9
2.2.2 Instance Attributes9
2.3 S-Device Supervisor Object9
2.3.1 Class Attributes9
2.3.2 Instance Attributes10
2.3.2.1 Semantics11
2.3.3 S-Device Supervisor Object States15
2.3.4 S-Device Supervisor Common Services15
2.3.5 S-Device Supervisor Object Specific Services16
2.4 S-Analog Sensor Object16
2.4.1 Class Attributes16
2.4.2 Instance Attributes17
2.4.2.1 Instance Attributes of Instance 1 / Pirani Instance17
2.4.2.2 Semantics of S-Analog Sensor Instance 118
2.4.2.3 Instance Attributes of Instance 2 / Hot Cathode Ion Gauge20
2.4.2.4 Semantics of S-Analog Sensor Instance 221
2.4.2.5 Instance Attributes of Instance 3 / Capacitance Diaphragm Gauge23
2.4.2.6 Semantics of S-Analog Sensor Instance 324
2.4.2.7 Object-Specific Services on Instance 3 /
Capacitance Diaphragm Gauge25
2.4.2.8 Instance Attributes of Instance 21 / Setpoint A
(Instance 22 / Setpoint B)26
2.4.3 Common Services29
2.4.4 Object-Specific Services on Instance 2 / Hot Cathode Ion Gauge29
2.4.4.1 SET DEGAS STATE29
2.4.4.2 SET EMISSION STATE29
2.4.4.3 Emission Control Mode30
2.4.5 Behavior30
3 I/O Assembly Object31
3.1 I/O Assembly Instances31
3.2 I/O Assembly Object Instance Data Attribute Format32
Appendix33
A: Range of Values33
B: Specific Codes33
C: Conversion of a Floating Number According to IEEE 75433
D: Typical Start-Up Procedure34
E: Literature37
For cross-references within this document, the symbol (→ XY) is used, for crossreferences to further documents listed under literature, the symbol (→ [Z]).
tira40e1 (2005-04) BCG450SDv1.cp3
1Start-Up of the Slave
1.1 Power Supply
Requirements
1.2 Front View of the
BCG450-SD
The BCG450-SD has to be powered with two voltages:
1.)24 Volt DC, 20 W at the 15 pole Sub-D connector for the gauge itself;
2.)24 Volt DC nominal, <2 W range +11 … +25 V) at the DeviceNet micro style
connector for the DeviceNet transceiver.
3
2
1
PositionFunction
1Address Switch × 10, decimal
2Address Switch × 1, decimal
3DeviceNet connector
4Data Rate Switch
5Network Status LED
6Module Status LED
7"Sensor cable" connector
(Power, analog I/O, RS232C I/O
and Relay contacts)
5
4
6
7
4tira40e1 (2005-04) BCG450SDv1.cp
1.3 Connectors on the
Device
The BCG450-SD uses a "Sealed Micro-Style Connector" for the DeviceNet connection. The DeviceNet part of the gauge is powered via the DeviceNet connector.
Pin Assignment of the Sealed
Micro-Style Connector
1Relay Setpoint A, n.o. contact
2Measuring signal output (0 … +10.13 V)
3Threshold Setpoint A, output (0 … +10 V)
9
1
4Relay Setpoint A, common contact
5Supply sensor electronics common
1)
6Threshold Setpoint B output (0 … +10 V)
7Degas on, active high
8Supply sensor electronics +24 Volt
9Relay Setpoint B, n.o. contact
1)
10Gauge identification
11Relay Setpoint B, common contact
1)
12Signal common GND
13do not connect
14do not connect
15do not connect
1)
Type of setpoint function assigned to relays is programmable (→ 26).
tira40e1 (2005-04) BCG450SDv1.cp5
1.4 Side View of the
BCG450-SD
1.5 Indicators and Switches
PositionFunction
8Potentiometer for Setpoint A threshold
9Potentiometer for Setpoint B threshold
10Special Calibration service / do not use
1.5.1 Module Status LED
Device StateLED StateDescription
Power OffdarkNo power applied to device
Device Self-Testflashing
green/red
Device OperationalgreenDevice is operating normally.
Unrecoverable FaultredDevice has detected an unrecoverable fault
Recoverable Faultflashing red Device has detected a recoverable fault,
Device is in self-test
e.g. missing DeviceNet power supply
6tira40e1 (2005-04) BCG450SDv1.cp
1.5.2 Network Status LED
1.5.3 Node Address Switch
1.5.4 Data Rate Switch
1.5.5 Setpoint
The network status LED indicates the status of the DeviceNet communication link.
StateLED state To indicate
Not Powered/not onlinedarkDevice 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.
Online, not connected flashing
green
Device is online but has no connections
in the established state.
• The device has passed the
Dup_MAC_ID test, is online, but
has no established connections to
other nodes.
• The device is not allocated to a
master.
Link OK online, connected green The device is online and has connec-
tions in the established state.
• The device is allocated to a master.
Connection time out flashing
red
One or more I/O Connections are in the
timed out state.
Critical link failure red Failed communication device. The
device has detected an error that has
rendered it incapable of communicating
on 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 the
value stored in the device’s non-volatile RAM (NVRAM), the new MAC ID will be
saved 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 the
device MAC ID.
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, and
500 kBaud, where:
1 125 kBaud
2 250 kBaud
5 500 kBaud
All remaining switch positions specify software selection of the data rate.
The device has two setpoint relays 1) (Setpoint A and Setpoint B). The setpoints of
these relays are adjustable only by two potentiometers (marked SETPOINT A and
SETPOINT B).
The relay contacts are available at the 15-pin D-Sub connector.
1)
Type of setpoint function assigned to relays is programmable (→ 26).
tira40e1 (2005-04) BCG450SDv1.cp7
2Object Structure
2.1 Connection Object
2.1.1 Vendor-Specific Object
Extension on Instance 2
Poll Connection
Class Code 05h = 05
The connection class allocates and manages the internal resources associated
with 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
Please refer to the DeviceNet specification for further information.
For the selection of the active input assembly the following vendor specific attribute
can be used.
Vendor specific extension:
d
AttributeIDRequirement in
Implementation
100OptionalGet/Set NV Poll Produce
Access
Rule
NV/V Name DeviceNet
Assembly
Instance
This vendor-specific attribute facilitates the configuration of the data assembly, sent
by the BCG450-SD to the DeviceNet Master as Poll response. It offers the possibility to select a (predefined) data assembly via a configuration tool + EDS file
(→ [1]). Attribute 100 allows the user to configure the Poll I/O Data Assembly
via EDS even when the Poll Connection of the BCG450-SD is in the established
state. The Assembly Number is stored non volatile. Modifications of the Poll
Produce Assembly Instance will take effect only after a reset of the BCG450-SD.
Thus, definition of the BCG450-SD data assembly can be done in two ways:
1) Standard methode (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 BCG450-SD. 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.
Description of AttributeSemantics
Data Type
USINTContains the Instance num-
ber of the assembly used by
this connection to send data
1, 2, 4, 5, 8, 9, 10, 12, 13
8tira40e1 (2005-04) BCG450SDv1.cp
2.2 Identity Object
Class Code 01h = 01
d
2.2.1 Class Attributes
Attribute IDAccess RuleNameDeviceNet
1GetRevisionUINTRevision of this object.
2GetMax InstanceUINTMaximum instance number of
This object provides identification of and general information about the device.
Description of AttributeSemantics of Values
Data Type
The current value assigned to this
Note: All class definitions are
required to include this class
attribute.
an object currently created in
this class level of the device.
attribute is one (01). If updates that
require an increase in this value are
made, then the value of this attribute
increases by one.
The largest Instance number of a
created object at this class hierarchy
level.
2.2.2 Instance Attributes
Attribute IDAccess RuleNV/VNameDeviceNet Data Type Description of Attribute
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
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.
Exception Status Bit Map
Exception Detail Alarm and
Exception Detail Warning
BitFunction
0ALARM/device-common
(The alarm or warning is not specific to the device type or device type
manufacturer.)
1ALARM/device-specific
2ALARM/manufacturer-specific
3reserved, set to 0
4WARNING/device-common
5WARNING/device-specific
6WARNING/manufacturer-specific
7
1 Expanded Method
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 with
the device. Each attribute is a structure containing three members; these three
members, 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 indicates
that 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 is
formatted 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 the
condition 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 and
warnings 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".
Common Exception Detail
12tira40e1 (2005-04) BCG450SDv1.cp
This structure relates exception conditions (i.e. alarms or warnings) which are
common 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=2] which is the value of the structure element Size. For each byte in the
Detail field, all bits which are not identified are reserved for future standardization.
Two bytes Common Exception Detail are provided: Common Exception Detail [0]
and Common Exception Detail [1]. The specific exception associated with each of
the bitmaps is given in the table below. The SIZE for this revision is two (2).
Loading...
+ 28 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.