
Manual – MOVIDRIVE® MDX60B/61B Communication and Fieldbus Unit Profile
39
5
MOVILINK® profile via CAN
CAN Interfaces of MOVIDRIVE® B
5.3
MOVILINK
®
profile via CAN
The MOVILINK
®
profile via CAN (SBus) is an application profile from SEW-
EURODRIVE specifically adjusted to SEW inverters. This chapter serves to support you
with diagnostics and creating own applications.
5.3.1
Telegrams
Different telegram types were defined for communication with a master (e.g. controller).
These types of telegrams can be divided into three categories:
• Synchronization telegrams
• Process data telegrams
• Parameter telegrams
CAN bus
identifier
On the SBus, it is necessary to differentiate between these various types of telegrams
by means of identifiers (ID or COB-ID (Communication Object Identifier)). Therefore, the
identifier of a CAN telegram is generated from the telegram type and the address set
using parameters P881/P891 (SBus address) or P882/P892 (SBus group address).
The CAN bus identifier consists of 11 bits because only standard identifiers are used.
The 11 bits of the identifier are divided into 3 groups:
• Function (bit 0 - 2)
• Address (bits 3 - 8)
• Process data/parameter data changeover (bit 9)
Bit 9 is used to distinguish between process and parameter data telegrams. The address
of parameter and process data telegrams includes the SBus address (P881/P891) of the
unit that is addressed by a request; the address of group parameter and group process
data telegrams includes the SBus group address (P882/P892).
02250BEN
5
4
3
2
1
0
0
X
X
X
X
Bit:
10
9
8
7
6
5
4
3
2
1
0
Function
Address
Reserved = 0
0 = Process data telegram
1 = Parameter data telegram
Содержание MOVIDRIVE MDX60B
Страница 2: ...SEW EURODRIVE Driving the world...
Страница 142: ......
Страница 143: ...SEW EURODRIVE Driving the world...