Page 11 of 62
NTI AG / LinMot
4 LinRS Message Format
The following tables define the principle structure of a LinRS Message.
Header
Data
Opt. Checksum
End
Start
Header
ID
Len
Start
Data 0
Data 1
Msg ID
Low
Data 2
Msg ID
High
…
Data
n-1
Check-
Sum
Low
Check-
Sum
High
End
Tele-
gram
01h
0..FFh
2..63
02h
0..FFh
0..FFh
0..FFh
0..FFh
0..FFh
0..FFh
04h
Length Count
Checksum Calculation
Byte Nr
Name
Description
Value
0
Start Header
Fix ID at telegram start
01h
1
ID
ID of LinMot Drive
0..FFh
2
Length
Length of telegram data n
2..63
3
Start Data 0
Fix ID at telegram start
02h
4
Data 1 Msg ID Low
Message Sub ID
0..FFh
5
Data 2 Msg ID High
Message Main ID
0..FFh
6
Data 3
Message data 0
0..FFh
..
..
..
0..FFh
n+2
Data n-1
Message data n-1
0..FFh
n+3
Checksum Low
Optional checksum Low Byte
0..FFh
n+4
Checksum High
Optional checksum High Byte
0..FFh
n+5/n+3
End Telegram
Fix ID at telegram end
04h
Data are transmitted lowest byte first highest byte last. Dummy Data could be added to get a fix master
transmission length.
4.1 ID
The ID is one byte that defines the address (ID) of the LinMot drive. This ID is defined by two Hex Switches or
by a parameter.
4.2 Length
The length defines the data length in bytes.
4.3 Data
In the data fields the command specific data are transmitted.
4.4 Checksum
The checksum field is optional. Three different methods are supported (UPID 2080h):
·
Byte wise addition and modulo 2^16 (fast and easy)
·
CRC-16-CCITT: Polynomial 1021h (input/result/start value bitwise reflected)
·
CRC-16-CCITT: Polynomial 1021h