Baumer
UDP header
The following table provides an overview of the UDP header.
Field name
BlockId
FrameType
Reserved
FrameCount / Index
Field
Offset
Unfragmented data
Single Frame
Fragmented data
First Frame
Consecutive Frame
Consecutive Frame
Consecutive Frame
Ill. 15: UDP – Packet framing example
Field
Offset
Unfragmented data
Fragmented data
Ill. 16: UDP – Body recomposition example
OX200 | V2
Offset
0
4
5
6
Block ID
Type
0
4
0x0A
0x00
0x00
0x00
0x00
0x0A
0x00
0x00
0x00
0x01
0x0A
0x00
0x00
0x00
0x02
0x0A
0x00
0x00
0x00
0x02
0x0A
0x00
0x00
0x00
0x02
Type
Type dependant data
1
0
D0
Dn
.....
D0
Dn
Dn+1
.....
.....
Operating Manual
Data type Description
UInt32
Incremented with each UDP packet
block sent (profiles can be sent in sev-
eral UDP packets in one block).
UInt8
0 = SingleFrame
1 = FirstFrame
2 = ConsecutiveFrame
For measurement results (Message-
Type = 0) always 0, as these fit in a
single UDP packet.
UInt8
UInt16
If FrameType = 1, then number of UDP
packets in a block.
If FrameType = 2, then position of the
current UDP packet in the block.
Res
Count
Body
6
8
0x00
0x00
0x00
D0
0x00
0x04
0x00
D0
0x00
0x01
0x00
Dn+1
0x00
0x02
0x00
Do+1
0x00
0x03
0x00
Dp+1
Do
Do+1
Dp
.....
Description
.....
Dn
.....
Dn
.....
Do
.....
Dp
.....
Dq
Dp+1
Dq
.....
|
3
35
Need help?
Do you have a question about the OX200 and is the answer not in the manual?