Gantner E Series Use and care manual

e.bloxx Communication Guide
Vers.-No. 12

e.bloxx Communication
HB_EBLOXX_COM_E_V12.doc 1
Gantner Instruments Test & Measurement GmbH


 Copyright 2003 by GANTNER INSTRUMENTS TEST & MEASUREMENT GMBH, Schruns (Austria).
Copyrights: Operating instructions, manuals and software are protected by copyright ©. All rights are reserved.
Copying, duplication, translation, installation in any electronic medium or machine-readable form in whole or in part is
prohibited. The sole exception is represented by creation of a back-up copy of software for own use as a safeguard, so
far as this is technically possible and recommended by us. Any infringement will render the party committing such
infringement liable to compensation payment.
Liability: Any claims against the manufacturer based on the hardware or software products described in this manual
shall depend exclusively on the conditions of the guarantee. Any further-reaching claims are excluded, and in particular
the manufacturer accepts no liability for the completeness or accuracy of the contents of this manual. The right is
reserved to make alterations, and alterations may be made at any time without prior notice being given.
Trade marks: Attention is drawn at this point to markings and registered trade marks used in this manual, in particular
to those of Microsoft Corporation, International Business Machines Corporation and Intel Corporation.
Important: before commencing installation, commissioning, putting into service and before any
maintenance work is carried out, it is essential that the relevant warning and safety instructions in this
manual are read!
!

e.bloxx Communication
2 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH

e.bloxx Communication
HB_EBLOXX_COM_E_V12.doc 3
Gantner Instruments Test & Measurement GmbH
General warning and safety instructions:
Dear customer,
We congratulate you on having selected a product (device resp. software) of Gantner Instruments Test & Measurement
GmbH. So that our product functions in your installation with safety and to your complete satisfaction, we take this
opportunity to familiarize you with the following ground rules:
1. Installation, commissioning, operation and maintenance of the product purchased must be carried out in accordance
with instructions, i.e. in accordance with the technical conditions of operation, as described in the corresponding
product documentation.
2. Before installation, commissioning, operation or maintenance it is therefore essential that you read the
corresponding chapter of this manual and observe its instructions.
3. If there are still some points on which you are not entirely clear, please do not take a chance, but ask the customer
adviser responsible for you, or ring the Gantner Instruments Test & Measurement GmbH hot line.
4. Where not otherwise specifically laid down, appropriate installation, commissioning, operation and maintenance of
the product is the customer’s responsibility.
5. Directly on receipt of the goods, inspect both the packaging and the device resp. data carrier itself for any signs of
damage. Also check that the delivery is complete (-> accessories, documentation, auxiliary devices, etc.).
6. If the packaging has been damaged in transport or should you suspect that the product has been damaged or that it
may have a fault, the product must not be put into service. In this case, contact your customer advisor. He will make
every effort to resolve the problem as quickly as possible.
7. Installation, commissioning and servicing of our product must only be carried out by suitably trained personnel. In
particular, correspondingly qualified specialists may only make electrical connections. Here, the appropriate
installation provisions in accordance with the relative national Electrical Engineers construction regulations (e.g.
ÖVE, [Austrian] VDE, [German]...) must be observed.
8. Where not otherwise stated, installation and maintenance work on our appliances is exclusively to be carried out
when disconnected from the power supply. This applies in particular to appliances which are normally supplied by
low-tension current.
9. It is prohibited to make alterations to the appliances or to remove protective shields and covers.
10. Do not attempt yourself to repair an appliance after a defect, failure or damage, or to put it back into operation again.
In such cases, it is essential you contact either your customer adviser or the Gantner Instruments Test &
Measurement GmbH hot line. We will make every effort to resolve the problem as quickly as possible.
11. Gantner Instruments Test & Measurement GmbH accepts no responsibility for any injuries or damage caused as a
result of improper use of the product.
!

