INFICON HPG400-SP ATM to High-Vacuum Gauge (Profibus) - Manual (Page 13)

tira36e1-a (0310) BPG/HPG400 v1.cp
13
3 Block Model
Data to the BPG400-SP / HPG400-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 BPG400-SP / HPG400-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.
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 BPG400-SP / HPG400-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/HP)
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
Block types