Page 6 of 20
NTI AG / LinMot
4 LinUDP V2 Telegram
In LinUDP V2 there are two telegrams used, one for the request from the master and the other one for the
response from the drive. These two telegrams have the following layout:
Name
Size [Byte]
DHCP Header
14
IPv4 Header
20
LinUDP Header
8
LinUDP Data
message dependent
4.1 DHCP Header
The DHCP Header looks like in the following table.
0. Byte
1. Byte
2. Byte
3. Byte
4. Byte
5. Byte
6. Byte
7. Byte
+0
Destination MAC ID
+8
Source MAC ID
Protocol Typ (0x0800)
4.2 IPv4 Header
The IPv4 header is described in the rfc0791 in chapter 3.1. Rfc0791 could be found on
. The sections options and padding are not used.
4.3 LinUDP V2 Header
The LinUDP V2 header consists of four parts. They are showing in the following table.
Name
Size [Byte]
Source Port
2
Destination Port
2
Length of UDP Telegram
2
UDP Checksum
2
The LinUDP V2 ports are fix assigned. For the Master it is port 41136 and for the drive it is port 49360. In
Hex-Code they are A0B0 and C0D0.
4.4 LinUDP V2 Data
In LinUDP V2 data are the data which we want to transfer. The construction of this data part always is the
same. The only difference are the source and destination, they are switched.
4.4.1 Request from the Master
The first 32 bits of the LinUDP V2 data define the request and the following 32 bits define the format of the
response. The following tables show how the request definition and the response definition look like. Each of
this parts have a byte order with Low Byte First.