e.bloxx Communication
4 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
12. Although every care is taken and we are continuously aiming for improvement, we cannot exclude completely the
possibility of errors appearing in our documentation. Gantner Instruments Test & Measurement GmbH therefore
accepts no responsibility for the completeness or the accuracy of this manual. The right is reserved to make
alterations, and we may carry out alterations at any time without giving prior notice.
13. Should you discover any fault with the product or in its accompanying documentation, or have any suggestions for
improvement, you may confidently approach either your customer adviser or Gantner Instruments Test &
Measurement GmbH directly.
14. However, even if you just want to tell us that everything has functioned perfectly, we still look forward to hearing
from you.
We wish you a successful application of our product. We will be pleased to welcome you as a customer again soon.
Contact address / manufacturer:
Gantner Instruments Test & Measurement GmbH
Montafonerstrasse 8
A - 6780 Schruns/Austria
Tel.: [phone] - 410
Fax: [phone] - 419
E-Mail: [email protected]
Web: www.gantner-instruments.com
Gantner Instruments Test & Measurement GmbH
Industriestraße 12
D-64297 Darmstadt
Tel.: [phone] - 0
Fax: [phone] - 26
E-Mail: [email protected]
Web: www.gantner-instruments.com

e.bloxx Communication
TABLE OF CONTENTS
HB_EBLOXX_COM_E_V12.doc 5
Gantner Instruments Test & Measurement GmbH
TABLE OF CONTENTS
1. ABOUT THIS MANUAL......................................................................................................................................................6
2. COMMUNICATION .............................................................................................................................................................6
2.1. Bus Interface .......................................................................................................................................................................6
2.2. Bus Protocol ........................................................................................................................................................................6
2.3. Character Formats ..............................................................................................................................................................6
2.4. Output Format .....................................................................................................................................................................7
3. ASCII PROTOCOL .............................................................................................................................................................9
3.1. Transmission Sequence......................................................................................................................................................9
3.2. Telegram Format...............................................................................................................................................................10
3.3. Instruction Set ...................................................................................................................................................................12
3.4. Instruction Parameters ......................................................................................................................................................13
4. PROFIBUS PROTOCOL ..................................................................................................................................................15
4.1. Transmission Sequence....................................................................................................................................................15
4.2. Diagnostic Data .................................................................................................................................................................16
4.3. Launching PROFIBUS-DP Communication with a Hilscher

Master ...............................................................................18
4.4. PROFIBUS-DP Configuration for a Siemens

S7-300 .....................................................................................................23
5. MODBUS-PROTOCOL.....................................................................................................................................................32
5.1. Transmission Sequence....................................................................................................................................................32
5.2. Telegram Format...............................................................................................................................................................33
5.3. Instruction Set ...................................................................................................................................................................33
5.4. Register Contents..............................................................................................................................................................39
6. LOCAL-BUS PROTOCOL................................................................................................................................................43
6.1. General..............................................................................................................................................................................43
6.2. Character Format ..............................................................................................................................................................43
6.3. Transmission Order...........................................................................................................................................................43
6.4. Primary Build-Up Of The Frame........................................................................................................................................43
6.5. Data Format Coding..........................................................................................................................................................44
6.6. Baud Rate .........................................................................................................................................................................44
6.7. Communication Procedure................................................................................................................................................45
6.8. Command Table................................................................................................................................................................45

e.bloxx Communication
COMMUNICATION
6 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
1. ABOUT THIS MANUAL
This manual describes the communication of the modules of the series e.bloxx. It contains detailed information like
telegram format, instruction set and parameters of the communication protocols ASCII, PROFIBUS-DP, MODBUS and
LOCAL-BUS.
A chapter describes the setup of a Hilscher
®
Master and a Siemens
®
S7-300 PLC for communication via PROFIBUS-
DP.
2. COMMUNICATION
2.1. Bus Interface
The bus interface of the series e.bloxx is a RS 485 interface according to the specifications of the EIA-RS485 USA
standard.
2.2. Bus Protocol
With the series e.bloxx all protocols are available within one download file. The module itself recognizes the type of
protocol for communication depending on the request from the host. Therefore the protocol has not to be selected
manually.
- ASCII protocol
- PROFIBUS-DP protocol according to DIN 19245, part 1
- MODBUS-RTU protocol acc. to Reference Guide PI-MBUS-300 Rev. D
- LOCAL-BUS protocol
2.3. Character Formats
The e.bloxx supports the following character format:
Format Start
Bit
Data
Bit
Parity
Bit
Stop
Bit
Char.
Length
8E1 1 8 E 1 11
Table 2.1 Supported character transfer format
The character format 8E1 with even parity (E=even) corresponds to the PROFIBUS-definitions according to DIN 19245,
part 1, and is supported by the sensor modules in the PROFIBUS protocol as well as in the ASCII, MODBUS and
LOCAL-BUS protocol. This character format is predefined with the e.bloxx modules and cannot be changed.

