INFICON BCG450-SP ATM User Manual
Communication Protocol
Profibus
DP/V1 Interface for Bayard-Alpert Pirani Capacitance Diaphragm Gauge
BCG450-SP
tira41e1 (2005-06) 1
About this Document
This document describes the functionality and programming of the Profibus interface of the BCG450-SP gauge.
For safety information on and technical data of the gauges, please refer
to the respective operating manuals (→ [1], [3]).
In information referring to the ionization vacuum measuring part of the gauge, the
short designation "BA" (Bayard-Alpert measuring principle) is used.
The designation "Pirani" is used in information referring to the Pirani vacuum
measuring part of the gauge.
Product Identification
Validity
In all communications with INFICON, please specify the information on the product
nameplate. For convenient reference copy that information into the space provided
below.
INFICON AG, LI-9496 Balzers
Model:
PN:
SN:
V W
This document applies to products with part numbers
BCG450-SP (with Profibus interface and switching functions)
353-554
353-556 (vacuum connection DN 40 CF-R)
The part number (PN) can be taken from the product nameplate.
(vacuum connection DN 25 ISO-KF)
Intended Use
Functional Principle
Trademarks
The BCG450-SP gauge allows vacuum measurement of non flammable gases and
gas mixtures (pressure ranges → [1], [3]).
The gauges can be operated with an INFICON controller or another instrument or
control device.
The function of the gauge is described in the operating manual (→ [1], [2], [3]).
The integrated Profibus interface allows operating the gauge in connection with
other suitable devices in a Profibus network according to the standard described in
[4], [5].
®
SEMI
Profibus This document contains Profibus-specific information described and
Semiconductor Equipment and Materials International, California
defined in the Profibus standard EN 50170 (→ [5]).
2 tira41e1 (2005-06) BCG450SPv1.cp
Contents
About this Document 2
Product Identification 2
Validity 2
Intended Use 2
Functional Principle 2
Trademarks 2
1 General Data 5
1.1 Data Rate 5
1.2 Device Address 5
1.3 Ident Number 5
1.4 Configuration Data 5
1.5 User Parameter Data 6
1.6 Types of Communication 6
2 Data Exchange Mode 7
2.1 Acyclic Data Transmission with Profibus DPV1 Functionality 7
2.2 Structure of the Cyclic Data Telegrams in Data Exchange Mode 8
2.2.1 Parameter Channel 9
2.2.1.1 PKE Parameter Signature Value 9
2.2.1.2 PWE Parameter (Process Value) 10
2.2.1.3 Error Code (Error Message) 10
2.3 Cyclic Message Telegrams 11
3 Block Model 12
3.1 Device Block 13
3.1.1 Information on the Individual Indices 14
3.1.1.1 Block Type ID 16 14
3.1.1.2 Device Type ID 17 14
3.1.1.3 Standard Revision Level ID 18 14
3.1.1.4 Device Manufacturer Identifier ID 19 14
3.1.1.5 Manufacturer Model Number ID 20 14
3.1.1.6 Software or Firmware Revision Level ID 21 14
3.1.1.7 Hardware Revision Level ID 22 14
3.1.1.8 Device Configuration ID 24 14
3.1.1.9 Device State ID 25 14
3.1.1.10 Exception Status ID 26 15
3.1.1.11 Exception Detail Alarm ID 27 16
3.1.1.12 Exception Detail Warning ID 28 18
3.1.1.13 Copy Common Exception Detail Alarm 0 ID 204 20
3.1.1.14 Copy Device Exception Detail Alarm 0 … 3 ID 205 20
3.1.1.15 Copy Device Exception Detail Alarm 4 … 5 ID 206 20
3.1.1.16 Copy Manufacturer Exception Detail Alarm 0 ID 207 21
3.1.1.17 Copy Common Exception Detail Warning 0 ID 208 21
3.1.1.18 Copy Device Exception Detail Warning 0 … 3 ID 209 21
3.1.1.19 Copy Device Exception Detail Warning 4 … 6 ID 210 21
3.1.1.20 Copy Manufacturer Exception Detail Warning 0 ID 211 21
3.1.2 Device Block, Device Behavior 21
3.1.2.1 Device Block State Command 22
3.2 Analog Input Block 23
3.2.1 One Of N Analog Input Function Block / SLOT 1 23
3.2.1.1 Block Type 23
3.2.1.2 Channel Instance Selector 23
3.2.1.3 PV Selector 23
3.2.2 Analog Sensor Input Function Block Instance 1 / SLOT 1 24
3.2.2.1 Process Value 24
3.2.2.2 Status 24
3.2.2.3 Data Type 24
3.2.2.4 Data Unit 25
3.2.2.5 Reading Valid 25
3.2.2.6 Full Scale 25
3.2.2.7 Safe State 26
3.2.2.8 Safe Value 26
3.2.2.9 Overrange 26
3.2.2.10 Underrange 26
3.2.3 Analog Sensor Input Function Block Instance 2 / SLOT 1 27
3.2.3.1 Process Value 27
3.2.3.2 Status 27
tira41e1 (2005-06) BCG450SPv1.cp 3
3.2.3.3 Data Type 27
3.2.3.4 Data Unit 28
3.2.3.5 Reading Valid 28
3.2.3.6 Full Scale 28
3.2.3.7 Safe State 28
3.2.3.8 Safe Value 29
3.2.3.9 Overrange 29
3.2.3.10 Underrange 29
3.2.4 Analog Sensor Input Function Block Instance 3 / SLOT 1 30
3.2.4.1 Process Value 30
3.2.4.2 Status 30
3.2.4.3 Data Type 30
3.2.4.4 Data Unit 31
3.2.4.5 Reading Valid 31
3.2.4.6 Full Scale 31
3.2.4.7 Safe State 32
3.2.4.8 Safe Value 32
3.2.4.9 Overrange 32
3.2.4.10 Underrange 32
3.2.5 Analog Sensor Input Function Block Instances 5 and 6 / SLOT 1 33
3.2.5.1 Process Value 33
3.2.5.2 Status 34
3.2.5.3 Data Type 34
3.2.5.4 Data Unit 34
3.2.5.5 Reading Valid 34
3.2.5.6 Setpoint Function 34
3.2.5.7 "Percentage of Atmosphere" 34
3.2.5.8 Atmosphere Reached 36
3.3 Transducer Block 36
3.3.1 One Of N Vacuum Gauge Transducer Block / SLOT 1 36
3.3.1.1 One Of N Status Extension 36
3.3.2 Heat Transfer Vacuum Gauge Transducer Block / SLOT 1 / Instance 1 36
3.3.2.1 Block Type 36
3.3.2.2 Status Extension 36
3.3.2.3 Sensor Alarm 36
3.3.2.4 Sensor Warning 37
3.3.3 Hot Cathode Ion Gauge Transducer Block / SLOT 1 / Instance 2 37
3.3.3.1 Block Type 37
3.3.3.2 Status Extension 37
3.3.3.3 Sensor Alarm 37
3.3.3.4 Sensor Warning 38
3.3.3.5 Emission Status 38
3.3.3.6 Emission Current 38
3.3.3.7 Degas Status 38
3.3.3.8 Emission User Mode State 38
3.3.3.9 Hot Cathode Block State Command 39
3.3.4 Diaphragm Gauge Transducer Block / SLOT 1 / Instance 3 40
3.3.4.1 Block Type 40
3.3.4.2 Status Extension 40
3.3.4.3 Sensor Alarm 40
3.3.4.4 Sensor Warning 40
3.3.4 Atmosphere Sensor Transducer Block
(Piezo Sensor) / SLOT 1 / Instance 4 41
3.3.4.1 Block Type 41
3.3.4.2 Atmosphere Sensor Block State Command 41
Appendix A: Definitions 42
Appendix B: Block Type 45
Appendix C: Electrical Connections 46
Appendix D: Literature 48
For cross-references to other documents, the symbol (→ [XY]) is used.
4 tira41e1 (2005-06) BCG450SPv1.cp
1 General Data
1.1 Data Rate
1.2 Device Address
The gauge supports all data rates defined in the EN 50170 standard (→ [5]) up
to 12 Mbaud. Automatic data rate setting is supported. Alternatively, a fixed data
rate can be selected.
The device address ( node address) must be set via two rotary switches when the
gauge is installed.
For unambiguous identification of the gauge in a Profibus environment, a node
address is required. The node address setting is made on the gauge.
The node address (0 … 125
(00 … 7D
) (default value 5C
hex
) is set in hexadecimal form
dec
) via the "ADDRESS" switches.
hex
The "MSD" switch is used for setting the high-order address
nibble and the "LSD" switch for defining the low-order address
nibble.
The node address is polled by the firmware when the gauge is switched on. If the
setting deviates from the stored value, the new value is taken over into the
NVRAM. If a value >7D
hex
(>125
) is entered, the node address setting currently
dec
stored in the device remains valid. However, the address can be set via the
Profibus master with the "Set Slave Address" service. This address setting will be
stored in the EEPROM of the gauge.
1.3 Ident Number
1.4 Configuration Data
The ident number assigned to the gauge by the PNO (→ [4]) is:
Gauge Ident number (hexadecimal)
BCG450-SP 08E6
Depending on the standard telegrams used (→ section "Cyclic Message Telegrams"), the following configuration data have to be transmitted to the gauge during
the configuration phase:
Standard telegram
Master ⇒ Slave
Standard telegram
Slave ⇒ Master
Configuration data
- 4 0x44, 0x84, 0x05, 0x05, 0x05,
0x03
- 5 0x44, 0x86, 0x05, 0x05, 0x05,
0x08
1 4 0xC6, 0x81, 0x84, 0x05, 0x05,
0x05, 0x05, 0x05, 0x03
1 5 0xC6, 0x81, 0x86, 0x05, 0x05,
0x05, 0x05, 0x05, 0x08
3 6 0xC6, 0x87, 0x8C, 0x0A, 0x0A,
0x05, 0x05, 0x05, 0x03
3 7 0xC6, 0x87, 0x8E, 0x0A, 0x0A,
0x05, 0x05, 0x05, 0x08
2 6 0xC8, 0x89, 0x8C, 0x0A, 0x05,
0x05, 0x0A, 0x05, 0x05, 0x05,
0x03
2 7 0xC8, 0x89, 0x8E, 0x0A, 0x05,
0x05, 0x0A, 0x05, 0x05, 0x05,
0x08
tira41e1 (2005-06) BCG450SPv1.cp 5
1.5 User Parameter Data
Depending on the pressure unit setting ( data unit), the following configuration
string has to be transmitted to the gauge (parameter data in hexadecimal format):
1.6 Types of
Communication
Pressure unit User parameter data string
COUNTS
Torr 00 00 00 05 15
Micron 00 00 00 05 16
mbar 00 00 00 05 1C
Pascal 00 00 00 05 1D
1)
If COUNTS is selected as pressure unit, a value is output, which can be converted into a corresponding pressure value by means of a formula (→ section
"Analog Sensor Input Function Block" for more information).
BCG450-SP works according to the Profibus DPV1 specification and can be
addressed in cyclic or acyclic data traffic (→ [4]).
Acyclic data traffic should be used to make device or process specific settings such
as definition of the Safe Values, Safe States etc. or for reading or writing of rarely
used attributes.
Cyclic data traffic is used for continuous exchange of the required process parameter values, i.e. pressure value and status indications. A number of standard
telegrams are available for cyclic data traffic. They can be selected according to
requirements (→ section "Cyclic Message Telegrams").
1)
00 00 00 03 E9
6 tira41e1 (2005-06) BCG450SPv1.cp
2 Data Exchange Mode
2.1 Acyclic Data Transmission with Profibus
DPV1 Functionality
Block, slot and
index assignment
The reading and writing operations defined in Profibus are based on a slot index
address scheme. In BCG450-SP, all device functions are organized in the following
blocks:
• A device block describing all organizational parameters of the gauge (serial
number, manufacturer, software version, …)
• An Analog Sensor Function Block describing the function of the pressure presentation
• An Analog Sensor Transducer Block describing the physical interface between
the gauge and the process (emission current, ion current, …).
The block model is described in detail in section "Block Model".
Each block is assigned to a separate slot. The exact assignment
Block ⇒ Slot ⇒ Index is described in section "Block Model". The Device Block is
assigned to Slot 0, the transducer and functional blocks to Slot 1.
Index
254
Device
Block
Block_1 Block_2 Block_3
0
There are 254 indices per slot. The indices can have a width of 255 bytes. All values that can be accessed via Profibus have to be mirrored to one of these slots/
indices.
The parameters are generally numbered in ascending order, starting with index 16.
Services such as "Degas On" or "Full scale" are numbered in descending order,
starting with index 15.
0123
tira41e1 (2005-06) BCG450SPv1.cp 7
Assignment of the block
elements to the slot indices
Index
2.2 Structure of the Cyclic
Data Telegrams in
Data Exchange Mode
Parameter_n
Block_x
Parameter_2
Parameter_1
16
0
In Data Exchange mode, the DP master class 1 cyclically transmits data from and
to all slaves that are connected to the bus.
In this document, data transmitted from the slave to the master are called "input
data" and data transmitted from the master to the slave are called "output data".
The input and output data of the BCG450-SP has two logic parts:
1) the parameter channel
2) the process data channel
There is a number of standard telegrams, consisting of:
a) the parameter channel only
b) the process data channel only
c) both, the parameter and process data channel
The parameter channels allows masters without Profibus DPV1 to access device
specific parameters that are not part of the normal cyclic data telegram. For masters with Profibus DPV1, no parameter channel is required.
Parameter_0
Operation_1
Operation_2
Operation_n
optional
Block_Type_Name
Attributes
Public
Operations Public
optional
Private
Input data
Output data
The input data (transmitted by the BCG450-SP) consists of the 8 bytes of the parameter channel (if there is a parameter channel in the standard telegram) and of
5 … 7 bytes of process data depending on the selected standard telegram.
Byte Byte
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Parameter channel Process data
PKE IND res. PWE
Where: PKE = Parameter Signature Value
IND = Sub Index
res. = reserved
PWE = Process Value
The output data (transmitted by the master) consist of 8 bytes of the parameter
channel or, if there is no parameter channel in the standard telegram, of 0 bytes.
Byte
1 2 3 4 5 6 7 8
Parameter channel
PKE IND res. PWE
Reading or writing command and definition of the slot
Index No. of the index to be
read (→ "Block Model")
Value to be read or written
8 tira41e1 (2005-06) BCG450SPv1.cp
2.2.1 Parameter Channel
The structure of the parameter channel is described in the table below.
The parameter channel (called PKW Interface hereinafter) consists of 8 bytes.
Octets
1 2 3 4 5 6 7 8
PKE IND res. PWE
The PKW Interface allows reading and writing of slave parameters with a maximum
data length of 4 bytes. Strings cannot be read.
The slave generates exactly one response per instruction transmitted by the master. The instruction and response cannot be blocked. This means that exactly one
instruction per output telegram can be transmitted to the slave and that exactly one
response per input telegram can be transmitted to the master. 4 bytes of actual
data can thus be transmitted at a time.
2.2.1.1 PKE Parameter
Signature Value
Instruction signature
The instruction and response are represented in the first two bytes (PKE) of the
parameter channel:
Bit position
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
AK res. Slot
Where: Bits Meaning
15 … 12
AK Instruction/response signature
11 … 8 Reserved
7 … 0 Define the slot from which data are read or onto which a
value is to be written
In Master ⇒ Slave communication, the AK field contains the instruction signature of
the master.
In Slave ⇒ Master communication, the AK field contains the instruction signature of
the slave.
AK Function
Master ⇒ Slave
(Instruction signature)
AK
normal
Function
Slave ⇒ Master
(Response signature)
AK
error
0 No instruction 0 No response
1 Read parameter value 1
Transmit parameter value
7
1)
(word)
2
Transmit parameter value
(double word)
11
Transmit parameter value
(byte)
2 Write parameter value
1 Transmit parameter value
(data type: word)
3 Write parameter value
2 Transmit parameter value
(data type: double word)
10 Write parameter value
11 Transmit parameter value
(data type: byte)
1)
Instruction cannot be executed (error code)
(word)
(double word)
(byte)
7
7
7
1)
1)
1)
On the left of the table, the instruction signatures of the master are listed according
to their function. On the right of the table, the corresponding normal responses (AK
Normal) and error codes (AK Error) transmitted by the slave are listed.
tira41e1 (2005-06) BCG450SPv1.cp 9
Instruction – response
sequence
1) The master transmits an instruction to the slave and repeats that instruction
until it receives a response from the slave.
2) The slave keeps transmitting the response to the instruction until the master
transmits a new instruction.
3) The master marks the end of the first instruction cycle by setting AK to zero.
Only after that, a new instruction/response cycle may be started.
2.2.1.2 PWE Parameter
(Process Value)
2.2.1.3 Error Code
(Error Message)
The PWE represents the data element to be transmitted.
If a byte is to be transmitted, that byte has to be in position 8 of the parameter
channel.
Integers are transmitted with bytes 7 and 8. Double integer and float values are
transmitted with bytes 5 … 8.
In the event of a transmission error (AK response signature = 7), the slave transmits an error code in byte positions 7 and 8 (data type: INT16).
Error code Meaning
0 Undefined slot
1 Parameter not changeable
2 Lower or upper value range limit overflow
3 Index error
5 Data type error
17 Instruction not allowed in this state
18 Other errors
201 Already in requested state
202 Object state conflict
The following diagram shows an example of a data request from a master to a
BCG450-SP via parameter channel.
Store
Data
DP-Master
Parameter
Request
(Client)
AK(IS) = 0
AK(RS) = 0
AK(IS) = 0
AK(RS) = 0
AK (IS) = 1
AK(RS) = 0
AK (IS) = 1
AK(RS) = 0
AK (IS) = 1
AK(RS) = 1
AK (IS) = 0
AK(RS) = 0
AK (IS) = 0
AK(RS) = 0
BCG450-SP
Parameter
Request
(Server)
Fetch
Data
10 tira41e1 (2005-06) BCG450SPv1.cp
2.3 Cyclic Message
Telegrams
The message telegrams listed below are implemented in the gauge. They can be
selected according to requirements. When selecting a message telegram, ascertain
what output format of the measured value (integer/float) is required and whether a
parameter channel is needed or not. The gauge can also be operated in such a
way that the master does not transmit any output data to the slave.
Standard
telegram
1
2
3
4
5
6
7
Master
⇔
Slave
M ⇒ S
M ⇒ S
M ⇒ S
S ⇒ M
S ⇒ M
S ⇒ M
S ⇒ M
Byte Meaning
1 Transition Command
2 Transition Command Value for Hot Ion Gauges
1 … 8 Parameter Channel
9 Transition Command
10 Transition Command Value for Hot Ion Gauges
1 - 8 Parameter Channel
1 Exception status
2 One Of N status extension
3 One Of N PV selector
4 … 5 Process value UINT16
1 Exception status
2 One Of N status extension
3 One Of N PV selector
4 … 7 Process value float
1 … 8 Parameter channel
9 Exception status
10 One Of N status extension
11 One Of N PV selector
12 … 13 Process value UINT16
1 … 8 Parameter channel
9 Exception status
10 One Of N status extension
11 One Of N PV selector
12 … 15 Process value float
Configuration data
In the following table, the possible reasonable combinations are listed with the
corresponding configuration data.
Standard telegram
Master ⇒ Slave
- 4 0x44, 0x84, 0x05, 0x05, 0x05, 0x03
- 5 0x44, 0x86, 0x05, 0x05, 0x05, 0x08
1 4 0xC6, 0x81, 0x84, 0x05, 0x05, 0x05,
1 5 0xC6, 0x81, 0x86, 0x05, 0x05, 0x05,
3 6 0xC6, 0x87, 0x8c, 0x0A, 0x0A, 0x05,
3 7 0xC6, 0x87, 0x8E, 0x0A, 0x0A,
2 6 0xC8, 0x89, 0x8c, 0x0A, 0x05, 0x05,
2 7 0xC8, 0x89, 0x8E, 0x0A, 0x05, 0x05,
Standard
telegram
Slave ⇒ Master
Configuration data
0x05, 0x05, 0x03
0x05, 0x05, 0x08
0x05, 0x05, 0x03
0x05, 0x05, 0x05, 0x08
0x0A, 0x05, 0x05, 0x05, 0x03
0x0A, 0x05, 0x05, 0x05, 0x08
tira41e1 (2005-06) BCG450SPv1.cp 11
3 Block Model
Data to the BCG450-SP can be transmitted by means of a number of communication protocols and corresponding masters. Profibus defines a master class 1 as
normal control unit of the slave (typically a PLC) and a master class 2 as configuration and service unit. The following communication protocols are defined according
to the Profibus DPV1 standard.
MS0 Cyclic data traffic between master class 1 and slave
MS1 Acyclic data traffic between master class 1 and slave
MS2 Acyclic data traffic between master class 2 and slave
In the BCG450-SP, all functions that are made available by the gauge via Profibus
are organized in blocks. Access to the individual parameters of the blocks is possible via acyclic services or, for byte, integer and float values, also in cyclic data
traffic via the parameter channel.
Block types
The following block types are defined in the gauge.
Device Block The Device Block contains all data that are required for de-
scribing the device and handling its state (status of Device
State Machine).
Transducer Block The physical, process specific functions or interfaces between
the BCG450-SP and the process such as current and voltage
values are represented in transducer blocks.
The following transducer blocks are implemented:
• One of N Vacuum Gauge Transducer Block
• Heat Transfer Vacuum Gauge Transducer Block (Pirani)
• Hot Cathode Ion Gauge Transducer Block (BA)
• Diaphragm Gauge Transducer Block (CDG)
Function Block Application specific values such as pressure values that result
from or can be calculated from the values of the transducer
block are represented in the function blocks.
• One of N Analog Input Function Block
• Analog Input Function Block, Instance 1, Instance 2,
Instance 3, Instance 4, Instance 5, Instance 6.
12 tira41e1 (2005-06) BCG450SPv1.cp
3.1 Device Block
The following table lists the services and parameters integrated in the Device Block
(→ Appendix A for abbreviations).
ID Name Structure Data type Bytes Access Value Store
15 Device Block State Simple Unsigned8 1 1_R/W
2_R/W
16 Block Type Simple Octet string 4 1/2_R 1 N
17 Device Type Simple Visible string 8 1/2_R CG N
18 Standard Revision Level Simple Visible string 9 1/2_R E54-0997 N
19 Device Manufacturer
Simple Visible string 20 1/2_R INFICON AG N
Identifier
20 Manufacturer
Model Number
21 Software or Firmware
Simple Visible string 20 1/2_R e.g.
353-554
Simple Visible string 8 1/2_R e.g. 1.01 N
Revision Level
22 Hardware Revision Level Simple Visible string 8 1/2_R e.g. 1.0 N
23 Serial Number Simple Visible string 30 1/2_R e.g. 100 N
24 Device Configuration Simple Visible string 50 1/2_R e.g.
BCG450-SP
25 Device State Simple Unsigned8 1 1/2_R V
26 Exception Status Simple Unsigned8 1 0_XI
V
1/2_R
27 Exception Detail Alarm Record
28 Exception Detail
Record
→ below
→ below
- 1/2_R V
- 1/2_R V
Warning
204 Common Exception
Simple UINT8 1 1/2_R V
Detail Alarm 0
205 Device Exception Detail
Alarm 0 … 3
206 Device Exception Detail
Alarm 4 … 5
207 Manufacturer Exception
Struct Array of
4 1/2_R V
4 bytes
Struct Array of
2 1/2_R V
2 bytes
Simple UINT8 1 1/2 _R V
Detail Alarm 0
208 Common Exception
Simple UINT8 1 1/2 _R V
Detail Warning 0
209 Device Exception Detail
Warning 0 … 3
210 Device Exception Detail
Warning 4 … 6
211 Manufacturer Exception
Struct Array of
4 1/2 _R V
4 bytes
Struct Array of 3
3 1/2_R V
bytes
Simple UINT8 1 1/2_R V
Detail Warning 0
N
N
tira41e1 (2005-06) BCG450SPv1.cp 13
3.1.1 Information on the
Individual Indices
3.1.1.1 Block Type ID 16
3.1.1.2 Device Type ID 17
3.1.1.3 Standard Revision Level
ID 18
3.1.1.4 Device Manufacturer
Identifier ID 19
3.1.1.5 Manufacturer Model
Number ID 20
3.1.1.6 Software or Firmware
Revision Level ID 21
3.1.1.7 Hardware Revision Level
ID 22
3.1.1.8 Device Configuration ID 24
3.1.1.9 Device State ID 25
The Block Type Parameter contains an ID which describes the block type. The
block type ID of the Device Block 1. The other defined block types are listed in
Appendix B.
The Device Type identifies the device type which is connected to the field bus via
Profibus.
The Device Type of the BCG450-SP gauge is "CG", the abbreviation of
"Combination Gauge".
This parameter describes the version of the "Sensor/Actuator Network Specific
Device Model" published by the SEMI
®
(Semiconductor Equipment and Materials
International, California), according to which the profile of this device has been
developed.
The fixed setting of this parameter is "E54-0997".
This parameter describes the manufacturer of the device, "INFICON AG".
This parameter represents the part number of the gauge (→ section "Validity").
BCG450-SP is available with two different vacuum connection types each, for ex-
ample:
Gauge Vacuum connection Part number
BCG450-SP 25 KF 353-554
This parameter indicates the software version of the Profibus option in the following
format: xxx_y.yy (where xxx is the version of the BCG450 firmware and y.yy is the
version of the profibus board).
This parameter indicates the hardware version of the gauge in the format "1.0".
This parameter indicates the device name.
This parameter indicates the status of the gauge. Due to the structure of the Device
State Machine, the following statuses are possible:
Parameter value Status
0 Undefined
1 Self testing
2 Idle
3 Self test exception
4 Executing
5 Abort
6 Critical fault
The device statuses are described in detail in section "Device Block, Device
Behavior".
14 tira41e1 (2005-06) BCG450SPv1.cp
3.1.1.10 Exception Status ID 26
The Exception Status describes the alarm and warning states of the gauge in an
"Expanded error output format".
A difference is made between warnings and errors.
Alarms and errors are divided into three groups (→ sections "Exception Detail
Alarm" and "Exception Detail Warning" for details):
• ALARM / Warning Device Common
For errors that occur independently of
the type of device used, e.g. supply
error, RAM, ROM, or EEPROM error.
• ALARM / Warning Device Specific
For device specific errors, e.g. filament
rupture (Pirani), or cathode rupture
(BA).
• ALARM / Warning Manufacturer
Specific
For errors defined by the manufacturer
that are not mentioned in the standard.
In each of the above groups, there are several error or warning conditions. The individual fields are presented in the "Exception Detail Alarm" and "Exception Detail
Warning". If an error message occurs in "Exception Detail Alarm" or "Exception
Detail Warning”, the corresponding bit is set in the Exception Status. Therefore, if
bits 0 … 6 of the Exception Status are on "0" there is no warning message pending.
If a bit is set, the actual error can be read in the corresponding group.
The Exception Status is output in cyclic data and informs on the current error status
using only one byte. If an error occurs, the current error status can be read via
acyclic services or in cyclic data exchange via the parameter channel. This ensures
that while the current error status is always available in the cyclic data, no unnecessary data overhead is transmitted.
Bit Function Meaning
0 ALARM, device common The bit is set if an error of the Alarm
Device Common group is detected.
1 ALARM, device specific The bit is set if an error of the Alarm
Device Specific group is detected.
2 ALARM, manufacturer specific The bit is set if an error of the Alarm
Manufacturer Specific group is detected.
3
- -
4 WARNING, device common The bit is set if an error of the Warning
Device Common group is detected.
5 WARNING, device specific The bit is set if an error of the Warning
Device Specific group is detected.
6 WARNING, manufacturer
specific
The bit is set if an error of the Warning
Manufacturer Common group is detected.
7 Expanded Format Is constantly on "1" and marks the use of
the expanded error output format.
tira41e1 (2005-06) BCG450SPv1.cp 15
3.1.1.11 Exception Detail Alarm
ID 27
If, in the Exception Status, one of the bits 0 … 2 is set, the current error can be
read in the "Exception Detail Alarm" parameter. The "Exception Detail Alarm" parameter consists of a total of 12 bytes that inform on the error status of the gauge.
Due to the use of the expanded error output format, these bytes have the following
structure:
ByteNo Name Description Value
Common Exception
Detail Alarm
0
Common Exception
Detail Size
Indicates the number of subsequent bytes that contain the
Common Exception Detail Alarm.
1 Common Exception
Detail 0
Contains current error messages
from the Common Exception
Depending on
error status
Detail Alarm group.
2 Common Exception
Detail 1
Contains current error messages
from the Common Exception
Detail Alarm group.
Depending on
error status
3
Device Exception
Detail Size
Indicates the number of subsequent bytes that contain the
Device Exception Detail Alarm.
4 Device Exception
Detail 0
(CDG error data)
This error information from the
Common Exception Detail Alarm
group refers to Capacitance
Depending on
error status
Diaphragm gauge.
5 Device Exception
Detail 1
(CDG error data)
This error information from the
Common Exception Detail Alarm
group refers to Capacitance
Depending on
error status
Diaphragm gauge.
6 Device Exception
Detail 2
(Pirani error data)
7 Device Exception
Detail 3
(Pirani error data)
8 Device Exception
Detail 4
(BA error data)
9 Device Exception
Detail 5
(BA error data)
10
Manufacturer
Exception Detail
Size
11 Manufacturer
Exception Detail 0
This error information from the
Common Exception Detail Alarm
group refers to Pirani.
This error information from the
Common Exception Detail Alarm
group refers to Pirani.
This error information from the
Common Exception Detail Alarm
group refers to BA.
This error information from the
Common Exception Detail Alarm
group refers to BA.
Indicates the number of subsequent bytes that contain the
Device Exception Detail Alarm.
Contains current error messages
from the Manufacturer Exception
Depending on
error status
Depending on
error status
Depending on
error status
Depending on
error status
Depending on
error status
Detail Alarm group.
Bit Common Exception Detail 0 Bit Common Exception Detail 1
0 0 0 0
1 0 1 0
2 EPROM exception 2 0
3 EPROM exception 3 0
4 RAM exception 4 0
5 0 5 0
6 0 6 0
7 0 7 0
2
7
1
16 tira41e1 (2005-06) BCG450SPv1.cp
Loading...