Network Configuration - ABB 2600T Series Operating Instructions Manual

The cyclic telegram can be formed by minimum 5 byte up to
15 bytes max. Structure of the input cyclic telegram from
2600T 266 PdP to Class 1 Master in Data_Exchange service.
In this table is reported the max.configuration when all the
three AI blocks output are transmitted to the Class 1 Master.
Different combinations are also possible according the GSD
module selections.
Index
Function
input Variables
Blocks
data
Process Value:
0, 1, 2, 3 Pressure, Level,
Flow, Volume
AI1_OUT
Status Byte for
4
Process Value
5, 6, 7, 8 Static Pressure
AI2_OUT
Status Byte for Static
9
Pressure
Auxiliary Value:
10, 11,
Sensor Temperature,
12, 13
AI3_OUT Pressure
Status Byte for
14
Auxiliary Value

11.2.1 Network configuration

When the 266 PdP transmitter has to be used in a profibus
project, the first operation is to import in the Host (Class 1
Master) the GSD file of the device. The manufacturer specific
GSD filename of the 2600T-266 PdP transmitter is AB013450.
GSD The GSD file can be downloaded from the ABB website
www.abb.com. When the GSD file has been imported in the
Host then the transmitter can be used in a network design. In
order to configure a Profibus Node for the 266 PdP: select the
266 PdP from the available GSD files list, assign a valid
Address (1....125) and then select from the GSD file the Module
with the required variables to be transmitted via cylcic telegram
for that specific Node Address.
Cyclic communication
The output of each AI block is 5 bytes. The Variable is 32 bit in
Floating Point format (4 bytes) plus a Status Byte (1 Byte).
Variable structure
The Floating Point format of each variable read by the Class 1
master is as follow:
Byte n
Bit 7 Bit 6 Bit 7 Bit 6
S 2 2 2 2 2 2 2 2
7 6 5 4 3 2 1
EXPONENT
Byte n+2
Bit 7
2 2 2 2 2 2 2
-8 -9 -10 -11 -12 -13 -14
MANTISSA
38 OI/266/PB-EN Rev. E | 2600T Series Pressure transmitters
access Data type
32 bits Floating
Read Point Format
(IEEE 754)
See Status Byte
Read
coding
32 bits Floating
Read Point Format
(IEEE 754)
See Status Byte
Read
coding
32 bits Floating
Read Point Format
(IEEE 754)
See Status Byte
Read
coding
Byte n+1
2 2 2 2 2 2 2
0 -1 -2 -3 -4 -5 -6 -7
MANTISSA
Byte n+3
Bit 7
2 2 2 2 2 2 2
-15 -16 -17 -18 -19 -20
MANTISSA
Example:
40 F0 00 00 (hex) = 0100 000 111 000 000 000 000 000 (binary)
Calculation:
Value = (-1) S * 2 (Exponent – 127) * (1 + Mantissa)
Value = (-1) 0 * 2 (129 – 127) * (1 + 2-1 + 2-2 + 2-3)
Value = 1 * 4 * (1 + 0.5 + 0.25 + 0.125) = 7.5
Status byte
The Status byte is the fifth byte of any out value and represents
the Quality of the variable. The 266 PdP supports both the
Classic Status and Condensed Status conditions as allowed by
the Profile 3.02. Depending by which of the two selections is
active, the list of the possible Status in output of the AI blocks
can be the following:
— Classic Status
Binary Code
0000 00xx
0000 11xx
0001 00xx
0001 1111
0100 0000
0100 0100
0100 1000
0100 1100
0101 00xx
0101 01xx
0110 00xx
1000 0000
1000 0100
1000 1010
1000 1110
1000 1001
1000 1101
1010 0100
2 2
-21 -22 -23
Decimal
Quality Sub-Status
Code
0-3 BAD non specific
12-15 BAD Device Failure
16-20 BAD Sensor Failure
31 BAD Out of Service
64 UNCERTAIN non specific
last usable value (LUV)
68 UNCERTAIN
– ( FSAFE_TYPE = 1)
substitute value
72 UNCERTAIN
– (FSAFE_TYPE = 0)
76 UNCERTAIN initial value (FSAFE_TYPE = 0)
80-83 UNCERTAIN sensor conversion not accurate
84-87 UNCERTAIN engineering unit range violation
96-99 UNCERTAIN simulated value
128 GOOD_NC ok
132 GOOD_NC Update Event
138 GOOD_NC Active Advisory Alarm high
142 GOOD_NC Active Critical Alarm high
137 GOOD_NC Active Advisory Alarm low
141 GOOD_NC Active Critical Alarm low
164 GOOD_NC Maintenance Required
11 Commissioning