e.bloxx Communication
COMMUNICATION
HB_EBLOXX_COM_E_V12.doc 7
Gantner Instruments Test & Measurement GmbH
2.4. Output Format
The user can preset the format in which data shall be output via the bus with the Configuration Software ICP100. The
modules adjust the data format accordingly and makes sure that data are available in the selected unit.
For the transmission in the ASCII and PROFIBUS format the format settings listed in table 2.2 and 2.3 can be chosen.
At the transmission in the MODBUS format the output format (integer or real) will automatically be confirmed (table 2.4).
The coding of a real value in the MODBUS and PROFIBUS format is as follows:
Coding of the real value: x = s ee...ee mmm.....mmm
Value: (-1)
s
· 2
e-127
· 1,m # : <1> <- 8 -> <----- 23 ----->
Format Settings Range of Values
Unit dependent on sensor
Field Length 1 . . . . . . . . . . . . . . . . . . 8
Decimals 0 . . . field length-1 (max 6)
Table 2.2 Format settings for transmission in the ASCII-format
Format Settings Length Range of Values
Bool 1 byte (dec 0: FALSE) and (dec 255: TRUE)
Integer 2 byte (dec - 32768) ≤ i ≤ (dec +32767)
Real 4 byte (dec - 2
129
)
≤ x ≤ (dec + 2
129
)
SET 8 1 byte (dec 0) ≤ i ≤ (dec 255 )
Table 2.3 Format settings for transmission in the PROFIBUS-format
Format Settings Length Range of Values
Integer 2 byte (dec - 32768) ≤ i ≤ (dec +32767)
Real 4 byte (dec - 2
129
)
≤ x ≤ (dec + 2
129
)
Table 2.4 Format settings for transmission in the MODBUS-format
Example: The value 50.3094 cm shall be displayed.

e.bloxx Communication
COMMUNICATION
8 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
Transmission in the ASCII-format:
Decimals Field Length 6 Field Length 7 Field Length 8
0 _ _ _ _ 5 0 _ _ _ _ _ 5 0 _ _ _ _ _ _ 5 0
1 _ _ 5 0 . 3 _ _ _ 5 0 . 3 _ _ _ _ 5 0 . 3
2 _ 5 0 . 3 1 _ _ 5 0 . 3 1 _ _ _ 5 0 . 3 1
3 5 0 . 3 0 9 _ 5 0 . 3 0 9 _ _ 5 0 . 3 0 9
4 E . 3 0 9 4 5 0 . 3 0 9 4 _ 5 0 . 3 0 9 4
5 - E . 3 0 9 4 0 5 0 . 3 0 9 4 0
6 - - E . 3 0 9 4 0 0
Table 2.5 Output formats for transmission in the ASCII-format ("_":blank).
Transmission in PROFIBUS- and MODBUS-format:
Decimals Integer Real
0 00 32 (50) 42 49 3C D3 (50.3094)
1 01 F7 (503) 42 49 3C D3 (50.3094)
2 13 A6 (5030) 42 49 3C D3 (50.3094)
3 xx xx (50309) 42 49 3C D3 (50.3094)
4 xx xx (503094) 42 49 3C D3 (50.3094)
5 xx xx (5030940) 42 49 3C D3 (50.3094)
6 xx xx (50309400) 42 49 3C D3 (50.3094)
Table 2.6 Output formats for transmission in the PROFIBUS- and the MODBUS-format
(the decimal notation is given in parentheses).
The following points have to be kept in mind:
- Decimals are not cut off, but are rounded off.
- In case of overflow with a transmission in ASCII format the identification key "E" (for Format Error) is indicated at the
first position in the transmission format.
- With a transmission in PROFIBUS and MODBUS format no identification key is given in case of an overflow. The
number of decimals must, however, not be selected too large, if the value is to be transmitted in integer format
(range of values in integer format limited to -32768 to +32767).

