Manual
ibaBM-DP
156
Issue 1.7
14.3.2 Telegram structure
The structure of the request and response telegram is identical. The structure is de-
scribed in the table below. All 2/4 Byte fields are formatted as Little Endian (“Intel”).
Offset Bytes Field
Values Description
0
2
id
Can be set to any value in the request, the value is mir-
rored in the corresponding response
2
2
fc
7
Exchange telegram identifier
4
2
length
272 Telegram length
6
2
reserved
0
8
4
success
Response only:
error messages, see below
12
1
bus
0..1 Bus number, ibaBM-DP interface
13
1
slave
1..126 Slave number
14
1
dummy1
0
15
1
dummy2
0
16
244 Data
-
Slave I/O data
- Request: input data (from DP Master's view)
- Response: output data (from DP Master's view)
260
1
DataSize
0..244
Response only:
actual user data length in the data field
261
3
Service1
0
Not used
264
1
MasterNr
-
Response only
: Profibus address of the master which
has written the output data to the slave
265
1
Service2
0
Not used
266
6
Timestamp
0
Response only:
counter 48 Bits: 33 Ticks/1µs
Field "Success":
Value
Description
1
Without error
-3
Bus number is wrong
-5
Slave number is wrong
-7
Simulation mode is not available