e.bloxx Communication
ASCII PROTOCOL
HB_EBLOXX_COM_E_V12.doc 9
Gantner Instruments Test & Measurement GmbH
3. ASCII PROTOCOL
3.1. Transmission Sequence
In the ASCII-protocol data are transmitted from and to the e.bloxx module by means of the following sequence:
SD .. .. ED SD .. .. .. .. .. .. .. .. .. ED
request telegram response telegram
T 1
request telegram
T 2 T 3
SD .. .. ED
T 1 : Time between two characters
T 2 : Time between request-telegram and corresponding response-telegram
T 3 : Time between response-telegram and next request-telegram
You will find the minimum and maximum appearing values for T 1 , T 2 and T 3 and the adjustment range in the following
table 3.1.
Protocol Baud rate T 1min T 1max T 2min T 2max T 3min T 3max
adjustable no no yes no no yes
A
S
C
I
I
19,200 bps
38,400 bps
57,600 bps
115,200 bps
0 1 CT
1... 42 CT
1..85 CT
1..85 CT
1..85 CT
T 2min
x
1.2
3 CT
0.1 sec
to
600 sec
Table 3.1 Values and adjustment range for the times T 1 , T 2 and T 3
(CT: character time: 1 CT = character length [bit] / baud rate [bps])
Notice: In the ASCII-protocol T 2max lasts at least 12 ms.
The values for T 2min and T 3max and the behavior of the sensor module if the time T 3max is exceeded (communication
timeout) can be adjusted by means of the Configuration Software ICP 100. The default values for the time T 2min is 1 CT
and for the time T 3max 60 sec.

e.bloxx Communication
ASCII PROTOCOL
10 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
3.2. Telegram Format
For the request and response telegram there is a difference between telegrams without and with check sum in the
ASCII protocol. The various telegrams differ by their varying Start-Delimiters (SD). A request telegram without check
sum will lead to a response telegram which also will contain no check sum. This is valid for requests with check sum as
well. Furthermore there are two short telegrams with a length of one character each. With these telegrams a positive or
negative acknowledge respectively can be performed.
Request Telegram Without Checksum Response Telegram Without Checksum
n+4 Characters n+2 Characters
Request Telegram With Checksum Response Telegram With Checksum
n+6 Characters n+2 Characters
Positive Acknowledge Negative Acknowledge
1 Character 1 Character
SD: Start-Delimiter (Length = 1 byte):
The Start-Delimiter SD marks the beginning of a telegram. In an ASCII protocol it has the following values:
SD Request Telegram Response Telegram
with check sum # >
without check sum $ =
Table 3.2 Start-Delimiter (SD) in the ASCII-protocol
DA: Destination-Address (Length = 2 byte):
The Destination-Address DA identifies the communication partner's address, to whom data shall be transmitted or from
whom data shall be requested. Destination-Address can have a value from 1 to 127 in an ASCII-protocol. Here the
value is given as a two-digit ASCII-string (ASCII "01".."7F").
ReqDataUnit: Request-Data-Unit (Length = 1 ... n byte):
The Request-Data-Unit identifies a data field in the request telegram, which contains data for the communication partner
with the DA address.
ResDataUnit: Response-Data-Unit (Length = 1 ... n byte):
SD DA ReqDataUnit ED
1 2 n 1
SD ResDataUnit ED
1 n 1
SD DA ReqDataUnit FCS ED
1 2 n 2 1
SD ResDataUnit FCS ED
1 n 2 1
ACK NAK

e.bloxx Communication
ASCII PROTOCOL
HB_EBLOXX_COM_E_V12.doc 11
Gantner Instruments Test & Measurement GmbH
The Response-Data-Unit identifies a data field in the response telegram, which contains data for the calling
communication partner.
FCS: Frame-Check-Sequence (Length = 2 byte):
The Frame-Check-Sequence FCS identifies the running digital sum of the telegram. This is the sum of the ASCII-values
in the telegram modulo 256. It is calculated in the ASCII-protocol from Start-Delimiter (SD), Destination Adress (DA) and
Data-Unit: CheckSum_ASCII = [SD+DA+DataUnit] mod 256. In the ASCII-protocol the value is indicated as a two-digit
ASCII-string (ASCII "00"..."FF").
ED: End-Delimiter (Length = 1 byte):
The End-Delimiter ED identifies the end of the telegram. In an ASCII-protocol it has the value hex 0D ("Cr").
ACK: Acknowledge (length = 1 byte):
With a request, where no data are returned, the proper performance of the instruction is acknowledged by an
"Acknowledge"-character (hex 06).
NAK: No-Acknowledge (length = 1 byte):
When a request has not been performed in correct way, a "No Acknowledge" (hex 15) is sent back.

e.bloxx Communication
ASCII PROTOCOL
12 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
3.3. Instruction Set
Check Sum Request Telegram Response With Orderly
Performance
Response in Case
of Error
read device identification
with # aa V cc <cr> > v..v cc <cr> NAK
without $ aa V <cr> = v..v <cr> NAK
read device information
with # aa S cc <cr> > s..s cc <cr> NAK
without $ aa S <cr> = s..s <cr> NAK
read status information
with # aa Z cc <cr> > z..z cc <cr> NAK
without $ aa Z <cr> = z..z <cr> NAK
read variable information
with # aa B kk cc <cr> > b..b cc <cr> NAK
without $ aa B kk <cr> = b..b <cr> NAK
read data from a variable
with # aa R kk cc <cr> > d..d cc <cr> NAK
without $ aa R kk <cr> = d..d <cr> NAK
write data to a variable
with # aa W kk d..d cc <cr> ACK NAK
without $ aa W kk d..d <cr> ACK NAK
Table 3.3 Instruction set in ASCII-protocol
Char Meaning Length Range
# start delimiter for request telegram with check sum 1 ASCII "#"
> start delimiter for response telegram with check sum 1 ASCII ">"
$ start delimiter for request telegram without check sum 1 ASCII "$"
= start delimiter for response telegram without check sum 1 ASCII "="
<cr> end delimiter (carriage return) 1 hex 0D
ACK positive acknowledge 1 hex 06
NAK negative acknowledge 1 hex 15
aa destination address 2 ASCII "01".."7F"
cc check sum 2 ASCII "00".."FF"
kk variable number 2 ASCII "00".."0F"
v..v device identification x ASCII - String
s..s device information 27 ASCII - String
z..z status information 4 ASCII - String
b..b variable information 29 ASCII - String
d..d variable value max. 8 ASCII - String
Table 3.4 Explanation of command characters in ASCII-protocol

e.bloxx Communication
ASCII PROTOCOL
HB_EBLOXX_COM_E_V12.doc 13
Gantner Instruments Test & Measurement GmbH
3.4. Instruction Parameters
device identification (v...v) length = x char
<vendor name> ASCII ("Gantner,") 1..32 char
<model name> ASCII (<type of module>,) 1..32 char
<hw version> ASCII ("xy.yy,") 1..8 char
<sw version> ASCII ("xy.yy,") 1..8 char
device information (s...s) length = 27 char
<location> ASCII 20 char
<serial number> ASCII 6 char
<number of variables> ASCII 1 char
status information (z...z) length = 6 char
<variable status> ASCII 4 char
<module status> ASCII 2 char
<variable st.> = K16..K13 K12..K9 K8..K5 K4..K1 = hex 0XYZ
0 X Y Z ASCII "0XYZ"
<module st.> = M8 M7 M6 M5 M4 M3 M2 M1 = hex XY
X Y ASCII "XY"
If the bit Kn in the variable status is set it indicates that an error has occurred in variable n. A variable error is given
when the measuring value is outside of the linearization, e.g. in consequence of a sensor break down or of a short
circuit of transmission.
If the bit Mn in the module status is set it indicates that an error has occurred in the sensor module. Valid is:
M1 = 1: EEPROM - error M5 = 1: (currently not occupied)
M2 = 1: FLASH - error M6 = 1: (currently not occupied)
M3 = 1: ADC - error M7 = 1: (currently not occupied)
M4 = 1: configuration - error M8 = 1: (currently not occupied)
variable information (b...b) length = 29 char
<variable type> ASCII 1 char
<variable name> ASCII 20 char
<data format> ASCII 1 char
<field length> ASCII 1 char
<decimals> ASCII 1 char
<unit> ASCII 4 char
<host input> ASCII 1 char

e.bloxx Communication
ASCII PROTOCOL
14 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
Coding <variable type>:
ASCII "0": Empty Variable (EM) "4": Digital Input Var. (DI)
ASCII "1": Analog Input Variable (AI) "5": Setpoint Variable (SP)
ASCII "2": Arithmetic Variable (AR) "6": Alarm Variable (AL)
ASCII "3": Digital Output Variable (DO) "9": Controller Variable (CO)
Coding <data format>:
ASCII "0": no format
ASCII "1": BOOL
ASCII "4": INTEGER
ASCII "6": LONG INTEGER
ASCII "8": REAL
ASCII "9": SET 8
Coding <host input>:
ASCII "0": host input is not possible
ASCII "1": host input is possible (tare/reset/dig.out/setpoint values)

e.bloxx Communication
PROFIBUS PROTOCOL
HB_EBLOXX_COM_E_V12.doc 15
Gantner Instruments Test & Measurement GmbH
4. PROFIBUS PROTOCOL
4.1. Transmission Sequence
In the PROFIBUS protocol the data are transmitted from and to the sensor module by means of the following sequence:
SD .. .. .. .. .. .. ED SD .. .. .. .. .. .. .. .. .. .. ED SD .. .. .. .. .. .. .. ED
request telegram response telegram request telegram
T 1 T 2
min T SDR : minimum time between request telegram and corresponding response telegram
max T SDR : maximum time between request telegram and corresponding response telegram
T SYN : time between response-telegram and next request-telegram
You will find the minimum and maximum appearing values for min T SDR , max T SDR and T SYN and the adjustment range
in the following table 4.1.
Protocol Baud rate min T SDR max T SDR T SYN
adjustable yes no yes
P
R
O
F
I
B
U
S
19.2 kbps
93.75 kbps
187.5 kbps
500 kbps
1,500 kbps
11 tbit
11 tbit
11 tbit
13 tbit
50 tbit
60 tbit
60 tbit
60 tbit
100 tbit
150 tbit
33 tbit
Table 4.1 Values and adjustment range for the times min T DSR , max T DSR and T SYN
The PROFIBUS-DP is running on the e.bloxx devices as software stack and is not based on an ASIC-device.
The PROFIBUS ID number for the e.bloxx modules is 6782 in hex format.
min T
SDR
min T SDR
T
SYN

e.bloxx Communication
PROFIBUS PROTOCOL
16 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
4.2. Diagnostic Data
This section describes the coding of the "Extended Diagnostic Data" of PROFIBUS-DP for the e.bloxx series. The
extended diagnostic data are added in the section of equipment specific status and error messages of the PROFIBUS-
DP "Get-Diagnostic-Data" frame. The displayed messages of a PROFIBUS-DP Master depend on the manufacturer
specification.
4.2.1. GSD File
For the e.bloxx series the GSD file GEA6782.gsd, V1.00, date July 8
th
2003 is the actual version. With the GSD file a
status or error message can be decoded by the PROFIBUS-DP master.
The corresponding part of the GSD file is:
" ...
Unit_Diag_Bit (0) = "Modbus Error 1"
Unit_Diag_Bit (1) = "Modbus Error 2"
Unit_Diag_Bit (2) = "Modbus Error 3"
Unit_Diag_Bit (3) = "Modbus Error 4"
Unit_Diag_Bit (4) = "Modbus Error 5"
Unit_Diag_Bit (5) = "Modbus Error 6"
Unit_Diag_Bit (6) = "Modbus Error 7"
Unit_Diag_Bit (7) = "Modbus Error 8"
Unit_Diag_Bit (8) = "Error Var 1"
Unit_Diag_Bit (9) = "Error Var 2"
Unit_Diag_Bit (10) = "Error Var 3"
Unit_Diag_Bit (11) = "Error Var 4"
Unit_Diag_Bit (12) = "Error Var 5"
Unit_Diag_Bit (13) = "Error Var 6"
Unit_Diag_Bit (14) = "Error Var 7"
Unit_Diag_Bit (15) = "Error Var 8"
Unit_Diag_Bit (16) = "Error Var 9"
Unit_Diag_Bit (17) = "Error Var 10"
Unit_Diag_Bit (18) = "Error Var 11"
Unit_Diag_Bit (19) = "Error Var 12"
Unit_Diag_Bit (20) = "Error Var 13"
Unit_Diag_Bit (21) = "Error Var 14"
Unit_Diag_Bit (22) = "Error Var 15"
Unit_Diag_Bit (23) = "Error Var 16"
... "
Diagnostic bits 0 to 7 will indicate module specific messages. Bits 8 to 23 are assigned to the variables 1 to 16 of each
module. Each module transmits 3 bytes, even though not all bits may be occupied for the module type.

e.bloxx Communication
PROFIBUS PROTOCOL
HB_EBLOXX_COM_E_V12.doc 17
Gantner Instruments Test & Measurement GmbH
4.2.2. Firmware Versions
"Extended Diagnostic Data" are supported via PROFIBUS-DP by the following firmware version and higher versions.
Device FW Version FUP File name
e.bloxx A1-x X1.00 / A1.03 mk18#_Standard_x100_a103.fup
e.bloxx A4-x X1.00 / A1.10 Mk26#_Standard_x100_a110.fup
e.bloxx A5-x X0.30 / A0.60 mk28#_Standard_x030_a060.fup
e.bloxx A9-x X1.00 / A1.10 Mk30#_Standard_x100_a110.fup
e.bloxx A6-2CF X1.00 / A1.10 Mk29#_Standard_x100_a110.fup
e.bloxx D1-x X1.00 / A1.10 Mk31#_Frequency_x100_a110.fup
e.bloxx D1-x X1.00 / A1.10 Mk31#_Standard_x100_a110.fup
Table 4.2 - Firmware Versions which support Extended Diagnostic Data
4.2.3. Diagnostic Data Decoding Table
The error codes in the GSD file are not all supported by each e.bloxx module.
GSD Coding Meaning of the Error Code
e.bloxx A1-x e.bloxx A4-x e.bloxx A5-1 e.bloxx A6-2CF e.bloxx A9-1 e.bloxx D1-x
Module Error 1 EEPROM – Error
x x x x x x
Module Error 2 FLASH – Error
x x x x x x
Module Error 3 ADC – Error
x x x x x x
Module Error 4 Configuration – Error
x x x x x x
Module Error 5 Currently not defined / reserved
Module Error 6 Currently not defined / reserved
Module Error 7 Currently not defined / reserved
Module Error 8 Currently not defined / reserved
Error Var 1 Error for variable 1 (sensor break, linearisation error)
x x x x x x
Error Var 2 Error for variable 2 (sensor break, linearisation error)
x x x x x x
Error Var 3 Error for variable 3 (sensor break, linearisation error)
x x x x x x
Error Var 4 Error for variable 4 (sensor break, linearisation error)
x x x x x x
Error Var 5 Error for variable 5 (sensor break, linearisation error)
x x x x x x
Error Var 6 Error for variable 6 (sensor break, linearisation error)
x x x x x x
Error Var 7 Error for variable 7 (sensor break, linearisation error)
x x x x x x
Error Var 8 Error for variable 8 (sensor break, linearisation error)
x x x x x x
Error Var 9 Error for variable 9 (sensor break, linearisation error)
x
Error Var 10 Error for variable 10 (sensor break, linearisation error)
x
Error Var 11 Error for variable 11 (sensor break, linearisation error)
x
Error Var 12 Error for variable 12 (sensor break, linearisation error)
x
Error Var 13 Error for variable 13 (sensor break, linearisation error)
x
Error Var 14 Error for variable 14 (sensor break, linearisation error)
x
Error Var 15 Error for variable 15 (sensor break, linearisation error)
x
Error Var 16 Error for variable 16(sensor break, linearisation error)
x
Table 4.3 - Diagnostic Data Decoding Table

e.bloxx Communication
PROFIBUS PROTOCOL
18 HB_EBLOXX_COM_E_V12.doc
Gantner Instruments Test & Measurement GmbH
4.3. Launching PROFIBUS-DP Communication with a Hilscher



Master
On the following pages the configuration of the Hilscher

Master will be described.
4.3.1. How to Launch PROFIBUS-DP Communication with a Hilscher
®
Master
The newest e.bloxx GSD file (GEA6782.gsd, shipped with the ICP 100 software and located in the \GSD directory in the
installation directory of ICP 100 or directly received from the Gantner Instruments Test & Measurement GMBH) has to
be copied to the directory "\Fieldbus\Profibus\GSD" in the SyCon

installation directory.
Now process the steps below in the Hilscher
®
Master software:
• In the software add one master to the system layout.
• Open the configuration of "Bus Parameters".
• Select the desired Baudrate and than set "Standard" first in the "Optimize" selection field.
• Next select "By User" in the "Optimize" selection field and on the window that opens change the items marked in the
next picture.